Skip to content

Latest commit

 

History

History
176 lines (131 loc) · 8.95 KB

REQ_s275330.md

File metadata and controls

176 lines (131 loc) · 8.95 KB

Requirements for EZGaz

Authors: Mehrdad Kiani (s275330)

Date: 27/03/2020

Version: 1

Change history

Version Changes
1 The first concept of model is defined

Contents

Stakeholders

Name Description
Administrator Manage users and update general information about the application
Users Ordinary users use the application to find a gas station in a price range or/and in a specific location
Gas station owner Gas station owners use the application to update the price of the fuel and also update the state of the station in the unforeseen circumstances like maintain the station's tanks

Context Diagram and interfaces

Context Diagram

Drawing3.png

Interfaces

Actor Logical Interface Physical Interface
Administrator GUI Screen, keyboard
User GUI Screen, keyboard
Gas station owner GUI Screen, keyboard

Stories and personas

Mina has been working for many years in Esfahan as a taxi driver. She works around 10 hours a day in the city and also she is an independent driver. Therefore, she does not have a specific route plane for driving and she can be everywhere in the city to serve the customers. Thus, her location in the city is dependent on the customer's rout. She uses the EZGas application on her smartphone to find the nearest and cheapest gas station. Mina believes that the application is a mandatory part of her job and without this, she will waste lots of time and money.

Reza is a new gas station owner. He is a gadget lover and tries to be an up to date person in technologies. Therefore, he wants to connect his business to new methods. He likes to use the EZGaz application to update the price of fuel because this is more convenient to inform the user new price by the app rather than any other way. Besides, due to the unforeseen circumstances in the station like maintenance of the fuel tanks, he can inform his lovely customers by the state of the station. Sometimes it will be closed for many hours in a week. Now, he can handle his responsibilities better than ever.

Shima works for a firm that develops many applications for transportation companies. Recently, her manager asks her to be an administrator of EZGas application due to her remarkable experiences in this field. She now, should manage and helps the users if they can't log in or in case of any other issues. Besides, she should publish the news about the new updates and new features of the application.

Functional and non functional requirements

Functional Requirements

ID Description
FR1 The user can set the maximum and minimum price of the fuel.
FR2 All user can update their personal information in the app like phone number.
FR3 The user can set the distance between her/his location and the gas stations.
FR4 The user can submit feedback or write comments for the gas stations.
FR5 It is possible for all user to log in or log out to record the history of activities.
FR6 User can share a favorite station via a link for others.
FR7 All users can write a bug report for the administrator.
FR8 It is possible for users to mark stations as a favorite station.
FR9 Gas station owner can submit the new price.
FR10 Gas station owner can change the state of the station. For example: Closed, Maintain, ...
FR11 Administrator can gather the information from the bug reports section.
FR12 Administrator can register a new gas station in the application.
FR13 Administrator can reset the password of users.

Non Functional Requirements

ID Type (efficiency, reliability, .. see ISO 9126) Description Refers to
NFR1 Usability Application should be used with no training by anyone All FR
NFR2 Performance All functions should complete in < 1 sec All FR
NFR3 Portability The application runs on MS Windows, Android, and IOS All FR
NFR4 Security All data should encrypt first and then store in database All FR
NFR5 Localization Fuel prices should be displayed in Euros All FR

Use case diagram and use cases

Use case diagram

Drawing4.png

Use Cases

Use case 1, Set up new business for gas station owner

Actors Involved Administrator, Gas station owner
Precondition Administrator receives a request for new gas station
Gas statin needs some tools and infrastructures to connect to the internet
Postcondition Other User can find the station on the application
Nominal Scenario Gas station owner gives the information to the administrator for registration
Administrator register the data in the application and inform the gas station owner
Variants

Use case 2, Find a station in the application

Actors Involved Users, Gas station owner
Precondition Both users and gas station owner use their smartphone or PC to search
Postcondition The result will show on the application
Nominal Scenario Users should set price and distance in the application to find the best result
Variants If the input value is abnormal the application popup a warning to the users

Use case 3, Manage the report bugs

Actors Involved Administrator
Precondition Application works with some unseen bugs
Postcondition Application improved
Nominal Scenario User report the bugs by the application. The administrator checks the reported bugs and sends them to the developers
Variants If the text of the report is not adequate the user will receive a warning

Relevant scenarios

Scenario 1

Scenario ID: SC1 Corresponds to Use case 1
Description Set up new business for gas station owner
Precondition No gas station location exist on the app
Postcondition Gas station located on the application map
Step# Step description
1 Administrator check received data for a new registration
2 Administrator input new data on the fields and register new gas station
3 After storing the data in DB, Administrator received a completion message

Scenario 2

Scenario ID: SC2 Corresponds to Use case 2
Description Find a station in the application
Precondition Both users and gas station owner use their smartphone or PC to search
Postcondition The result will show on the application
Step# Step description
1 User fill fields like price and location and submit the inputs
2 After retrieving the requested data by the application, the result will be shown on the screen

Scenario 3

Scenario ID: SC3 Corresponds to Use case 3
Description Manage the report bugs
Precondition Application works with some unseen bugs
Postcondition Application improved if the reported bugs are acceptable by the developers
Step# Step description
1 Users submit a report about a bug in contact us section
2 Administrator will receive a notification about a user repot
3 Administrator check the text or image correspond to a bug
4 Administrator sends the reported bug to the developers

Glossary

Drawing1.png

System Design

Deployment Diagram