MITS5502 Assignment 3: Sunshine Motors System Design and Report

This report presents the specification and design documents for the Sunshine Motors system, developed as part of a software engineering assignment. The report begins with an executive summary, system description, scope, and feasibility analysis. It then details functional and non-functional requirements, assumptions, and constraints. Use case diagrams, use case descriptions, and a context model are provided to illustrate system functionality. The design document covers architectural design, hardware specifications, class diagrams, and interface designs, including login, dashboard, payment process, and registration pages. Business process models, sequence diagrams, and interaction diagrams depict various system processes, such as car loan requests, payment processing, and registration. The report concludes with recommendations, and a conclusion.

Table of Contents
Specification Document..................................................................................................................................................1
1.1 Executive Summary.........................................................................................................................................1
1.2 System Description..........................................................................................................................................1
1.3 Scope...............................................................................................................................................................1
1.4 Feasibility Analysis...........................................................................................................................................1
1.4.1 Project description...................................................................................................................................1
1.4.2 Possible solution......................................................................................................................................1
1.4.3 Feasible solution......................................................................................................................................1
1.5 Requirements Specification.............................................................................................................................2
1.5.1 Functional................................................................................................................................................2
1.5.2 Non-Functional........................................................................................................................................2
1.6 Assumptions/ Constraints...............................................................................................................................3
1.6.1 Assumptions............................................................................................................................................3
1.6.2 Constraints..............................................................................................................................................3
1.7 Use Case Diagrams..........................................................................................................................................4
1.7.1 Figure 1 below dhow use case diagram of Sunshine moto system..........................................................4
1.8 Use Case Descriptions.....................................................................................................................................4
1.8.1 Table 1 below show use case description of Sun shine Motor Company................................................4
1.9 Context Model.................................................................................................................................................5
1.9.1 Figure 2 below show context model of Sun shine system.......................................................................5
Design Document............................................................................................................................................................6
1.10 Executive Summary.........................................................................................................................................6
1.11 Architectural Design........................................................................................................................................6
1.11.1 Main User Interface.................................................................................................................................6
1.11.2 Application logic......................................................................................................................................6
1.11.3 Data store................................................................................................................................................6
1.11.4 Figure 3 below shows high level architecture of sunshine system..........................................................7
1.11.5 Figure 4 below show low level Sunshine Motors.....................................................................................7
1.12 Hardware Specification...................................................................................................................................8
1.12.1 Table 2 below show Hardware specification of Sun Shine Motors..........................................................8
1.13 Class diagram...................................................................................................................................................9
1.13.1 Figure 5 below show a detailed class diagram of sunshine motors.........................................................9
1.14 Interface Design..............................................................................................................................................9
1.14.1 Figure 6 below show login page of Sun shine system..............................................................................9

1.14.2 Figure 7 below show dashboard of sunshine systerm...........................................................................10
1.14.3 Figure 8 below show payment process at Sunshine motor system.......................................................10
1.14.4 Figure 9 below show registration of customer at Sunshine Motors sytem............................................11
1.15 Business Process Models...............................................................................................................................12
1.15.1 Figure 10 below show car loan request process at Sunshine Motors....................................................12
1.15.2 Figure 11 below show payment process at Sunshine Motor Company.................................................12
1.15.3 Figure 12 below show inventory monitoring at Sun shine Company.....................................................13
1.15.4 Figure 13 below show a customer requesting for vehicle servicing at Sunshine Motors company.......14
1.16
Sequence Diagram.........................................................................................................................................15
1.16.1 Figure 14 show sequence diagram of login process..............................................................................15
1.16.2 Figure 15 below show sequence diagram of payment process.............................................................16
1.16.3 Figure 16 Below show sequence diagram of registration process.........................................................17
1.17 Interaction diagram.......................................................................................................................................17
1.17.1 Figure 17 below shows car loan request interaction diagram at Sunshine Motor................................17
1.17.2 Figure 18 below show customer making payment interaction Diagram at Sunshine Motors
Company.
17
1.17.3 Figure 19 below show registration interaction diagram at Sunshine Motors Company........................18
1.17.4 Figure 20 below show state chart diagram of loan request at sunshine Motors...................................18
1.17.5 Figure 21 below show state diagram of Payment at sunshine motors..................................................18
1.18 Recommendation..........................................................................................................................................19
1.19 Conclusion.....................................................................................................................................................19
1.20 Reference......................................................................................................................................................20
Specification Document
1.1 Executive Summary.
The Sunshine Company has decided to automate all its business process by developing Sunshine system.
This system will help Sunshine employee to easy their work and enable client s to borrow, order for moto
vehicle repairing services and paying.
1.2 System Description
The sunshine system is a web based system that will help manager of Sunshine company monitor inventory,
it will also help mechanics in making their work easy because system auto assign mechanics
work .Mechanic checks work order and picks work of the day. The system has automated all the process of
the company by eliminating paper work.Systerm helps client to borrow cars and bring vehicle for repairing
at the company

1.3 Scope
The sunshine moto system is going to cover by motor vehicle user with needs of repairing their vehicle and
enhance car loaning services. The system is used within company by company’s employees, work bays and
customer all over the glob because system shall be hosted online.
1.4 Feasibility Analysis.
1.4.1 Project description
This project will enable sunshine company to provide quality services and cab wastage by automating
business process.
1.4.2 Possible solution.
The project undertakes to implement three solution; online payment system, Car loaning system and
inventory management system. The solution are well analyzed and required information for decision making
are provided to sunshine management.
Solutions possibilities of the project are evaluated and determined in details by comparing software
specification document, design specification document and schedule
1.4.3 Feasible solution
The best economical, technical and productive solution is selected to be implemented
1.5 Requirements Specification
1.5.1 Functional
Before all user start using the system they have to be registered
The most important function is to only grant access to users that are listed in the database. The customer
will provide the information on who will be allowed access. To implement the security, the web page must
check the database to see if the Username and Password are valid. If they are not, the user will receive an
“Invalid login. Please try again.” Response.
The customer shall be able to request for a car Loan on system. Customer shall login on system and click
request loan icon on dashboard then follows instructions to enable him/her acquire car loan.
The system shall allow customer signs work order when they bring their vehicle for servicing at the work
bay.
The system shall enable purchasing officer in monitoring the levels of inventory and request supplier to
supply products to sunshine company.
The system shall enable mechanics to login on system and assign him/her self-daily task or checking his/her
worker schedule on system.
The system shall auto all allocate mechanics to work bay.

The system shall assign mechanics work order.
The customer shall use the system to describe the service on work order and indicates the faults on the
vehicle.
The system track work progress of worker order.
The mechanics on completion of service on vehicle, the mechanics login on system and indicate it as
complete.
The mechanic shall login on system and request for consumable and common parts to be used in servicing
the vehicle.
The system notify service assistant about completion of work.
The system shall check if parts are available in the inventory.
1.5.2 Non-Functional
Performance Requirements
The software will be accessed more than one user at time. Only csv files of different sales from different
branches over a specified period of time. 95% of the transactions shall be processed in less than 1 minute
Safety Requirements
Importing anything else other than csv file can result into damage of the software but this is prevented by
inbuilt function which gives an alert in case any is detected.
Security Requirements
Access to the database should be restricted to people that are required to view information about recently
imported csv files. Passwords and ID’s should be regulated to be at least a certain length and must contain
non-alphanumeric characters in both the password and ID
Portability
To ensure portability the system will be developed in R, PHP and JAVASCRIPT.
Reliability & Availability
Internet Service Provider
The software shall provide a contractual agreement with an internet service provider for T1 multi bonding
access with 99.9999% availability.
The software shall provide a contractual agreement with an internet service provider who can provide
99.999% availability through their network facilities onto the internet.
Usability.
Graphical User Interface
The software shall provide a uniform look and feel between all the web pages.
The software shall provide a digital image for bar graphs in the product catalog.
The software shall provide use of icons.

1.6 Assumptions/ Constraints
1.6.1 Assumptions.
All users are computer literate.
All users can access the internet.
1.6.2 Constraints
These are the anticipated constraints:
The time it takes for the database to update inventory availability information should not exceed 5 seconds.
The application shall be web base application
The application will be delivered over the internet and can be used by only those with smartphones
1.7 Use Case Diagrams
1.7.1 Figure 1 below dhow use case diagram of Sunshine moto system.

1.8 Use Case Descriptions
1.8.1 Table 1 below show use case description of Sun shine Motor Company.
Use case Name Description
Login All system users are supposed to login on system
with password and username.
Authentication The system has to verify the details of user before
accessing system.
Registration All system user have to be registered and store in
a database.
Make payment Customer access system and pay for service
Check inventory Staff access system and check inventory levels
Assign System assign mechanics a workbay
Notification System notify customer

1.9 Context Model
1.9.1 Figure 2 below show context model of Sun shine system

Design Document.
1.10 Executive Summary.
On completion of Software specification document the company has embarked on designing the system.
1.11 Architectural Design
The architectural design considered for sunshine motor system follows a Client Server architectural style,
with the client stub consisting of the main user interfaces (browser and the text editor) that the actors interact
with, and the server stub consists of the application logic and the respective data repositories that are
created, updated and manipulated. Components in the client and server stub collaborate closely to achieve
the desired functionalities.
1.11.1 Main User Interface
This module consists of the interfaces that the actors use to communicate with the rest of the system
components. It consist of the text editor which receives the voice commands issued by an actor and
processes them and returns a result or feedback, a browser that loads and runs the web pages on command
from the actor.
1.11.2 Application logic.
It composed of several modules that are in charge of different responsibilities and these include;
 Authentication module
It is responsible for registering the drivers and parking operators as well as authorizing access to the
mobile application through use of login credentials.
 Loan Request module
Responsible to request available car for borrowing they system does manipulation and check
database if system is available and returns result.
 payment module
It is responsible for calculating the total service charge amount that is supposed to be paid by the
customer and enabling the customer to make the payments.
1.11.3 Data store
The system maintains two data stores that is a data dictionary, and project system files data store. The data
dictionary is an SQLite data store that keeps records of the html syntactical rules and guidelines that are
allowable, system preferences and user preferences. The files data store is a directory that keeps records of
the created system files. Other modules have access to create, modify, and delete the files in these
repositories.

1.11.4 Figure 3 below shows high level architecture of sunshine system.
1.11.5 Figure 4 below show low level Sunshine Motors.

1.12 Hardware Specification.
1.12.1 Table 2 below show Hardware specification of Sun Shine Motors.
Name specification
Operating system Microsoft window 7 and above, Linux and Solaris
Server side PHP (works with API)
Database Mysql
Processor 3GHZ or more
Memory(RAM) 4GB or bigger
HardDrive 500GB or more
Data Back up device. any
Power Device Electric 12Ac or dc 12
Networking devices Router, modem ,switch,fibre cables and Ethernet
cables
Printers any can be used
Monitor Any monitor can be used so long it works well

1.13 Class diagram.
1.13.1 Figure 5 below show a detailed class diagram of sunshine motors
1.14 Interface Design
1.14.1 Figure 6 below show login page of Sun shine system

1.14.2 Figure 7 below show dashboard of sunshine systerm
1.14.3 Figure 8 below show payment process at Sunshine motor system.

1.14.4 Figure 9 below show registration of customer at Sunshine Motors sytem.

1.15 Business Process Models
1.15.1 Figure 10 below show car loan request process at Sunshine Motors.
1.15.2 Figure 11 below show payment process at Sunshine Motor Company.

1.15.3 Figure 12 below show inventory monitoring at Sun shine Company.

1.15.4 Figure 13 below show a customer requesting for vehicle servicing at Sunshine Motors
company.

1.16 Sequence Diagram
1.16.1 Figure 14 show sequence diagram of login process

:Authentication
User
Database
Username/
password
User :
<<create>>
fetchUser
(credetials)
1: [user not
Found]
display login
page with failure
messsages
2: [user Found]
Success
1.16.2 Figure 15 below show sequence diagram of payment process

1.16.3 Figure 16 Below show sequence diagram of registration process
1.17 Interaction diagram.
1.17.1 Figure 17 below shows car loan request interaction diagram at Sunshine Motor
1.17.2 Figure 18 below show customer making payment interaction Diagram at Sunshine Motors
Company.

1.17.3 Figure 19 below show registration interaction diagram at Sunshine Motors Company.
1.17.4 Figure 20 below show state chart diagram of loan request at sunshine Motors
1.17.5 Figure 21 below show state diagram of Payment at sunshine motors

1.18 Recommendation.
This software specification and design specification are well detailed and captures all system and user
requirements, so they can be used during implementation of system.
1.19 Conclusion
The report has covered all requirement of Sunshine Motors company.

1.20 Reference.
(1).Thomas M. Connolly and Carolyn E. Begg .Database systems a practical approach to Design,
implementation and management. 6th Ed, vol 3 .Harlow, Essex, England: Addison-Wesley Pearson
Education Limited, 2015, pp, 109 -111
(2).Pressman, Simenon .Software Engineering. Practitioner’s Approach. 8thEd vol 6. Inc., 1221 Avenue of
the Americas, New York, McGraw-Hill, 2017.pp, 399-450.
(3).Lethbridge, M Timothy. Object-Oriented Software Engineering: Practical Software Development Using
UML and Java 3ndEd ,VOL 6. New York, McGraw-Hill.2016,pp, 200-300.