• Разработчик архитектуры

• Проектировщик
• Разработчик архитектуры

• Apply Services Litmus Tests
• Identify and Associate Services to Goals

• Apply Services Litmus Tests
• Identify and Associate Services to Goals

• RUP Service-Oriented Modeling and Architecture  >  Identification  >  Goal-Service Modeling  >  Goal-Service Model
• RUP Service-Oriented Modeling and Architecture  >  Specification  >  Perform Service Specification  >  Goal-Service Model
• Service Identification  >  Goal-Service Modeling  >  Goal-Service Model
• Service Identification  >  Goal-Service Model
• Service Specification  >  Perform Service Specification  >  Goal-Service Model

This model is developed iteratively, firstly during Task: Goal-Service Assignment the model includes all candidate services mapped to the business strategy in terms of business goals. During Task: Apply Services Litmus Tests service exposure decisions are taken and so the mapping of exposed services must be checked and if necessary refined to ensure that the details are correct. An instance of the Goal-Service model should address all business domains that are within the scope of the project.  It is preferable to create a single Goal-Service Model instance for the project, rather than one per domain. 

This work product may be represented in a number of ways, described below, the manner of its representation is far less important than the fact that its information has to be kept up-to-date as the details of the service model change. Therefore it is common for this model to be represented in a form that facilitates rapid review and change.

UML Representation:

• A Model, stereotyped <<Goal Service Model>> containing the set of Artifact: Business Goal and Artifact: Service Specification and their dependencies that constitute the goal service model.

Requirements Representation:

• As an Artifact: Business Goal may be considered as a requirement for IT Capabilities to support, it is therefore possible to capture the business strategy in a requirements tools, as described in Tool Mentor: Identify Business Goals Using Rational RequisitePro.
• In such a case the set of Artifact: Service Specification, whether candidate or exposed, may be traced to these business goals using mechanisms defined by the requirements tool.

Tabular Representation:

• In a simple document or spreadsheet form the relationship between goals and services may easily be represented, using a format such as the following (note that a non-leaf goal may not necessarily be traced to a service if all of it's sub-goals are traced):

• Goal-Service Modeling

• Creating a Goal-Service Model using RequisitePro