Software Engineering Methodology

This report provides details about the software engineering methodology, including specification document, design document, and bibliography.

Running head: Software Engineering Methodology
Software Engineering Methodology
Name of the student:
Name of the university:
Author note:

1Software Engineering Methodology
Table of Contents
Specification document..............................................................................................................2
Design Document.......................................................................................................................5
Bibliography:............................................................................................................................24

2Software Engineering Methodology
Specification document
Executive summary:
The following part of the report describes the details of the information system that is
proposed to be used with in the organization of Sunshine Motors. It produces a clear
description of the specifications that will be provided in the system helping the managers as
well as the clients to effectively manage the information.
System Description:
Sunshine Motors is one of the old car dealerships and recently its new management
team has decided to develop a new system for their service department. The new system that
was decided to implement will allow the company to store its detailed record of the clients
including their details related to name, address, contact details, besides it will also help in
storing information about the model, registration and color of the vehicles. The new system
that is designed will also help in storing information related to the history of the services
provided by the labours and the mechanical parts that are involved in the process. The system
is designed in such a way so that it can store information about the mechanics who are
available. The mechanics can enter their information into the specified system. Besides the
mechanics, the front office staffs are also equipped with the advantage for entering
information at any of the ten terminals. The system will also enable the road staffs to enter
details about the arrival of the client with their vehicles. As the company provides loan cars
to its clients, so the system is also designed to store information about when the cars are
available, and also details of the client to whom the loan cars are provided and for what
amount of time. The information system that is designed for the company is also equipped
with the specifications for checking the inventory levels for any orders at any time.

3Software Engineering Methodology
Scope:
The current system that the company of Sunshine Motor is using to serve its clients is
manual based and hence implementing this upgraded information system into their business
process will help them in managing the increased workload demand by managing them
effectively.
Feasibility Analysis:
The proposed system is quite feasible for the customers as well as the managers of the
company of Sunshine Motors as the managers can effectively manage the information related
to their clients and also the vehicles by keeping daily record in the system rather than using
the details manually. The mechanics working under the company can also store their data
related to the serving of the clients accordingly at any time. Besides the system is also
feasible from the customers end as they get a lot of benefit while using this system.
Whenever they come to pick up a vehicle, they are provided with an invoice message related
to their payment that needs to be paid and whenever the invoice is fully paid, the flag is
closed. This system enables the customers to view their payment details and also allows them
to open accounts with the system while receiving monthly statements through their post.
Though the system provides feasibility to the managers and its customers but still it
has some issues that are faced within it like, it becomes difficult to keep a daily track of the
work orders and thus the company faces difficulty in answering the phone calls of the
customers. Also, as the business is gradually growing hence it faces problems regarding
keeping track of the customers and their inventory levels.
Requirement Specification:
Functional: The functional requirement of the proposed system includes the
following:

4Software Engineering Methodology
1. Displaying the customer’s name
2. Available vehicles
3. Displaying history of the services that are provided
4. Displaying details of the parts used for specific services
5. Keeping records of the mechanics
6. Reporting requirements
7. Administrative functions
Non-functional: The non-functional requirement of the system includes-
1. Performance
2. Scalability
3. Availability
4. Maintainability
5. Serviceability
6. Manageability
7. Usability
Assumptions/Constraints:
Some of the constraints that are identified includes:
1. The clients or the mechanics do not have the right to edit any data in the system
2. Online payment facility may be restricted if in case the company do not want this
facility.

5Software Engineering Methodology
Design Document
Executive summary:
This part of the report reflects the details of the architectural design of the information
system. The different parts that are designed within the system is reflected in this part along
with the detailed process details.
Architectural Design:
The entire architecture of the management system is divided several categories like
the part which will be managed by the mechanics, the part which will be used by the
managers and the part related to the payment details. The mechanics who are entitled under a
rostered day off can enter their details about serving the clients in any one of the terminals.
Mechanics can also access the system to assign their next day work order whenever they are
free. Each of the work order contains a standard work items to specific services, customers
can also note if there is any fault within the services. With different services, mechanics may
need new parts that needs to be used and thus they can access the log details of the parts and
the system simultaneously updates the inventory database of the system.
The next part of the architectural design of the management system, is comprised of
specifications that are to be used by the managers. The managers of the company need to
access the inventory log to record the parts that are used by the mechanics. The system is well
designed so as to check the inventory levels at any time and also to order additional stocks
when required. The entire system is designed to handle upto 5000 parts and the warning
levels of the consumable parts are specified by the purchasing officers within the system.

6Software Engineering Methodology
The next part of the system comprises of the payment related specifications.
Customers while picking up any vehicles are provided with an invoice message about the
payment that needs to be done and once the payment is completed the ticket gets closed.
Customers who are having an account on the system, will get a monthly statement from the
system. The payment system is designed in such a way so that it sends a copy of the payment
to the customers in their account or via text messages in case the customer has their mobile
numbers registered within the system.
Hardware specification:
Processor: Intel Opteron
Hard Disk: 10TB
Ram: 32 GB

7Software Engineering Methodology
INTERACTION DIAGRAMS:
Figure 1 Interaction diagram 1
Figure 2 Interaction diagram 2

8Software Engineering Methodology
Figure 3 Interaction diagram 3
Figure 4 Interaction diagram 4
INTERFACE DESIGN:

9Software Engineering Methodology
Figure 5 Wireframe 1

10Software Engineering Methodology
Figure 6 Wireframe 2

11Software Engineering Methodology
Figure 7 Wireframe 3
CONTEXT DIAGRAM:

12Software Engineering Methodology
Figure 8 Context diagram
SEQUENCE DIAGRAM:
Figure 9 Sequence diagram 1

13Software Engineering Methodology
Figure 10 Sequence diagram 2
Figure 11 Sequence diagram 3

14Software Engineering Methodology
Figure 12 Sequence diagram 4
STATE DIAGRAMS:
Figure 13 State diagram 1

15Software Engineering Methodology
Figure 14 State diagram 2
Figure 15 State diagram 3

16Software Engineering Methodology
Figure 16 State diagram 4
USE CASE DIAGRAMS:

17Software Engineering Methodology
Figure 17 Use case diagram 1

18Software Engineering Methodology
Figure 18Use case diagram 2

19Software Engineering Methodology
Figure 19 Use case diagram 3

20Software Engineering Methodology

21Software Engineering Methodology
Figure 20 Use case diagram 4

22Software Engineering Methodology
CLASS DIAGRAM:
Figure 21 Class diagram
BPMN DIAGRAMS:
Figure 22 BPMN diagram 1

23Software Engineering Methodology
Figure 23 BPMN diagram 2
Figure 24 BPMN diagram 3

24Software Engineering Methodology
Figure 25 BPMN diagram 4
ARCHITECTURAL DIAGRAM:
Figure 26 Architectural diagram

25Software Engineering Methodology

26Software Engineering Methodology
Bibliography:
Arora, P. K., & Bhatia, R. (2018). Agent-Based Regression Test Case Generation using Class
Diagram, Use cases and Activity Diagram. Procedia Computer Science, 125, 747-753.
Gaidarski, I., Minchev, Z., & Andreev, R. (2018, December). Model Driven Architectural
Design of Information Security System. In International Conference on Soft Computing and
Pattern Recognition (pp. 349-359). Springer, Cham.
Karim, S., Liawatimena, S., Trisetyarso, A., Abbas, B. S., & Suparta, W. (2017, November).
Automating functional and structural software size measurement based on XML structure of
UML sequence diagram. In 2017 IEEE International Conference on Cybernetics and
Computational Intelligence (CyberneticsCom) (pp. 24-28). IEEE.
Li, Q., & Chen, Y. L. (2009). Data flow diagram. In Modeling and Analysis of Enterprise
and Information Systems (pp. 85-97). Springer, Berlin, Heidelberg.
Mythily, M., Valarmathi, M. L., & Durai, C. A. D. (2018). Model transformation using
logical prediction from sequence diagram: an experimental approach. Cluster Computing, 1-
12.
Razali, R., Najafi, P., & Mirisaee, S. H. (2010, June). Combining Use Case Diagram and
Integrated Definition's IDEFO—A preliminary study. In The 2nd International Conference
on Software Engineering and Data Mining (pp. 231-236). IEEE.
Santa Rosa, J. G., Borges, T. H., Santos, J. B., Filgueria, M. S., Oliveira, T., Scliar-Cabral, L.,
... & Stransky, B. (2016, July). Prototyping and Interface Design of an Automated Screening
Test to Evaluate the Linguistic Processing Abilities of School Children. In International
Conference of Design, User Experience, and Usability (pp. 208-215). Springer, Cham.

27Software Engineering Methodology
Villavicencio, M., & Izquierdo, E. (2016, April). Evaluation of prototyping tools based on
categories and parameters. In 2016 IEEE Colombian Conference on Communications and
Computing (COLCOM) (pp. 1-6). IEEE.