Example XBB requirements and constraints PIM

This example shows in a simple manner how the characteristics/requirements can be made transparent based on requirements, constraints, qualities and principles. This example shows how the characteristics of the different xBB can be mapped based on ArchiMate concepts. This will soon become an important mechanism in the various xBB catalogues. In addition to this approach, the characteristics can also be elaborated via the internal characteristics of the entities in EA. Such as requirements, constraint and scenario. Finally, there is the option to use tagged values. The working group has determined that making associations between ArchiMate concepts is preferable. If an elaboration with ArchiMate concepts is insufficient and you want to rely on internal properties or tagged values, this must be short-circuited.

Diagram in standard mode

Outlook

Application component within the Microsoft Office Suite.


Details van Outlook

Delivery reliability of internal messages

Given the importance of the content of the emails, delivery reliability of messages is desirable.


Details van Delivery reliability of internal messages

Standardized solutions

Within the organization, standard software is chosen for office automation. Custom applications in this regard are not permitted.


Details van Standardized solutions

Attachment size maximum 20MB

Technical limitation in the current configuration of the Outlook component.


Details van Attachment size maximum 20MB

Personal Information Manager

Unlocking a number of functionalities related to the management of personal and team activities and communication.


Details van Personal Information Manager

E-mail

Sending and receiving electronic messages.


Details van E-mail