4.2.1 Background

One of the most common tasks performed by an Architect is adding existing assets (e.g. reusing existing Services) to a Solution.  Scenario 1.2 above mentions this task multiple times, when it describes how Arlen will use the system to add existing Services and Events to the Solution.  This scenario dives a little deeper into how this is done.

4.2.2 Participants

• Arlen [Architect]

4.2.3 System Narrative

Arlen is presented with a list of Solutions for which he is an Architect (i.e. has been granted the Architect role).  Arlen chooses the Solution he wants to modify and is presented with a Solution Overview page.  The Solution Overview page will display, among other things, the current list of assets included in the Solution.

Arlen chooses the “Add Existing Asset to Solution” action from the Solution Overview page.  This action provides a way for Arlen to browse existing assets found in the repository (e.g. Services, Compositions, Events, etc...).  Once Arlen finds the existing asset he is looking for, the system simply adds a reference to it in the current Solution.