Systems Analysis Activities

CIS 281
Jennifer Pierce
Systems Analysis Activities
1. Gather Detailed Information
2. Define Requirements
3. Prioritize Requirements
4. Develop User-Interface Dialogs
5. Evaluate Requirements with Users

1. Gather Detailed Information
Your job as an analyst is to learn EVERYTHING
there is to know about the system!
This is accomplished by -
Conducting interviews and surveys with end users
Studying the existing system processes and documentation
Understanding how the system interfaces with other
internal and external systems
Researching how vendors and other businesses have
implemented a similar solution
Conducting Interviews
The end user is an important source of information on the
current system
Determine which stakeholders should be involved
Meet with small groups for fact-finding
Meet with larger groups to get feedback and develop new ideas
Prepare questions that ask
What? What if? Where? How?
Use Open-Ended questions to find out more information
Use Closed-Ended questions for facts

Understand end user activities and work flow
Watch the end user at work with the current system
Document current business processes, inputs and outputs
Determine what information is required for each process
Study the existing system, processes, and
documentation
An in-depth understanding is crucial
Review current processes and documentation with the end users
Avoid introducing old issues and unnecessary processes into the
new system
Understand the system interfaces
Interfaces with systems inside of the organization
Interfaces with systems outside of the organization
Research similar solutions implemented by other
businesses or vendors
Vendor solutions may incur less risk and be more cost effective
Other organizations may have already implemented a similar
solution
Research vendor solutions thoroughly to make sure they meet
all the system requirements
2. Define Requirements
Use the information you learned about the
system to define the requirements
2. Define Requirements
Document current process using workflow and activity diagrams
Requirement Models can be used to identify, build, and refine requirements
Activity Diagrams indicate the steps in the process requiring decisions,
parallel paths, and loops
Functional Requirements:
Determine functions and processes
performed by the system
Non-Functional Requirements:
Determine interface format requirements
from the user
3. Prioritize Requirements
Determine the most important
parts of the system
3. Prioritize Requirements
Identify crucial functions versus functions that the users would like to have
Prioritizing helps prevent scope creep
Priorities help determine which functions are implemented with each
project iteration
High priority functions are implemented
in the first iteration of the project
Lower priority functions are introduced in
later iterations
4. Develop User Interface Dialogs
Allow the user to provide input on
the new system
4. Develop User Interface Dialogs
Use abstract models, storyboards, and
application prototypes to allow the
end user to see the new system and
how it functions
Prototype interfaces may be user later on
as part of the new system
5. Evaluate Requirements with Users
Continue to meet with end user to
evaluate system models and prototypes
5. Evaluate Requirements with User
End users will continue their work while
analysts build models and prototypes
Analysts will return to the end user with
current models and prototypes to confirm
requirements are still being met
The process repeats until models are
complete and meet the requirements