Software Engineering

14
CHAPTER 1 
Introduction to Software Engineering
2. 
Software implementation IPT:
 Represents the organizational entity responsible for 
implementing the software product by developing implementation plans and sched-
ules; designing, coding, and testing software building blocks (e.g., software units); 
integrating and testing software components; and testing the integrated product.
3. 
Software test and evaluation IPT:
 Represents the organizational entity responsi-
ble for planning, detailing, and conducting software product acceptance testing. 
Represents the customer, project manager, and enterprise in assessing the qual-
ity, performance, and characteristics of the software product under simulated or 
actual operational testing.
4. 
Computing environment IPT:
 Represents the organizational entity responsible 
for planning, defining, implementing, and testing the intended computing envi-
ronment the software product is being developed to operate within.
5. 
Post-development process IPT:
 Represents the organizational entity responsible 
for planning, defining, and implementing the product replication, distribution, 
training, and support processes.
An integrated product team is responsible for the definition of a product or pro-
cess throughout all phases of the product life cycle, including software architecting, 
implementation, distribution, training, and support. A typical IPT might be composed 
of software engineering, implementation, testing, and evaluation, and specialty engi-
neering (maintainability, safety, human factors, logistics, etc.), as well as including 
customer and management representatives. Integrated product teams apply advanced 
methods and tools for planning, information gathering, design trade-off analysis, and 
modeling and simulation, which significantly improve IPPD effectiveness. Each IPT 
strives to derive the following benefits of an IPPD
3
:
1. 
Reduced time to deliver a product
. What were formerly sequential decisions can 
now be made concurrently from an integrated perspective, with all stakehold-
ers accounted for. All decisions should be based on a system software life-cycle 
perspective that minimizes the number and magnitude of changes during devel-
opment and deployment of the software. A subsequent reduction in extended 
and expensive rework cycles has a positive impact on schedules and overall 
software life-cycle costs.
2. 
Reduced system and product costs
. Proper emphasis on IPPD at the beginning 
of the software development process helps to optimize the product and process 
funding profile. Pre-IPPD funding profiles based on historical data may no 
longer be relevant. Early software project phases may require additional invest-
ment, but unit costs and overall life-cycle costs may be reduced due to fewer 
design or engineering changes, better capability to meet schedule objectives, 
and extensive use of trade-off analyses to reach cost-effective solutions.
3. 
Better risk mitigation
. Team planning at the earliest stages of software develop-
ment promotes better understanding of available technologies and processes. 
3 
Software Acquisition Gold Practice, Integrated Product and Process Development (IPPD), 
 
http://goldpractice.thedacs.com/practices/ippd/
.

---