Case Study Analysis: Software Engineering Methodology

CASE STUDY ANALYSIS
Software Engineering Methodology
Design Document
The Name of the Class (Course)
Professor (Tutor)
The Name of the School (University)
The City and State where it is located
The Date

CASE STUDY ANALYSIS
Table of Content
Table of Content..............................................................................................................................2
Executive Summary.........................................................................................................................3
Architectural Design........................................................................................................................4
Hardware Specifications..................................................................................................................5
PC.................................................................................................................................................5
Mobile..........................................................................................................................................6
Detailed Class Diagram...................................................................................................................7
Business Process Model..................................................................................................................8
Interface Design...............................................................................................................................9
Wire Frames.................................................................................................................................9
Sequence Diagram.....................................................................................................................12
State Diagram.............................................................................................................................13
Interface Diagram..........................................................................................................................14
Table of Content
Figure 1: Architectural Design........................................................................................................4
Figure 2: PC requirement table........................................................................................................5
Figure 3: Mobile requirement table.................................................................................................6
Figure 4: Class Diagram..................................................................................................................7
Figure 5: Business process model....................................................................................................8
Figure 6: Updating wireframes........................................................................................................9
Figure 7: Work Order Interface.....................................................................................................10
Figure 8: Car Loan Interface..........................................................................................................10
Figure 9: Payment Interface...........................................................................................................11
Figure 10: Session Start Interface..................................................................................................11
Figure 11: Sequence Diagram.......................................................................................................12
Figure 12: State Diagram...............................................................................................................13
Figure 13: Interface Diagram.........................................................................................................14

CASE STUDY ANALYSIS
DESIGN DOCUMENT
Executive Summary
This project is a vehicle mechanical service company system for “Sunshine Motors”
which does not have a previously created system because the current one was manual. The
project is supposed to help manage the vehicles being brought to the company premises for
repair by with their owners. The mechanics who are available within the day are assigned to the
tasks according to their expertise and if a car is still needed by the owner, they will be loaned one
by the company. The system should be scalable in that it should allow for addition of Work Bays
and of new parts/consumables needed for new/upcoming jobs. A work order is treated as a
session which begins when placed and is closed once the job is done sending a notification to the
customer and creates an invoice for the job. When the customer comes back, they pay for the
invoice and the invoice is flagged closed but in case of users within the system, the invoice is
added to the monthly invoice. The project will have both mobile and web interfaces that will
help in the updating of the system database details.
The proposed project is supposed to solve the issue of keeping of records manually. The
system should accommodate all the company data and provide scalability in case the company
decides to increase their business scope for example, the expansion to the neighboring area to
create new work bays. The company should be able to easily increase their business by either
adding data into the database as well as adding of new modules which interact with their system.
This section tries to explain how the system is supposed to function:

CASE STUDY ANALYSIS
Architectural Design
This section explains briefly explains the functionalities of the business. The system is
not to be used by the customers rather it is to be used by the company workers. The company
workers interact with the system in order to create customer functionalities that help with the
running of the business. These functionalities help in asset tracking of the business.
Figure 1: Architectural Design