Difference between revisions of "Main Page"

From Coest Body of Knowledge
Jump to: navigation, search
(Components of Traceability)
(What is Traceability?)
(2 intermediate revisions by one user not shown)
Line 4: Line 4:
 
== What is Traceability? ==
 
== What is Traceability? ==
  
There are many definitions of software traceability; however we define it as "the ability to interrelate any uniquely identifiable software engineering artifact to any other, maintain required links over time, and use the resulting network to answer questions of both the software product and its development process."
+
There are many definitions of software traceability; CoEST defines it as "the ability to interrelate any uniquely identifiable software engineering artifact to any other, maintain required links over time, and use the resulting network to answer questions of both the software product and its development process."
  
To make a system traceable, navigable links must be created between artifacts that are otherwise disconnected.  
+
To make a system traceable, navigable links must be created between artifacts that are otherwise disconnected, i.e. requirements, code, and test cases. [Example]. These links must be documented and stored so that they can later be retrieved.  
  
 +
Traceability is a required component of the approval and certification process in most safety-critical systems, where systems must demonstratively meet a set of standards and mitigate any potential hazards. Codes and test cases must be linked to a requirement of the system. [Expand on this with isolette example?]
  
 +
In practice,relatively few systems have meaningfully benefited from traceability.  Producers of medical equipment, for example, typically create and document traceability information immediately prior to the certification process, and the resulting data is often incomplete, incorrect, or contradictory. 
  
 +
CoEST's vision is that traceability strategy become a built-in, implicit part of systems in a way that is cost-effective and responsive to the needs of stakeholders.
  
 
== Components of Traceability ==
 
== Components of Traceability ==
Line 18: Line 21:
  
  
 +
'''Trace:''' The data in question.
  
 +
'''Source Artifact:''' The origin of a trace.
  
'''Source Artifact:''' Where the trace starts.
+
'''Target Artifact:''' The destination of that trace. (Note: Example here?)
 
+
'''Trace:''' The data in question.
+
 
+
'''Target Artifact:''' Where the data ends up.
+
  
 
== Examples ==
 
== Examples ==

Revision as of 06:34, 29 April 2014

Under Construction


What is Traceability?

There are many definitions of software traceability; CoEST defines it as "the ability to interrelate any uniquely identifiable software engineering artifact to any other, maintain required links over time, and use the resulting network to answer questions of both the software product and its development process."

To make a system traceable, navigable links must be created between artifacts that are otherwise disconnected, i.e. requirements, code, and test cases. [Example]. These links must be documented and stored so that they can later be retrieved.

Traceability is a required component of the approval and certification process in most safety-critical systems, where systems must demonstratively meet a set of standards and mitigate any potential hazards. Codes and test cases must be linked to a requirement of the system. [Expand on this with isolette example?]

In practice,relatively few systems have meaningfully benefited from traceability. Producers of medical equipment, for example, typically create and document traceability information immediately prior to the certification process, and the resulting data is often incomplete, incorrect, or contradictory.

CoEST's vision is that traceability strategy become a built-in, implicit part of systems in a way that is cost-effective and responsive to the needs of stakeholders.

Components of Traceability

Trace Artifact: units of data that are amenable to being traced. Often, what constitutes an artifact (the project as a whole? Some element of the project?) is not predetermined, which makes traceability within the project more challenging.



Trace: The data in question.

Source Artifact: The origin of a trace.

Target Artifact: The destination of that trace. (Note: Example here?)

Examples

Challenges

Tracing is often done ad-hoc, after the fact. Since it can be costly to make a system exhaustively traceable, it must be determined what the needs are of the system or stakeholder: what information needs to be tracked?









MediaWiki has been successfully installed.

Consult the User's Guide for information on using the wiki software.

Getting started