VIT MITS5002: Specification Document for Sunshine Motors

This specification document outlines the system analysis and design for Sunshine Motors' vehicle service system. The report begins with an executive summary, followed by a detailed system description that encompasses customer, mechanic, and system interactions. It defines the scope, conducts a feasibility analysis (technical, financial, and organizational), and specifies both functional and non-functional requirements. The functional requirements include authentication, authorization, inventory management, and payment processing. Non-functional requirements focus on security, maintainability, and availability. The document also includes assumptions, constraints, and use cases, with a detailed use case description for 'Decrement Inventory'. Furthermore, it provides a context model, levelled set of functional models, and a bibliography. The system is proposed to be developed using NodeJS and MongoDB, with a frontend using Angular, HTML, and CSS, aiming to automate various back-end processes, integrate a payment gateway, and improve overall operational efficiency and customer satisfaction.

Running head: SPECIFICATION DOCUMENT
Specification Document
Name of the Student
Name of the University
Author’s note:

1SPECIFICATION DOCUMENT
Executive Summary
The report reflects the system analysis and design of the Sunshine Motors proposed system. The
system will be implemented for the internal works only. However, the report properly describes
the customer perspective on the system. The Use Case diagrams shows the interaction of
customer, mechanic and other actors with the system. The Decrement Inventory Use Case has
been selected for showing the use case description.

2SPECIFICATION DOCUMENT
Table of Contents
System Description:.........................................................................................................................3
Scope:..............................................................................................................................................3
Feasibility Analysis:........................................................................................................................4
Requirement Specifications:............................................................................................................5
Functional Requirements:............................................................................................................5
Non-Functional Requirement:.....................................................................................................6
Assumptions/Constraints:................................................................................................................7
Use Cases:........................................................................................................................................8
Context Model:..............................................................................................................................10
Levelled Set of Functional Models:...............................................................................................11
Bibliography:.................................................................................................................................12

3SPECIFICATION DOCUMENT
System Description:
The proposed system will be implemented in a car service providing organization. The
Sunshine Motors is also known as the dealer of old cars. The organization is now rapidly
growing and needs changes in the current processes. The organization currently wants to
implement a vehicle mechanical service company system. This system will record the customer
information, vehicle information and service history. The system will record the mechanic data
into the database along with the equipment they use for service. The system will be developed
such a way that it maintains the mechanic roster. The system will also track which mechanic is
free. If a new service order occurs then system will allocate the service to that mechanic. Along
with mechanic work, the system will track the usage of items in a service along with the work
bay. The system will include various organization policies like at least five out of ten mechanic
must be available in shop, one mechanic can use only one workbay for service and many more.
The system will also handle the inventory of common items and consumables. These
items and consumables are used by the mechanic to service a vehicle. The mechanic will
mention the name and amount of items and consumables to be used for a job and the system will
deduct that amount from available stock. The system will handle all the back process of a
service. The staff of the system will work as the input/output of the system. The system will have
an extension for the customers so that they can register, login and access the system
functionality. The customers can see the status of the vehicle service through the application. The
system will integrate a payment gateway which will allow the customer pay for the service they
got from Sunshine Motors.

4SPECIFICATION DOCUMENT
Scope:
The scope of the Sunshine Motors Vehicle Service System are as following.
i. Tracking all the service related activities of Sunshine Motors
ii. Providing service to customer
iii. Maintaining the inventory of parts and consumables
iv. Automation of back processes
v. Integrated payment gateway in the Vehicle Service System
vi. Notifying the staff about new service
vii. Real time data transmission throughout the application
viii. Different terminals for different staffs
ix. Service status will be tracked
x. Track of mechanic works
xi. Mechanic roster management
xii. Database for recoding all the service, customer and mechanic data
xiii. Auto job allocation
Feasibility Analysis:
Technical: The Sunshine Motors Vehicle Service System will be developed using
NodeJS and MongoDB. The font end of the system will be developed using angular, html and
CSS. Thse technologies are free to use and very robust. The system will be able to integrate real
time data flow using socket IOs. As the No-SQL is to be used in the system, the system can
handle a lot of data very easily. The system will have better security and processing. The cost of

5SPECIFICATION DOCUMENT
the system will be minimal where the service will improve many times from the current
situation.
Financial: The system will be deployed in a cloud environment. The NodeJS and
MongoDB are open source technologies. The NodeJS supports many extensions that can be used
to make the application more robust. The overall cost of the system will high than conventional
ASP and PHP applications. However, in terms of performance and security, the NodeJS is much
better. The improvement in the operations and real time data tracking will allow the organization
to be more robust and precise. The system development can be justified by the advantages it will
receive from the implementation of the system.
Organizational Feasibility: The organization wants a system that can handle the entire
business processes. The system needs to be reliable, robust, highly capable of processing queries,
and able to handle huge amount of data. The proposed system will convert the manual system of
Sunshine Motors to automatic. The organization operations will be more structured, efficient and
cost effective. The inventory management will track of every items that are used in service. The
customer satisfaction level will increase.
Requirement Specifications:
Functional Requirements:
Authentication: Authentication refers to the condition of checking customer validity to
access the system. A user will get authentication to access the system only if the customer id and
password is verified. The system authentication can be implemented in many other ways but as
per the scenario of this organization, this is the most suitable method.

6SPECIFICATION DOCUMENT
Authorization: The authorization refers to the condition of checking whether the user
have authority to access the requested data or function. The system will have different
authorization levels. Each level will be associated with each user. The authorization will done
based on the login id of the customer. The system will show only the authorized functions to the
users to minimize the chance of authorization conflict. However, if a user tries to trick the system
then it can easily detect the fraud.
Maintain Inventory: The system needs to maintain the inventory of sunshine motors.
The system will track how much parts and consumables are used in services and how many are
available in stock. If the stock level reaches the minimum amount then system will inform the
purchase manager new parts. New parts that are not listed in the inventory can be asked by the
mechanic to buy. The system will store the details of the items and track the usages and
purchases.
Payment: The system will handle the payment customers make for the service they get
from sunshine motors. The system will automatically calculate the charge based on the items
used, complexity of task and hours required for service. The system will provide options to the
customer to make payment using debit card, credit card, digital wallet or cash. In either of the
case, the system will record the payment details either automatically or through admin input.
Non-Functional Requirement:
Security: As the system will be handling sensitive data of the organization and handle
customer payments, its needs to be highly secure. The system will prevent any kind of physical
security flaws. Each device installed in the organization premise will have updated antivirus
support.

7SPECIFICATION DOCUMENT
Maintainability: The system should be maintained properly. The software patches will be
installed periodically. Audit will be conducted in each quarter to make sure everything is find
and secure.
Availability: The system should be available 24*7. The customer can request for service
at any time. During the office hours, the server should never fail to be running as if system goes
down then organization processes will be hampered.
Assumptions/Constraints:
Assumptions: The first assumption is that system will be accessed from a web browser.
The system will connect the customer perspective with the organization perspective. This means
that both the customer and staff will use same system’s different parts. A centralized database
will be connected to the system. The system needs to be in the cloud environment as the
customer will access the system from remote locations. The management will have the highest
authority over the system. The management can make changes in any data recorded into the
system. The customer registration with suspicious email ids must be approved by the
administrator. Each user will access different interfaces which will be based on the basic works
they do in organization. In order to book a service, the customer needs to login to the system or
the system will not active the service booking form for the client.
Constraints: The real constraint of system development is the collection of requirements.
The system has many aspects which will be based on the business operations. Collecting data
from the staff and customer and converting those data into system requirements are very
complicated process. The system coding is also a constraint of the system. NodeJS is a high level
language needs a skilled personnel. As the complexity of the system is high, without a team of

8SPECIFICATION DOCUMENT
experts a system cannot be implemented. Providing real time data flow in the system is one of
the trickiest part of the system while the database is an important factor.
Use Cases:
Figure 1: Use Case Diagram

9SPECIFICATION DOCUMENT
(Source: Created by Author)
Use Case Name Decrement Inventory
Use Case ID Mechanic_UC_02
Actors Mechanic
Precondition The mechanic must be assigned to a service
Activities Actor System
The mechanic open the system
The mechanic click on use items
link
System redirect the user to a new
page where all the item types are
visible
Mechanic select the item and
specify the amount
System verify whether mentioned
amount is available in inventory
System shows an alter
The mechanic sees the
confirmation alert
Mechanic confirms the item usage If the amount is available then
system subtract selected amount
from available amount
Post condition The available items will be changed
Exception The items are available but due to low supply is restricted for special
cases

10SPECIFICATION DOCUMENT
Context Model:
Figure 2: Context Level Diagram
(Source: Created by Author)

11SPECIFICATION DOCUMENT
Levelled Set of Functional Models:
Figure 3: Functional Model Diagram
(Source: Created by Author)

12SPECIFICATION DOCUMENT
Bibliography:
Arora, P.K. and Bhatia, R., 2018. Agent-Based Regression Test Case Generation using Class
Diagram, Use cases and Activity Diagram. Procedia Computer Science, 125, pp.747-753.
Balanis, C.A., 2016. Antenna theory: analysis and design. John wiley & sons.
Dennis, A. and Wixom, B.H., 2018. Systems analysis and design. Wiley.
Ding, Z., Jiang, M. and Zhou, M., 2016. Generating Petri net-based behavioral models from
textual use cases and application in railway networks. IEEE Transactions on Intelligent
Transportation Systems, 17(12), pp.3330-3343.
Gupta, A.K., 2017. Response spectrum method in seismic analysis and design of structures.
Routledge.
Jagtap, S., Gawde, V., Pawar, R., Shendge, S. and Avhad, P., 2016. Generate Test Cases From
UML Use Case and State Chart Diagrams. International Research Journal of Engineering and
Technology (IRJET), 3, pp.873-881.
Kumar, B. and Singh, K., 2015. Testing uml designs using class, sequence and activity
diagrams. International Journal for Innovative Research in Science and Technology, 2(3), pp.71-
81.
Oinas-Kukkonen, H. and Harjumaa, M., 2018. Persuasive systems design: key issues, process
model and system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge.
Uke, S. and Thool, R., 2016. UML based modeling for data aggregation in secured wireless
sensor network. Procedia Computer Science, 78, pp.706-713.