Information Technology Reference
In-Depth Information
4. They must be designed to be self-explanatory needing little or no training for
use by trained individuals.
Procedures are step-by-step instructions and explain how to perform/accom-
plish an activity. Standards prescribe the parameters for the performance of the
activity. A guideline is similar to a standard but is more suggestive and less
prescriptive in nature than standards. Formats and templates assist the performers
in comprehensively capturing the information. Format and template are similar in
nature except that a template contains helpful hints to aid the users in capturing the
information within the document. A checklist is tickler for the memory to alert the
individual performing the activity to any missing information. The process ties up
all these pieces together to present a comprehensive whole.
A comprehensive process for requirements engineering and management would
include the following artifacts:
1. An overall process document linking all the artifacts that deal with require-
ments engineering and management with in the organizations
2. A set of procedures for:
a. Elicitation of requirements
b. Gathering of requirements
c. Analysis of requirements
d. Establishment of requirements
e. Measurement and analysis for the performance of requirements engineering
and management activity
f. Verification and validation of the deliverables of the activity of require-
ments engineering and management
3. A set of formats and templates for
a. Capturing the information during elicitation and gathering of requirements
b. Document the URS
c. Document the SRS
d. Defect reporting during verification and validation activities
4. Checklists for:
a. Elicitation and gathering of requirements
b. Documenting URS
c. Documenting the SRS
d. Verification and validation.
Now let us not misunderstand that all the above must be paper-based docu-
ments. It could be soft copies or could be embedded inside a software tool.
Search WWH ::
Custom Search