Feb 2013Lesson 38 Software Acquisition Development
Feb 2013
Lesson 3.8: Software Acquisition: Development and Management
The Linkage Between Systems Engineering and Software Development
The DOD policy is to design and develop software based on Systems Engineering principles.
Some examples of the linkages based on these principles are shown below.
Why Worry About Software?
Software is an integral part of most defense systems. Following are two reasons why software development requires special attention:
●
●
Software development can be difficult to monitor because it is a complex, changeable, and invisible product.
Once software development is late, adding more resources typically results in making the project even later.
Software Risk Management
Most software development projects are very large and complex. Breaking a software-intensive project into more manageable parts helps the people involved better understand the tasks and resources needed. By understanding the complexity of an effort, managers are better able to plan and manage the risk.
1
Feb 2013
Software Items (SIs): The Building Blocks
As part of the Systems Engineering Process, the software is usually broken down into smaller building blocks called Software Items (SIs). After being developed and individually tested,
Software Items are integrated with the hardware and ultimately the entire system.
A Software Item (SI) is a collection of software that performs closely related functions. Each SI is uniquely designated throughout the life cycle for purposes of:
●
●
●
●
●
Managing requirements.
Conducting qualification testing.
Controlling interfaces.
Ensuring configuration management.
Mitigating risk.
Note: In the past, Software Items were called Computer Software Configuration Items
(CSCI).
SIs and Work Breakdown Structures
As you learned in a previous lesson, a Work Breakdown Structure (WBS) divides complex projects into pieces so that risks can be identified and managed.
As illustrated below, WBS can be used to organize the Software Items (SIs)
Lesson 3.8: Software Acquisition: Development and Management
The Linkage Between Systems Engineering and Software Development
The DOD policy is to design and develop software based on Systems Engineering principles.
Some examples of the linkages based on these principles are shown below.
Why Worry About Software?
Software is an integral part of most defense systems. Following are two reasons why software development requires special attention:
●
●
Software development can be difficult to monitor because it is a complex, changeable, and invisible product.
Once software development is late, adding more resources typically results in making the project even later.
Software Risk Management
Most software development projects are very large and complex. Breaking a software-intensive project into more manageable parts helps the people involved better understand the tasks and resources needed. By understanding the complexity of an effort, managers are better able to plan and manage the risk.
1
Feb 2013
Software Items (SIs): The Building Blocks
As part of the Systems Engineering Process, the software is usually broken down into smaller building blocks called Software Items (SIs). After being developed and individually tested,
Software Items are integrated with the hardware and ultimately the entire system.
A Software Item (SI) is a collection of software that performs closely related functions. Each SI is uniquely designated throughout the life cycle for purposes of:
●
●
●
●
●
Managing requirements.
Conducting qualification testing.
Controlling interfaces.
Ensuring configuration management.
Mitigating risk.
Note: In the past, Software Items were called Computer Software Configuration Items
(CSCI).
SIs and Work Breakdown Structures
As you learned in a previous lesson, a Work Breakdown Structure (WBS) divides complex projects into pieces so that risks can be identified and managed.
As illustrated below, WBS can be used to organize the Software Items (SIs)