Overview of Software Engineering

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

OVERVIEW OF SOFTWARE ENGINEERING1
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’

OVERVIEW OF SOFTWARE ENGINEERING2
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.

OVERVIEW OF SOFTWARE ENGINEERING3
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’