A person, organization, or system that has one or more roles that initiates or interacts with activities; for example, a sales representative who travels to visit customers. Actors may be internal or external to an organization.

Naming conventions: Usage Noun e.g. Government employee, Company, Citizen. Avoid User, system.

This is an example of modeling and naming conventions that can be used within an architecture repository. This elaboration is an example of how to develop a metamodel and its conventions. In this case for a data architecture development. The metamodel has been developed based on the DMBoK framework. This means that part of the framework has been developed and the others have not yet. Here, particularly from the point of view of the data architect, is an elaboration of modeling conventions and architectural models. Working with meta data requires a white paper on metadata modeling methods.

Description of the structure of the organization based on business roles and/or actors. Often based on an existing enterprise architecture framework.

1. The usual or expected function of an actor, or the part somebody or something plays in a particular action or event. An actor may have a number of roles.
2. The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities.

1. A repeatable activity; a discrete behavior that a building block may be requested or otherwise triggered to perform.
2. An element of behavior that provides specific functionality in response to requests from actors or other services.

Enterprise Architect webviewer op basis van Form Factory CMS

Verschillende soorten architectuur repositories op basis van het Interactory Framework

Welcome page

Goal : Providing insight into the business processes and functions to be realized and the allocation to actors. Support by the underlying applications and technology. Obliged: Depending on the size, this can be combined with the application view and technology view in an overview view.

This is an example of modeling and naming conventions that can be used within an architecture repository. This elaboration is an example of how to develop a metamodel and its conventions. In this case for a data architecture development. The metamodel has been developed based on the DMBoK framework. This means that part of the framework has been developed and the others have not yet. Here, particularly from the point of view of the data architect, is an elaboration of modeling conventions and architectural models. Working with meta data requires a white paper on metadata modeling methods.