Systems Analysis and Design
System Analysis
Requirements Modeling
Agenda






Interesting News and Articles
Systems Analysis Phase Overview
Team Oriented Methods and
Techniques
System Requirements Checklist
Fact Finding Methods
Class Exercise
Systems Analysis



Understand the proposed project
Ensure that the project will support
business requirements
Build a solid foundation for system
development
Systems Analysis Skills

Analytical skills


Identify problem, evaluate the key
elements, and develop a useful solution
Interpersonal skills

Work with, balance conflicting needs of
users, and communicate effectively
Team Oriented Methods and Techniques


Joint Application Development (JAD)
Rapid Application Development (RAD)
Joint Application Development


JAD is a team-oriented technique for
fact-finding and requirements modeling
In other words, JAD is a popular factfinding technique that brings users into
the development process as active
participants
Joint Application Development


A JAD team may include users,
managers, IT professionals who works
together to identify and document
requirements for a new system
The objective is to analyze the existing
system, work on potential solutions,
and agree on requirements for the new
system.
Joint Application Development

Advantages




More accurate statement of system requirements
Better understanding of common goals
Stronger commitment to the success of the new
system
Disadvantages


More expensive
Can be cumbersome if the group is too large
Rapid Application Development



RAD is a team-based technique that
speeds up information systems
developments.
Like JAD, RAD uses a group approach,
but goes much further.
RAD resembles a condensed version of
the entire SDLC, with users involved
every step of the way.
RAD Phases and Activities

Requirement planning


User Design


Interact with users, build models and prototypes, and
conduct intensive JAD-type sessions
Construction


Users, managers, and IT staffs agree upon business needs,
project scope and system requirements
Program and application development, coding, integration
and system testing
Cutover

Data conversion, full scale testing, system changeover, user
training
Rapid Application Development

Advantages


The system can be developed more quickly
with significant cost savings
Disadvantages


RAD does not emphasize the company’s
strategic business needs
Risks in term of long-term objective,
quality, consistency, and efficiency
System Requirements

A system requirement is a characteristic or
feature that must be included in an
information system to satisfy business
requirements and be acceptable to users.





Outputs
Inputs
Processes
Performance
Controls
Outputs Requirements Samples



The inventory must produce a daily
report
The purchasing system must provide
supplier with up-to-date specifications
The Web site must report online volume
statistics
Inputs Requirements Samples


Each input form must include date,
time, product code, customer number,
and quantity
Manufacturing employees must swipe
their ID cards
Processes Requirements Samples


The students records system must allow
record access by either students name
or number
The video rental system must not
execute new rental transaction for
customers who have overdue tapes
Performance Requirements
Samples



The system must support 25 users
online simultaneously
Response must not exceed four seconds
The system must be operational seven
days a week, 365 days a years
Control Requirements Samples



The system must provide log-on
security
An employee record must be updated
by a member of human resource
department
The system must maintain separate
levels of security for users and
administrators
Scalability

A system’s ability to handle increased
business volume and transactions in the
future.
Fact-Finding

Answer Who, What, When, How and
Why?





Interviews
Document Review
Observation
Questionnaires and Surveys
Research
The Need for Recording the
Facts




Record information as soon as you
obtain it
Use the simplest record method
possible
Record your findings in such a way that
they can be understood by someone
else
Organize your documentation
Question?