ARIS: Level Based modeling of IS Functions (IT Capabilities). Taming the complexity:

ARIS defines IS Functions (Capability in ARIS 7.1) as a generic IT resource that supports a function within a process. (I truly love the way IDS has defined this tricky aspect, which many manager in IT are not able to capture immediately).

For example, if we consider an application such as Microsoft EPM Project server, which support “Project Management” capability.

However, Project Management function capability is at a higher solution level, and it is more interesting to identify the activities/components of the Project Management process such as resource management, Project execution, Project risk management and so on.

It would also be interesting to identify what features of the just mentioned activities EPM supports. For example, features of the activity “Resource Management” such as Time sheeting, allocation of resources, Management of resource information, assignment of resources, Effort tracking and so on. I would recommend a breakdown of capabilities to this level of detail is needed for any decent level of architecture analysis.

Level 1 (Component level): Project Management

Level 2 (Activity/ Component level): Resource Management

Level 3 (Features level): Time sheeting, allocation of resources,,,,

Note that there can be a need to breakdown the level of details into further details, level 4 in this case. By this hierarchical approach, link IT applications and their capabilities. The level of detail of the capabilities can be captured in an attribute.