Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Error formatting macro: alias: java.lang.NullPointerException
SWE-034 - Acceptance Criteria
Unknown macro: {div3}

1. Requirements

2.5.3 The project shall define and document or record the acceptance criteria and conditions for the software.

1.1 Notes">1.1 Notes

NPR 7150.2A does not include any notes for this requirement.

1.2 Applicability Across Classes





























Key:    A_SC = Class A Software, Safety-Critical | A_NSC = Class A Software, Not Safety-Critical | ... | - Applicable | - Not Applicable
X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

Unknown macro: {div3}

2. Rationale

Software development teams can better organize their development tasks if they have well defined plans for software activities. Customers and project personnel must include pre-determined criteria in these plans to evaluate the software work products. These criteria include clearly understanding what the customer wants the product to do and what constitutes an acceptable software product. The development team should document the agreed-to acceptance criteria and the planned activities in a software acceptance plan contained in the Software Development/Management Plan (see [SWE-102]) or a separate Verification and Validation Plan, as a formal means of guiding these activities.

Unknown macro: {div3}

3. Guidance

'Acceptance criteria' is defined (1)as the criteria that a system or component must satisfy in order to be accepted by a user, customer, or other authorized entity (ISO/IEC/IEEE 24765:2010 Systems and software engineering - Vocabulary), and, (2) those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted (A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fourth Edition). The purpose of this requirement is for the software development team to work with the customer up front to define the criteria to be used for software acceptance. The acceptance criteria and timing can help

&nbsp &nbsp &nbsp &nbsp * define the software support manpower levels on a project
&nbsp &nbsp &nbsp &nbsp * determine the 'hand over' for the software development organization to a software operation and maintenance organization,
&nbsp &nbsp &nbsp &nbsp * help define what a contractor has to do to complete before flight certification can be achieved

Unknown macro: {div3}

4. Small Projects


Unknown macro: {div3}

5. Resources

  1. add
  2. add

5.1 Tools


Unknown macro: {div3}

6. Lessons Learned


  • No labels