• SWE Pages
  • Review - SWE-002 - Software Engineering Initiative
  • Review - SWE-003 - Center Improvement Plans
  • Review - SWE-005 - Software Processes
  • Review - SWE-095 - Report Engineering Discipline Status
  • Review - SWE-208 - Advancing Software Assurance and Software Safety Practices
• Topic Pages
  • Review - 7.01 - History and Overview of the Software Process Improvement (SPI) Effort

Review Pages

The review pages in this set were built as an proposal for making changes to implement Bidirectional Traceability into SWEHBVD as a part of the new Activity pages. Some of the additional cross references have already been made as a part of implementing the "Additional Guidance" sections in SWEs and Topics. The proposed rules for adding these cross references would be: 

• If an inference is obvious from the wording of the text, add a "See also" statement immediately below or in line with the sentence containing the inference. 
• If an inference is LESS obvious, but still significant, from the wording of the text, add a "See also" statement immediately below or in line with the sentence containing the inference. 
• If there is no inference in the text, DO NOT add the SWE or "Topic link. This will mean that not all SWEs and topics will be forced to be cross referenced just because they are a part of an Activity. 

In applying these rules you can see the following cross referencing applied: 

Example using Activity A.00.2 - History of Improvement Efforts