System Analysis and Design and Implementation at Sunshine Motors

This report provides a comprehensive analysis and design of a new system for Sunshine Motors, transitioning from a manual to a digital system. It identifies key stakeholders, recommends a system acquisition strategy using a weighted alternative matrix, and addresses economic and organizational issues. The report proposes a client-server based architectural design to integrate customer data and facilitate data sharing across departments. It also details the user interface design, including structure diagrams, interface flows, wireframes, and program specifications. The new system aims to improve client information management, vehicle details, service history, and mechanic records. The report concludes with references to relevant literature on system analysis, design, and implementation.

Running head: SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
System Analysis and Design – Sunshine Motors
Name of the Student
Name of the University
Author Note

1SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
Stakeholders
In an organization, the individual person or an entire group consisting of different
individuals are collectively known as the stakeholders. The stakeholders within an organization
are responsible for a system within the organization, the implementation of the system and the
developments required regarding the system (Alles et al. 2018). Every stakeholder has to have
active cooperation within the organization to discuss about the introduction of new systems
associated with the organization in a different and unique way. The implementation on the
Sunshine Motors also has several stakeholders involved and they can be listed as below in
accordance of the project:
 Developers
 Project Managers
 Managers of Sunshine Motors
 Customers
Recommended Strategy for System Acquisition
Acquisition strategy can be regarded as an integral part of the acquisition planning
activities consisting of development behind a plan with comprehensive and integrated thinking.
This strategy is required to meet program objectives as well as identify and manage program
risks with the implementation of description of the business and the technical and support
strategies in the business organization (Diedrich and Guzman 2015). This strategy helps a
business organization to carry out their operations within a dynamic business environment with
the assistance it provides to the development process. The evolution of acquisition strategy had
always focused on making the existing business processes to propagate at a much smoother

2SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
acceleration for an organization (Veryard 2014). This is done to make sure that the utilization of
this strategy would attract the customers more and increase the organization’s sales structure. For
the case of Sunshine Motors, the organization is looking forward to change the entire business
process from a traditional manual based system to an entirely new traditional system. The new
software system would enable the organization to keep records of the information about clients,
details of the vehicles used and history of service details. The system is also expected to hold the
records of the mechanics that the company employs.
System Acquisition Weighted Alternative Matrix
Evolution
criteria Relative
importance
(weight)
Alternative 1: Score
(1-5) Alternative 2, Web shop Score (1-5)
Technical issues:
Development
of the
required in-
house skills
10
Progressive in J
Query, Java
script, HTML 2
Java and c language has
been used, a level of
knowledge is required in
both Java and c
Language
2
Insertion of
the previously
existing data
within the new
system
25
Inserting data
into system
manually by
various
departments
5 Delivering existing data
to the web designer 3
Maintaining the new operating system
This technology would be managed and maintained by the IT professionals and the
existing employees who would be handling the operations in the organization.
The services would be provided by the retailers.

3SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
Issues with the Economic Factors
Cost for Setup
The required resources that would be needed for the project are available and some of
them can also be hired (Valacich and Schneider 2015). The hired resources would indeed affect
the budget allocated for the project from the side of the organization.
The entire cost for the project as a whole needs to be decided before the project
implementation starts. The budget also needs to be verified with the exterior companies.
Issues with the organization
Interface customization
The association of the traditional system suitable to the implemented system
Relevant idea about the webpage and flexible design
Introduction of system to staff
After the new system is implemented in the business process and introduced within the
system, the employees are expected to be flexible enough to perform the mandatory work
required in the project (Laudon and Laudon 2015).
The timeline of the project would be pre defined and made definite for the employees for
their deliverables to make sure that the requirements for the projects would be delivered on time
by the staff.

4SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
Meeting of business requirements
It was found that some of the business requirements have already met because they were
available, and on the other hand some of them needed to be hired (Pearlson, Saunders and
Galletta 2016).
The timeline required for the fulfilment of the business requirements are made flexible
enough to make proposed workflow according to the plan.
Architectural Design
As per the research done on the most suitable architectural design to implement the new
system for Sunshine Motors, it is identified that client-server based architectural design would be
best suitable (Galliers and Leidner 2014). The reasons why this architectural design would be the
most appropriate for the purpose can be described as below:
 The customer data needed to be included within the database systems are found to
be related with the data of each customer. The details about each customer would
be located within a central database and would be accessible from all the various
platforms available.
 The proposed system has the capability of being integrated easily with the other
systems that have already existed within the organization about the departments
of accounting and marketing following it s architectural design and framework
(Apel et al. 2016).
 The data and information that has been stored within the main server of Sunshine
Motors must be accessible from all the departments in the organization. The
architectural design as per requirements is able to make the process for sharing of

5SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
data much easier (Brisaboa et al. 2015). The requirements that are needed for the
architectural design are as listed as below:
Design for the User Interface
The User Interface and its design are entirely based on the requirements of a user based
on the things he or she might need to do with the system. Therefore, the design for the User
Interface depends mostly upon the necessary elements required to fulfil the needs of a user
depending on the four elements of System UI design, namely, accessibility, understanding,
simplification of actions and documentation (Fuggetta and Di Nitto 2014). Below would be the
Structure Diagram for the interface and the flow of interface along with the wireframe:
Specifications for the Program
Form 1
Program specification form: This would be the specification of the program for the system of
Sunshine Motors.

6SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
References
Alles, M., Brennan, G., Kogan, A. and Vasarhelyi, M.A., 2018. Continuous monitoring of
business process controls: A pilot implementation of a continuous auditing system at Siemens.
In Continuous Auditing: Theory and Application (pp. 219-246). Emerald Publishing Limited.
Apel, S., Batory, D., Kästner, C. and Saake, G., 2016. Feature-oriented software product lines.
Springer-Verlag Berlin An.
Brisaboa, N.R., Cortiñas, A., Luaces, M.R. and Pol’la, M., 2015. A reusable software
architecture for geographic information systems based on software product line engineering.
In Model and Data Engineering (pp. 320-331). Springer, Cham.
Diedrich, A. and Guzman, G., 2015. From implementation to appropriation: understanding
knowledge management system development and introduction as a process of
translation. Journal of Knowledge Management, 19(6), pp.1273-1294.
Fuggetta, A. and Di Nitto, E., 2014, May. Software process. In Proceedings of the on Future of
Software Engineering (pp. 1-12). ACM.
Galliers, R.D. and Leidner, D.E., 2014. Strategic information management: challenges and
strategies in managing information systems. Routledge.
Laudon, K.C. and Laudon, J.P., 2015. Management information systems (Vol. 8). Prentice Hall.
Pearlson, K.E., Saunders, C.S. and Galletta, D.F., 2016. Managing and Using Information
Systems, Binder Ready Version: A Strategic Approach. John Wiley & Sons.
Valacich, J. and Schneider, C., 2015. Information Systems Today: Managing in a Digital World
Plus MyMISLab with Pearson eText--Access Card Package. Prentice Hall Press.

7SYSTEM ANALYSIS AND DESIGN – SUNSHINE MOTORS
Veryard, R., 2014. The economics of Information Systems and software. Butterworth-
Heinemann.