Report: Service Portfolio
This report describes the service model comprehensively, in terms of the specifications detailed within it. The report is best used when the service model represents a comprehensive survey of the services provided by the enterprise and can therefore be seen as representing the portfolio of services in the enterprise. The report can be used to describe the service model at different stages: during elaboration; when you identify the first services and specifications and how they relate to the existing portfolio; and during construction, when the design is complete, to identify services added to the portfolio. This report is used by various people interested in the service model, such as software architects, use-case designers, designers, testers, reviewers, and managers.
Relationships
Related Elements
Main Description

1. Brief Description

An Introduction to the service model, describing the scope and purpose.

2. Service Specification Overview

An overview table should provide the name, status and source for each specification, optionally the qualification results can be shown (see Task: Apply Services Litmus Tests). An example of such a table is shown below.

Service Name Status Source Qualification
CustomerQualification exposed Process Aligned, Composable, Described, Reusable
CustomerCreditAuthorization accepted Legacy Aligned, Composable
CustomerBackgroundCheck candidate Rule

In this example we see services that are in different states and have been identified from different sources. Note that our candidate service has not yet been qualified.

3. Listing of all Specifications

This section presents the service specifications hierarchically, listing all operations provided by the specification as well as all implementing services. If the model has several levels of packages, all packages will be flattened and the service specifications presented in alphabetical order. For each specification the following will be provided.

  • Its name.
  • A brief description.
  • A list of the operations owned by the specification, including the name, signature, and a brief description of each.
  • A list of all the services that implement the specification and the provider for each service.

4. Diagrams of the Service Model

The diagrams, primarily class diagrams, of the entire service model are included here. Note: These diagrams are not related to the architectural views of the model.