Systems analysis

activities
Presentation created by: Michael Glispie

Gather Detailed Information

This is the first and most important step because this is
where the analyst gets the needed information to
continue on in the project.

An analyst can gain information by interviewing the

employees or by simply watching the employees work.

Information Gathering Techniques

The analyst can Interview users and stakeholders,
distribute and collect questionnaires, observe business
procedures, and collect active user comments.
Interviewing the stakeholders is very important because
it will give the analyst a better insight of what the
company needs the system to do, business processes,
and the business procedures of the company.

Define Requirements
The analysts uses all the information he has gathered
and figures out the functional requirements.
Additionally the analyst needs to define the
requirements for reliability, security, and any other
nonfunctional requirements.
The analyst will create models to record the
requirements which will be reviewed with the users, and
others and will be refined to reflect updated information

Prioritize requirements
Requirements prioritization is where the analyst will put
the requirements suggested by the users in the order of
most crucial to least crucial for the system.

This is where insight about what the organization will

better prepare an analyst for prioritizing the
requirements for the system.

Prioritize Requirements
It is important to prioritize because resources are
always limited in what can be done to the system.
Additionally not all the requirements stated by the
users will be needed.
This stage helps in determining number, composition,
and iteration order.

Develop User-Interface Dialogs

This is important because the new system might do
something that the previous version of the system did
not do.
This can make users uncertain about system
requirements and the use of models such as use case,
interaction diagrams, and activity diagrams can be
difficult to interpret.

Develop User-Interface Dialogs

A prototype on the actual input/output device that the
user will be using might be better suited to explain the
new system to users.
The prototype interface can also be used as a staring
point for developing a part of the system, and can be
expanded on to become a fully functional part of the
system.

Evaluate Requirements with Users

The analyst might have to incorporate new input and refine the
models after returning to the user for any additional input or
confirmation.
The analyst might need to produce prototypes of the user
interfaces and other system parts to prove that the chosen
technologies will do what they are suppose to do
Prototypes may also be needed to show the user what the
system can do with new technologies implicated within the
system to help with identifying what they require for the system