Comprehensive Report: Online Motor Vehicle Registration System Design

This report details the design and analysis of an online motor vehicle registration system, addressing the requirements of the Australian motor vehicle registration authority. It encompasses use case descriptions for both customers and the authority, outlining functionalities such as online registration, renewal, and viewing of vehicle and insurance details. The report employs various UML diagrams, including sequence, activity, and state transition diagrams, to illustrate system behavior and interactions. Furthermore, it explores prototyping tools like Axure RP and Azure to facilitate the development process. The report provides a comprehensive overview of the system's components, functionalities, and design considerations, ensuring efficient and user-friendly vehicle registration processes. The report is contributed by a student to Desklib, a platform offering AI-based study tools and solutions for students.

Running head: Motor registration System 1
The online motor vehicle registration system
Student name
Institution
Location of Institution
Professor’s name
Date

Motor Registration System 2
Table of Contents
List of figures...................................................................................................................................2
1.0 Introduction................................................................................................................................3
1.1 Use case..................................................................................................................................3
1.1.1 Use case description..................................................................................................4
1.1.2 Sequence diagram......................................................................................................5
1.1.3 Activity diagram........................................................................................................7
1.1.4 State transition diagram...........................................................................................10
1.1.5 Prototyping tool.......................................................................................................11
1.1.6 Azure........................................................................................................................12
1.1.7 Basic specifications.................................................................................................12
Conclusion.....................................................................................................................................12
References......................................................................................................................................13
List of figures
Figure 1: Add a new registration use sequence diagram.................................................................5
Figure 2: Add new registration by authority activity diagram........................................................6
Figure 3 View car registration and CPT insurance state machine diagram.....................................8

Motor Registration System 3
1.0 Introduction.
System analysis and design is the process of problem identification, coming up with ways of
solving the problem and dividing the problem to be solved into modules. This process is
important as it gives the software development team the prior knowledge of the system should
be. Proper analysis will automatically lead to good software. Australian motor vehicle
registration compliance involves a lot of activities and most of the information is supposed to
keep safe which can not be fully supported by paperwork, hence there is the need for an online
motors registration system in the company.
1.1 Use case description
Add a new Registration by authority Use case.
Classes involved in this use case include;
a) Car
This class shows the registration number of the car, the year it was manufactured and the
insurance number from the insurance company to be viewed by the customer. The information
about the car will be filled in by the authority. The car,s information will be important to both the
customer to be able to know the details about his car so that incase of replacement it wont be a
problem and the authority to know the quality of the vehicles dealt in.
b) Customer
The customer class shows customer’s details like names, phone number, address, date of birth,
email and the operations performed by the customer to ensure the success of the organization, to

Motor Registration System 4
be kept by the authority. The customer’s details will be provided by the customer when he will
be registering into the system. This information will be important to the authority because incase
the vehicle has warrant and it spoils, they will refer to the information from the system to know
if the vehicle was bought from them.
c) CPT insurance
CPT insurance class contains information about insurance. These include insurance name, policy
number and payment status. This is the specific insurance company that the customer will have
ensured the car in. A single car can be insured by more than one insurance company. The
customer will be providing information about the insurance company from which he will have
taken the cover.
1.1.1 Use case description
A use case is a term used in system engineering. This a description of the way users will perform
their functions as expected in the system [1].
Use case Add a new registration
Actor Organization’s Authority
Trigger The system shows that there is new
information that has to be added to the
system.
Precondition A new customer has registered into the
system, bought a car and insured it in a given

Motor Registration System 5
insurance company.
Description This case illustrates the condition where a
purchase of a car needs to be updated into the
system by the authority.
Postconditions The customer must be able to view the made
registration.
The information must be correct.
Table 1 use case description.
1.1.2 Sequence diagram
In this diagram, we majorly base on objects. The diagram shows the objects in interaction in a
given order within the system. Objects and classes are used to show the diagram of the system.
Lines called the message are used to show the connection. The objects' operations flow from one
object to another [2].

Motor Registration System 6
Figure 1: Add new registration by the authority sequence diagram.
The authority is the only user who will be able to add a new registration. New registration details
will include, customer’s information to be provided by the customer, motors’ information from
the user manual of the vehicle from the manufacturer and insurance company’s information from
which the car will be insured. Once the registration has been updated to the database of the
system, the data is kept for future use by the customer or to be updated by the authority. Once the
customer has added a new registration, he will be required to log out of the system to enable
proper information management and confidentiality.

Motor Registration System 7
1.1.3 Activity diagram
Activity diagram for adding a new Registration by authority (based on updated problem domain
model)
An activity diagram is a UML diagram that depicts the flow of activities within the system. The
activities flow in a given order starting from the first activity to the last one. Once a single step is
skipped the whole process has interfered with hence the activities must flow sequentially[3] .
Figure 2: Add new registration by the authority activity diagram
Add new registration activity diagram shows the flow of activities within the system.This will be
the most important part in the system since the most important functionality of the system will be
to store and display the kept information The authority will be logging into the system, verify

Motor Registration System 8
from the system if the registration is new or not, if not, the system terminates the process, if new,
the system will prompt the authority to feed in all the necessary information such as information
about the car, customer and CPT insurance [4]. Once the authority will have fed in the
information, he will instruct the system to store the information to the database to be used by the
customer later. The authority will be required to log into the system in the next visit.
View car registration and insurance details by a customer,
Classes involved in this use case are;
CPT Insurance
CPT insurance contains information relating to car insurance. The information will include
insurance name, policy number, and terms of the insurance. The customer will be providing
insurance information. The CPT insurance may have insured the car under different insurance
covers such as accident, theft or fire. All the policies will be provided in the system.
Marker
It has details of the person who made the car such as the person’s or organization’s name to be
accessed by the customer. This information will be fed into the system by the authority from the
manual.
Model
The model class shows the model name of the car. This information will be of use to the user. It
will be obtained from the manual by the authority once the customer orders for the car.

Motor Registration System 9
Engine.
It contains the properties of the engine that was used in the car. The engine is the most important
part of any machine. The type of the engine must be known to the user for her to sure of the type
he needs since there are different types of engines.
Other classes include; brakes, gearbox, gearbox type, wheel, and suspensions. This information
will be important to the user in case of the vehicle breakdown and the need for spare parts
replacements. The customer will be able to view the information since it will be stored in the
system's database.
i) Use case description of view registration and insurance information by customer.
Use case Customer Views car registration and
insurance information
Actor Customer
Trigger Customers want to know details about his
vehicle and the information concerning the
insurance company that has insured the car.
The customer has an issue with the insurance
company.
Preconditions There is information about registration and
insurance companies.

Motor Registration System 10
The customer is authorized and can access the
information.
Description The scenario describes the case where the
authority has registered the car, the customer
has registered into the system and the car is
insured. All these will ensure the success of
this scenario.
Postconditions The insurance company information is up to
date.
The customer is convinced of the information
in the system and logged out of the system.
The customer must have logged out of the
system.
Table 2 use case description.
1.1.4 State transition diagram.
This is a Unified modeling language diagram used in system analysis when explaining the
behavior of the system [5]. The behavior of the system includes, when its launched, when
running and when not in operation. The states of the system are procedural, that is, from
launching, running and finally stopping.

Motor Registration System 11
Figure 3 View car registration and CPT insurance by customer state machine diagram.
When the customer will be viewing the registration and CPT insurance, the system will be
supposed to be in the running state until the process is done. After the customer will have
launched the system, he will be prompt by the system to enter the login credential if he has ever
registered or registere to the system if never registered. The customer will then search for the
information from the system about the vehicle and the CPT insurance. The system will fetch the
information from the database and display it to the user. Once the customer is done with viewing
the information, he will log out from the system to avoid unauthorized access to the system and
the system will stop running.
1.1.5 Prototyping tool
A prototype is a sketch that resembles a fully functioning software system. Prototyping tools are
equipment used in creating prototypes faster and more effective. Prototyping is crucial as it
helps a system developer to know how the system will look like after development. There are
many different prototyping tools [6]. The choice of the tool depends on the system to be

Motor Registration System 12
developed, availability of the tool and the taste of the system developers. These tools include
Azure, InVision, Adobe experience design, web-flow, and sketch. Each has its advantage over
the others [7].
1.1.6 Azure
To develop a good prototype for the online car registration system, I will use Axure RP pro as
my prototyping tool. It is a software that runs majorly on windows operating system. Axure rp
pro enables prototype developers to come up with wireframe models, make prototypes and come
up with functional requirement specifications because of its in-built controls [8]. It is fast as
compared to other prototyping tools making the developer more productive in prototype
generation.
1.1.7 Basic specifications.
Azure as a prototyping tool should have layout control to enable the user to use it well, an output
to Microsoft word and excel that will help document the system's functional requirements and
should support the project team members by making their work easier.
Conclusion.
Generally, an online system works efficiently. When the above-found information, diagrams, and
tools will be implemented when developing the online motors registration system, the company
will have an easy time while using the system. The azure prototyping tool enables UX designers
to create users’ friendly prototypes which will lead to a better system. Any problem has to be
analyzed before real development is done to avoid some error in the final product and for proper
planning.

Motor Registration System 13
References
[1].A. de Souza and A. Cavalcanti, "Visual Language for Use Case Description", Software:
Practice and Experience, vol. 46, no. 9, pp. 1239-1261, 2015. Available:
10.1002/spe.2376.
[2].H. Gaines, Cryptanalysis. Newburyport: Dover Publications, 2014.
[3].[4]H. Balagatabi, Activity diagram testing using coloured petri net theory. Skudai, Johor:
Pusat Pengurusan Penyelidikan, Universiti Teknologi Malaysia, 2009.
[4].M. Gousset, B. Keller and M. Woodward, Professional application lifecycle management
with Visual Studio 2012. Hoboken, N.J.: Wiley, 2012.
[5].R. Tinder, Asynchronous sequential machine design and analysis. [San Rafael, Calif.]:
Morgan & Claypool Publishers, 2009.
[6].E. Schwartz, Axure RP 6 prototyping essentials. Birmingham: Packt Publishing, 2012.
[7].R. Dudley and N. Duchene, Microsoft Azure. Birmingham: Packt Pub., 2010.
[8].D. Garber, J. Malik, A. Fazio and P. Monterde, Windows Azure hybrid cloud.
Indianapolis, Ind.: John Wiley & Sons, 2013.
.