[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- Balasubramaniam Ramesh & Mathias Jarke
- Toward Reference Models for Requirements Traceability
- IEEE Trans Software Engineering V27n1(Jan 2001)pp58-93
- =POLL TOOLs REQUIREMENTS MODEL REMAP DEMO KBSA ConceptBase DFD ERD
- Reference models describe ideas that are shared across many pieces of software. They take extra effort up-front but can be reused as a source in many projects.
- 4 year study of how requirements are traced in American software development. Focus groups, interviews, tools.
- One size does not fit all: there are low and high end users of traceability.
- STAKEHOLDER, SOURCE, OBJECT : Sets,
- TRACES_TO:@(Object, Object),
- MANAGES:@(STAKEHOLDER, SOURCE),
- DOCUMENTS: @(SOURCE, OBJECT),
- HAS_ROLES_IN: @(STAKEHOLDER, OBJECT | TRACES_TO)
(End of Net RameshJarke01_Requirements_Metamodel
- Generate particular models by specializing and instantiating parts of the meta-model.
- dimensions:= What >< Who >< Where >< Why >< when.
- Lower level users ConceptBase: requirements, compliance verification procedures, system subsystems components, external systems. Tend to not document rationales.
- High end users need 4 separate diagrams. Includes rationales.
- Implemented the high level model using
- SLATE::tool="system Level Automation Tool for Engineers".
- Input into DFDs and ERDs and CASE tools.
- Distinguishes 18 types of links.
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]