Systems Analysis Assessment 2: AAA Mechanics Ltd - INFS 1024

This report presents a comprehensive Systems Analysis Assessment 2 for AAA Mechanics Ltd, addressing system requirements, use cases, and domain modeling. The analysis begins with identifying stakeholders and their goals, followed by the application of various techniques like surveys, interviews, and brainstorming to gather functional requirements. The report details primary functional and non-functional requirements, including recording client, vehicle, and employee information, and sending automated notifications. Use cases are defined for actors such as admin, employees, managers, and customers, with descriptions and a use case diagram illustrating their interactions. Domain modeling, including domain classes, attributes, and a class diagram, is used to represent the structure of the system. The report then delves into use case modeling, providing fully developed use case descriptions, activity diagrams, and system sequence diagrams. Finally, a CRUD (Create, Read, Update, Delete) analysis is conducted to verify all required use cases. This assessment provides a thorough examination of the system's design and functionality.

INFS 1024 UO Systems Analysis
Assessment 2 – Scenario 2
<Title>
<Date>
Prepared by
<Name>

Table of Contents
1. SYSTEM REQUIREMENTS................................................................................................3
Stakeholders..........................................................................................................................3
Techniques.............................................................................................................................3
Primary Functional Requirements.........................................................................................4
Non-Functional Requirements..............................................................................................4
2. USE CASES...........................................................................................................................5
Actors....................................................................................................................................5
Use Cases and Descriptions..................................................................................................5
Use Case Diagram.................................................................................................................6
3. DOMAIN MODELLING.....................................................................................................10
Domain Classes and Attributes...........................................................................................10
Domain Model Class Diagram............................................................................................10
Associations.........................................................................................................................11
4. USE CASE MODELLING..................................................................................................12
Fully Developed Use Case Description...............................................................................12
Activity Diagram.................................................................................................................13
System Sequence Diagram..................................................................................................15
CRUD Analysis...................................................................................................................17
References................................................................................................................................19

1. SYSTEM REQUIREMENTS
Stakeholders
The party which possess interest within company and can either get affected or be affected
through activities carried out by businesses is referred to as stakeholder (Alkadeem and et. al,
2019). Important stakeholders of AAA Mechanics Ltd are shown below:
Role Goal/Desire Benefits/Reason
Mechanics They will enter the details
through which all the assets can
be maintained.
By entering data it will be easy
to acknowledge their
participation within particular
project.
Front Office Staff To maintain their clients and
provide details to other
departments as per requirements.
To make sure that appropriate
billing is done by clients after
having services.
Roadway Staff To address requirements of each
client in an effective way.
Details of clients can be
maintained completely like who
comes and what they need
(Awasthi and Omrani, 2019).
Purchasing Officer Manage the inventory To ensure that there operations
are not stopped
Finance Manager To enhance profitability of AAA
Mechanics
Make sure that each department
have relent finance through
which operations of firm can be
effectively carried out.
Marketing Manager To reach out maximum number
of clients and provide them with
appropriate services.
Rationale behind this is to reach
maximum people and enhance
brand awareness.
Techniques
Surveys, interviews, prototyping and brainstorming can be carried out for collection of
functional requirements. With respect to AAA Mechanics Ltd, Interviews can be used as
it will provide details about what firm lacks and what is required by them to improvise

their functionalities (Beratan, 2019). This can be attained from point of view of their
stakeholders who work with them. Front office manager can be interviewed as they are
the one with whom clients deal directly and are rendering their services to each
department directly or indirectly. Few questions have been illustrated below which can be
asked:
1. Do you think that problems are being faced by AAA Mechanics Ltd?
2. What kinds of problems are faced and provide an in-depth insight into them?
3. Which is the immediate problem which needs a quick solution? Why do you think
so?
4. What is probable solution to deal with difficulties?
5. What sort of system you are talking about and what it is all about?
6. Do you think that new system will address all shortcomings which are being faced
by AAA Mechanics?
7. What will be benefit of recording all the information either its of clients, vehicles
and employees?
8. Will there be a centralised system through which those details can be accessed?
9. How employees will be benefited by proposed or a new system? Will needs of
each department will be addressed?
10. Do you think that through this there will be affirmative impact on their clients?
Primary Functional Requirements
Activities which must be carried performed by system denotes functional requirements.
The primary requirements with respect to AAA Mechanics Ltd system are recording
information of clients, details of vehicle along with service history (De Rooij, Mannak
and Janowicz-Panjaitan, 2019). New system is liable for handling all these functions.
Along with this, details of employees will also be stored so that when they are required
then can be accessed easily.
Non-Functional Requirements
Characteristics of system which are other than tasks which have to be carried out is
referred to as non-functional requirements. Basically, it implies needs which illustrates
peculiar criteria which can be utilised for judging system operations. With respect to
AAA Mechanics Ltd, they includes sending email to purchasing officer when threshold
value is attained as well as mail will be sent clients with respect to servicing of their

vehicles. Along with this, offers can also be interacted among their users through which
their clients can also grown.
2. USE CASES
Actors
The role which is being played by individuals or other systems which communicates with
subject is referred to as actor. With respect to AAA Mechanics Ltd, actors will be those
who have some role within system and can access it as per their requirements (Fadillah
and Fitriana, 2019). The actors are admin, employees, manager and customers.
Use Cases and Descriptions
The methodology which is being utilised for carrying out system analysis for
identification, clarification and organisation of requirements is referred to as use case.
This involves set of probable sequences for having communication among users and
systems within peculiar environment that is associated with its goal. The use case for
AAA Mechanics Ltd are illustrated below along with their description:
Use Case Description
Admin  They are liable for managing entire
system and ensure that it is working as
per the required standards.
 They will ensure that they have
appropriate system guidance through
which each employee and multiple
clients can have access to it as per their
requirements (Falcidieno, Ruggiero and
Torti, 2019).
Employees  They can login within the system and
enter all their details.
 The major benefits they can have
through this will be that there working
hours can be monitored.
Managers  Managers of AAA Mechanics will be
liable for ensuring that they have

sufficient employees within working
premises.
 They can add details about new vehicles
which are being within the firm
(Falcidieno, Ruggiero and Torti, 2019).
Customers  Customers can register within the
system and login with their details.
 They can mark feedbacks and can check
out what is being offered by AAA
Mechanics.
Use Case Diagram
Admin: They are liable for verifying details entered by employees and their customer and
ensure that they have access to system when they enter details next time. Both the entities
will be provided with unique username and password (Genta and Morello, 2019. They
test system to make sure that it is working as per required standards.

Employees: They can register within the system and enter details as per what is being asked.
Then system will generate username and password which is available. Through this they can
enter all assets and documents like their license, qualification and other assets which they
have to enter (Mullarkey and Hevner, 2019). In addition to this, time sheet information can
also be added and supervisor details so that there want be any problem with extra working
hours or salary which is being issued to employees of AAA Mechanics Ltd.

Managers: They can register into system and enter details of new vehicles they have. In
addition to this, managers will also send mails to customers to whom they have sold
vehicles with respect to their servicing. Furthermore, they are also responsible to
authenticate each user so that they do not waste their time with fake customers (Oshana
and Kraeling, 2019). Managers will also manage entire system so that their probable
clients do not have any problem while trying to login within their system. Furthermore,
they can also have details have loan cars and maintain details related with those.

Customers: They are the one for whose easiness system is being developed, they can
register and login into system. As per their requirements they can check out for the
vehicles they need and in case if they face any trouble or have any kind of queries then
they can ask for the same on the system. Along with this, they can give feedback as per
their experience (Haberfellner and et. al, 2019). By registering into the system they can
have regular updates of offers provided by them and can have a reminder about servicing
which their vehicle needs.

3. DOMAIN MODELLING
Domain Classes and Attributes
The group of devices and computers on a network which are being administered like a
unit with common procedures and rules is referred to as domain. Objects which illustrate
domain entities are referred to as domain objects or entities and the classes which they
instantiates are defined as domain classes (Wang, Zhao and Qiao, 2019). With respect to
AAA Mechanics, the domain classes includes login, validate, user or customer
management, admin option and employee management.
Domain Model Class Diagram
The login option illustrates the section where employees as well as their clients can
register as well as login as per their requirements. The error message will be displayed if
userid and password do not match. This implies that all details which are being entered
will be validated.
Furthermore, admin have different options which involves employees their details,
categories of vehicles they have and their management along with this they are also liable

for managing their users. Within the users management, they can be added up, viewed
and removed (Alkadeem and et. al, 2019). Same goes with the employee management.
The primary key and relationship is clearly illustrated within the diagram. AdminID,
empID, uno and vehID illustrates the primary key that are liable for depicting uniquely
identify each domain class or an entity.
Associations
The relationship among different classes is referred to as association. The domain classes
diagram illustrates the relation shared among different classes with respect to AAA
Mechanics Ltd. They are illustrated below:
 Admin have one to many relationships with employees as they have the access to
the employees and can make modifications accordingly.
 With respect to user management again one to many relationship is there as
multiple customers are being managed by them but the latter do not possess any
ability to do anything (Awasthi and Omrani, 2019).
 Admin has association with vehicles and they further divide them on the basis of
category as well as verify their entire details by which an appropriate interaction
can be carried out with their customers.

4. USE CASE MODELLING
Fully Developed Use Case Description
This section illustrates the use cases description for book car service, this is shown below:
Admin: They can login within system, manage booking as well as make enquiries related
with this. Along with this, they will also add car details and have feedback from their
probable customers. After this, admin can logout from the system.

User: The customers or users can register into Book Car service system and login as per their
requirements. They can search for car, make reservations for same and can give feedback in
that context. Along with this, user can have entire details about bookings they have made. In
case they forget password then same can be received through email. Through user can have
access to what they are looking forward for.
Activity Diagram
The enhanced version of flow chart that are used for modelling flow from one activity to
another is referred to as activity diagram. It is utilised for illustration of dynamic aspects
associated with system (Beratan, 2019).

Admin: The figure shown below clearly illustrates the activities tahta re being carried out by
admin of book car service system and it illustrates flow of information.

User: As per requirements of user, after making a login into system they can carry out their
operations as shown below within activity diagram.
System Sequence Diagram
The object interactions which are being arranged with respect to time are referred to as
system sequence diagram. Within this, visually communication takes place by making use
of vertical axis of diagram for representing time along with what messages are being sent
and when it is being done.

Admin: The way in which admin will carry out their operations has been illustrated by the
sequence diagram illustrated below. In this they can enter all the details of vehicle along with
its rent, analyse the feedback given by users and respond to them accordingly (Fadillah and
Fitriana, 2019).

User: They can register, search for car, have its details, carry out booking, check information
about booked car and have an acknowledgement for the same.
CRUD Analysis
The verification of all required use cases which have been identified for maintaining data
that is being illustrated by domain model class diagram refers to CRUD. It stands for
Create, read, update and delete (De Rooij, Mannak and Janowicz-Panjaitan, 2019).
Admin
Domain Class/ Data Entity CRUD Verified Use Case
Admin Create Verify user
Report/ Read Look up for the users
Furnish details to users
Update Process the booking

Update account of users
Delete Update user account for
archive
User
Domain Class/ Data Entity CRUD Verified Use Case
User Create Register into Book car
service
Report/ Read Look up for services
Check details of vehicles
Update Process the booking
Carry out booking
Delete Update user account
CRUD table illustrating Use cases along with corresponding domain classes
Use Case vs. Domain Class Admin User
Create user C C
Look up for the
users/services
C R (read)
Furnish details R (report) R (read)
Process the booking C R (read)
Update user account UD (Archive) UD (Archive)

References
Books & Journals
Alkadeem, R. and et. al, 2019. Project behaviour in different types of project management
organisations: a system dynamics approach. International Journal of Process
Management and Benchmarking, 9(4), pp.499-521.
Awasthi, A. and Omrani, H., 2019. A goal-oriented approach based on fuzzy axiomatic
design for sustainable mobility project selection. International Journal of Systems
Science: Operations & Logistics, 6(1), pp.86-98.
Beratan, K.K., 2019. Improving problem definition and project planning in complex natural
resource management problem situations using knowledge brokers and visual design
principles. Ecology and Society, 24(2).
De Rooij, M.M., Mannak, R.S. and Janowicz-Panjaitan, M., 2019. Dataset on performance
management systems' design in project-based organizations. Data in brief, 25, p.104185.
Fadillah, A.P. and Fitriana, D., 2019, November. Design of Project Data Management
Information System. In IOP Conference Series: Materials Science and
Engineering (Vol. 662, No. 2, p. 022014). IOP Publishing.
Falcidieno, M.L., Ruggiero, M.E. and Torti, R., 2019. Design and project for special naval
vessels: new developments and evolutions related to representation. International
Journal on Interactive Design and Manufacturing (IJIDeM), 13(1), pp.287-294.
Falcidieno, M.L., Ruggiero, M.E. and Torti, R., 2019. Design and project for special naval
vessels: new developments and evolutions related to representation. International
Journal on Interactive Design and Manufacturing (IJIDeM), 13(1), pp.287-294.
Genta, G. and Morello, L., 2019. The automotive chassis: volume 2: system design. Springer
Nature.
Haberfellner, R. and et. al, 2019. Systems engineering. Springer International Publishing.
Mullarkey, M.T. and Hevner, A.R., 2019. An elaborated action design research process
model. European Journal of Information Systems, 28(1), pp.6-20.
Oshana, R. and Kraeling, M. eds., 2019. Software engineering for embedded systems:
Methods, practical techniques, and applications. Newnes.
Wang, S., Zhao, Z. and Qiao, Y., 2019, February. Application of Genetic Algorithms in
Project Declaration. In Journal of Physics: Conference Series (Vol. 1168, No. 5, p.
052006). IOP Publishing.
<2000>