|
A requirement is a singular documented need of what a particular
product, service or methodology should be or do. A requirement must be
precisely formulated and its meaning must be unequivocally understood
by the all involved parties (Evaluation Specification author, product
vendor, service provider, etc.). It encompasses the following
information:
| About |
The requirement title. |
VbO* |
| Statement |
An unambiguous and verifiable description of the requirement.
|
Yes |
| Rationale |
A statement why this requirement is considered to be important and/or what needs to be accomplished.
|
No |
| Quality Measure |
A
description of the criteria which will satisfy the originator of the
function (functional requirements), or quantify necessary behavior
(non-functional requirements). |
No |
| Public Comment |
Additional information, which is intended to help offerors better understand the requirement statement. |
Yes |
| Private Comment |
Additional information, which is intended to help internal users better understand the requirement statement. |
No |
| Requirement Level |
A term to signify a requirement, according to RFC 2119 |
Yes |
| Requirement Weight |
The relative importance of a requirement, expressed in terms of percent.
|
No |
* Viewable by Offeror
You can edit and modify requirements to your discretion. Likewise, you
can add new requirements or remove requirements that are not needed.
There are so-called template requirements, which you can
view and import into your Evaluation Specification in a drag-and-drop
fashion as needed. There are two kinds of template requirements:
- Partner Requirements: Requirements that you expect your business partner to meet.
- Non-functional Requirements: Requirements that you expect a product, service or methodology to meet.
The following screen shot shows a Requirement form.
|
EAS