Software Engineering

6
SECTION 1
  Software Engineering Fundamentals
life-cycle complications during the engineering of the product. It encourages the 
use of integrated product teams to ensure that an array of software technical disci-
plines is involved in architectural decision making. This ensures that a more robust 
structural framework is established upon which to base the product realization. In 
addition, IPPD emphasizes the concurrent establishment of post-development pro-
cesses and infrastructure. The software replication, distribution, training, and sus-
tainment processes must be available when the product is ready to be deployed.
The central theme of this manuscript is to present architectural-driven develop-
ment. This is fundamental to the software engineering paradigm that emphasizes the 
importance of designing the complete software product before initiating the soft-
ware implementation activity (programmatic design, code, integration, and testing). 
Software implementation represents the manufacturing of a software product, while 
software replication represents the software production process. Manufacturing is to 
produce something into a finished product using raw materials. Mass production is 
the manufacturing of carbon copies of a finished product on a large industrial scale. 
Software implementation involves the programmatic design, coding, and testing of 
software units, modules, routines, objects, etc. These software units represent the 
“raw material” utilized in the manufacturing of a software product. These software 
units must be identified and specified to establish the physical architecture. Then, 
these structural units must be assembled, integrated, and tested in a manner that 
results in a complete software configuration item. This approach executes the FAIT 
(fabrication, assembly, integration, and testing) convention used by international 
 on systems engineering.
Finally, this section presents the impediments to the design of software prod-
ucts due to software’s nonmaterial nature. It presents the software design chasm as 
an illustration characterizing the difficulty associated with defining an architectural 
framework for the structural configuration of a software product. It presents the soft-
ware engineering principles and practices that vanquish this dilemma and provides a 
rigorous, disciplined approach to designing the software architecture.
4 
ISO/IES 26702:2007, IEEE Standard for Application and Management of the Systems Engineering 
Process, and IEEE 1220–2005, IEEE Standard for Application and Management of the Systems 
Engineering Process.

---