1
Copyright Joe Kasser 1999

•
Primary
–
Learn the importance of good requirements
–
Learn how to evaluate requirements
–
Understand the difficulty of writing effective requirements
•
Secondary
–
Learn to collaborate in an on-line environment
2 Copyright Joe Kasser 1999

3


The purpose of a document
Requirements
 Requirements for requirements
 Attributes of good documents





Metrics for documents
Defective requirements
Guidelines for workshop
Exercise (duration of the semester)
Summary and reporting
Copyright Joe Kasser 1999

4
 To communicate something to someone
 SOW - communicates the government's needs to potential offerers
 PROPOSAL - communicates to the government, that
 we understand the need
AND
 have the optimal (most cost effective and best technical) solution
 REQUIREMENTS - Communicate to the designer
 what is to be designed
CHANGE REQUEST - communications a change
Copyright Joe Kasser 1999

5
• Purpose
– Communicate to the designer what is to be designed
• Formats
– document text format
– report from the requirements database
– graphic format
• Types
– extrinsic
– intrinsic
Copyright Joe Kasser 1999

6
*
• The customer/user
• Extrinsic sources
• Lessons learned documents
• Analysis and extrapolation
• Government mandates
• Other places
* Kasser, J.E., Applying TQM to Systems Engineering, p210.
Copyright Joe Kasser 1999

Manuals
Requirements
Test Plans
Design plans & documents
Test Procedures
7
Designs Tests
Copyright Joe Kasser 1999
Reports

8
509.1 DADS shall monitor and provide reports (to the operator) on all requests for
DADS products and services. This capability shall include recording the name and organization of the requester, the product or service requested, the date and time of the request, the service priority, the current disposition of the request, and the date and time of service completion.
Copyright Joe Kasser 1999

9
509.1 DADS shall monitor and provide reports to the operator about the state of transactions in the system. This capability shall contain the following: a. the name and organization of the requester b. the product or service requested c. the date and time of the request d. the service priority e. the current disposition of the request f. the date and time of service completion.
Copyright Joe Kasser 1999

10
202.1 DADS shall statistically monitor the integrity of data stored in the archive and safe-store in order to detect degrading media .
Define the following terms
Statistically monitor
Integrity
Degrading media
Copyright Joe Kasser 1999

11
 Shall be

Complete

Testable

Achievable

Relevant

Grouped

Specific

Traceable
 Shall not be

Vague

Overlapping

Redundant
 Shall not use
 including
 for example
 etc.
 should
Copyright Joe Kasser 1999

12
 Complete


Correct
Concise


Organized
Unambiguous


Pertinent
Customer's language
Copyright Joe Kasser 1999

13
 Document type specific
 Qualitative basis
 the presence of characteristics of good documents
 Quantitative

RATIO of number of defects to opportunity for defects
 Quality

Producing the product to specifications in the most cost effective manner
Copyright Joe Kasser 1999

14
•
Each person
– reviews a requirements document
– Counts number of requirements
–
Counts number of defective requirements
–
Posts individual counts in requirements workshop conference
•
Discuss in team study groups
•
Summarize into team count
•
Post team count in requirements workshop conference
•
Discuss in requirements workshop conference
Copyright Joe Kasser 1999

15 Copyright Joe Kasser 1999