View Archive - NAF:NSOV-3 Service Orchestration Subview



The NSOV-4 Service Orchestration subview is part of the NATO Service-Oriented View .

Version & Date

Not applicable - no longer in use: archived.

See NAF Release History.


From the NATO Architecture Framework v3, CHAPTER 4, Section 4.6.5

The purpose of the Service Orchestration subview is to identify and describe how services in general, and web services in particular, are utilized in the execution of operational activities, and how services are used, in conjunction, to support operational processes.

Covered by NATO release conditions.


From the NATO Architecture Framework v3, CHAPTER 4, Section 4.6.5

A service orchestration, in general, is a set of services, used in conjunction, capable of satisfying certain operational objectives that cannot be achieved by any of the services alone.

At the construction level, a web service orchestration is the set of interactions between web services at message level. Depending on purpose, it may not be enough to only determine which web services are used. It may also be necessary to resolve timing issues, semantic misunderstandings, and quality of service discrepancies, which may appear at the construction level when web services interact. On a construction level the orchestration of web services, requires the various composing systems to collaborate in a controlled (orchestrated) manner.

Orchestration is commonly controlled from the perspective of one of the parties involved. The orchestration then essentially creates an operational process internal to that party, through the utilization of services. When orchestration is elaborated across organisation boundaries, involving multiple parties, control becomes more dispersed across the participating parties and focus shifts more to the consumer and the transaction that this consumer wants to execute. In that case, the term ‘service choreography’ is used.

Orchestration is controlled by utilizing some form of scripting, e.g. using some formal language. Scripting can benefit from the power of a formal or programmatic language, e.g. addressing sequential, conditional and parallel execution of services in general, or web services specifically, among many other flow controls.

Orchestration leads to the emergence of higher order services, where the combined use of services serves to deliver a higher order functionality or effect. In the case of web services this creates a composite web service.

Covered by NATO release conditions.

From the NATO Architecture Framework v3, CHAPTER 5, Section

This view specifies how services can be combined and sequenced to provide a ‘higher level’ service. Note that there might be several instances (products) of this view since there are generally several different possible service combinations.

The view is best presented by means of a UML composite structure diagram but other possibilities also exist.

It should be noted that no decision concerning implementation of the service is actually made in this view - i.e. the orchestration is a requirement specification rather than a design. In fact, none of the service subviews describe the implementation of the services - this is covered in the NSV-12 view.

Covered by NATO release conditions.

Data Objects


Configuration History


The chapter 5 description uses the term view when it should properly use subview as is used in the chapter 4 definition.


Other Frameworks



  • Section 4.6.5 (page 228 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
  • Section (page 401 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
  • page 9 of the MODAF Service Oriented Viewpoint. 27th November 2008.


Category:Framework -> View
Category:NAF -> Subview



© 2010 Eclectica Systems Ltd.