IEEE Std 1062, 1998 and 1062-1993 and 1062-1998 aIEEE Recommended Practice for Software Acquisition -Description

Abstract: A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.

Keywords: acquirer, modified-off-the-shelf software, software acquisition life cycle, software acquisition process, supplier

Content

• 1. Overview
• • 1.1 Scope
  • 1.2 Terminology
• 2. References
• 3. Definitions
• 4. Introducing the software acquisition process
• • 4.1 Software acquisition life cycle
  • 4.2 Nine steps in acquiring quality software
• 5. Software acquisition process
• • 5.1 Planning organizational strategy
  • • 5.1.1 Initiate a planning process
    • 5.1.2 Set organizational strategy
    • 5.1.3 Establish general practices
  • 5.2 Implementing organization's process
  • • 5.2.1 Establish a software acquisition process
    • 5.2.2 Include contracting practices
    • 5.2.3 Obtain services from other organizations
    • 5.2.4 Assign responsibility for success of software acquisition process
    • 5.2.5 Tailor the process
  • 5.3 Defining the software requirements
  • • 5.3.1 Define the software being acquired
    • 5.3.2 Establish proposal evaluation standards
    • 5.3.3 Establish acquirer and supplier obligations
    • 5.3.4 Develop plans to evaluate and accept software and services
    • 5.3.5 Develop contingency plans
  • 5.4 Identifying potential suppliers
  • • 5.4.1 Gather information on available software products
    • 5.4.2 Evaluate software during a demonstration
    • 5.4.3 Survey users of the supplier's software
    • 5.4.4 Review performance data from previous contracts
    • 5.4.5 Survey several suppliers' offerings
  • 5.5 Preparing contract requirements
  • • 5.5.1 Determine the quality of the work
    • 5.5.2 Determine how payment is to be made
    • 5.5.3 Determine nonperformance remedies
    • 5.5.4 Prepare contract provisions
    • 5.5.5 Review contract provisions with legal counsel
  • 5.6 Evaluating proposals and selecting supplier
  • • 5.6.1 Evaluate supplier proposals
    • 5.6.2 Visit supplier facilities
    • 5.6.3 Select a qualified supplier
    • 5.6.4 Negotiate the contract
  • 5.7 Managing for supplier performance
  • • 5.7.1 Manage the contract during execution
    • 5.7.2 Monitor supplier's progress
  • 5.8 Accepting the software
  • • 5.8.1 Evaluate and test the software
    • 5.8.2 Maintain control over the test
    • 5.8.3 Establish an acceptance process
  • 5.9 Using the software
  • • 5.9.1 Evaluate contracting practices
    • 5.9.2 Evaluate user satisfaction
    • 5.9.3 Evaluate supplier performance
• 6. Summary
• Annex A Checklists to assist organizations in establishing their own software acquisition process
• • A.1 Checklist 1: Organizational strategy
  • A.2 Checklist 2: Define the software
  • A.3 Checklist 3: Supplier evaluation
  • A.4 Checklist 4: Supplier and acquirer obligations
  • A.5 Checklist 5: Quality and maintenance plans
  • A.6 Checklist 6: User survey
  • A.7 Checklist 7: Suuplier performance standrard
  • A.8 Checklist 8: Contract payments
  • A.9 Checklist 9: Monitor supplier progress
  • A.10 Checklist 10: Software evaluation
  • A.11 Checklist 11: Software test
  • A.12 Checklist 12: Software acceptance
• Annex B Acquisition Plan guidelines
• • B.1 (AP Section 1) Introduction
  • B.2 (AP Section 2) References
  • B.3 (AP Section 3) Definitions
  • B.4 (AP Section 4) Software acquisition overview
  • • B.4.1 (AP Section 4.1) Organization
    • B.4.2 (AP Section 4.2) Schedule
    • B.4.3 (AP Section 4.4) Resource summary
    • B.4.4 (AP Section 4.4) Responsibilities
    • B.4.5 (AP Section 4.5) Tools, techniques, and methods
  • B.5 (AP Section 5) Software acquisition process
  • • B.5.1 (AP Sections 5.1 through 5.9) Software acquisition process
  • B.6 (AP Section 6) Software acquisition reporting requirements
  • B.7 (AP Section 7) Software acquisition management requirements
  • • B.7.1 (AP Section 7.1) Anomaly resolution and reporting
    • B.7.2 (AP Section 7.2) Deviation policy
    • B.7.3 (AP Section 7.3) Control procedures
    • B.7.4 (AP Section 7.4) Standards, practices, and conventions
    • B.7.5 (AP Section 7.5) Performance tracking
    • B.7.6 (AP Section 7.6) Quality control of the Plan
  • B.8 (AP Section 8) Software acquisition documentation requirements
• Annex C Guidelines for compliance with IEEE/EIA 12207.1-1997
• • C.1 Overview
  • • C.1.1 Scope and purpose
  • C.2 Correlation
  • • C.2.1 Terminology correlation
    • C.2.2 Process correlation
    • C.2.3 Life cycle data correlation for Software Acquisition Plans
    • C.2.4 Life cycle data correlation between other data in IEEE/EIA 12207.1-1997 and IEEE Std 1062, 1998 Edition
  • C.3 Document compliance
  • • C.3.1 Compliance with information requirements of IEEE/EIA 12207.0-1996
    • C.3.2 Compliance with generic content guidelines of IEEE/EIA 12207.1-1997
    • C.3.3 Compliance with specific content requirements of IEEE/EIA 12207.1-1997
    • C.3.4 Compliance with life cycle data objectives
  • C.4 Conclusion

links: [Standard Status] - [Purchase] - [PDF^*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only