Sunshine Motors Systems Analysis & Design

This assignment delves into the systems analysis and design of Sunshine Motors, a hypothetical automotive service provider. It outlines functional requirements such as car maintenance, inventory management, and client relationship management. The document also explores non-functional requirements including performance, security, and usability. Use case diagrams illustrate interactions between users and the system, while references to relevant literature enhance the technical depth of the analysis.

Running head: BCO2041 SYSTEMS ANALYSIS AND DESIGN
BCO2041 Systems Analysis and Design
Name of the Student
Name of the University
Authors note

1BCO2041 SYSTEMS ANALYSIS AND DESIGN
Part 7
Functional requirement
i. User authentication using the generated user ID and Password.
ii. The system will provide easy interface to record the vehicle details, client details,
as well as service history details for the vehicles for easy and future reference.
iii. The developed system must be able to generate the economic reports for Sunshine
motors so that the top level management can easily find out where to invest to
improve business.
iv. The admin of the system will be able to manage the roster of the mechanics who
will be available for service at a given day while ensuring the enough workforce.
v. The system must be able to assign and track the client orders, mechanics working
on them, work bay used for the orders, progress at a given time for a servicing
order, time for completion of the order.
vi. As the organization loans cars to their clients thus the system needs have a
module that will keep track of the cars which are available for the clients and
which are provided to the clients.
vii. The system will be able to generate notification for the parts in the inventory that
are under a certain reordering level (This reordering level can be set by the users).
viii. The system has to be capable of calculation of the total amount (that includes
labour cost for the mechanics, work items that are used by the mechanics during
the completion of the records)
ix. The system must support the integration with the other third party applications
(Such as MS Excel and MYOB) and with any other existing information system.

2BCO2041 SYSTEMS ANALYSIS AND DESIGN
Non-functional requirement
Following are the non-functional requirements for the proposed system of Sunshine
Motors.
Availability: As the system will be storing and processing the operational data for
different operations of the organization thus it is important that the system must be available
while having a very low downtime.
Ease of Use: The users of the system are IT illiterate, thus it is important that the
system should have an easy to use interface.
Integrity, reliability, Confidentiality of the stored data: The system will be
storing the financial data of the organization, client’s, mechanic’s personal information thus
the system must be able to secure the integrity, reliability, and confidentiality of the data.
Part 8
8.1 Event list
Create Roster of mechanics ensuring that minimum five mechanics are available
every day.
Creating a work order
Picking a work order by a mechanic
Use a work item for a work order to service a car.
Log the use of the work item and adjust the inventory database.
If a work item is not available, then inform service manager to get the item urgently.
Assign mechanic on other work orders.

3BCO2041 SYSTEMS ANALYSIS AND DESIGN
Completing a work order.
Mark work order as complete order.
Notify the client through mail about the completion of their orders.
Payment by client.
Ordering required parts required for servicing of the cars and maintain the stock level
of the parts.
Flagging client payments as partial or completed for future reference.
8.2 Use cases
Creating roster
The mechanics and the front office staff of Sunshine Motors will enter their
working days on the terminals available at their work space. The successful completion of
this use case generates the roster that will ensure five mechanics on a given day with an
additional mechanic who will be available for any emergency and extra work demand.
Record details of the client, vehicles, service history of the car
This use case includes the activities such as recording of the clients of sunshine
motors, their vehicle details as well as their service history so that they can be notified for
different offers and completion of their work orders.
Creating and picking up work order
After the client drops his/her car at the counter by signing and completing a work
order, the service writer at the desk creates the work order and when a mechanic is free then
he picks the orders which are arranged according to their completion time.

4BCO2041 SYSTEMS ANALYSIS AND DESIGN
Assigning work bay
After picking a work order, the mechanic have to find free working bay so that the
mechanic can service the car on that working bay while collecting the required work items
from the inventory.
Loan cars
In case any work item is not available in the inventory, the servicing of the cars will
be delayed until the working item is available. For this time being the organization provides
car loans to the clients. In addition to that, the organization also provide car loans whenever
there are cars are available.
Manage inventory
After the work items and consumables are picked from the inventory it is important to
manage the database of the items so that the products reordering level can be maintained and
organization does not go out of the consumables and work items.
Complete work order and notify clients
When the service order for a car is completed the system will mark the work order is
complete and will notify the clients about the completion of the order while generating the
invoice calculating the prices of the work items, labour costs and other relevant costs.
Payment by the client
When the client comes to pick their car after servicing, they have to make the
payment according to the invoice. The clients can pay partial or complete at the time of
taking the car. If the payment is made partial, then the system will flag the payment as partial
and create a reminder for the financial manager till which time the complete payment will be
done.

5BCO2041 SYSTEMS ANALYSIS AND DESIGN
Generate financial report
This use case includes the generation of daily and different periodical financial
reports for the organization.

6BCO2041 SYSTEMS ANALYSIS AND DESIGN
8.3 Use case diagram for Sunshine Motors

7BCO2041 SYSTEMS ANALYSIS AND DESIGN
Bibliography
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John Wiley & Sons.
Pearlson, K. E., Saunders, C. S., & Galletta, D. F. (2016). Managing and Using Information
Systems, Binder Ready Version: A Strategic Approach. John Wiley & Sons.
Friedenthal, S., Moore, A., & Steiner, R. (2014). A practical guide to SysML: the systems
modeling language. Morgan Kaufmann.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Buede, D. M., & Miller, W. D. (2016). The engineering design of systems: models and
methods. John Wiley & Sons.