Traceability in Requirements Management: Techniques, Tools, and Importance, Slides of Elements of Engineering Systems

Download Traceability in Requirements Management: Techniques, Tools, and Importance and more Slides Elements of Engineering Systems in PDF only on Docsity!

Traceability

Requirements Management Traceability Systems Engineering STD

Contents

• Terminologies
• Techniques
• A model of traceability
• Tools : case study (RTM, Slate, DOORS : what will be available at HPI !!)

A recent event : Mad cow and Hamburger !!

Terminologies

• Part of requirement management process
• Technique to provide relationship between requirement design and final implementation
• How and why system development products satisfy stakeholders requirements
• Ability to discover the history of every feature of a system
• A quality factor
• Many standards (2167-A then 498) require the development of traceability documents

Techniques

• Cross reference schemes
• Keyphrase dependancy
• Templates
• Matrices
• Matrix sequence
• Hypertext
• Integration documents All differs in the intent of information traced and objective of tracing

Essence of traceability

• Of What (information)
• In what way (information prsentation)
• For whom
• Example : Who coded the program
  • Who : we need the programmer
  • What way : name, the company, the team?
  • For whom : to whom this information is addressed (not anybody can have any information : information abstraction and ... Security)

Cross references and index schemes

• References made across several items (design, modules, requirements,..) in order to link two items or artifacts.
• Example : There should be a high-level of traceability between "Logical Architecture" and "Physical Architecture"
• The logical and physical architecture are tied together with a collection of cross - reference tables in the " Traceability Matrix"

Tracing languages

• Database query languages Used in existing powerfull RT tools (RTM use runtime version of Oracle)
• Regular expressions Used in formal TOOR approach TOOR
• is designed for tracing requirements in system development.
• It considers as objects, in the computing science sense of the word, any artifacts used during the development of a software system, e.g., an interview transcript, a video tape, a design chart, a program specification text, a system manual, etc.
• It also considers the possible relations between any two objects as an object itself

TOOR. A formal approach

• Developped at Oxford (Goguen, Pinheiro)
• Object based ( see RTM tool too )
• Declaration using FOOP (based on OBJ)
• Traceability links between any artifacts created by different documents
• Graphical interface
• Tracing are forward and backward

TOOLS : RTM

• Requirements Traceability Module (Chipware)
• Other tools : DOORS (telelogic), Slate (QSS)
• Essential approach
  • A generic meta model
  • All links are specified in the relation between between classes
  • Document generation
  • Can be customised to any meta-model defined by user

A model of traceability

STACKHOLDER OBJECT SOURCE Manages Documents Is concerned by Traces to Separation between source and other objects

• Email
• Doc
• phone call
• Meeting minutes
• A Requirement
• A Designed architecture
• A software module
• A manager
• A user
• A programmer

A model of traceability

Syst_components Requirement Developed_for Verification_proced Derive Allocated_to External_System Performed_on satisfy Interface_with

Relative importance of dependancy links

• Attribution of weight on on link
  • Qualitative
  • Quantitative
• Example : The voltage change in one component affect another component
• Links can be many levels of abstraction
  • Requirement and derived rtequirement
  • Requirement and stackholder
  • Not injective or surjective relation

Conclusions

• A model of traceability should be defined
• A need for a tool
• Two way to implement the tool
  • Specific tool for RT
  • A database system as Oracle.