GUIDANCE
The Pricing Handbook / Appendix 19C

19. Software Pricing

19C. SAMPLE SOFTWARE WORK BREAKDOWN STRUCTURE

 

The following sample Work Breakdown Structure is based on the sample Software WBS contained in NRaD’s Software Size, Cost and Schedule Estimation Process, modified for this handbook. It is oriented to the development of a MIL-STD-498 or DoD-STD-2167A software product. The sample WBS is very detailed and is meant to be tailored to each project's specific tracking needs and requirements.

  1. PROJECT MANAGEMENT
    1. Project Management Plan
      1. Define task execution plans
      2. Define project schedule/milestones
      3. Define prelim SW functional requirements
      4. Develop project WBS
      5. Define SW management metrics process
      6. Define/allocate project functions
        1. Hardware engineering
        2. Software engineering
        3. Configuration Management
        4. Software Quality Assurance
        5. Inspect, Validate & Verify (IV&V)
        6. Project support
        7. Software metrics
        8. Determine staffing
      7. Determine SWE tool requirements
      8. Determine training requirements
      9. Plan activities/reviews
    2. Management Reporting

     

  2. SOFTWARE ESTIMATION
    1. Preliminary project estimate
      1. Establish cost estimation methodology/tools
      2. ID similar functions/historical projects
      3. Identify project objectives and requirements
      4. Plan the activities/initial WBS
      5. Estimate product size
      6. Estimate cost and effort
      7. Estimate schedule
      8. Identify potential risk areas
      9. Set up cost estimate tracking metrics
      10. Review/refine with project personnel
    2. System Requirements Phase Estimate
      1. Establish software estimate file
      2. Develop top-level SW requirements WBS
      3. Develop baseline software estimates
      4. Formal inspection/approval of estimate
      5. Refine/record/track estimates
    3. Software Requirements Phase Estimate Update
      1. Update top-level design WBS
      2. Update baseline requirements phase estimates
      3. Conduct formal inspection of estimate
      4. Refine/record/track estimates periodically
    4. Design Phase Estimate Update
      1. Develop detailed CUT WBS
      2. Update baseline CUT estimates
      3. Formal inspection of estimate
      4. Refine/record/track estimates periodically
    5. Code and Unit Test Phase Estimate Update
      1. Update detailed WBS
      2. Update/revise estimates
      3. Update/revise risk assessment
      4. Update preliminary maintenance estimate
      5. Refine/record/track estimates periodically
      6. Formal inspection of estimate
    6. Integration Phase Estimate Update
      1. Update detailed WBS
      2. Update/revise estimates
      3. Update/revise risk assessment
      4. Update/revise maintenance estimate
      5. Refine/record/track estimates periodically
      6. Formal inspection of estimate
      7. Post-Deployment Phase Estimate
      8. Close out/report final cost/schedule/size

     

  3. RISK MANAGEMENT
    1. Preliminary Risk Management Plan
      1. Identify potential risk areas
      2. Analyze risk areas
      3. Prioritize risks
      4. Identify risk tracking metrics
      5. Write Plan
    2. Risk Management Plan review/inspection
      1. Update Risk Management Plan
      2. Baseline Risk Management Plan
      3. Update/revise risk assessment

     

  4. SOFTWARE METRICS
    1. Software Metrics plan
      1. Process Effectiveness Metrics
      2. Process Cost Metrics
      3. Cost/Schedule Tracking Metrics
      4. Performance Measurement Indicators
      5. Software Quality Metrics
    2. Update/revise Metrics Plan
    3. Track/analyze cost/schedule/size estimate variances
    4. Track/analyze cost estimating effort and tool costs
    5. Track/analyze cost/schedule variance
    6. Track/analyze requirements and design progress
    7. Track/analyze code and test progress
    8. Track/analyze person-months effort
    9. Track/analyze program size
    10. Track/analyze computer resources utilization
    11. Track/analyze requirements stability
    12. Track/analyze design stability
    13. Track/analyze complexity metrics
    14. Track/analyze modules metrics
    15. Track/analyze testing metrics
    16. Track/analyze defects metrics
    17. Track/analyze product and operational metrics
    18. Formal reports
    19. Report final project analysis

     

  5. SYSTEM ENGINEERING
    1. Analyze operational requirements
    2. Hardware/software trade-off studies
    3. Sizing/timing studies
    4. Define computer resource constraints
      1. Memory
      2. Throughput
      3. I/O channel utilization
      4. I/O throughput
      5. Storage
      6. Database overhead
    5. Identify risks
    6. Preliminary System Segment Specification (SSS)
      1. Define system states
      2. Define modes of operation
      3. Define system capability
      4. Define external inter. requirements
      5. Write external interface descriptions
      6. Define physical characteristics
      7. Define system quality requirements
        1. Reliability
        2. Maintainability
        3. Availability
        4. Environmental conditions
        5. Transportability
        6. Flexibility and expansion
      8. Specify design/construct requirements
      9. Define system workmanship requirements
      10. Define system interchange requirements
      11. Define system safety requirements
      12. Define system security requirements
      13. Determine Government Furnished Equipment
      14. Define computer resource reserve capacity
      15. Define system logistics
      16. Specify personnel requirements
      17. Define training requirements
      18. Determine for each System/Segment
        1. Purpose
        2. Description
        3. Identify capabilities
        4. Identify requirements precedence
        5. Validate and Verify (V&V) requirements
        6. QA provisions
        7. Inspection responsibility
        8. Special Tests and exams
        9. Requirements cross reference
    7. Preliminary Interface Requirement Specification (IRS)
      1. Identify HWCIs/CSCIs interfaces
      2. Draw interface diagram(s)
      3. Identify for each interface
        1. Timing
        2. Protocol
        3. Priority
        4. Unit of measure
        5. Limits/ranges
        6. Data elements
        7. Precision
    8. SSS/IRS inspection(s)/review(s)
    9. System Requirements Review (SRR)
    10. Update SSS
    11. Baseline SSS
    12. Update Preliminary IRS

     

  6. CONFIGURATION MANAGEMENT (CM)
    1. Preliminary CM Plan
    2. CM Plan review/inspection
    3. Update CM Plan
    4. Baseline CM Plan
    5. Set Up Configuration Control Board (CCB)
    6. Conduct/maintain Configuration Status (CS) accounting
      1. Prepare Configuration Status Report (CSR)
    7. Conduct Functional Configuration Audit (FCA)
    8. Conduct Physical Configuration Audit (PCA)
    9. Process Engineering Change Proposals (ECPs)
    10. Process System Change Notices (SCNs)
    11. Generate inputs to the Software Version Document (SVD)
    12. Prepare Version Control Reports

     

  7. SOFTWARE QUALITY ASSURANCE (SQA)
    1. Preliminary SQA Plan
    2. Plan SW quality metrics process
    3. SQA Plan inspection(s)/review(s)
    4. Update SQA Plan
    5. Baseline SQA Plan

     

  8. SOFTWARE DEVELOPMENT PLAN (SDP)
    1. Preliminary SDP
      1. Define formal review procedures/criteria
      2. Define Software Development Library procedures
      3. Define corrective action process
      4. Define Problem/Change Report Format
      5. Define design standards
      6. Define coding standards
      7. Define testing approach
      8. Define requirements traceability process
    2. SDP inspection(s)/review(s)
    3. Update SDP
    4. Baseline SDP

     

  9. INTERFACE REQUIREMENTS
    1. Analyze Preliminary IRS
    2. Interface Design Document
      1. Interface 1 to N define
      2. Data elements
      3. Message descriptions
      4. Priority
      5. Communications protocol
      6. Interface inspection(s)/walk-through(s)
      7. Interface rework
    3. Interface Design Document (IDD) inspection(s)
    4. IDD rework
    5. Participate in Preliminary Design Review (PDR)
    6. Update Interface Design Document
    7. Baseline Interface Design Document

     

  10. DATABASE REQUIREMENTS
    1. Preliminary Database Design Document (DDD)
      1. Analyze database requirements
      2. Identify data requirements
      3. Perform database studies
    2. Database Design Document inspection(s)
    3. Participate in PDR
    4. Update Database Design Document
    5. Baseline Database Design Document

     

  11. DEVELOPMENTAL SOFTWARE
    1. Analyze system requirements
    2. Identify software requirements
    3. Determine derived software requirements
    4. Identify candidate COTS software
    5. Identify candidate reusable software
    6. Perform feasibility studies
    7. Select computer language(s)
    8. Allocate functions/identify CSCIs
    9. Determine software requirement testability
    10. CSCI 1 to N
      1. FUNCTIONAL REQUIREMENTS
        1. Analyze CSCI requirements
        2. Preliminary Software Requirements Specification
          1. Identify internal interfaces
          2. Identify functional/derived requirements
            1. engineering
            2. data elements
            3. safety
            4. security
            5. human engineering
          3. Identify software quality factors
          4. Identify design constraints
          5. Identify qualification methods
          6. Trace requirements to SSS
        3. Software Requirements Specification (SRS) inspection(s)/review(s)
        4. Software Specification Review (SSR)
        5. Update SRS
        6. Baseline SRS
      2. PRELIMINARY DESIGN
        1. Preliminary Design analysis
        2. Identify CSUs
        3. Identify internal interfaces
        4. Identify external interfaces
        5. Preliminary Software Design Documents (SDDs)
          1. Overview
          2. Architecture
          3. Memory/processing time allocation
          4. CSCI design description
            1. CSU 1 - N
              1. Identify allocated requirements
              2. Identify CSUs
              3. Identify relationships between CSUs
              4. Data flow and execution control
              5. Identify derived requirements
              6. Trace requirements to SRS
              7. CSU inspection(s)/walk-through(s)
              8. CSU design rework
          5. Preliminary SDD inspection(s)/review(s)
          6. Preliminary Design Review (PDR)
          7. Update Preliminary SDD
      3. DETAILED DESIGN
        1. Detailed SDD
          1. CSU 1 - N
            1. Describe constraints
            2. Describe input/output data elements
            3. Describe local data elements
            4. Describe interrupts and signals
            5. Describe algorithms
            6. Describe data structures
            7. Describe local datafiles/database
            8. Describe limitations
            9. Trace requirements to Preliminary SDD
            10. CSU inspection(s)/walk-through(s)
            11. CSU design rework
          2. SDD inspection(s)/review(s)
          3. SDD rework
          4. Critical Design Review (CDR)
          5. Update SDD
          6. Baseline SDD
      4. CODE and UNIT TEST
        1. CSU 1 - N
          1. Design/document unit test
          2. Code and compile
          3. Write comments/header
          4. Code inspection(s)/walk-through(s)
          5. Rework
          6. Testing and analysis
          7. Rework
          8. Maintain Software Development Folder (SDF)
          9. Turn over accepted CSU to CM
      5. TEST READINESS REVIEW
      6. CSU INTEGRATION and TESTING
        1. Analyze Software Test Report
        2. Perform necessary rework
        3. Perform CSU regression testing
        4. Update SDFs
      7. TEST READINESS REVIEW
      8. CSCI INTEGRATION and TESTING
        1. Analyze Software Test Report
        2. Perform necessary rework
        3. Perform CSU regression testing
        4. Update SDFs

     

  12. SOFTWARE INTEGRATION & TESTING
    1. Software Test Plan
      1. Determine general test requirements
      2. Determine test classes
        1. stress
        2. timing
        3. erroneous input
        4. maximum capacity
      3. Determine test levels
        1. CSCI
        2. CSCI to CSCI integration
      4. CSCI to HWCI integration
      5. System
      6. Determine test definitions
        1. Test 1 - N
          1. determine objective
          2. determine special requirements
          3. identify test type/class
          4. determine qualification method
          5. cross reference to SRS requirements
          6. determine type of data to record
          7. identify assumptions/constraints
          8. determine test schedule
          9. identify data analysis techniques
    2. Perform Integration & Testing
      1. System
        1. Integrate CSCIs
        2. Write System Test Description
        3. Conduct Test Readiness Review
        4. Perform testing and analysis
        5. Write System Test Report
        6. Rework
        7. Regression testing
        8. CSCI
          1. Integrate CSUs
          2. Write Software Test Description
          3. Conduct Test Readiness Review
          4. Perform testing and analysis
          5. Write Software Test Report
          6. Rework
          7. Regression testing
          8. CSU
            1. Integrate CSUs
            2. Write Software Test Description
            3. Conduct Test Readiness Review
            4. Perform testing and analysis
            5. Write Software Test Report
            6. Testing and analysis
            7. Rework
            8. Regression testing