Process Construction Guidelines

Process Framework

The OPEN Process Framework (OPF) recognizes that no two endeavors are exactly alike. Endeavors vary greatly in objectives, size, scope, complexity, criticality, and application domain. They also vary in terms of available schedule, resources, technology, and organizational culture. Therefore, no single process or methodology, no matter how tailorable, will be optimal for all applications. Thus, the OPEN Consortium of methodologists, developers, tool vendors, and academics has produced a process framework rather than an individual process. In a sense, OPF is not a development process, but rather an industry-standard process for producing development processes that meet the differing needs of specific endeavors.

Process Framework Repository

As a framework, the OPF contains a class library of reusable process components that is much too large and complete to be used as is on any project or even a program of related projects. Instead, only appropriate cost-effective process components are selected and tailored to produce a process that is appropriate for the specific needs of the endeavor. This framework is stored in a repository of reusable process component classes and instances.

Metamodel, Framework, and Process

As illustrated in the following figure, the OPEN Consortium of methodologists, academics, CASE tool vendors, and industry experts constructs, extends, and maintains the OPEN process metamodel which defines the process component classes and instances stored in the OPEN Process Framework (OPF) repository. The process team on an endeavor selects items in the repository and uses them to construct the endeavor-specific process. The process team can also extend the repository by adding new classes and tailor the endeavor-specific process by modifying its process components.

Construction Process

To produce an endeavor-specific process, the following teams typically perform the following tasks iteratively and incrementally in roughly the following order:

1. Resource Management.
   The endeavor’s management team (e.g., program management team or project management team) staffs the endeavor’s process team.
2. Process Needs Assessment.
   The process team assesses the endeavor’s specific needs for process.
3. Process Construction.
   The process team constructs an appropriate endeavor-specific process by selecting reusable process components from the process framework’s repository.
4. Process Tailoring.
   The process team tailors the constructed process (and its process components) to better meet the specific needs of the endeavor. The process team also continuously iterates the process based upon the results of analyzing inputs from the endeavor’s staff.
5. Process Documentation.
   The process team documents the endeavor’s process in the associated process description document and conventions.
6. Training Delivery.
   The training team provides appropriate training to both the endeavor staff and the customer organization in all aspects of the endeavor process.
7. Process Mandating.
   The endeavor management team formally mandates the use of the endeavor process.
8. Process Consulting.
   The process team supports the endeavor staff by answering process questions and mentoring staff members.
9. Quality Assurance.
   The endeavor’s staff and quality team continuously evaluate the effectiveness of the process in terms of work product quality and staff efficiency. Upon completion of the endeavor, they also capture process lessons learned.
10. Process Framework Iteration.
    The process team continuously iterates the organizational process framework based on actual usage, technological advances, and academic research. This may include adding, deleting, or modifying process components.