Although there 10 main service views they are identical to the systems views. Many of the Service for the deifinition of services only make sense if they are combined with systems views. Services by there nature are interface definitions or specifications of services that are enabled by systems. As such the workflow is very similar

Initially the Service taxanomy is defined in a SvcV-1, the functionality of the services is then expanded upon in the SvcV-4, from this proper service interfaces can defined and are noted on the SvcV-1 and the SvcV-2. The SvcV-10c event traces are also used to support the flow analysis. Once defined the services are trace abck to the operational activities and capabilities that they expose and the matrix views of the interactions between services and systems generated (SvcV-3a,b and SvcV-6).

This flow should be repeated for each system use cases or set of scenarios when services are expected to support the capability. This implies an Agile iterative approach to the development of the architecture because during each iteration the existing information needs to revalidated and potential restructured if the behaviors of the different scenarios contradict.