Chapter Three
Requirement Identification and
Validation
Learning Objectives
Describe the difference between functional and
nonfunctional system requirements
Identify and understand the different types of
users who will be involved in investigating system
requirements
Learning Objectives (continued)
Describe the kind of information that is required
to develop system requirements
Determine system requirements through review
of documentation, interviews, observation,
prototypes, questionnaires, vendor research, and
joint application design sessions
Discuss the need for validation of system
requirements to ensure accuracy and
completeness and the use of a structured
walkthrough
what are requirements?
Requirements are statements that define what a
system must be able to do (functional) and what
qualities it must have (non-functional) to satisfy
stakeholder needs.
It is a vital feature of a new system which may include
processing or capturing of data, controlling the
activities of business, producing information and
supporting the management.
System Requirements
New system capabilities and constraints
Functional requirements
Activities system must perform (use cases)
Based on procedures and business functions
Documented in analysis models
Nonfunctional requirements
Technical environment or performance objectives
Usability, reliability, and security requirements
Stakeholders—The Source of
System Requirements
People with interest in successful system
implementation
Three primary groups of stakeholders
Users (use system)
Clients (pay for and own system)
Technical staff (ensure system operation)
Every type of stakeholder is identified by analyst
Stakeholders Interested
in New System Development (Figure 4-4)
More On Users as Stakeholders
Horizontal user roles – information flow across
departments
Vertical user roles – information needs of clerical
staff, middle management, and senior executives
Business users perform day-to-day operations
Information users need current information
Management users need summary information
Executive users need strategic information
External users may have access to system
Techniques for Information Gathering
Analysis phase done to understand business
functions and develop system requirements
Original structured approach
Create model of existing system
Derive requirements from existing system model
Current approach
Identify logical requirements for new system
Balance the review of current business functions
with new system requirements
Relationship Between Information
Gathering and Model Building (Figure 4-6)
Themes for Information-Gathering
Questions (Figure 4-7)
Fact-Finding Methods
Review existing reports, forms, and procedure
descriptions
Interview and discuss processes with users
Observe and document business processes
Build prototypes
Distribute and collect questionnaires
Conduct joint application design (JAD) sessions
Research vendor solutions
Review Existing Reports, Forms,
and Procedure Descriptions
Source: External industry-wide professional
organizations and trade publications
Source: Existing business documents and
procedure descriptions within organization
Identify business rules, discrepancies, and
redundancies
Be cautious of outdated material
Obtain preliminary understanding of processes
Use as guidelines/visual cues to guide interviews
Sample Order Form for RMO (Figure 4-8)
Conduct Interviews and Discussions with Users
Effective way to understand business functions
and rules
Time consuming and resource expensive
May require multiple sessions to
Meet all users
Understand all processing requirements
Can meet with individuals or groups of users
List of detailed questions prepared
Sample Checklist to Prepare for User Interviews
(Figure 4-9)
A Sample Open-Items List (Figure 4-11)
Observe and Document Business Processes
Varies from office walkthroughs to performing
actual tasks
Not necessary to observe all processes at same
level of detail
May make users nervous, so use common sense
Can document workflows with UML activity
diagrams
Validating the Requirements
Make sure gathered information is correct
Structured walkthrough
Effective means of implementing quality control
early in project
Verify and validate system requirements
Review of findings from investigation and of
models based on findings
Project manager responsible for system quality
Systems analyst, project manager are partners
Summary (continued)
Gathering system requirements
Functional and nonfunctional
Work with various stakeholders (users, clients,
technical staff)
What kind of information do I need?
What are the business processes and operations?
How are the business processes performed?
What are the information requirements?
Summary (continued)
Primary information-gathering techniques
Review existing reports, forms, and procedure
descriptions
Conduct interviews and discussions with users
Observe and document business processes