[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)

RameshJarke01

  1. Balasubramaniam Ramesh & Mathias Jarke
  2. Toward Reference Models for Requirements Traceability
  3. IEEE Trans Software Engineering V27n1(Jan 2001)pp58-93
  4. =POLL TOOLs REQUIREMENTS MODEL REMAP DEMO KBSA ConceptBase DFD ERD
  5. 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.
  6. 4 year study of how requirements are traced in American software development. Focus groups, interviews, tools.
  7. One size does not fit all: there are low and high end users of traceability.
  8. RameshJarke01_Requirements_Metamodel::=following
    Net
    1. STAKEHOLDER, SOURCE, OBJECT : Sets,
    2. TRACES_TO:@(Object, Object),
    3. MANAGES:@(STAKEHOLDER, SOURCE),
    4. DOCUMENTS: @(SOURCE, OBJECT),
    5. HAS_ROLES_IN: @(STAKEHOLDER, OBJECT | TRACES_TO)

    (End of Net RameshJarke01_Requirements_Metamodel)

  9. Generate particular models by specializing and instantiating parts of the meta-model.
  10. dimensions:= What >< Who >< Where >< Why >< when.
  11. Lower level users ConceptBase: requirements, compliance verification procedures, system subsystems components, external systems. Tend to not document rationales.
  12. High end users need 4 separate diagrams. Includes rationales.
  13. Implemented the high level model using [SLATE].
  14. SLATE::tool="system Level Automation Tool for Engineers".
  15. Input into DFDs and ERDs and CASE tools.
  16. Distinguishes 18 types of links.

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.



To see the complete bibliography (1Mb+) select:[Bibliography]