ACTIVITIES OF

THE ANALYSIS
PHASE
By: Devin Sherrer

GATHER DETAILED INFORMATION

Obtain information from the users or future users through interviews

or observation

Review planning documents and policy statements

Study systems already in place (if applicable) and its documentation

Study similar problems and solutions to assist with solving the

current problem

Identify and understand all activities of existing and future users

Learn all locations the system will need to use or access

Understand how the system interacts with interfaces and other

systems

Thoroughly understand the business area (e.g. accounting) that the

system is being developed/modified for

It is extremely important to have all necessary information about a

systems needs before designing the system

DEFINE REQUIREMENTS

Use gathered information to define requirements for the new

system

Determine the functions a system must perform

Understand how to optimize the user interface experience and

make it easy to understand

Maximize system performance must be reliable, fast, and

secure

Create models of requirements to review with users, analysts,

and anyone else to be involved with using the system

Modify the models, if necessary, after reviewing with the

system users

Keep current models and constantly review with users

One must understand what the system requires to be able to

create the system and satisfy all stakeholders needs

PRIORITIZE REQUIREMENTS

Establish the most important requirements of the system

Some requirements may be desirable for users; however, they

may not be essential to the system

Must understand the organization of the system as well as what

the users need to determine what are the absolute requirements
of the system

Limited resources means do not include a portion of the system

that is not entirely necessary or essential to the system

Build in high-priority requirements first so you will have the

opportunity to refine or modify those requirements if necessary

Provide feedback to users about what requirements are necessary

and what requirements are not essential

Without prioritizing, portions of the system may be built then

deemed unnecessary which would mean time and money has
been wasted

DEVELOP USER-INTERFACE DIALOGS

Use similar interfaces of existing interfaces when replacing an old

system when possible. This helps the user more easily understand
the new interface

Automate functions that were manually performed or not performed

at all in the old system

Use models to understand when and how the system will need to
communicate with the user

Users are often more concerned with the interface than any other
part of the system

Use models or actual devices the user will use (e.g. computer) to
develop the interface itself

Make a prototype interface, a simple interface handling only a few

tasks, then develop that interface as you progress

The user interface is the place where the user will be interacting
with the system; therefore, the interface must be easily

EVALUATE REQUIREMENTS WITH

USERS

Work with users to develop the system

Provide the users with constant feedback about the system and
its requirements

Allow user to have input during the process of building the system

Refine models to incorporate any input that a user may have as

long as it is deemed essential

Inform the user about new technologies that can help the system
if applicable

Create prototypes when a paper model is inadequate to show the

user the system or when something needs to be tested with real
technology

It is very important to continue to receive user input and update

models and prototypes until the user is satisfied with the product

THE
END