Skip to content

Latest commit

 

History

History
168 lines (117 loc) · 7.39 KB

REQ_s274475.md

File metadata and controls

168 lines (117 loc) · 7.39 KB

Official Requirements Document

Author: Fereshteh Feizabadi

Date: 3 April

Version: 2

Contents

Abstract

EZGas is a crowdsourcing service that allows users to: collect prices of fuels in different gas stations locate gas stations in an area, along with the prices they practice.

Stakeholders

Stakeholder name Description
Driver Uses the application for checking the prices of fuels in different gas stations and according to their locations
Gas station personel Uses app for updating the price of the fuel
Administrator Application administrator, IT administrator, DB administrator
Developer Develop the application
Data Analyst Interested in collecting data, processing and performing statistical analyses of data in order to help company understand how to make better business decisions

Context Diagram and interfaces

Context Diagram

context-diagram

Interfaces

Actor Logical Interface Physical Interface
Driver GUI Touch screen
Gas station GUI Touch screen
Google map web service Internet connection

Stories and personas

User 1 : Julia is a mother, she is a house wife and regularly uses car to go for shopping. It’s important for her to help other people too, so whenever she goes to the new gas station, she pined it on the map in the application and write her feedback about it and the price of the fuel.

User 2 : Simone is a man who is father of 2 children. He works in a factory and he goes to the work every day and for him is important to save money for fuel, because he always use his car to go to the factory, pick the children from school, weekends shopping or going out with family. Simone prefer to find the nearest fuel station to his current location with the lowest price. It’s important for him that the prices of the fuels are reliable and updated, also the location of the station should be the nearest and map routes him to the station. Moreover he can put feedback and give reviews about the station.

Functional and non functional requirements

Functional Requirements

ID Description
FR1 Show and suggest to user the nearest gas station with the cheapest price
FR2 Record the users reviews and comments
FR3 Give and record the scores of users in their account
FR4 Manage accounts of the users
FR5 Save the location of gas station on the google mape
FR6 Save the price of the fuel for a certain gas station
FR7 Produce reports about changes of fule price in different areas that gas stations are located
FR8 Provide statistical reports to IT administrators related to the fuel price and gas station location or other types of reports according to the users

Non Functional Requirements

ID Type (efficiency, reliability, .. see iso 9126) Description Refers to
NFR1 Usability Application should be used with no training by any user All FR
NFR2 Performance All functions should work in < 0.5 sec All FR
NFR3 Portability The application runs on Android and IOS mobile phones All FR
NFR4 Reliability The application shows the correct location of the gas stations All FR
NFR5 Reliability The data about fuel prices and the nearest gas station should be correct All FR
NFR6 Reliability The application should run without error or bug All FR
NFR7 Reliability The application data (gas stations list, accounts list, user‘s reviews, scores and so on) should be backed up schedule. All FR
NFR8 Efficiency The application should has user friendly interface (UI/UX) to encourage user to work with it easily All FR
NFR9 Maintainability The application should be updated regularly to fix bugs or adding new features All FR

Use case diagram and use cases

Use case diagram

use-case-diagram

Use Cases

Use case 1, UC1 - FR1 Find the nearest gas station on google map sorted by cheapest price

Actors Involved Driver, Google map
Precondition Current location of user on the map, Internet connection, availability of google map service
Post condition Estimated distance from current location to the gas station, routing, shows the fuel price
Nominal Scenario Shows the nearest gas stations to user sorted by price
Variants

Use case 2, UC2 - FR2 Gas station personel update the price of fuel

Actors Involved Gas station personel
Precondition user login into app
Post condition user should select the right gas station
Nominal Scenario modify the price of the fuel
Variants

Use case 3, UC3 - FR3 Driver enter reviews or comments

Actors Involved Driver
Precondition User login into app
Post condition User should choose one gas station
Nominal Scenario User put review and comment about Gas station
Variants

Use case 4, UC3 - FR4 Statistical reports for administrator about the fuel price and gas station location

Actors Involved User
Precondition Enough precise data about fuels and gas stations
Post condition Proper tools for creating reports and data mining
Nominal Scenario Creating practical reports
Variants

Relevant scenarios

Scenario 1 - Statistical reports for administrator

Scenario ID: SC1 Corresponds to UC1, UC2
Description Statistical reports for administrator about the fuel price and gas station location
Precondition Enough precise data about fuels and gas stations
Postcondition Proper tools for creating reports and data mining
Step# Step description
1 Data analyst selects the parameters ( price, location, certain gas station, time )
2 Choosing the factors that are important to be in the repots.
3 Data analyst choose the proper software such as Power BI, SQL server, Visual studio for creating queries and report dashboard.
4 Present the report and use it for making proper decision

Glossary

UMLClass-Glossary