copyright joe kasser 19991 dr. joseph kasser umuc on-line requirements workshop

Copyright Joe Kasser 19991

Dr. Joseph Kasser

UMUC On-lineRequirements

Workshop


Objectives

• 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


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

Workshop Agenda


The purpose of a documentTo 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


Requirements• Purpose– Communicate to the designer what is to be designed

• Formats– document text format– report from the requirements database– graphic format

• Types– extrinsic– intrinsic


Where do requirements come from?*

• The customer/user

• Extrinsic sources

• Lessons learned documents

• Analysis and extrapolation

• Government mandates

• Other places* Kasser, J.E., Applying TQM to Systems Engineering, p210.


Requirements drive design and test

Requirements

Design plans &documents

Designs

Test Plans

Test Procedures

Tests

Manuals

Reports


Sample requirement

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.


Better requirement

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 requesterb. the product or service requestedc. the date and time of the requestd. the service prioritye. the current disposition of the requestf. the date and time of service completion.


Requirement or wish?

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 termsStatistically monitorIntegrityDegrading media


Requirements for Requirements

Shall be Complete Testable Achievable Relevant Grouped Specific Traceable

Shall not be Vague Overlapping Redundant

Shall not use including for example etc. should


Attributes of good documents

Complete Correct Concise Organized Unambiguous Pertinent Customer's language


Metrics for documents

Document type specificQualitative 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


Guidelines for the workshop • 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


Summary and reporting

copyright joe kasser 19991 dr. joseph kasser umuc on-line requirements workshop

Documents

shouldcopyright joe

changecopyright joe

time of service completion

service requestedc

service prioritye

dads products

cost effective mannercopyr

current disposition