1.
Terms for Requirements specifications
A requirements specification is a
systematically represented
collection of requirements
Typically for a system or
component that satisfies given
criteria
Terms
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

2.
Documentation types
Data perspective: (Data)
In this, a static-structural
perspective on requirements of
system is adopted
Behavioral perspective:
(State)
In this, information about
system and how it is
embedded into system
context is documented in a
state-oriented manner
Functional perspective: (Logic)
The functional perspective documents
which information is received from
system context and manipulated by
system or one of its functions
Data
perspective:
(Data)
Data
perspective:
(Data)
Behavioral
perspective:
(State)
Behavioral
perspective:
(State)
Functional
perspective:
(Logic)
Functional
perspective:
(Logic)This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

3.
Requirements documentation using
structured text
Structured text uses a defined
structure to document
requirements
Advantages
Ensures desired aspects are covered
Advantages
Needs training on writing structured
textThis document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

4.
Hybrid requirements documents
Contain a combination of natural
language and conceptual models
Advantages
Takes advantages of different types of
documentation
Disadvantages
Disadvantages of structured text and
conceptual models still apply
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

5.
Advantages of using standard outlines
Advantages
Incorporate new project team members
Quickly find needed content
Selective reading and validation
Automatic verification of requirements document with
respect to completeness
Allow re-use of contentThis document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

6.
Customized standard contents
Customized document structures
adapt standardized document
structures for specific project
conditions
Customized document structures
MUST address following aspects:
Introduction
Purpose
System coverage
Stakeholders
Definitions, Acronyms, and Abbreviations
References
Overview
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

7.
Quality criteria for requirements
documents
For requirements documents,
following criteria holds:
Unambiguity
Consistent
Clear Structure
Modifiability
Extendibility
Completeness
Traceability
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

8.
Glossary
Stakeholders interpret same terms differently
which is a frequent cause for conflicts
To avoid this, everyone involved in
development process must share same
understanding of terminologies used
A glossary improved understandability of
requirements
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

9.
Let’s discuss few sample questions
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

10.
Question 2
2. You have to elicit requirements for a sales software that shall operate
worldwide. In the initial elicitation of requirements, participants from all
30 branches should be involved. Project management has decided that
for the documentation of the initial requirements a wiki system is to be
used. Which of the following statements is most likely correct?
a. The approach makes no sense as a wiki system is no requirements management tool
b. The approach makes sense as all people involved can collaboratively write down and
comment on the initial requirements
c. The approach makes no sense as the initial requirements analysis has to be
performed by a requirements engineer in form of interviews
d. The approach makes sense as wiki systems provides a history (of the modifications
made)
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

11.
Correct Option for Question 3
C. Vocabulary is vital to understand a domain
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

12.
Question 5
5. Which statement about apprenticing is false?
a. Apprenticing is an observation technique
b. Apprenticing is an individual-orientated technique
c. Apprenticing should, if possible, take place in the environment in
which the new system will later be deployed
d. Further questions are not allowed during apprenticing, as these may
influence the observation
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

13.
Correct Option for Question 6
A. Techniques for elicitation
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

14.
Question 8
8. Stakeholder maps are virtual diagrams that depict the relation of
stakeholders to the solution and to one another. Which of the
following forms can be used as stakeholder map?
a. RACI Matrix
b. Decision tree
c. OPAS
d. Stakeholder onion diagramThis document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

15.
Correct Option for Question 9
C. Definition - Looking for a finite answer
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

16.
Thank you and best of Luck!
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/4-documenting-requirements-2559

17.
1
Flevy (www.flevy.com) is the marketplace
for premium documents. These
documents can range from Business
Frameworks to Financial Models to
PowerPoint Templates.
Flevy was founded under the principle that
companies waste a lot of time and money
recreating the same foundational business
documents. Our vision is for Flevy to
become a comprehensive knowledge base
of business documents. All organizations,
from startups to large enterprises, can use
Flevy— whether it's to jumpstart projects, to
find reference or comparison materials, or
just to learn.
Contact Us
Please contact us with any questions you may have
about our company.
• General Inquiries
support@flevy.com
• Media/PR
press@flevy.com
• Billing
billing@flevy.com