Requirements Traceability-Software Requirement-Lecture Slides, Slides of Software Project Management

This course includes types of requirements, modeling of non functional, static and dynamic modelling, requirement elicitation and use case modeling. This lecture includes: Classifications, Requirements, Traceability, Interface, Design, Generic, Analyse, Collect

Typology: Slides

2011/2012

Uploaded on 08/07/2012

angana
angana 🇮🇳

4.4

(52)

158 documents

1 / 28

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
Requirements Traceability
Lecture # 20
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c

Partial preview of the text

Download Requirements Traceability-Software Requirement-Lecture Slides and more Slides Software Project Management in PDF only on Docsity!

1

Requirements Traceability

Lecture # 20

2

Recap of Last Two Lectures

  • We talked about different aspects of

requirements management, i.e.,managing the changes in requirementsin detail

  • Requirements cannot be managed

properly if requirements traceability isnot implemented

4

Tracing Requirements

  • It is important to trace requirements

both ways– Origin of a requirement– How is it implemented

  • This is a continuous process

5

Classifications of Requirements

Traceability

  • Backward-from traceability• Forward-from traceability• Backward-to traceability• Forward-to traceability

7

Forward-from Traceability

  • Links requirements to design and

implementation components

8

Backward-to Traceability

  • Links design and implementation

components back to requirements

10

Backwards and Forwards

Traceability

Business plan

Requirements document

Design specification

Forward-to traceability

Forward-from traceabilityBackward-from traceability

Backward-to traceability

11

Categories of Traceability

  • Requirements-sources traceability• Requirements-rationale traceability• Requirements-requirements

traceability

  • Requirements-architecture traceability• Requirements-design traceability• Requirements-interface traceability

13

Requirements-Rationale

Traceability

  • Links the requirement with a

description of why that requirementhas been specified. This can be adistillation of information from severalsources

14

Requirements-Requirements

Traceability

  • Links requirements with other

requirements which are, in some way,dependent on them. This should be atwo-way link (dependent on them andis-dependent on)

16

Requirements-Design

Traceability

  • Links requirements with specific

hardware or software components inthe system, which are used toimplement the requirement

17

Requirements-Interface

Traceability

  • Links requirements with the interfaces

of external systems, which are used inthe provision of the requirements

19

A Generic Traceability Table

A

A

A

Aii

R01R02R03 Rnn

20

Need for Traceability Policy

  • Huge amount of information, which is

expensive to collect, analyze, andupdate

  • Need to continuously update

traceability information

  • A traceability policy is needed