|
Requirement Templates Packages |
|
|
|
|
Release 1.1 of the Evaluator's Application Suite (EAS) adds functionality to the Evaluation Specification Editor (ESEdit). Requirement Views, which represent one of these functional enhancements, are domain-oriented collections of requirement templates. You can copy requirement templates into an Evaluation Specification via drag and drop. A requirement template is converted into an ordinary requirement when you drop it, meaning that you can make changes if desired.
Requirement templates save you from the effort of having to phrase requirements, which is often a time-consuming task. You can shorten the time needed to prepare Evaluation Specifications even further.
Viewed from a different perspective, each Requirement View provides a "window" into the central knowledge base on the BMO Server, grouping together requirement templates that belong to a certain context (e.g. "Security", "Team Development", etc.). Hence, a Requirement View is synonymous with a Requirement Templates Package (RTP).
Requirement Templates included in a Requirement Templates Package share a common set of properties with requirements included in Evaluation Specifications. Thus, when you import a Requirement Template, all property values (e.g. "Requirement Statement", "Rationale", "Quality Measure", "Private Comment", "Public Comment") are preserved.
The first Requirement Templates Packages to become available will focus on functional requirement templates that you need in the context of software evaluation and selection.
|
EAS