Page History

...

One approach to this might be to combine the Development and Assurance elements into a single activity to reinforce the notion that the two groups are expected to work in a coordinated way even though not in a closely coupled way. To show this, look at the Activity - Software Design - Combined page. This page shows the combination of Development Tasks and Assurance Tasks in a single activity. 

...

In building the third Activity example, Activity - Software Design - Combined, It became apparent that there are some new pages in the SWEHB tat are different from the typical SWE or Topic. In the latter days of SWEHBVC some work was done on a small number of pages in the 7.18 - Documentation Guidance. They were moved into Topic 8.16 - SA Products. As these pages developed further, they became more than just a "minimum content" description. They blossomed into very detailed guidance pages, looking somewhat like activity descriptions. 

...

• In my attempt to be inclusive in my Activity - Software Design - Combined page, I may have too much detail in section 3.2 where I go down to the task level on the 8.55 - Software Design Analysis page. 
• Conversely, there may not be enough detail in the activity to cover other tabs in the 8.55 - Software Design Analysis page such as:
  •  Safety Analysis During Design 
  • Analysis Reporting Content 

...

• Copy of SWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures
• Copy of SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking
• Copy of SWE-089 - Software Peer Reviews and Inspections - Basic Measurements
• Copy of Activity - Software Peer Reviews and Inspections - Combined

6.7.1 Removing Metrics From The Template

Tab 1 of the activity did not change much from the previous examples of this activity. Significant changes needed to be made in tabs 2 and 3.  

...

In both tabs 2 and 3 the metrics detail is gone. It  was deleted because there was too much detail and it made the presentation of the activity too confusing. 

...

...

6.7.2 Addition of "Clarifying Statement" 

Note the addition of "Another clarifying statement to further describe the SWE" in tab 1. This was added because the excerpt for a SWE page is the requirement. It does not contain any "reusable text" describing the purpose of the page. In the case of the Peer Review SWEs, reworking the guidance tabs made it clear why the three SWEs were needed: 

• SWE-087 - Establishes the Peer Review Process to be used in the project
• SWE-088 - Establishes individual Peer Review content for each of the documents to be reviewed
• SWE-089 - Establishes Metrics for the Process as well as the individual reviews

This distinction between the SWEs was not brought out in the Rationale statements. Expressing them in the activity add some clarity for the user. 

6.7.3 Summarizing the Combined Activity Structure

There are several features of the combined structure. whether they are net positives or net negatives will be for us to debate. We need to consider several questions for each. Some of these items imply a significant amount of work to get the SWEs and Topics ready for the reorganization. There is a lot of work remaining to get the PATs configured and made available.  

1. Combining the Development and Assurance activities 
   1. Does it reinforce the concept of "working together" 
   2. Are the tasks for Development and Assurance so different that they lead to confusion or do they serve to bring the work to a logical conclusion?
2. Omitting Metrics from the Combined Activity page
   1. Since Metrics are in the SWE page, tab 4 and 7, they are unnecessary clutter in the Activity page?
   2. Are a few of the key metrics desirable to have in the Activity to ensure that the whole reason for having Metrics is not lost?
3. Clarifying statements and Tab 2 in the SWEs
   1. Should the clarifying statements be consolidated in the Tab 1 to explain why there are so many SWEs on this subject?
   2. Should the rationale statements in the SWEs be updated to explain how the collection of related SWEs work together? 
4. Updating in Tab 3 - adding subheadings to clarify tasks. Much of the content is well organized, this is just adding subheadings that make the tasking more obvious
   1. Is it appropriate to say that Development teams have "tasking" imposed on them by the NPR? Is that a Center responsibility through their Asset Libraries and SEPG organizations?
5. Updating in Tab 4 - Adding Tasking, Work Products, and Metrics
   1. Is it okay to leave the Small Projects content in at the top of the page? 
   2. Should Small Projects be move elsewhere? Does it need it's own sub-heading
6. Divergence through content coming out of 8.16 topics 
   1.  Is there a close alignment of all the 8.16 topics with the development requirements of the SWEs.
   2. Some of the 8.16 topics span a wide range of SWEs as in "Topic 8.16 - Software Design Analysis", tasks reach out beyond Design. 
7. Completing the creation of PATs - there are just over 30 now, There are probably as many as a hundred total depending on how we want to break out some of the SWE content that is currently in bulleted lists in tabs. 
   1. Should we prioritize the creation of PATs over the creation of activities? 
   2. Are the Activities more important than the PATs? 
   3. Are they of equal importance - build PATS as the content in Tab 3s are updated? 
8. Rollout of Activity in the reorganization
   1. Should it be done all at once, individually, or in some sort of logical groupings? 
   2. How should the Activity reorganization be coordinated with other things like Blog postings - Blog postings could be the announcement mechanism for letting the community know about the various updates. 

6.7.4 Key Points for the Presentation at KSC in February

1. What are the key things that we want to keep in the new structure?
2. What are the things that we need to rethink? 
3. How much should we be reveling to the SWWG at the meeting in February?  
4. What things are we needing input on from the SWWG to  influence the changes to the SWEHB? 
5. What items can we say we are rolling out at the meeting? 
   1. Blogs
   2. Reorganization of the Requirements buttons
   3. Creation of the Activity button
   4. Reorganization of Topics - uniform numbering of topics 
   5. Updating Acronyms and Terms in accordance with NPR 7150.2 and NASA-STD-8739.8