ISS 2113 SOFTWARE REQUIREMENT

CHAPTER 1
SOFTWARE REQUIREMENT
FUNDAMENTALS

MDM. MARINA BINTI HASSAN, CTFL

Requirements Determination
Objectives
Understand how to create a requirements definition.
Become familiar with requirements analysis techniques.
Understand when to use each requirements analysis
technique.
Understand how to gather requirements using interviews,
JAD sessions, questionnaires, document analysis, and
observation.
Understand when to use each requirements-gathering
technique.
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

What is a Requirement
A requirement is a statement of what
the system must do or
characteristics it must have
written from businessperson perspective (what of

system) and sometimes called business or user

requirements
later in design, requirements become more
technical (how of system) and written from
developers perspective. So sometimes called
system requirements
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

What Are Requirements?

System Requirements :
Functional requirements
Non-functional requirements
Functional Requirements the activities the

system must perform

Business uses, functions the users carry out

Use cases

Non-Functional Requirements other system

characteristics

Constraints and performance goals

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Product vision and project scope

Establish business requirements and align them

with software requirements specs

Clear vision and scope lead to more focused requirements

Document contains 3 sections:

Business requirements and context
Product vision
Project scope and limitations

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Business requirements and context

Brief description of the rationale and business

opportunity for the product to be developed.

Main business objectives and some quantifiable
success criteria for financial or technical benefits
objectives.
A quantifiable financial benefit is: The product helps
reduce customer support cost by 30% during the first
year of operations.
A quantifiable technical benefit is: The average delay to
deal with and service a customer complaint will be
around 8 hours.

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Business requirements and context (cont)

Risks associated with the business requirements and

their management.
Risk assessment, prioritization, monitoring,
mitigation and control. (Elaboration on the
technical and non-technical project risks will be
included in the software project plan document).
Description of the different types of product users
and other stakeholders.
Context and environment in which the product will
be operating.
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Product vision
Clear statement of the product goals.
Capture the views of possibly many stakeholders and types of
users
Identify main functionalities and product features
List all the assumptions and dependencies

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Project scope and limitations

List functionalities and features to be included in

different releases or versions of the product.

Scope for each release is developed in line with the

stakeholders objectives and priorities.

Describe limitations - includes the functionalities

and features that will not be provided by the product

in any of its future releases.

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

FURPS+ Requirements Acronym

Functional requirements
Usability requirements
Reliability requirements
Performance requirements
Security requirements
+ even more categories
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Requirements definition: Functional vs.

Nonfunctional Requirements
Requirement definition report usually just

called Requirement definition- is a straightforward

text report that simply list the functional and
nonfunctional requirements in an outline format.
A functional requirement relates directly to a
process the system has to perform or information it
needs to contain.
Nonfunctional requirements refer to behavioral
properties that the system must have, such as
performance and usability.
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

FURPS+ Requirements Acronym

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

System Requirements
System requirements specifications that define the new
system
Functional requirements
Activities system must perform (use cases)
Based on procedures and business functions
Documented in analysis models
Nonfunctional requirements
Technical requirement hardware and software
Performance requirement workload measures
Usability requirement user interface, workflow
Reliability requirement outages, error detection
Security requirement access & protection
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Models and Modelling

Analyst describes information system
requirements using a collection of models
Complex systems require more than one type
of model
Models represent some aspect of the system
being built
Process of creating models helps analyst
clarify and refine design
Models assist communication with system
users
ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Some Analysis and Design Models

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Reasons for Modelling

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Types of Models
Different types of models are used in information
systems development
Mathematical formulas that describe
technical aspects of the system
Descriptive narrative memos, reports, or lists
that describe aspects of the system
Graphical diagrams and schematic
representations of some aspect of the system

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

StakeholdersThe 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

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Stakeholders
Who do you involve and talk to?
Stakeholders persons who have an interest in the

successful implementation of the system

Internal Stakeholders persons within the
organization
External stakeholders persons outside the
organization
Operational stakeholders persons who regularly
interact with the system
Executive stakeholders persons who dont directly
interact, but use the information or have financial
interest

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

Quantifiable Requirements
Avoid vague and unverifiable requirements which

depend for their interpretation on subjective

judgment

This is critical for non-functional requirements

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

System Requirements and Software

Requirements
System requirements - are for the system as a

whole; sometimes referred to as user

requirements

Includes hardware, software, firmware, people,

information, techniques, facilities, services, and other
support elements

Software requirements derived from system

requirements

ISS 2113 SOFT. REQ, CHAPTER 1

MDM. MARINA BINTI HASSAN, CTFL

THE END