Skip to content

Latest commit

 

History

History
170 lines (126 loc) · 8.82 KB

REQ_s271199.md

File metadata and controls

170 lines (126 loc) · 8.82 KB
Raw

Requirements for EZGaz

Authors: Hesam Mashhadi Mohammad (s271199)

Date: 29/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

James is a delivery man who works for a resturant. As he has to drive his car through different destination every day and he must be on time to get the customer's orders as soon as possible he has always had problem with running out of fuel. To solve this problem he started using the EzGas application. using this application he is able to find the nearest gas station with the lowest price quickly and not be worry about running out of gas. before that he sometimes was not able to get the orders to the customers on time and because of that had struggle with his boss most of the time. he thinks that EzGas application is an important part of his career now and help him a lot.

Sam owns a gas station. As his gas station is not in the city center, usually there is not enough customers over there. Using the EzGas application now he is able to offer competetive prices and services and advertise his gas station on the app. As a result now his gas station is most of the time full of cars and people who knows that he offers the best prices in the area.before that however sam tried to provide good services and prices he did not have enough customers. So he thinks that the EzGas application helps gas station owners like him to make themselves known for people.

Sara is an application developer who has been working in this field for years. due to her expreince her boss recently asked Sara to start providing support for users of EzGas application. She has to help users either drivers and owners of gas station to solve their problems. Sara is also suppose to publish news 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