A role describes the functional relationship that a user or organization has for an object.
role type
A role type is a configured prototype that describes a functional role that users or organizations can have for an object class. Every role defined for an object is based on a configured role type.
This business question requires users and organizations to be in the repository as well as the applications and components that you want to define roles for.
user
A user is a person with a license to Alfabet. Users are bundled in user groups, which determines the access permission to an object.
organization
An organization is a business-driven governance structure such as an administrative or functional unit in the company.
application
An application is a complete installation of a software offering a functionality to an end user. The application might consist of or require other technical components to run.
component
A standard component is a reusable block of functionality that provides technical functionality to an application or to the platforms that an application runs on. Components do not usually provide functionality to end users. Typical components are operating systems, database management systems, or application servers. A component that is used in an application's platform is a local component and is not is reusable.
The following table lists the information required in order to have meaningful data for the business question Who is responsible for our assets?:
Class
Explanation
Assets
The data capture template focuses on capturing responsibilities for the object classes Application and Component. However, responsibilities can be captured in Alfabet for almost all object classes.
Role
A role references the asset, the responsible person or organization, and the role type that the role is based on.
Role Type
Role types are preconfigured. The configuration includes the object classes for which the role types are available as well as whether the role can be filled by a single user and/or organization or multiple users and/or organizations.
The following preconfigured role types are available:
Application Manager: A person who is the subject matter expert for the application from a functional and technical point of view.
Architect: A person who is responsible for the governance of the asset.
Asset Owner: A person or organization who legally owns the asset. These users and organizations are responsible for making asset allocation decisions based on strategic and operational objectives.
Business Owner: A person or organization who owns the asset and is responsible for managing the functional requirements.
Capability Owner: A person who is responsible for the business capability/IT capability.
IT Owner: A person or IT organization owning the asset and thus typically responsible for approval decisions.
Operations: An IT organization responsible for the operations of the asset.
Project Manager: A person who is responsible for planning, organizing, managing, and executing projects from beginning to end including the project's budget, resources, and scheduling.
Staffing Manager: A person who is responsible to allocate and balance the human resources required for a project.
Stakeholder: A person or organization that has an interest in the assets and therefore requires read-only access permissions.
Person
The user that is responsible to fulfill the role for the object.
Organization
The organization that is responsible to fulfill the role for the object.