Overview of Software Engineering

This article provides an overview of software engineering, including use case diagrams, descriptions, and diagrams for 'Add a New Registration by Authority' and 'View Car Registration and Insurance Details by a Customer'.

Running head: OVERVIEW OF SOFTWARE ENGINEERING
Overview of Software Engineering
Name of Student-
Name of University-
Author’s Note-

1OVERVIEW OF SOFTWARE ENGINEERING
Use case diagram for ‘Add a New Registration by Authority’
Figure 1: Use Case Diagram
(Source: Created by Author using Visio)
Use Case Descriptions for ‘Add a New Registration by Authority’

2OVERVIEW OF SOFTWARE ENGINEERING
Use Case Name Motor Registration System
Scenario The actor authority adds a new registration in the system. The authority
adds new registration with customer and their cars in the system. The
authority will also store the details of the CTP insurance associated with
the customer in the system.
Triggering
Event
When the customer registers themselves in the system and registers their
cars, the authority stores the details of the customer along with the
authority so that the data related with the customer are synchronized in the
system.
Brief
Description
The details of the car and the details of the customers will be stored in the
system. The motor registration system can store the details of customer
along with the details of the cars. There are car insurance taken by many
customers and those CPT insurance are also stored in the system. The
authority has to login in system so that to view the data, update the data or
to send email to the customers when necessary.
Actors The actors involved with the use case is Authority who is involved with
the system.
Related Use
Case
View Car Registration and Insurance Details by a Customer
Stakeholders The stakeholders are the owner of motor registration, the customers, the
insurance providers and the authority involved with the system.
Pre-conditions The authority needs to sign in to the system so that they might have access
to the system.

3OVERVIEW OF SOFTWARE ENGINEERING
The authority needs to have the details of the cars so that they can update
it on the system.
The authority needs to have new registration details to add the data to the
system.
The email address of all the customers should be present with the
authority.
Post-Conditions The registration of the customer is to be completed after authority
completing registration system.
The customer registration process is to be completed with the system.
Flow of
Activities
Actor System
Authority The system needs to have a proper user interface
so that the actor can provide the details in the
system. The system should be efficient so that
the actors feels easy to complete the process.
Exceptional
Scenario
The two exceptional scenario in the system is log in the system and add
new members to the system. Both the scenarios are added externally in
the system.
System Sequence Diagram for ‘Add a New Registration by Authority’

4OVERVIEW OF SOFTWARE ENGINEERING
Figure 2: Sequence Diagram
(Source: Created by Author using Visio)
Updated UML Class Diagram for ‘Add a New Registration by Authority’

5OVERVIEW OF SOFTWARE ENGINEERING
Figure 3: Updated Class Diagram
(Source: Created by Author using Visio)

6OVERVIEW OF SOFTWARE ENGINEERING
Activity Diagram for ‘Add a New Registration by Authority’
Figure 4: Activity Diagram
(Source: Created by Author using Visio)
Use case diagram for ‘View Car Registration and Insurance Details by a
Customer’

7OVERVIEW OF SOFTWARE ENGINEERING
Figure 5: Use Case Diagram
(Source: Created by Author using Visio)
Use case description for ‘View Car Registration and Insurance Details by a
Customer’
Use Case Name Motor Registration system
Scenario The customer has to view car registration and view the insurance details
that are stored with the system.
Triggering
Event
When the authority approves the registration process, this use case can be
followed to view the data of the system.

8OVERVIEW OF SOFTWARE ENGINEERING
Brief
Description
When the customer completes the registration process, this process of
viewing the car registration and the insurance details is to be taken place.
The customer can view the data of their car details and their insurance
details in the system so that they can renew their insurance policies and
get the details of every parts of their car in the system.
Actors The actor is customer
Related Use
Case
Related use vase with this use case is updating new registration system so
that the customers can view accordingly.
Stakeholders The stakeholders are the owner of motor registration, the customers, the
insurance providers and the authority involved with the system.
Pre-conditions The authority needs to sign in to the system so that they might have access
to the system.
The authority needs to have the details of the cars so that they can update
it on the system.
The authority needs to have new registration details to add the data to the
system.
The email address of all the customers should be present with the
authority.
Post-Conditions The registration of the customer is to be completed after authority
completing registration system.
The customer registration process is to be completed with the system.
Flow of
Activities
Actor System
Patients The patient needs to view their summary data

9OVERVIEW OF SOFTWARE ENGINEERING
from the system so that they can view their
presents status and can share the data with
others.
Exception
Condition
Register online and logout are the two exceptional scenarios as this is not
present in the case study. The register online helps to register the
customer and logout helps to exit from the system.
State Transition Diagram for ‘View Car Registration and Insurance Details
by a Customer’
Figure 6: State Transition Diagram
(Source: Created by Author using Visio)
Prototyping Tool for Motor Registration system

10OVERVIEW OF SOFTWARE ENGINEERING
The verification and validation technique that can be used for this project is auditing,
desk checking, documentation checking, face validation, inspections, reviews, Turing tests and
walkthrough processes.
Auditing method is generally used for determining the investigation adequacy that is to
be used in the overall development process so that the practices standards as well as the
guidelines can be achieved. Auditing is the process that includes meeting mixture, observations
as well as examinations. The audit processes is generally performed by the auditor and it consists
of reviews and testing methods that are done in periodic basis. Auditing also includes traceability
that comes within the development process.
The desk checking is the first step in the process and this is the initial step that can be
taken in the system. This techniques includes analysing some program by the help of hand by
sitting at one particular desk. This technique is more effective when this process of conducted by
other person or some other group of people.
Documentation checking mainly includes assessment quality that includes all the
documentation aspect rather than using quality of the content. There is a quality characteristics
includes accessibility, accuracy, clarity, completeness, maintainability, readability and
portability.
Face validation is the technique that is included in the project as because the team
members of the project, the potential users of model as well as the people who have knowledge
about the system that is being studied mainly happens on the estimates as well as intuition,
compare the model subjectively and includes system behaviours that comes under the identical

11OVERVIEW OF SOFTWARE ENGINEERING
condition. This techniques is basically used for preliminary approach so that verification and
validation is done effectively.
Inspections are mainly conducted by the team having upto six members so that the
development work of the project can be done with the project specification along with project
design and project code. In the design inspection, there is moderator, reader, designer, tester,
implementer, and recorder. Reviews are mainly carried out with as same manner with the
inspection as well as with walkthrough in the particular way that the team has selected for the
project. The review techniques of verification also includes managers and the reviews results in
providing management as well as sponsor evidence for developing the model that is being
developed along with the project objectives. The review of the project also helps to evaluate
model as the development standards, guidelines as well as includes specifications. The review
technique includes high technique level compared than inspection technique and walkthroughs.
Tiring tests are mainly depended on the SMEs (Subject matter Experts) who have
knowledge related with the system that is under the study. SMEs are mainly presented with
different sets of output data, one data comes from a particular model and the other comes from
the system. In turning test, the SMEs has to make the difference between the two models.
Walkthrough is the last technique that can be used for validation technique in the system.
This walkthrough is also known as structured walkthrough and team consists of moderators,
members of 3 to 6, and model developer. All the members except the model developer are
directly involved with development effort. The roles of the team members associated with the
walkthrough are presenters, coordinator, scribes, user representatives and other reviewers.
Conclusion

12OVERVIEW OF SOFTWARE ENGINEERING
From the above report, it can be stated that a new motor registration system is to be
developed that will be capable of registering the details of the cars along with their customers in
the system. The motor vehicle registration compliance wants to register the customers and their
registered cars in the system so that they can be tracked easily. The system that is be developed
states that the customer can view their car insurance policies and the registration of their cars in
the system. The customers can register themselves and have their details of the car in the system.
The authority of the system will approve the registration with the system so that the customer
along with their cars are secured safely in the system. This report states the use case diagram, the
state transition diagram, and the activity diagram of two of the activities that takes place in the
system. This report also defines the use case description of the system that helps to define the use
cases in the system.

13OVERVIEW OF SOFTWARE ENGINEERING
Bibliography
[1] C.A. Balanis. Antenna theory: analysis and design. John wiley & sons, 2016.
[2] A. Dennis, B.H. Wixom, and R.M. Roth. Systems analysis and design. John wiley & sons,
2018.
[3] W. Pedrycz. Granular computing: analysis and design of intelligent systems. CRC press,
2016.
[4] A.T. Azar and S. eds. Vaidyanathan. Chaos modeling and control systems design (Vol. 581).
Germany: Springer, 2015.
[5] D.C., Montgomery. Design and analysis of experiments. John wiley & sons, 2017.
[6] E. Tappia, D. Roy, R. De Kosterand, M. Melacini. Modeling, analysis, and design insights
for shuttle-based compact storage systems. Transportation Science, 51(1), 2016, pp.269-295.