5.2.1 Background

In addition to the reasons documented in Section 5.1.1, architects may want to propose new Compositions to be used by other architects for their Solutions.  For these reasons, the system allows users to directly managed Compositions.

5.2.2 Participants

• Arlen [Architect]

5.2.3 System Narrative

Arlen logs into the system and navigates to the Composition Management page.  He is presented with a list of all Compositions in the system.  The following actions are available:

• Filter Compositions (various filter criteria such as classifications, name, etc)
• View Composition Details (available for each Service in the list)
• Create Composition

The list of Compositions can be filtered via a typical set of optional filters based on both standard meta-data and user-defined meta-data.  The Compositions may be grouped by some sort of namespace or domain attribute.

When Arlen clicks the View Composition Details action, he is presented with detailed information about the Composition, including but not limited to:

• Meta-data such as name, description, status
• The Composition Type (orchestration, collaboration, choreography)
• The Composition’s version history
• Any available attached Documentation
• Links to any Components that implement the Composition
• Activity history for the Composition

Additionally, Arlen may be able to perform some or all of the following actions (depending on his permissions):

• Add asset to Composition (Service, Task, Event, Rule)
• Remove asset from Composition (Service, Task, Event, Rule)
• Edit Composition meta-data
• Delete the Composition
• Create additional Documentation

The Create Composition action behaves nearly the same as the one defined in Section 4.4, except that the resulting Composition is not added to a Solution.