Tracing Requirements in Software Engineering

undefined
 
 
Links in the requirement chain
 
 
Chapter 29
undefined
 
This chapter will help you to
 
Understand requirements tracing
Understand links and dependencies
between requirements
Identify anything necessary to modify to
implement a requirements change
 
EECS812: Software Requirements Engineering
 
2
undefined
 
Tracing requirements
 
Follow
requirements
forward and
backward
Traceable
versus traced
 
EECS812: Software Requirements Engineering
 
3
undefined
 
Tracing requirements
 
EECS812: Software Requirements Engineering
 
4
undefined
 
Motivations for tracing
requirements
 
EECS812: Software Requirements Engineering
 
5
 
Finding missing requirements
Finding unnecessary requirements
Certification and compliance
Change impact analysis
Maintenance
Project tracking
Reengineering
Reuse
Testing
undefined
 
The requirements traceability
matrix – functional requirements
 
 
EECS812: Software Requirements Engineering
 
6
undefined
 
The requirements traceability matrix –
nonfunctional requirements
 
Quality
Portability
Security
 
 
EECS812: Software Requirements Engineering
 
7
undefined
 
Tools for requirement tracing
 
Matrix helps find suspect links
 
EECS812: Software Requirements Engineering
 
8
undefined
 
A requirements tracing procedure
 
EECS812: Software Requirements Engineering
 
9
 
Educate the team
Select the link relationships
Choose the type of traceability matrix
Identify the parts of the product  to trace
Identify individuals and roles
Make sure links are updated
Define labeling conventions
Provide ongoing
Audit the trace
 
undefined
 
Summary
 
Always do at least a minimum of
requirements tracing
Understand links and dependencies
between requirements
Try to identify anything you might need to
modify to implement a requirements
change
 
 
EECS812: Software Requirements Engineering
 
10
Slide Note
Embed
Share

"This chapter delves into requirements tracing, links, and dependencies in software engineering, emphasizing the importance of understanding and identifying necessary modifications to implement requirements changes. Motivations for tracing requirements, including finding missing or unnecessary requirements, certification and compliance, change impact analysis, maintenance, project tracking, reengineering, reuse, and testing, are discussed. Tools and procedures for requirement tracing, as well as the role of traceability matrices, are also covered."


Uploaded on Aug 14, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Chapter 29 Links in the requirement chain EECS812: Software Requirements Engineering Professor Hossein Saiedian

  2. This chapter will help you to Understand requirements tracing Understand links and dependencies between requirements Identify anything necessary to modify to implement a requirements change EECS812: Software Requirements Engineering 2

  3. Tracing requirements Follow requirements forward and backward Traceable versus traced EECS812: Software Requirements Engineering 3

  4. Tracing requirements EECS812: Software Requirements Engineering 4

  5. Motivations for tracing requirements Finding missing requirements Finding unnecessary requirements Certification and compliance Change impact analysis Maintenance Project tracking Reengineering Reuse Testing EECS812: Software Requirements Engineering 5

  6. The requirements traceability matrix functional requirements EECS812: Software Requirements Engineering 6

  7. The requirements traceability matrix nonfunctional requirements Quality Portability Security EECS812: Software Requirements Engineering 7

  8. Tools for requirement tracing Matrix helps find suspect links EECS812: Software Requirements Engineering 8

  9. A requirements tracing procedure Educate the team Select the link relationships Choose the type of traceability matrix Identify the parts of the product to trace Identify individuals and roles Make sure links are updated Define labeling conventions Provide ongoing Audit the trace EECS812: Software Requirements Engineering 9

  10. Summary Always do at least a minimum of requirements tracing Understand links and dependencies between requirements Try to identify anything you might need to modify to implement a requirements change EECS812: Software Requirements Engineering 10

Related


More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#