Application Component (System, Module, Submodule)

There is only a single template for systems, modules, and submodules, as they all represent some application component. The description should include a concise yet apt description of the purpose of the application, why it exists in the organization, what it provides to the users and how it relates to the other organizational components. This is best described using natural language, accompanied by a context diagram to show how the system fits into the overall architecture:

It is also convenient to include the main features to describe what the system actually does. A textual description, list of use cases, or any other high-level representation of the capabilities and features will be beneficial:

In most cases, systems do not work in isolation and are integrated with other systems to achieve goals. From the IT perspective, it should be documented, how the system communicates with other systems and what data they exchange. It is also a good idea to document what data it consumes and what data it produces. The aim is not to list all integrations and data flows, though. It is sufficient to create just an overview of the integrations describing only the most important and frequent ones: