Site Map

Repository:   Work Products  Work Units  Producers  Stages  Endeavors  Languages

Website Organization  OPF_Repository Organization  Website Overview  Standards Compliance  Sources


The webpages documenting the repository of process components metaclasses and associated process component classes are primarily organized hierarchically, in accordance with the structure of the OPEN metamodel. However, each webpage contains numerous hyperlinks to useful information on other webpages.

The following tables contain links to the webpages that document the reusable process component metaclasses and process component classes:

Work Products

Work Product Sets:  Architecture  Configuration Management  Content Management  Deployment  Design  Digital Branding  Disaster Recovery  Environments  Implementation  Integration  Management  Maintenance  Metrics  Operations  Process  Quality  Requirements  Retirement  Reuse  Risk Management  Safety  Security  Test  Training  User Support

Models:  Data  Function  Object  Process  Quality  State  Use Case

Diagrams:  Requirements  Architecture  Design

Work Product Sets
(Sorted by Activity)
Models, Diagrams, and Versions



Work Units

Go directly to:  Architecture Engineering  Common_Work Units  Configuration Management  Content Management  Deployment  Design  Digital Branding  Disaster Recovery  Environments Engineering  Implementation  Integration  Management  Maintenance  Metrics Engineering  Operations  Process Engineering  Quality Engineering  Requirements Engineering  Retirement  Reuse Engineering  Risk Management  Safety Engineering  Security Engineering  Testing  Training  User Support

To provide maximum flexibility in the production of an OPEN-complient process, any activity can theoretically be composed of any set of tasks and any task can theoretically be implemented with any set of techniques. In practice however, most tasks are clearly associated with only one activity (e.g., the requirements elicitation task is clearly a part of the requirements engineering activity rather than of the integration activity), and breaking this natural association produces activities that are not functionally cohesive, that violate the abstraction implied by their name, and that are generally difficult to understand, learn, and use. Similarly, many techniques are associated with only one (or a small number of) tasks.

Therefore, the following table of links to work units is organized to clearly group:

Work Units
Activities Tasks Revelant Techniques
Architecture Engineering:
Contact Center Architecture Engineering
Database Architecture Engineering
Data Center Architecture Engineering
Enterprise Architecture Engineering
Hardware Architecture Engineering
Information Architecture Engineering
Security Architecture Engineering
Software Architecture Engineering
System Architecture Engineering
Common (Subactivities):
• None (not applicable)
Configuration Management:
Content Management
Digital Branding:
Disaster Recovery:
Environments Engineering:
Application Maintenance
Component Maintenance
Data Maintenance
Hardware Maintenance
Software Maintenance
Documentation Maintenance
Metrics Engineering:
Quality Engineering:
Requirements Engineering:
Reuse Engineering:
Risk Management:
Safety Engineering:
Security Engineering:
User Support:
Work Flows


Organizations Teams Roles Tools Persons


Cycles Phases Builds Milestones

Endeavors and Languages

Endeavors Languages

To make it easier to locate them, the webpages for individual conventions are listed in other tables, colocated with their associated work units, work products, or tools.

Website Organization

This website is primarily organized into the following five areas:

  1. OPF Repository Organization:
  2. Website Overview:
  3. Standards Compliance:
  4. The repository of reusable process components (see preceding tables)