Skip to content

Latest commit

 

History

History
172 lines (123 loc) · 7.4 KB

REQ_s269522.md

File metadata and controls

172 lines (123 loc) · 7.4 KB

Official Requirements Document

Author: Luca Marongiu

Date: 31/03/2019

Version: 2

Contents

Abstract

A car driver is driving along the streets of its city, when he notices that the fuel level of its machine has a low value, he wants to get gas without spend too much. With the help of EZGas (a useful crowdsource application) the car driver can see the best choice for its goal seeing also the closest to him.

At the same time the owners of the gas stations can offer their prices and their special offers (presence of Autogrill or restaurants) through the same application locating also their gas station. After getting gas the car driver writes also its personal review in order to improve the service given by the app.

Stakeholders

Stakeholder name Description
Drivers Uses the application to search the best gas station
Gas stations owners Uses the application to offer their prices and to promote their services

Context Diagram and interfaces

Context Diagram

context diagram

Interfaces

Actor Logical Interface Physical Interface
Driver GUI Screen, keyboard or Touch screen
Gas stations operator GUI Screen, keyboard or Touch screen

Stories and personas

Bob is a car driver and he rides tens of km every day, when he is getting gas he wants to keep the best choice in terms of money and distance from him. Bob is also interested on making his launch breaks the most relaxing possible, maybe by eating something of good or drinking well.

Bob can make its personal account in the EZGas application signing its favourite choices around certain geographic areas. For every gas station that Bob visit, he can write a review visible by all the other car drivers but also by the gas stations owners (rating from 0 to 5).

Pablo is a Gas station attendant and he wants to promote his activity in order to achieve more customers, he can sign up the EZGas application by writing all the informations in terms of services and prices, he can write also weekly (or daily) promotion. Pablo can also see the customers opinions by reading the reviews on its activity, in this way he can recognize the points to improve of its gas station.

Functional and non functional requirements

Functional Requirements

ID Description
FR1 Record the gas stations location
FR2 Record the gas stations price
FR3 Record the gas stations weekly (or daily) promotions
FR4 Record the favoutite car drivers gas stations
FR5 Record some car drivers reviews for every gas station

Non Functional Requirements

ID Type (efficiency, reliability, .. see iso 9126) Description Refers to
NFR1 Usability Application should be used with no training by drivers and gas station owners All FR
NFR2 Portability The application runs on MS Windows (7 and more recent) All FR
NFR3 Precision The application should locate the gas station with a good precision (tolerance of 10 meters) FR1
NFR4 Localisation Decimal numbers use . (dot) as decimal separator

Use case diagram and use cases

Use case diagram

case diagram

Use Cases

Use case 1, UC1 - FR1 Record gas station location

Actors Involved Gas station ower
Precondition Gas station (GS) exists
Post condition GS.location != null
Nominal Scenario Gas station operator update GS.location
Variants

Use case 2, UC2 - FR2 Record gas station prices

Actors Involved Gas station ower
Precondition Gas station (GS) exists
Post condition GS.prices > 0
Nominal Scenario Gas station operator update GS.prices
Variants

Use case 3, UC3 - FR3 Record gas station promotions

Actors Involved Gas station ower
Precondition Gas station (GS) exists
Post condition GS.numberPromotions >= 0
Nominal Scenario Gas station owner updates (adds or removes) a Gas station promotion
Variants

Use case 4, UC4 - FR4 Record car drivers favourite gas stations

Actors Involved Driver
Precondition Driver exist and Driver.numberVisited > 0
Post condition Driver.numberFavourites >= 0
Nominal Scenario The Driver updates its list of favourite gas stations
Variants

Use case 5, FR5 Record car drivers reviews

Actors Involved Driver
Precondition Driver exist ,Gas station (GS) exists , Driver.numberVisited > 0
Post condition GS.numberReviews > 0
Nominal Scenario Driver writes a review of one of the gas stations that he visited
Variants

Relevant scenarios

Scenario 1

Scenario ID: SC1 Corresponds to UC4
Description Driver adds one gas station to his favourite
Precondition Driver exists
Postcondition count of favourites of Driver increments
Step# Step description
1 Driver visit Gas station GS
2 number of Driver gas station visited increment
3 Driver update its favourite list
4 The number of Driver favourites increases

Scenario 2

Scenario ID: SC2 Corresponds to UC5
Description Driver writes a review and a Gas station owner (GSO) read the rerview
Precondition Driver exist ,Gas station (GS) exists
Postcondition number of reviews of GS increases
Step# Step description
1 Driver visit Gas station GS
2 GSO read the review
3 number of reviews for GS increases
4 GSO possibly make some changes related to prices or promotions due to a bad review

Glossary

glossary