5.1.1 Background

Architects may want to document existing Services prior to their use in any Business Problem tracked using the Overlord:DTG application.  Alternatively, the application may not have sufficient buy-in from Project Managers and Business Analysts.  In these cases, users can decide to directly manage logical assets such as Services and Compositions.

5.1.2 Participants

• Arlen [Architect]

5.1.3 System Narrative

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

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

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

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

• Meta-data such as name, description, status
• The Service’s version history
• Any available attached Documentation
• Links to the Service Contract and Service Interface
• Links to any Components or Compositions that implement the Service
• Links to any Compositions the Service is a part of
• Activity history for the Service

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

• Edit Service meta-data
• Delete the Service
• Modify the Service Interface
• Modify the Service Contract
• Create additional Documentation

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