Architecture Work Products

Definitions

Architecture Work Product

a work product produced during the architecting activity

Architecture Set of Work Products

the cohesive collection of architecture work products

Work Products

Business Engineering

The OPF repository contains the following set of predefined business engineering architecture work products:

• Class Responsibility Collaborator (CRC) Card,
  which is a large index card that informally documents the responsibilities of a type during architecting of the business object model.
• Business Object Model,
  which documents the object model of the customer organization’s reengineered business enterprise.
• Business Process Model,
  which documents the process model of the customer organization’s reengineered business enterprise.
• Business Organization Chart,
  which is a chart that documents the organizational structure of customer organization’s reengineered business enterprise.
• ApplicationBusinessCase,
  which documents the results of a cost/benefit analysis of a single application.
• Application Strategy,
  which documents the customer organization’s strategy for producing future applications.
• Relationship Strategy,
  which documents the customer organization’s strategy for forming and maintaining business relationships.
• Business Architecture Document,
  which documents the new architecture of the customer organization’s reengineered business enterprise.
• Business Transition Plan,
  which documents the customer organization’s plans for transitioning their current business enterprise based on the results of business engineering.
• Reuse Strategy,
  which documents the customer organization’s strategy for reusing components across current and future applications.
• Technology Strategy,
  which documents the customer organization’s strategy for using technologies on current and future applications.

Application Development

The OPF repository contains the following set of predefined application development architecture work products:

• Architectural Mechanism,
  which provides ways of implementing quality requirements.
• Architecture,
  which is the most important, pervasive, top-level, strategic inventions, decisions, and their associated rationales about the overall structure (i.e., essential elements and their relationships) and associated characteristics and behavior.
• Architecture Patterns,
  which is a standardized generic solution to common architectural problems in given contexts.
• Contact Center Architecture Document,
  which formally documents the architecture of a contact (a.k.a., call) center. which formally documents the logical and physical architecture (including mechanisms and technology selections) of a system application.
• Contact Center Architecture Document,
  which formally documents the architecture of a contact (a.k.a., call) center.
• Data Center Architecture Document,
  which formally documents the architecture of a data center.
• Information Architecture Document,
  which formally documents the architecture of an application's major data components including its content.
• Software Architecture Document,
  which formally documents the architecture of an application's major software components.
• Software Architecture Prototype,
  which is a prototype (i.e., partial application) that is used to verify the software architecture of an application.
• System Architecture Document,
  which formally documents the overall architecture of an application.
• Technology Readiness Assessment,
  which documents the assessed maturity of the critical technologies used in the development of an application.

Guidelines

• Different endeavors require different processes, which in turn will require different architecture work products.
• Every endeavor does not require the production of every architecture work product.
• Select only those architecture work products that are appropriate for the endeavor.
• Selected architecture work products should be:
  • Relevant.
  • Useful.
  • Usable.
  • Cost-effective.