E-Mechanics Services

Requirements Document
Problem Statement: In our daily life, when our cars are out of order, we face problem in order to
service them on time, and the problem goes more critical when we are in such a place that we
don’t know where are the mechanics and how to get them. Sometimes we go to the mechanic
shop, but we have to wait because there are other works that the mechanic should have to do, so
we will have to wait for a long time, which is too tedious and time-consuming Job.

In order to solve this problem, we are planning to provide a platform for the user
(Customer and Mechanics) , So customer can easily access mechanics and can find what services
are provided by the mechanic, and where is the location of the mechanics which are nearby.

Requirements:
We have two types of the Requirements:
Functional Requirements: Some of the functional requirements are Given below.
We have the three modules of this project:
1) Customer
2) Mechanic’s
3) Admin
1) Customer: The customer has the following functions:
 Register Himself: The customer should provide his basic information about himself, like
name, Phone Number, CNIC Number, Picture.
 The app will access his current location from the google maps.
 The Customer can Post a Review for a mechanic. He will give stars to him and will answer
some basic multiple-choice question, from this we can judge the efficiency of the
mechanics.
 The user can also delete his account.
 The Customer can also make a booking with the mechanic and can get time, so he will not
wait too much for his turn.
2) Mechanic Module: The Mechanic has the following Requirements:
 His will Register himself. Provide his basic Information.
  He will point out his Services and the charges that he will get for the type of services.
 The App will access his location and will save it on the time of registration.
 He will also include the time of availability. for example, 8:00 Am to 7:00 PM
 When the customer makes a request, the mechanic will have a push up notification, he
will then accept the request, if one mechanic has accepted the request then the
notification will be automatically marked as already appointed.
 The mechanics can also see his history and the review of the customer. He can also post a
Review for the customer which he has served.
 Mechanic can change his profile.
 Mechanic can delete his account and can change the location of his shop.
3) Admin:
For the admin we will provide a Dashboard from which he accesses all the information and
both customer and the user. He can also ban the account of the customer or the mechanic.
But he can notify the customer or mechanic in advance with a warning that his account will be
banned or will be disable for some time.

Non-Functional Requirements:
Feasibility study: The objectives of the feasibility study are to find out that project can be
done and to suggest possible alternate solutions. Feasibility Study is done to check
whether the proposed system will be able to work within available resources (hardware,
software, other equipment), it is also used to determine whether there is enough financial
budget to develop and implement the proposed system, and whether the proposed
system will work as per the expectation of the user or not.
Technical Feasibility: Technical feasibility is necessary to check whether the system which
is to be developed is technically feasible or not. I.e. whether the technology used to
develop the system is feasible. Our application requires internet connection. The
technologies which can help to develop such an application are Java, MySQL, PHP and
Android Environment. The supporting tools for above technologies are Android Studio,
MySQL and Android phone. All the above technologies are available. Although few of
above require training for some amount of time, but it feasible enough to cope-up with
the time allotted for the project. So, it is technically feasible.
Operational Feasibility: Once the system will be deployed whether the System or
application will work in the environment of the Client? Or will it be User-Friendly? Or will it
adjust according to Operating System and other resources of the Client? Etc., questions are
needed to be checked. The systems should hold good GUI facilities which will attract the
user to use the system. The system will be developed using version of android that is very
easily available in all android mobiles.
Economic Feasibility: Development costs: Care is taken by us to make sure that our system
is developed using all available technology and resources. Operational costs: Our system is
developed in such a way that user of the system requires only interaction with system to
totally understand and use it flexibly.
Maintenance and support costs: The user of the application only needs a good internet
connection (if possible, then 3G internet connection) to work with the application.
Time Feasibility: The Proposed System is a mobile application so it will take some duration
of time to satisfy the objective of completing the system (Application). The duration that is
allotted to develop the system is quite feasible in respect to time. V.
System features
1. Notification: Used to notify user of the service response
2. Service Request: User request for services provided by service centre.
3. Mechanics:
 Personal Information.
 Services Provided
 Review
 Cost against Services