| Description | The OV-2 DoDAF-described Model applies the context of the operational capability to a community of anticipated users. The primary purpose of the OV-2 is to define capability requirements within an operational context. The OV-2 may also be used to express a capability boundary. |
|---|---|
| External references |
DoDAF2 - OV-2 |
| Dictionary |
SysFEAT - DoDAF 2 |
| Parent Domain |
DODAF2 - Operational Viewpoint |
| Concept | Description |
|---|---|
Business Outcome Event |
A Business Outcome Event is a Business Event that signals the happening of a change in the state of a Business Operating Asset, produced by the Business Behavior of a Business Agent, for the benefits of an internal or external consumer (especially Customers). |
Business Scenario |
A Business Scenario is a story describing how Business-Entity (Department Type) interact wtiht its partners (Partner Department) to achieve Business Outcome Events in a specific Eco-System (Business Environment). This includes: 1) A course of events represented by Resource Object Flows depicting the story towards the delivery of expected Business Outcome Events. 2) Interacting Business Entities (Department Types) who participate to the story in the considered Eco-System. |
Department Type |
A Department Type is a Mezzo Org-Unit which serves as an administrative unit template in both government and business Organizations. Examples: - Sales department; - Finance department; - Logistics department..
|
NeedLine Requirement |
|
Organizational Position |
An Organizational Position is a type of position held by people when part of a Department Type. Examples: - Sales representative - Developer - Storekeeper - Architect |
| Concept | Description |
|---|---|
Org-Unit |
An Org-Unit is a type of Human Resource that represent a unit of social groups within an organization, responsible for operating one or more enterprise's Business Functions. |