BUSINESS ANALYST TRAINING

Feb - 2014
 DAY 6
 Users of Requirements

 Types of Requirements

 Structure of Requirements Document

USERS OF REQUIREMENTS DOCUMENT
TYPES OF REQUIREMENTS
 User Requirements

 System Requirements
FUNCTIONAL & NON-FUNCTIONAL REQUIREMENTS
 Functional Requirements

 Non-Functional Requirements

 Domain Requirements
FUNCTIONAL REQUIREMENTS CHARACTERISTICS
 Precise

 Unambiguous

 Complete

 Consistent
NON-FUNCTIONAL REQUIREMENTS
NON FUNCTIONAL REQUIREMENTS CHARACTERISTICS
Pro perty Mea sure
Sp eed Processed transactio ns/secon d
User/Ev ent respo nse time
Screen refresh time
Size K Bytes
Number o f RAM ch ip s
Ease of use Training time
Number o f help frames
Reliability Mean time to failu re
Prob ability of u nav ailability
Rate of failure o ccurrence
Availab ility
Robu stn ess Time to restart after failu re
Percentage of events causing failu re
Prob ability of d ata co rrup tion o n failure
Po rtability Percentage of target dep enden t statements
Number o f targ et sy stems
DOMAIN REQUIREMENTS CHARACTERISTICS
 New Functional Requirements

 Constraints on Existing Requirements

 Define Specific Computations.

They should be:

 Understandable

 Implicit Enough
STRUCTURE OF REQUIREMENTS DOCUMENT
Chapter Description

Preface This should define the expected readership of the document and describe its
version history, including a rationale for the creation of a new version and a
summary of the changes made in each version.

Introduction This should describe the need for the system. It should briefly describe the
system’s functions and explain how it will work with other systems. It should
also describe how the system fits into the overall business or strategic
objectives of the organization commissioning the software.

Glossary This should define the technical terms used in the document. You should not
make assumptions about the experience or expertise of the reader.

User requirements Here, you describe the services provided for the user. The nonfunctional
definition system requirements should also be described in this section. This
description may use natural language, diagrams, or other notations that are
understandable to customers. Product and process standards that must be
followed should be specified.

System architecture This chapter should present a high-level overview of the anticipated system
architecture, showing the distribution of functions across system modules.
Architectural components that are reused should be highlighted.
STRUCTURE OF REQUIREMENTS DOCUMENT
Chapter Description
System This should describe the functional and nonfunctional requirements in more
requirements detail. If necessary, further detail may also be added to the nonfunctional
specification requirements. Interfaces to other systems may be defined.

System models This might include graphical system models showing the relationships between
the system components and the system and its environment. Examples of
possible models are object models, data-flow models, or semantic data models.

System evolution This should describe the fundamental assumptions on which the system is
based, and any anticipated changes due to hardware evolution, changing user
needs, and so on. This section is useful for system designers as it may help
them avoid design decisions that would constrain likely future changes to the
system.
Appendices These should provide detailed, specific information that is related to the
application being developed; for example, hardware and database descriptions.
Hardware requirements define the minimal and optimal configurations for the
system. Database requirements define the logical organization of the data used
by the system and the relationships between data.

Index Several indexes to the document may be included. As well as a normal

alphabetic index, there may be an index of diagrams, an index of functions, and
so on.
WAYS OF WRITING SRS
Notation Description

Natural language The requirements are written using numbered sentences in natural language.
Each sentence should express one requirement.

Structured natural The requirements are written in natural language on a standard form or
language template. Each field provides information about an aspect of the requirement.

Design description This approach uses a language like a programming language, but with more
languages abstract features to specify the requirements by defining an operational model
of the system. This approach is now rarely used although it can be useful for
interface specifications.

Graphical notations Graphical models, supplemented by text annotations, are used to define the
functional requirements for the system; UML use case and sequence diagrams
are commonly used.

Mathematical These notations are based on mathematical concepts such as finite-state

specifications machines or sets. Although these unambiguous specifications can reduce the
ambiguity in a requirements document, most customers don’t understand a
formal specification. They cannot check that it represents what they want and
are reluctant to accept it as a system contract
THANK YOU