Software Engineering

1.9 
Reviews and audits
A typical software development project is defined by a series of phases of time dur-
ing which the product is defined, designed, implemented and tested. Each phase of 
FIGURE 1.3
Hierarchy of organizational, technical, and project plans and schedules.

---

19
1.9 
Reviews and audits
activities concludes with a formal review of the product development status, and 
involves most of the stakeholders. It is necessary to conduct technical reviews of 
the software architecture, implementation, and test status to ensure that the techni-
cal organizations are prepared for project reviews. In addition, the IPPD philoso-
phy broadens the number and scope of these reviews to address the definition and 
status of the software post-development processes. 
Figure 1.4
 provides a concep-
tual schedule of technical reviews that support formal project reviews. Section 3 
provides a detailed agenda for each formal review that addresses the project and 
product status, key architectural decisions, proposed changes under review, and the 
plans for the next stage of software development.
Technical reviews address the software product under development while the 
post-development reviews address the development of post-development processes. 
Technical reviews address the state of the evolving software requirements and func-
tional and physical architectures. The development effort then transitions to focus on 
software implementation, which involves a series of technical reviews to assess the ade-
quacy of software programmatic designs, integration, and testing activities. The main 
difference between project and technical reviews is the level of formality and participa-
tion. Technical reviews do not involve project management or stakeholder participation.
The post-development process reviews address the status of distribution, train-
ing, and support process definition and implementation. These processes must be