System Analysis and Design

This document provides an overview of system analysis and design for an online solar power system for Bob Sparks. It includes tasks such as requirements elicitation, use case diagram, domain class diagram, activity diagram, and system sequence diagram.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design for Online SolarPower
System for Bob Sparks
Name of the Student
Name of the University
Author’s note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Task 1. Requirements Elicitations:..................................................................................................2
Task 2. Use Case Diagram:.............................................................................................................4
Task 3. Domain Class Diagram:......................................................................................................5
Task 4. Activity Diagram:...............................................................................................................6
Task 5. System Sequence Diagram:................................................................................................7
Bibliography:...................................................................................................................................9

2SYSTEM ANALYSIS AND DESIGN
Task 1. Requirements Elicitations:
Interview: Interview information gathering technique can be referred to as the formal
meeting that is conducted face-to-face between the interviewee and interviewer. The interviewee
is the staff or any other type of user of the system and the interviewer is the analyst. The
interview is considered as the primary method of information collection. The interview should be
conducted by an expert analyst otherwise the collected data will not be effective for project
development (Granhag et al. 2015). The interview is done on a specific place such as project
team working area or office premise. The time of conducting the interview is also predefined.
The analyst create a set of questions that are asked to the interviewer but the conversation is not
limited to those questions.
The advantages of interview are getting better insight user perspective, arranging session
easily with a person and providing more value to a stakeholder. The interview is done face-to-
face with the participant. This allows the analyst to freely communicate with the participant. The
analyst can ask various questions that are associated with the main question analyst had prepared
before interview. In a one to one interview, the participant feels more valuable as everything
he/she says is considered significant data.
The disadvantages of interview are high time consumption and missing out ideas of
various stakeholders. The interview process is very time consuming and it focuses only one or
two people of a single stakeholder category. The quality of information may be high but the
amount is very low. Therefore, it becomes of the most costly information gathering technique of
all.

3SYSTEM ANALYSIS AND DESIGN
Questionnaire: The questionnaire is the method that allows the analysts to understand the
beliefs, attitudes, characteristics, and behavior of several key stakeholders of the proposed
system. The questionnaire is done by creating a set of questions for individual user category and
collecting the submitted answers form the participants (Yousuf and Asger 2015). The
questionnaire is done using email, google forms or spreadsheet. The participants submit their
response within provided time. A questionnaire can consist of subjective, option selection or
both type of questions.
The advantages of questionnaire are quick completion, collecting data from huge amount
of participants and easy analysis of data. As lot of participants of different stakeholder categories
can submit their questionnaire forms simultaneously independent of where they are. The time is
required to develop the questions and submitting the form. The data collected from questionnaire
are in organized format. If the analyst knows which tool to use, it becomes very easy for analysis
for data evaluation. The analyst enter the collected data in the tool and finds the required output.
The disadvantages of questionnaire are low quality of data and no way confirm the
collected data is valid or not. Questionnaire are done anonymously. The reason is hiding the
identity of the participant. It is for allowing the participant share all the data freely without
thinking about consequences.
Comparison: Interview technique allows the analyst collected much more data than
intended. If several persons are considered in a group meeting then clash of available time is
inevitable. However, as the interview is done with one person only, there is no issues regarding
clash of time. Interview method is better than reviewing input, output and documents because,
interview method is designed to collect new perspective to build the system which is not possible
using reviewing input, output and documents. Researching vendor solution on the other hand

4SYSTEM ANALYSIS AND DESIGN
provides much more rich solution than interview. Only problem with .researching vendor
solution is compatibility. Observation and documentation of business procedure, on the other
hand, works with authentic data in comparison with the questionnaire process. The questionnaire
takes a lot less time than collecting active user comments and suggestions.
Task 2. Use Case Diagram:
Figure 1: Use Case Diagram of Online SolarPower System for Bob Sparks

5SYSTEM ANALYSIS AND DESIGN
(Source: Created by Author)
The use case diagram has three actors and nine use cases. Each of the user case is
associated with at least one actor. During the use case design, it has been assumed that the staff
and customer has different consultation forms. That is why two individual use cases has been
provided to customer and staff actor. It is also designed that bob will not do any general work.
All the general work will be done by the staff. Bob will do general work in special case that are
considered exception. Bib will access the reports from the system. No other work done by bob
will be recorded into the system.

6SYSTEM ANALYSIS AND DESIGN
Task 3. Domain Class Diagram:
Figure 2: Domain Model Class Diagram of Online SolarPower System for Bob Sparks
(Source: Created by Author)
Class diagram has nine classes. Each classes has different attributes. The customer class
two subclasses to show a register customer and potential customer. It is assumed that to submit a
consultation form, the customer does not need to register into the system. However, to buy a
system the customer be registered. The payment cab be done using visa card or master card. As
there is not difference in data type for either of the cards each sub class will have no attribute.

7SYSTEM ANALYSIS AND DESIGN
Task 4. Activity Diagram:
Figure 3: Activity Diagram of Online SolarPower System for Bob Sparks
(Source: Created by Author)
In order to develop the activity diagram, the straight process of purchase has been
selected. Here the staff has been omitted. The system represents the staff and system both.

8SYSTEM ANALYSIS AND DESIGN
Task 5. System Sequence Diagram:
Figure 4: Sequence Diagram of Online SolarPower System for Bob Sparks
(Source: Created by Author)
The sequence diagram shows the purchase of the system. The sequence diagram has been
created based on the classes customer, system and payment.

9SYSTEM ANALYSIS AND DESIGN
Bibliography:
Granhag, P.A., Oleszkiewicz, S., Strömwall, L.A. and Kleinman, S.M., 2015. Eliciting
intelligence with the Scharff technique: Interviewing more and less cooperative and capable
sources. Psychology, Public Policy, and Law, 21(1), p.100.
Yousuf, M. and Asger, M., 2015. Comparison of various requirements elicitation
techniques. International Journal of Computer Applications, 116(4).