Srs Easy Auto

215
srs
srs (software requirments specifications)

SRS Easy Auto

If a person decides to purchase a vehicle, he/she will be overwhelmed by multitude of options ranging from hatchbacks to SUVs. Such decision making and final purchase is a hectic job, but the story doesn’t end here; remembering pre-defined maintenance timeline and scheduled service is also quite cumbersome. Majority people don’t know exact inspection and service deadlines and end up in a higher maintenance cost. Easy Auto app will try to tackle these problems. It will not only assist in buying an ideal vehicle that fits to the requirements, but also help in after-sale services and maintenance tasks.


 

Scope of Project Easy Auto:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Easy Auto:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Easy Auto:

Module I: Purchase Decision
M1.1: The app will provide the best vehicle(s) available in the market to purchase after taking input from the user on these factors (not limited to only these – you can add as well):
 Seating capacity
 Luggage/trunk space
 Engine size and technology
 Fuel type and advertised economy
 Driving modes availability
 Off road/on road driving (4- or 2-wheeler)
 Safety features
M1.2: The app will show all nearest dealerships/showrooms of the selected car based on the current location of the user.
Module II: Maintenance Services
M2.1: The app will have a comprehensive maintenance section which will have month wise or odometer-reading wise maintenance timetable which user can view.
M2.2: The app will notify the user of next upcoming maintenance activity (monthly or odometerreading whichever comes earlier).
M2.3: The app will calculate total distance covered by the car using GPS. For accuracy, user will have the option to override this reading.
M2.4: After a particular maintenance service has been done, the app will take total cost incurred and will save it in a database for comparison purposes for the next same maintenance service.
M2.5: All maintenance services will auto update for their next schedule.
An example maintenance chart is available in this link:
https://www.suzukipakistan.com/customer-care (click on Schedule Maintenance tab)

 

NON-FUNCTIONAL REQUIREMENTS Easy Auto:

  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes



 

Use Case Diagram of Diagnosis of Easy Auto

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



 

 

Usage Scenarios Diagnosis of Easy Auto:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

 

ADOPTED METHODOLOGY for Easy Auto:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.



 

Work Plan of Diagnosis of Easy Auto:

Work plan



for complete srs contact us

watsapp: 03469806607