Nosaukums | <p>This document specifies the application module for Requirement management.</p>
<p>The following are within the scope of this document:</p>
<ul>
<li>representation of the data that identify a requirement and its versions;</li>
<li>the assignment of a requirement to a product or other item;</li>
<li>the identification of the source of a requirement;</li>
<li>relationships between requirements;</li>
<li>characterization of a version of a requirement, suitable for one or more application domains and one or more life-cycle stages;</li>
<li>identification of a universe of discourse suitable for the description of requirements;</li>
<li>relationships between requirements that are expressed at the view definition level;</li>
<li>assignment of date and time properties to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of approval data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of identification and alias identification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of person and organization data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of contract data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of security classification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of language data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>representation proxy.</li>
</ul> |
Darbības sfēra | <p>This document specifies the application module for Requirement management.</p>
<p>The following are within the scope of this document:</p>
<ul>
<li>representation of the data that identify a requirement and its versions;</li>
<li>the assignment of a requirement to a product or other item;</li>
<li>the identification of the source of a requirement;</li>
<li>relationships between requirements;</li>
<li>characterization of a version of a requirement, suitable for one or more application domains and one or more life-cycle stages;</li>
<li>identification of a universe of discourse suitable for the description of requirements;</li>
<li>relationships between requirements that are expressed at the view definition level;</li>
<li>assignment of date and time properties to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of approval data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of identification and alias identification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of person and organization data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of contract data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of security classification data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>assignment of language data to requirements, requirement definitions, requirement versions, relationships between requirement versions, sources, relationships between requirement collections, requirement tracing relationships, and requirement assignments;</li>
<li>representation proxy.</li>
</ul> |