Alfabet enables a single-source of truth about the applications in your IT portfolio. All applications should be documented to ensure that the application portfolio is a reliable source to make good strategic decisions.
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.
The Application Manager user profile is for users who are responsible for capturing data relevant for application portfolio management. The user profile Application Manager has been provides Write permissions for the class Application and read-only permissions to all other relevant classes in the business, information, and technology architectures. A user with this user profile has the following permissions:
Permissions to create new applications in the Applications data workbench. You can specify all relevant information about an application including its basic data, responsible roles , lifecycle as well as the business capabilities that the application supports, the information flows with other applications in order to transfer business data, or the components that the application uses.
role
A role describes the functional relationship that a user or organization has for an object.
lifecycle
The lifecycle describes the planned schedule of a current real-world object in different lifecycle phases of a product. Lifecycle phases will be different depending on the object class. Lifecycle phases for an application are Pilot, Production, Retired, and Sunset.
information flow
An information flow describes the exchange of business data between source and target applications.
business data
Business data is the information exchanged between applications or components. Business data is transferred by information flows.
Permissions to edit applications displayed in the Applications data workbench. All applications that you are the authorized user of and all applications associated with an authorized user group that you are a member will be visible.
authorized user
An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for.
user group
A user group determines the visibility of objects. One or more user groups may be granted authorized access to an object. The object is visible to all users assigned to a specified user group.
Read-only permissions for referenced data. You will be able to see existing assets such as business capabilities or technological components that already exist in the repository. References to other objects can only be made if they already exist in the repository. Click to understand the dependencies between objects.
business capability
A business capability is a high-level description of what is done in a company to meet its business objectives. Market development, product development, and support and services are examples of business capabilities.
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.