This addition to SWEHBVD was started in 2023. It encompasses several major changes in how the SWEHB is used This table contains the major steps in the buildout of Activities in SWEHBVD 6/12/2023 Done 3/1/2024 Convert appropriate topics to Generic Topics This tab contains specific examples of next buildout actions. It presents suggested changes to SWEs and SM for consideration by the Activity team to consider and approve for implementation or discard. Accepted items will be implemented based on an agree to priority. We need to come up with a way to ensure that each SWE and SM item point to all of the appropriate other SWEs and SM within the scope of an Activity. Initially, each activity was built to contain the SWEs and SM that were most directly associated to the Activity / Phase of a project. Many were obvious by their title, others were included because of their location in NPR 7150.2 ( e.g. Cybersecurity Requirements). This would make it easier to ensure that SWEs and SM are tied into the appropriate Activity (bi-directional traceability). This would affect all SWEs and SM to update their Related Links lists. Activities would be added to the appropriate "Related SM" pages. There are a number of Analysis topics in this Activity, tab "01 - Analysis". These should be called out in the Activity where they are used by SA. For example, 8.54 - Software Requirements Analysis should probably be called out in A.03 Software Requirements as a related Topic. These are being added to all appropriate Activities: Need Activity locations for: There are a couple of pages that are in A.02 Software Assurance and Software Safety Activity that deal with Auditing. Should they be also put into other Activities as a reminder of the need for auditing in these activities? Currently, all of the IV&V SWEs and SM are in A.02 Software Assurance and Software Safety Activity in the IV&V tab. Should this be copied also into A.06 Software Testing Activity? If so, how should it be represented, since it is not applicable in all projects. Currently, all of these SWEs and SM are in A.02 Software Assurance and Software Safety Activity in the "Safety Critical" tab. Where else should they be placed to ensure that they are taken into consideration in Life Cycle Activities?
See edit history of this section
Post feedback on this section
1. Introduction
The Activity View of SWEHB is based on the Software Development Life Cycle 2. Buildout of Activities
Description Status Date Complete Build Relevant SWEs page for all SWEs and SM Done Build "Relevant SM" page for all SWEs and SM Done 6/12/2023 Number / Renumber topics in SWEHBVD Done 6/14/2023 Build Traceability of Subjects to SWEs and SM page Done 6/14/2023 Build Distribution tables for all SWEs and SM 6/30/2023 Update SWEs to point to relevant SWEs and SM In Progress Update SMs to point to relevant SWEs and SM Done Add Introduction text to all Activities In Progress Review all Introduction text to all Activities Put Subjects table into all Activities Done 8/15/2023 Put SWEs into all Activities Done 8/15/2023 Put Work Products into all Activities Done 8/15/2023 Put Topics into all Activities Done 8/15/2023 Put PATs into all Activities In Progress Finish building PATs Fix Quotes from References in all pages 3. Detail
3.1 Things to do in all SWEs and SM
3.1.1 Bidirectional Traceability of SWEs and SM
3.1.2 Completeness of Activities
Actions
3.1.3 Add Activities into "Related Links" tables
3.2 Things to do in A.02 -Software Assurance and Software Safety
3.2.1 Location of Analysis in SWEs and SM
3.2.2 Location of Audit SWEs and SM
3.2.1 - Location of IV&V SWEs and SM
3.2.3 Safety and Hazard SWEs and SM
3.3 Things to do in A.13 - Institutional Requirements
Activity View in SWEHBVD
Web Resources
View this section on the websiteUnknown macro: {page-info}