Application
This factsheet is very close to the standard LeanIX definition. Below is a Channel 4 view.
Definition
Applications are logical systems or programs that process or analyse data to support business tasks, processes, or aspects of our business model.
Description
Applications are central to the EAM (it's what the licence model is built on) and as such it links many of the factsheets to one another.
Applications are the tools used by teams (Organisation) to perform business tasks, as part of a Value Chain, which means they support a Business Capability at a high level and a Process (Business Context) at a more detailed level. All applications are made from one or more IT Components, which are likely what you see as the more traditional definition of an application, but in our model components are software and services. In performing these tasks it is very likely the application works on (CRUD) data, this is modelled at a semantic level. Finally, it is also common applications 'talk' to each other, this is defined through their Interfaces.
Subtypes
There are no active subtypes for this factsheet
Model
Modelling an application would be expected to have the minimum structure detailed below:
Ideally an application shall be modelled as shown below, with the addition of [[Business Capability]] and [[Organisation]] to help build out the context in which the application serves. Also by adding the relation to a [[Tech Capability]] to the IT Component, it will appear in the [[Technical Reference Model]] (TRM)
Example
With a SaaS application it isn't necessary to model the sub-components, but it is generally needed as a Application to model any [[Interface|Interfaces]] is may have.
In most cases it is required that an Application, such as Advance Scheduling System | LeanIX is modelled in full.
C4 Factsheet
Mandatory Fields
There are no mandatory fields on this factsheet.
Modifications
We've extended the Application factsheet in one section.
Accessibility
Accessibility Score: Is a combination of the following fields to provide a single 'score' of the accessibility of the applications.
Screen Reader: Does the application support screen readers?
Adjustable Font Size: Can the user adjust the font size to aid reading?
Tab Function: Has the application been designed with tab navigation?
Non Standard Resolution: Is the application compatible with non standard screen resolutions?
High Contrast: Does the application provide a high contrast version?
Assessment Metrics
Implementation
Tag
Ensure the Application is tagged with one (and only one) Technology Vertical tags, reflecting the owner of the Application.
Information
Please complete the following (but they are not mandatory)
Name - the application full name, do not include the supplier name nor the version in this field or use the acronym.
Alias - used for capture the acronym e.g. A55
Description - a concise description to help someone that is not familiar with the app or it's use.
Factsheet Status
The following need to be resolved, but the factsheet is still useable.
Assessment Metrics
Last updated