First steps in the development of a Program Organizational Architectural Framework (POAF)

Abstract

The target audiences for this paper are systems engineers and architects involved in the design of complex systems such as program organizations. This is the first in a series exploring how the design of program organizations developed for the purpose of designing and developing aerospace and defense systems can be optimized. The objective of this paper is to lay the groundwork for an architecture framework for the development of a program organization. The draft standard ISO/IEC 42010 is used to define the structural requirements of the architecture framework. In addition, we use the Zachman Architecture Framework TM to organize the framework and the Department of Defense Architecture Framework Version 2.0 (DoDAF 2.0) to create the model environment for the Program Organizational Architecture Framework (POAF). This approach to defining the POAF ensured that we would have the data needed to support our objective to optimize the design of the program organization and hopefully reduce the number of defects inherent in the design. We also believe that we have sufficiently defined the characteristics of a POAF to spur more research in this area.

A cost platform based on the design requirements for the optimal design and cost minimization of the nuclear fuel cycle facility

“…Research related to the managing requirements of the PRIDE facility using requirements and system engineering was carried out (Park et al, 2012). The usage of this technology is steadily increasing in the areas of private, national defense, and nuclear energy industries (Thomas et al, 2013;Williams and Stracener, 2013;Boy and Schmitt, 2013;Owen et al, 2013).…”

Decision-making in the program organization architecture framework-owner view (POAF-OV)

“…We present in this paper the Program Organization Architecture Framework (POAF) described in [3,6] and we introduce an analytical technique for supporting the decisionmaking process in the POAF-Owner Viewpoint (OV). We illustrate a simplified application of Enterprise X Program Management Office (EXPMO) to define the evolution of its PMO from its current state to final state and optimize some aspects of its design.…”

“…Also, a systemic approach is required to look at different perspectives and elements of the organization, such as the environment the organization will operate in. Designing the organization also depends on the information needs that reside in an organization and the communication structure in place to pass on the relevant information [2,3]. These contributions have to be organized and coordinated formally in an architecture framework.…”