Software Engineering

323
Software Engineering. DOI: 
© 
2012
 Published by Elsevier Inc. All rights reserved.
2013
http://dx.doi.org/10.1016/B978-0-12-407768-3.00019-7
Software Implementation
19
CHAPTER 
CHAPTER OUTLINE
19.1  Products of software implementation ................................................................ 325
19.2  Software engineering tasks (software implementation stage) ............................. 327
19.3  Software implementation tasks (software implementation stage) ....................... 327
19.4  Computing environment tasks (software implementation stage) ......................... 329
19.5  Post-development process tasks (software implementation stage) ..................... 329
19.6  Software test and evaluation tasks (software implementation stage) .................. 330
19.7  Reviews and milestones (software implementation stage) ................................. 332
The software implementation stage involves the transformation of the software 
technical data package (TDP) into one or more fabricated, integrated, and tested 
software configuration items that are ready for software acceptance testing. The pri-
mary activities of software implementation include the:
●
  Fabrication of software units to satisfy structural unit specifications.
●
  Assembly, integration, and testing of software components into a software con-
figuration item.
●
  Prototyping challenging software components to resolve implementation risks 
or establish a fabrication proof of concept.
●
  Dry-run acceptance testing procedures to ensure that the procedures are properly 
delineated and that the software product (software configuration items (CIs and 
computing environment) is ready for acceptance testing.
Software implementation begins with the effort of software fabrication. 
Fabrication
 is an act of making something. Software fabrication involves program-
matic design, source code editing or programming, and testing of each software 
unit. This series of technical tasks represents how software procedures, routines, 
modules, objects, or graphical models are produced. Each software unit is presumed 
to be suitable for their intended purpose or role in the overall architectural context. 
The result of software fabrication should be a documented unit of source code that 
has been tested against its structural unit specification. This source code (software 
unit) is then available to be assembled, integrated, and compiled with other fabri-
cated software elements to craft larger software components. These integrated soft-
ware components are tested against structural component specifications to ensure 

---