Lesson 17 Requirements Discovery

• Define system requirements and differentiate between

functional and nonfunctional requirements.
• Understand the activity of problem analysis and be able to
create an Ishikawa (fishbone) diagram to aid in problem
solving.
• Understand the concept of requirements management.
• Identify seven fact-finding techniques and characterize the
advantages and disadvantages of each.
Lesson Map
 Introduction to Requirements Discovery

Requirements discovery includes those

techniques to be used by systems analysts to identify
or extract system problems and solution requirements
from the user community.

Problem analysis is the activity of identifying the

problem, understanding the problem (including
causes and effects), and understanding any
constraints that may limit the solution.
Introduction to Requirements
Discovery
A system requirement (also called a
business requirement) is a description of the
needs and desires for an information
system. A requirement may describe
functions, features (attributes), and
constraints.
 Types of Requirements
A functional requirement is a function or
feature that must be included in an
information system in order to satisfy the
business need and be acceptable to the
users.
A nonfunctional requirement is a
description of the features, characteristics,
and attributes of the system as well as any
constraints that may limit the boundaries of
the proposed solution.
 Types of Nonfunctional Requirements
Requirement Type Explanation
Performance Performance requirements represent the performance the system is required
to exhibit to meet the needs of users.
· What is the acceptable throughput rate?
· What is the acceptable response time?
Information Informationn requirements represent the information that is pertinent to the
users in terms of content, timeliness, accuracy, and format.
· What are the necessary inputs and outputs? When must they
happen?
· What is the required data to be stored?
· How current must the information be?
· What are the interfaces to external systems?
Economy requirements represent the need for the system to reduce costs or
increase profits.
· What are the areas of the system where costs must be reduced?
· How much should costs be reduced or profits be increased?
· What are the budgetary limits?
· What is the timetable for development?
Control Control requirements represent the environment in which the system must
(and Security) operate, as well as the type and degree of security that must be provided.
· Must access to the system or information be controlled?
· What are the privacy requirements?
· Does the criticality of the data necessitate the need for special
handling (backups, offsite storage, etc.) of the data?
 Types of Nonfunctional Requirements (concluded)
Requirement Type Explanation

Efficiency Efficiency requirements represent the systems ability to produce outputs

with minimal waste.
· Are there duplicate steps in the process that must be eliminated?
· Are there ways to reduce waste in the way the system uses it
resources?
Service Service requirements represent needs in order for the system to be
reliable, flexible, and expandable.
· Who will use the system and where are they located?
· Will there be different types of users?
· What are the appropriate human factors?
· What training devices and training materials are to be included in
the system?
· What training devices and training materials are to be developed
and maintained separately from the system, such as stand- alone
computer based training (CBT) programs or databases?
· What are the reliability/availability requirements?
· How should the system be packaged and distributed?
· What documentation is required?
An Ambiguous Requirements Statement

Requirement:
Create a means to transport a single
individual from home to place of work.

Management IT User
Interpretation Interpretation Interpretation
 Results of Incorrect Requirements

• The system may cost more than projected.

• The system may be delivered later than promised.
• The system may not meet the users’ expectations and that
dissatisfaction may cause them not to use it.
• Once in production, the costs of maintaining and enhancing the
system may be excessively high.
• The system may be unreliable and prone to errors and downtime.
• The reputation of the IT staff on the team is tarnished because
any failure, regardless of who is at fault, will be perceived as a
mistake by the team.
 Relative Cost to Fix an Error
Phase in Which Found Cost Ratio

Requirements 1

Design 3-6

Coding 10

Development Testing 15-40

Acceptance Testing 30-70

Operation 40-1000
Criteria to Define System
Requirements
• Consistent
• Complete
• Feasible
• Required
• Accurate
• Traceable
• Verifiable
 The Process of Requirements
Discovery
• Problem discovery and analysis
• Requirements discovery
• Documenting and analyzing requirements
• Requirements management
 Ishikawa Diagram
The Ishikawa diagram is a graphical tool used to
identify, explore, and depict problems and the causes
and effects of those problems. It is often referred to as a
cause-and-effect diagram or a fishbone diagram.
 Requirements Discovery
Fact-finding is the formal process of using
research, interviews, questionnaires,
sampling, and other techniques to collect
information about problems, requirements,
and preferences. It is also called information
gathering.
 Seven Fact-Finding Methods
• Sampling of existing documentation, forms,
and databases.
• Research and site visits.
• Observation of the work environment.
• Questionnaires.
• Interviews.
• Prototyping.
• Joint requirements planning (JRP).
 Documenting and Analyzing Requirements

A requirements definition document should

consist of the following.
– The functions and services the system should
provide.
– Nonfunctional requirements including the system’s
features, characteristics, and attributes.
– The constraints that restrict the development of the
system or under which the system must operate.
– Information about other systems the system must
interface with.
Sample Requirements Definition Outline
Requirements Definition Report
1. Introduction
1.1 Purpose
1.2 Background
1.3 Scope
1.4 Definitions, Acronyms, and Abbreviations
1.5 References
2. General Project Description
2.1 System Objectives
3. Requirements and Constraints
3.1 Functional Requirements
3.2 Nonfunctional Requirements
4. Conclusion
4.1 Outstanding Issues
Appendix (optional)
Validating Requirements
Requirements validation is an activity that checks the
requirements definition document for accuracy,
completeness, consistency, and conformance to
standards.

Requirements Management
Requirements management is the process of
managing change to the requirements.
 Sampling

• Sampling is the process of collecting a

representative sample of documents, forms,
and records.
– Determining the sample size:
• Sample Size = 0.25 x (Certainty factor/Acceptable
error)2

– For a 90% certainty:

• Sample Size = 0.25(1.645/0.10)2 = 68
 Sampling Techniques
Randomization is a sampling technique
characterized as having no predetermined pattern
or plan for selecting sample data.

Stratification is a systematic sampling technique

that attempts to reduce the variance of the
estimates by spreading out the sampling—for
example, choosing documents or records by
formula—and by avoiding very high or low
estimates.
 Observation
Observation is a fact-finding technique wherein the
systems analyst either participates in or watches a
person perform activities to learn about the system.
Advantages?
Disadvantages?

Work sampling is a fact-finding technique that

involves a large number of observations taken at
random intervals.
 Observation Guidelines
• Determine the who, what, where, when, why, and how of the
observation.
• Obtain permission from appropriate supervisors or managers.
• Inform those who will be observed of the purpose of the
observation.
• Keep a low profile.
• Take notes during or immediately following the observation.
• Review observation notes with appropriate individuals.
• Don't interrupt the individuals at work.
• Don't focus heavily on trivial activities.
• Don't make assumptions.
Questionnaires
Questionnaires are special-purpose documents that allow the
analyst to collect information and opinions from respondents.
– Advantages?
– Disadvantages?
Types of Questionnaires
Free-format questionnaires offer the respondent greater latitude
in the answer. A question is asked, and the respondent records the answer in the
space provided after the question.
Fixed-format questionnaires contain questions that require
selection of predefined responses from individuals.
Types of Fixed-Format Questions
Multiple-choice questions
Rating questions
Ranking questions
Multiple-choice questions
Rating questions
 Questionnaire Procedure
1.Determine what facts and opinions must be
collected and from whom you should get them.
2.Based on the needed facts and opinions,
determine whether free- or fixed-format
questions will produce the best answers.
3.Write the questions.
4.Test the questions on a small sample of
respondents.
5.Duplicate and distribute the questionnaire.