Page 1 of 4. Showing 36 results (0.008 seconds)
SWE-095 - Directorate Measurement System
1. Requirements 4.4.6 Each NASA Mission Directorate shall establish its own software measurement system to include the minimum reporting requirements in SWE … and define a software measurement system with reporting requirements necessary to manage and provide insight needed on Mission Directorate projects. The minimumSWE-055 - Requirements Validation
Learned database notes the following: Mars Climate Orbiter Mishap Investigation Board - Phase I Report. Lesson Number 0641: A mishap could have been prevented … . cd smproj reports sa sre tool ansc asc bsc bnsc csc cnsc dsc g f esc ll pi pm sar Migration of unmigrated content due to installation of a new pluginSWE-118 - Software Test Report
1. Requirements 5.3.2.1 The Software Test Report shall include: a. Overview of the test results: (1) Overall evaluation of the software as shown … on the outcome of those tests. Test reports capture that information and more for purposes including but not limited to: Documenting what was done and howSWE-092 - Measurement Collection and Storage
are expensive to collect, report, and analyze so if no one is using a metric, producing it is a waste of time and money. Each organization or Mission Directorate … specific criteria, definitions, and a description of how to perform each step in the collection process. "When we use terms like defect, problem reportSWE-054 - Corrective Action for Inconsistencies
is not readily apparent. This analysis could be similar to that used for change requests and problem reports (see SWE-113). Sample corrective actions include: Split … on the project: A system or process for entering and tracking corrective actions (e.g., Problem Report and Corrective Action (PRACA), change request/problemSWE-040 - Access to Software Products
to be provided. See SWE-117 for report requirements. Software cost data and parameters Costing data is typically organized and supplied according to the contract SOW … for the environment. See SWE-070 and SWE-136. Results of software testing Refer to SWE-067 and SWE-069 for the testing reporting requirements. ResultsSWE-053 - Manage Requirements Changes
changes to requirements. Many of these tools will keep version histories and are able to provide reports on the changes. Some of those reports may be useful … in the Faster, Better, Cheaper mode: Requirement changes without adequate resource adjustment." cd smproj reports sa sre tool analysis ansc asc bsc bnsc cscSWE-065 - Test Plan, Procedures, Reports
. Software Test Report(s). 1.1 Notes The requirements for the content of a Software Test Plan, Software Test Procedure, and Software Test Report are defined … reports ensure that results of verification activities are documented and stored in the configuration management system for use in acceptance reviews or readinessSWE-069 - Document Defects and Track
the following to allow report generation from the defect data: Date reported. User information (name, contact information, etc.). Organizational data (department who … for additional information for prioritizing defects. Use constructive communication. Keep channels of communication open between those who enter problem reportsSWE-018 - Software Activities Review
dispositioned and/or closed. The issue can be tracked in a suitable tool, such as a risk management system, a configuration management system, or a problem reporting … that discrepancies between the review team and the Project can be resolved immediately.". sam ivv csma cce cd smproj reports records sa process ansc asc bsc bnsc csc
