• the Name

• the internal Code

• the Application type:

• In-House: an in-house application, also known as an internal or proprietary application, is a software application developed specifically for use within a single organization. Unlike off-the-shelf software that is commercially available to the public, in-house applications are custom-built to meet the specific needs and requirements of the organization that develops them. These applications are typically used to address unique business processes, automate tasks, and improve operational efficiency within the organization.

• Middleware: middleware is a type of software that acts as an intermediary layer between different applications, systems, or components. It facilitates communication, data exchange, and integration among various software systems, enabling them to work together cohesively.

• Office System: an office system application typically refers to software or a suite of tools designed to facilitate various office-related tasks and streamline workflows. These applications are meant to improve productivity, communication, and collaboration within an office environment. Depending on the specific needs of the organization, an office system application can encompass a wide range of functionalities.
Some examples of well-known office system applications include Microsoft Office 365, Google Workspace (formerly G Suite), and Zoho Office Suite. These applications typically offer a combination of the features mentioned above and cater to the needs of businesses and organizations of different sizes and industries.

• Software Package: a software package application is a specific type of software package that provides a set of related programs or applications to address a particular domain or solve specific problems. It is a collection of software tools bundled together as a unified solution, often with a common theme or purpose. These applications are designed to be installed and used collectively to provide a comprehensive solution to users' needs.

• System Application: a system application, also known as a system software or system-level software, refers to a category of software that is essential for the operation and management of a computer system. Unlike application software, which is designed for end-users to perform specific tasks, system applications work behind the scenes to facilitate the functioning and interaction of hardware, software, and users. System applications are critical for the overall operation, performance, and security of a computer or device.

• if it is an Application template: to be selected if the application is used to create other applications

• the Cloud Computing, which indicates how the application should be installed:

• On premises: the application is installed and runs on computers on the premises (in the building) of the company.

• Infrastructure as a Service (IAAS): the application is installed and runs on an external provider infrastructure (physical or virtual machines and other additional resources such as images in a virtual-machine image-library, raw (block) and file-based storage, firewalls, load balancers, IP addresses, virtual local area networks (VLANs), and software bundles).

• Platform as a Service (PAAS): the application is installed and runs on an external provider computing platform including operating system, programming language execution environment, database, and web server. Internal/external developers can develop and run their software solutions on a cloud platform.

• Software as a Service (SAAS): the application is designed, installed and runs by an external delivery partner. Some customization can be implemented during the design phase.

• a Comment.

• the Service Legal Agreement: displays the indicators that define the application quality level.

• Functional Scope of the application. See Defining Application Functional Scope.

• Responsibility: it relates to the person or persons responsible for the application. See Assigning an Application to Persons.

• Technology used. See Specifying the Technologies of an Application.

• Exchanges with other objects. See Specifying Data Exchanged With Other Applications.

• the Data processed by the application. See Defining the Data Used by an Application.

• Data Subjects' Rights & Notice Management.

• the Risks associated with the application. See Specifying the Risks Associated with an Application.

• Gantt Chart of the application presenting the application lifeline. See Defining Application Life.

• associated Attachments. See Attaching Documents to an Application.