View source for Requirement Management
From T-VEC Wiki
The T-VEC Tabular Modeler (TTM) provides native support for requirements management, but integrates also with Telelogic's DOORS requirements management tool. See http://en.wikipedia.org/wiki/Requirements_management for more details about Requirement Management. ==TTM Requirements Management== TTM manages requirements through a hierarchical decomposition where each requirement is comprised of a: *Requirement ID - Requirement IDs are unique strings that include the characters: a-z, A-Z, 0-9, _, ., and must begin with an alphabetical character. *Heading- A short description of the Requirement *Description - A single line of text that further describes the Requirement *Text -Any additional text The hierarchical decomposition of the requirements is managed through the model view. Requirements are decomposed by creating child requirements which display below their parents within the model view. Add and delete requirements as described in Building Models. Child requirements are created when a requirement is added while an existing requirement is selected. ===Linking Requirements=== Requirements can be linked to Types, Constants, and Inputs are for documentation only. These requirement associations are not used as part of test generation in VGS. Requirements for these model elements are assigned to both assertions and non-behavioral model elements the same way as described in Specifying Requirements for Non-Behavioral Model Elements. Requirements are typically associated with the behavior of Terms, Outputs, and Mode Machines. The Requirement ID column in the Term, Output, and Mode Machine Behavior/Transitions tables provide a drop-down checklist for associating requirements with specific behavior. Test vectors generated to test the behavior specified in each table row include Requirement IDs assigned to the table row.
Retrieved from "
What links here
About T-VEC Wiki