Changes between Version 4 and Version 5 of path:tutorial:traceability

Timestamp:

01/09/2014 06:20:17 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:tutorial:traceability

@@ -5 +5 @@
 '''Keywords:''' Requirements, Testing, Separation of Concerns, Traceability, Program Comprehension, Dynamic Analysis
 
-Requirements traceability is considered to be important for software understanding as it supports answers for questions such as why a particular source code entity was implemented.
+Requirements traceability is considered to be important for software understanding as it supports answers for questions such as "why a particular source code entity has been implemented".
 However, the presence of and traceability to requirements is increasingly lost in later more code-centric development activities. 
 Tracing which parts of the system contribute to which requirement is therefore hard and so limits understandability.
@@ -15 +15 @@
 A requirement is traced to a source code entity if it has been executed at least once in a specific test case that is linked to this requirement. 
 Depending on the coverage of test cases, large parts of the system can be traced and classified to requirements automatically.
-Thus, our approach allows developers to comprehend the system from the users point of view and to answer for typical software maintenance questions such as ”how is this requirement implemented?” or ”which source code entities are related to the user’s failure report?”.
+Thus, our approach allows developers to comprehend the system from the users point of view and to answer typical software maintenance questions such as ”how is this requirement implemented?” or ”which source code entities are related to the user’s failure report?”.
 
 == Demonstration ==