UNDER CONSTRUCTION
View this section on the website
See edit history of this section
Post feedback on this section
- 1. Introduction
- 2. Institutional Activities
- 3. Activities
- 4. Distribution of SWEHB Pages
- 5. Activity Page Structure
- 6. Alternative Activity Styles
1. Introduction
1.1 Activity Concept
Currently the SWEHB is a collection of pages:
- SWEs - Requirements from NPR 7150.2D along with Rationale, Guidance, Small Projects, Resources, Lessons Learned and Software Assurance, if applicable
- Topics - Additional guidance for appropriate for some SWEs
- PATs - Process Asset Templates - derived from SWEs and Topics
- Other pages - such as Document Contents, FAQs, etc.
Pages include links to other pages based on the relevance of the content on those pages.
The notion of Activity is a natural way to bring together pages from the existing SWEHB into a collection of pages that have a common purpose, an Activity.
1.2 Activity Sequence
Software Engineering activities are conducted in a predictable sequence. This sequence may be a once through / "waterfall" cycle. Or, it may be an iterative or evolutionary series of cycles which build toward a final product. Regardless of the model chosen, individual activities in all these cycles are very similar.
The major activity groupings here give you a quick way to find guidance in the SWEHB to help you satisfy the needs of the development project while also satisfying the requirements of NPR 7150.2.
The activities associated with Software Development are listed in the tabs of this page. Each tab takes you to a list of links to pages where the activity is is explained in more detail. At the lowest level, there is a list of links to specific pages in the SWEHB where details of the activity are explained and more guidance is provided. In some cases, templates or other Process Assets are included to further help you in conducting the activity.
1.1 Activity Groupings
The tabs in this page initially will contain all of the activities in Ch 2 through 5 of NPR 7150.2. This is done to ensure that all SWEs are accounted for.
As the page matures, Topics, PATs, and other resources will be distributed to enrich the content of the activities.
2. Institutional Activities
The Institutional Activities include activities associated with OCE, OSMA, and Centers as well as Software Development Project teams. Each activity contains several requirements (from NPR 7150.2D chapter 2) ensuring that higher levels of management establish certain means and infrastructure for projects to use in their projects. In some cases, requirements for Project teams are included describing the use of the management provided resources in their projects.
For example: Management is responsible for providing training for engineers who develop software. Project teams are responsible for ensuring that team members have had this training (in addition to other training on project specific systems and software) so that they may produce high quality software.
2.1 OCE and OSMA Software Engineering Initiative
Agency Level Activities are intended to provide "enabling support" to project teams. These activities include direction, guidance and support to project teams. The requirements describing these activities are found in NPR 7150.2D Chapter 2. The full activity includes some requirements from Chapters 3 through 5 which are the responsibility of the project teams to satisfy. Many of the names for these Activities come directly from NPR 7150.2D. In a few cases, the names are changed to better express the full scope of the Activity.
| Activity Name | Activity Components |
|---|---|
| OCE and SMA benchmarking and determining the capability and maturity of software development groups. Benchmarking techniques derived from CMMI best practices. | |
| Training at all levels from Agency (engineering practices and related training) down to project needs (training for personnel on using development tools). | |
| Development of repeatable processes and practices for OCE, SMA and Center development activities. | |
Determining the applicability of NPR 7150.2 requirements to a particular project. Includes requirements necessary for particular software classifications. Includes SWEs from section 3.5 Software Classification Assessments. | |
Suggested measurements and practices for software projects. NPR 7150.2D para 5.4.1 Software measurement is a primary tool for managing software processes and evaluating the quality of software products. Analysis of measures provides insight into the capability of the software organization and identifies opportunities for software process and product improvements. Software measurement programs at multiple levels are established to meet measurement objectives. The requirements below are designed to reinforce the use of measurement at the project, Center software organization, and NASA Chief Engineer levels to assist in managing projects, assuring quality, and improving software engineering practices. | |
NPR 7150.2D para 2.1.1.6 The NASA OCE shall maintain an Agency-wide process asset library of applicable best practices and process templates for all size projects | |
| Requirements related to the licensing, sharing and reuse of some or all of software products. |
3. Activities
The Software and Assurance activities associated with Software Development Projects are listed as links below.
Each page will contain an activity description and contain links to all the associated SWEs, Topics, PATs, and other pages in the SWEHB that are associated with the activity.
3.1 Software Activity Pages
Links go to existing pages. Underlined (Red in edit mode) links have not yet been created. All activity pages to be children of the Software Project Activities page.
Content structure is contained in the Activity Template.
Project Software Activities
| Activity Name | Activity Components |
|---|---|
| Life Cycle Planning | NPR 7150.2D para 3.1.1 Software life cycle planning covers the software aspects of a project from inception through retirement. The software life cycle planning is an organizing process that considers the software as a whole and provides the planning activities required to ensure a coordinated, well-engineered process for defining and implementing project activities. These processes, plans, and activities are coordinated within the project. At project conception, software needs for the project are analyzed, including acquisition, supply, development, operation, maintenance, retirement, decommissioning, and supporting activities and processes. The software effort is scoped, the development processes defined, measurements defined, and activities are documented in software planning documents. |
| Software Peer Reviews and Inspections | NPR 7150.2D para 5.3.1 Software peer reviews and inspections are the in-process technical examination of work products by peers to find and eliminate defects early in the life cycle. Software peer reviews and inspections are performed following defined procedures covering the preparation for the review, the review itself is conducted, results are recorded, results are reported, and completion criteria is certified. When planning the composition of a software peer review or inspection team, consider including software testing, system testing, software assurance, software safety, software cybersecurity, and software IV&V personnel. |
| Used when software is acquired or secured from outside sources. | |
| Used for monitoring progress and keeping the project under control through minor adjustments | |
| Used for establishing cost of development of the software products. It includes multiple models and parameters, direct and indirect costs, for the work so that tracking can be effectively done. | |
| Used for establishing and maintaining the development and delivery schedule. Takes into account dependencies on other projects and programs. Includes time for reviews and tracking of issues to resolution, | |
| Ensures that the project follows established processes and practices. Includes audits and corrective actions. | |
| Independent testing and evaluation of software against requirements and performance criteria. Applicable to certain categories of projects. Includes planning, execution of tests and tracking issues and risks to closure. | |
| Includes determining of software is considered safety-critical, and implementing additional requirements to ensure safety of the software product. | |
Evaluation of software requirements and planning for their realization in the final software products. | |
NPR 7150.2D para 4.2.1 Experience confirms that the quality and longevity of a software-reliant system is primarily determined by its architecture. The software architecture underpins a system’s software design and code; it represents the earliest design decisions, ones that are difficult and costly to change later. The transformation of the derived and allocated requirements into the software architecture results in the basis for all software development work. | |
NPR 7150.2D para 4.3.1 Software design is the process of defining the software architecture, components, modules, interfaces, and data for a software system to satisfy specified requirements. The software architecture is the fundamental organization of a system embodied in its components, their relationships to each other and the environment, and the principles guiding its design and evolution. The software architectural design is concerned with creating a strong overall structure for software entities that fulfill the allocated system and software-level requirements. Typical views captured in an architectural design include the decomposition of the software subsystem into design entities, computer software configuration items, definitions of external and internal interfaces, dependency relationships among entities and system resources, and finite state machines. The design should be further refined into lower-level entities that permit the implementation by coding in a programming language. Typical attributes that are documented for lower-level entities include the identifier, type, purpose, function, constraints, subordinates, dependencies, interface, resources, processing, and data. Rigorous specification languages, graphical representations, and related tools have been developed to support the evaluation of critical properties at the design level. Projects are encouraged to take advantage of these improved design techniques to prevent and eliminate errors as early in the life cycle as possible. Software, developed or purchased, has additional requirements to comply with from Section 508 of the Rehabilitation Act, as defined in NPR 2800.2. | |
| NPR 7150.2D para 4.4.1 Software implementation consists of implementing the requirements and design into code, data, and records. Software implementation also consists of following coding methods and standards. Unit testing is also usually a part of software implementation (unit testing can also be conducted during the testing phase). |
Includes integration of modules into a final deliverable package and testing of that package to determine if it is ready for delivery. NPR 7150.2D para 4.5.1 The purpose of testing is to verify the software functionality and remove defects. Testing verifies the code against the requirements and the design to ensure that the requirements are implemented. Testing also identifies problems and defects that are corrected and tracked to closure before product delivery. Testing also validates that the software operates appropriately in the intended environment. Please note for Class A software there are additional software test requirements and software integration requirements as defined in NPR 8705.2. | |
| Final determination of the readiness of the software for release. Includes acceptance testing, and other readiness criteria. |
| Addresses any ongoing maintenance considerations for the software products. NPR 7150.2D para 4.6.1 Planning for operations, maintenance, and retirement are typically considered throughout the software life cycle. Operational concepts and scenarios are derived from customer requirements and validated in the operational or simulated environment. Software maintenance activities sustain the software product after the product is delivered to the customer until retirement. |
| Addresses any ongoing operations considerations for the software products NPR 7150.2D para 4.6.1 Planning for operations, maintenance, and retirement are typically considered throughout the software life cycle. Operational concepts and scenarios are derived from customer requirements and validated in the operational or simulated environment. Software maintenance activities sustain the software product after the product is delivered to the customer until retirement. |
| Addresses any retirement or replacement considerations for the software products NPR 7150.2D para 4.6.1 Planning for operations, maintenance, and retirement are typically considered throughout the software life cycle. Operational concepts and scenarios are derived from customer requirements and validated in the operational or simulated environment. Software maintenance activities sustain the software product after the product is delivered to the customer until retirement. |
Includes control over software products during development along with any associated work products. NPR 7150.2D para 5.1.1 Software Configuration Management (SCM) is the process of applying configuration management throughout the software life cycle to ensure the completeness and correctness of software configuration items. SCM applies technical and administrative direction and surveillance to identify and record the functional and physical characteristics of software configuration items, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. SCM establishes and maintains the integrity of the products of a software project throughout the software life cycle. Use of standard Center or organizational SCM processes and procedures is encouraged where applicable. | |
Planning, monitoring and controlling risks which could impact the software products. NPR 7150.2D para 5.2 Record, analyze, plan, track, control, and communicate all of the software risks and mitigation plans. | |
Identification and tracking of non-conforming products and software. Includes ensuring that defects are removed or fixed. | |
| Includes the closing of projects and dispositioning work products that may need to be used in subsequent projects related to the software products. NPR 7150.2D para 4.6.1 Planning for operations, maintenance, and retirement are typically considered throughout the software life cycle. Operational concepts and scenarios are derived from customer requirements and validated in the operational or simulated environment. Software maintenance activities sustain the software product after the product is delivered to the customer until retirement. |
3.2 Software Assurance Activities
4.1 Software Assurance Description
4.1.1 The Software Assurance activities provide a level of confidence that software is free from vulnerabilities, either intentionally designed into the software or accidentally inserted at any time during its life cycle, that the software functions in an intended manner, and that the software does not function in an unintended manner. The objectives of the Software Assurance and Software Safety Standard include the following:
a. Ensuring that the processes, procedures, and products used to produce and sustain the software conform to all specified requirements and standards that govern those processes, procedures, and products.
(a) A set of activities that assess adherence to, and the adequacy of the software processes used to develop and modify software products.
(b) A set of activities that define and assess the adequacy of software processes to provide evidence that establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended purposes.
b. Determining the degree of software quality obtained by the software products.
c. Ensuring that the software systems are safe and that the software safety-critical requirements are followed.
d. Ensuring that the software systems are secure.
e. Employing rigorous analysis and testing methodologies to identify objective evidence and conclusions to provide an independent assessment of critical products and processes throughout the life cycle.
4.1.2 Project and SMA Management support of the software assurance function is essential for software assurance, software safety, and IV&V processes to be effective. The software assurance, software safety, and IV&V support include the following:
a. The Project and SMA Management are familiar with and understand the software assurance, software safety, and IV&V function’s purposes, concepts, practices, and needs.
b. The Project and SMA Management provide the software assurance, software safety, and IV&V activities with skilled resources (people, equipment, knowledge, methods, facilities, and tools) to accomplish their project responsibilities.
c. The Project and SMA Management act upon information provided by the software assurance, software safety, and IV&V function throughout a project.
4.1.3 The Software Assurance and Software Safety Standard’s requirements apply to organizations in their roles as both Acquirers and Providers.
Many of the activities of Software Assurance run parallel to Software Development Activities. In fact, development activities that have specific SA participation have a tab in the SWE specifically for Software Assurance participation.
To further this relationship, the activities below draw on the SA requirements and tasks from NASA-STD-8739.8B and are associated with the SWEs in NPR 7150.2D.
| Activity Name | Activity Components |
|---|---|
Planning of Software Assurance activities in a Software Development Project are done in a collaborative fashion along with the Software Development team. It includes cost estimates and schedules. | |
| Software Assurance tasks found in Development Activities which audit the processes and work products associated with individual SWEs. |
| Software Assurance Analysis tasks in Software Requirements and related activities which further improve the quality of the Software Requirements. Reducing requirement ambiguity, defects, and associated re-work in the of the software. |
| Software Assurance Analysis tasks in Software Design and related activities which further improve the quality of the Software Design. Reducing defects and associated re-work in the design of the software. |
| Software Assurance Analysis tasks in Software Source Code and related activities which further improve the quality of the Software Source Code. Reducing defects and associated re-work in the of the software. |
| Software Assurance Analysis tasks in Software Testing and related activities which further improve the quality of the Software Testing. Improving test coverage, reducing test defects and associated re-work in the of the software. |
| Software Assurance Analysis tasks in Software Reporting and related activities which further improve the overall Software Development Processes. Improving the Development Processes reduces defects and associated re-work in the of the software. |
| Independent testing and evaluation of software against requirements and performance criteria. Applicable to certain categories of projects. Includes planning, execution of tests and tracking issues and risks to closure. | |
| |
| SA Test Witnessing |
4. Distribution of SWEHB pages
This tab contains a distribution of SWEs into Activities. Each SWE in the SWEHBVD is in the table. The table lists the Primary Activity in which the SWE is located. Also, for those SWEs that are associated with other activities, the associated activities are listed. This table will be used to distribute the SWEs into activities ensuring that none are lost in the distribution process.
Under Construction in separate spreadsheet. This table will be updated periodically as the spreadsheet is completed.
4.1 SWE pages
4.2 Topic Pages
Includes Recommended Content pages from some of the topic pages.
| Topic # | Activity | Associated Activities |
| 6.1 - Design for Safety Checklist | SA Safety and Hazard Analysis | |
| 6.2 - Checklist for General Software Safety Requirements | SA Safety and Hazard Analysis | |
| 6.3 - Checklist for Choosing a Real Time Operating System (RTOS) | Implementation and Unit Testing | |
| 6.4 - Checklist for Choosing Off-The Shelf Software (OTS) | Implementation and Unit Testing | |
| 6.5 - Checklist for C Programming Practices | Implementation and Unit Testing | |
| 6.6 - Checklist for C++ Programming Practices | Implementation and Unit Testing | |
| 6.7 - Checklist for Ada Programming Practices | Implementation and Unit Testing | |
| 6.8 - Checklist for Fortran Programming Practices | Implementation and Unit Testing | |
| 6.9 - Checklist for Generic (Non-Language-Specific) Programming Practices | Implementation and Unit Testing | |
| 6.10 - Checklist for General Good Programming Practices | Implementation and Unit Testing | |
| 6.11 - Examples of Programming Practices for Exception Handling | Implementation and Unit Testing | |
| 7.1 - History and Overview of the Software Process Improvement (SPI) Effort | Process Definition | |
| 7.2 - Classification and Safety-Criticality | Requirement Mapping, Tailoring, and Classification | |
| 7.3 - Acquisition Guidance | Acquisition | |
| 7.4 - Flowdown of NPR Requirements on Contracts and to Other Centers in Multi-Center Projects | Life Cycle Planning | Acquisition |
| 7.5 - Work Breakdown Structures That Include Software | Software Scheduling | Cost Estimation |
| 7.6 - Software Test Estimation and Testing Levels | Software Scheduling | Cost Estimation |
| 7.7 - Software Architecture Description | Software Architecture | |
| 7.8 - Maturity of Life-Cycle Products at Milestone Reviews | Software Scheduling | Life Cycle Planning |
| 7.9 - Entrance and Exit Criteria | Software Scheduling | Life Cycle Planning |
| 7.10 - Peer Review and Inspections Including Checklists | Peer Reviews and Inspections | |
| 7.11 - SWE History | n/a | |
| 7.12 - Retired | n/a | |
| 7.13 - Transitioning to a Higher Class | Requirement Mapping, Tailoring, and Classification | |
| 7.14 - Implementing Measurement Requirements and Analysis for Projects | Measurements and Metrics | |
| 7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009 | Software Architecture | Software Design |
| 7.16 - Appendix C. Requirements Mapping and Compliance Matrix | Requirement Mapping, Tailoring, and Classification | |
| 7.17 - 7150.2C Appendices (Definitions, References, etc.) | n/a | |
| 7.18 - Documentation Guidance | n/a | |
| CR-PR - Software Change Request - Problem Report | Non-Conformance and Defect Management | |
| IDD - Interface Design Description | Software Architecture | Software Design |
| Inspect - Software Inspection, Peer Reviews, Inspections | Peer Reviews and Inspections | |
| Maint - Software Maintenance Plan | Maintenance | |
| Metrics - Software Metrics Report | Measurements and Metrics | |
| SCMP - Software Configuration Management Plan | Configuration Management | |
| SDD - Software Data Dictionary | Software Design | |
| SDP-SMP - Software Development - Management Plan | Life Cycle Planning | |
| SRS - Software Requirements Specification | Software Requirements | |
| STP - Software Test Plan | Integration and Testing | |
| STR - Software Test Report | Integration and Testing | |
| SUM - Software User Manual | Operations | Acceptance and Release |
| SwDD - Software Design Description | Software Design | |
| Test - Software Test Procedures | Integration and Testing | |
| Train - Software Training Plan | Training | |
| VDD - Version Description Document | Acceptance and Release | |
| 7.19 - Software Risk Management Checklists | Risk Management | |
| 7.20 - Assessing - Meets the Intent | Risk Management | |
| 7.21 - Multi-condition Software Requirements | Integration and Testing | Safety-Critical Software |
| 8.1 - Off Nonimal Testing | SA Design Analysis | SA SW Testing Analysis |
| 8.2 - Software Reliability | SA Design Analysis | |
| 8.3 - Organizational Goals of Software Assurance Metrics | Measurements and Metrics | |
| 8.4 - Additional Requirements Considerations for Use with Safety-Critical Software | SA Safety and Hazard Analysis | |
| 8.5 - SW Failure Modes and Effects Analysis | SA SW Requirements Analysis | SA Safety and Hazard Analysis |
| 8.6 - IV&V Surveillance | IV&V | Acquisition |
| 8.7 - Software Fault Tree Analysis | SA Safety and Hazard Analysis | |
| 8.8 - COTS Software Safety Considerations | SA Safety and Hazard Analysis | |
| 8.9 - Software Safety Analysis | SA Safety and Hazard Analysis | |
| 8.10 - Facility Software Safety Considerations | SA Safety and Hazard Analysis | |
| 8.11 - Auto-Generated Code | Implementation and Unit Testing | |
| 8.12 - Basics of Software Auditing | SA Auditing | |
| 8.13 Test Witnessing | SA SW Testing Analysis | SA Auditing |
| 8.14 SA Tasking for NPR 7150.2B | ? | |
| 8.15 - SA Tasking Checklist Tool | ? | |
| 8.16 - SA Products | n/a | |
| Audit Reports | SA Reporting | |
| Checklists and Guidance Lists | n/a | |
| IV&V Program Execution Plan | SA Planning | IV&V |
| Objective Evidence | All SA Activities | |
| Software Assurance Plan | SA Planning | |
| Software Assurance Status Reports | SA Reporting | |
| Software Design Analysis | SA Design Analysis | |
| Software Requirements Analysis | SA SW Requirements Analysis | |
| Software Safety and Hazard Analysis | SA Safety and Hazard Analysis | |
| Source Code Quality Analysis | SA SW Source Code Analysis | |
| Testing Analysis | SA SW Testing Analysis | |
| 8.17 - Software Safety Audit Checklists | SA Auditing | |
| 8.18 - SA Suggested Metrics | Measurements and Metrics | |
| 8.19 - Dead / Dormant Code and Safety Critical Software | Licensing, Sharing and Reuse | SA Safety and Hazard Analysis |
| 8.20 - Safety Specific Activities in Each Phase | SA Safety and Hazard Analysis | |
| 8.21 - Software Hazard Causes | SA Safety and Hazard Analysis | |
| 8.22 - Hazardous Commands | SA Safety and Hazard Analysis | |
| 8.23 - Software Contents of a Certification of Flight Readiness | Acceptance and Release | |
| Software Design Principles | Software Design | SA Design Analysis |
| Software Safety and Design Principles | SA Design Analysis | Software Design |
| Coding Standards | Software Design | SA Design Analysis |
| Command Receipt Acknowledgement | Software Design | SA Design Analysis |
| Data Interface Integrity | Software Design | SA Design Analysis |
| Dead Code Exclusion | Software Design | SA Design Analysis |
| Fault Detection and Response | Software Design | SA Design Analysis |
| Flight Software Modification | Software Design | SA Design Analysis |
| Incorrect Memory Use or Access | Software Design | SA Design Analysis |
| Initialization - Safe Mode | Software Design | SA Design Analysis |
| Invalid Data Handling | Software Design | SA Design Analysis |
| Resource Margins | Software Design | SA Design Analysis |
| Resource Oversubscription | Software Design | SA Design Analysis |
| Resource Usage Measurement | Software Design | SA Design Analysis |
| Safe Transitions | Software Design | SA Design Analysis |
| Thread Safety | Software Design | SA Design Analysis |
4.3 PAT Pages
4.4 Other Pages
Add page/groups from 8739.8B
- SA Tasks
- IV&V Overview and Requirements
- SA Tailoring Standard Requirements
5. Activity Page Structure
We will need to decide how to consistently display information about activities. Since we have two groups involved with the Activity pages. There are multiple ways of displaying the information related to an Activity.
5.1 Common Elements in the Activity Structure
| Tab | Title | Content |
| 1 | Introduction | Brief description of the activity and its scope. If applicable, a quote from the NPR or STD is used to amplify the description. |
| 1.1 | Inputs | List of some of the inputs from other activities that are necessary for the activity to begin. |
| 1.2 | Predecessor Activities | List of some of the other activities that must be started (not necessarily completed) so that this activity may begin. |
| 1.3 | Outputs | List of some of the outputs or work products of the activity. These are typically used as inputs by the downstream activity. In some cases there is a supporting SWE associated with the work product. |
| 1.4 | Successor Activities | Links to Activities which might be started or supported by this activity. |
| 1.5 | Activity Repetition | Describe what conditions determine if the activity needs to be repeated, such as re-planning after a change in requirements or schedule constraints.
|
| 1.6 | Center Resources from SPAN | Add links to SPAN activity pages that are appropriate for this activity. Use links from the Activity section of the SPAN front page. SPAN. This further differentiates SWEHB from SPAN in the sense that PATs are templates derived from SWEHB guidance, SPAN assets and templates are Center defined and developed resources. |
| 2 | Defining the Activity | This tab contains the links to pages in the SWEHB that are at the heart of the activity. |
| 2.1 | SWEs | This section contains the links to SWE pages that form the heart of the activity. |
| 2.2 | Topics and other Supporting Materials | This section is for SWEHB pages, other than SWEs, that directly support the activity. This section contains Topics, document content pages, PATs, and other pages. |
| 2.3 | Other Associated SWEs, Topics, etc. | Includes other SWEHB pages that are indirectly associated with the activity. May include SWEs, Topics, document definition pages, PATs, etc. They may have been mentioned in the guidance of another page. |
5.1 Combined Format
In the combined format, Activities that are closely related such as Planning may have a combined format. Tab 2 information is associated with both Software Engineering and Software Assurance content. An additional tab is provided to include SA tasks (from the included SWEs) that apply to the activity.
A risk associated with this way of displaying Activity information is that it may be difficult to easily pick out the SA pieces from the Engineering pieces of an activity. It will be critical to specify who is involved in each element of the activity. An example of this can be found in Planning where the Engineering and Assurance elements of the activity run in parallel and have considerable overlap. Engineering will plan certain processes and then Assurance will plan the auditing of those processes.
5.2 Separate Formats
In separate formats, there is only one template. The indication of who is performing the activity is indicated in the title of the Activity. In this example, SA activities include the SA Task lists from the associated SWEs. Software Engineering Activities would not have SA Tasks displayed in section 2.1.
6. Alternative Activity Styles
The Activity is a new concept for organizing content in SWEHB. In this tab, we explore various ways to display activity content while keeping several requirements in mind:
- minimize the creation of new content by reusing existing content as much as possible.
- minimize training necessary to use the activity, it should be obvious how to use the activity and its information
- make the activity inclusive so that Software Developers and Software Assurance and others can use it easily
6.1 Initial Reactions to First Two Templates
At our 12/13/2023 meeting, there was some discussion about the organization and content of the two templates reviewed. It was not clear how these templates would accomplish the inclusivity requirement above. In this tab, we will explore some alternatives to these first two templates to attempt to get an Activity organization that satisfies all of the requirements.
