anova logo

Software Development Project

Artifact Sets

Engineering Set

Requirements Set

1. Vision document

2. Requirements model

Design Set

1. Design model

2. Test model

3. Software architecture description

Implementation Set

1. Source code baselines

2. Associated compile-time files

3. Component executables

Deployment Set

1. Integrated product executable baselines

2. Associated run-time files

3. User manual

Management Set

Planning Artifacts


1. Work/deliverable breakdown structure

2. Business case

3. Release specifications

4. Software development plan

Operational Artifacts


5. Release descriptions

6. Status assessments

7. Software change order database

8. Deployment documents

9. Environment



Engineering Set

Vision Document Outline

I. Feature set description

A. Precedence and priority

II. Quality attributers and ranges

III. Required constraints

A. External interfaces

IV. Evolutionary appendices

A. Use cases

1. Primary scenarios

2. Acceptance criteria and tolerances

B. Desired freedoms (potential change scenarios)



Architecture description Outline

I. Architecture overview

A. Objectives

B. Constrints

C. Freedoms

II. Architecture views

A. Design view

B. Process view

C. Component view

D. Deployment view

III. Architecture interactions

A. Operational concept under primary scenarios

B. Operational concept under secondary scenarios

C. Operational concept under anomalous scenarios

IV. Architecture performance

V. Rationale, trade-offs, and other sunstantiation




Management Set

Business Case Outline

I. Content (domain, market, scope)

II. Technical approach

A. Feature set achievement plan

B. Quality achievement plan

C. Engineering trade-offs and technical risks

III. Management Approach

A. Schedule and schedule risk assessment

B. Objective measures of success

IV. Evolutionary appendices

A. Financial forecast

1. Cost estimate

2. Revenue estimate

3. Bases of estimates



Release Specification Outline

I. Iteration Content

II. Measurable objectives

A. Evaluation criteria

B. Follow-through approach

III. Demonstration plan

A. Schedule of activities

B. Team responsibilities

IV Operational scenarios

A. Demonstration procedures

B. Traceability to vision and business case



Release Description Outline

I. Content

A. Release baseline content

B. Release metrics

II. Release notes

A. Release specific constraints or limitations

B. New feature set

III. Assessment results

A. Substantiation of passed evaluation criteria

B. Follow up plans for failed evaluation criteria

C. Recommendations for next release

IV Outstanding issues

A. Action items

B. Post mortem summary of lessons learned



Software Development Plan Outline

I. Content (scope, objectives)

II. Software development process

A. Project primitives

1. Life-cycle phases

2. Artifacts

3. Work flows

4. Checkpoints

B. Major milestone scope and content

C. Process improvement procedures

III. Software engineering environment

A. Process automation (hardware and software resource configuration)

B. Resource allocation procedures (sharing across organizations, security access)

IV Software change management

A. Configuration control board plan and procedures

B. Software change order definitions and procedures

C. Configuration baseline definitions and procedures

V. Software assessment

A. Metrics collection and reporting procedures

B. Risk management procedures (identification, tracking and resolution)

C. Status assessment plan

D. Acceptance test plan

VI. Standards and procedures

A. Standards and procedures for technical artifacts

VII. Evolutionary appendices

A. Minor milestone scope and content

B. Human resources (organization, staffing plan, training plan)