Quick explanations

SE fundamentals and the description are based on SWEBOK. RSE equivalent terms and the description of RSE practice are based on the opinion of research software developers.

RSE awareness and RSE usage are coarse estimates of recognition/adoption of the practices for research software. 0=effectively no awareness/usage to 3=widespread awareness/usage. Sources for the estimates are noted in parentheses.

SER potential is a coarse estimate of the potential for additional software engineering research to increase the awareness/adoption by RSEs. 0=effectively no opportunity to 3=significant SE research would be beneficial. Opportunity briefly describes the software engineering research opportunity.

How to contribute

Use the comment section to suggest changes or discuss this term. Use Github discussions for discussion of the overall approach, or Github issues for specific concerns.

Term: Requirements tracing

Source: SWEBOK section 01.07.04

SE Fundamental RSE Equivalent
  • Requirements tracing
  • Traceability
 Not provided
Fundamental description RSE practice
A requirement should be traceable backward to its source and forward to its implementing design entities. Not provided
SER potential (source) and
opportunities 		RSE awareness (source) and
usage (sources)
Not provided (Not provided) Not provided (Not provided)
Not provided Not provided (Not provided)

Updated:

Comments