This page details the purpose, scope and working arrangements for the Service Architecture Team (SAT).

Purpose

The Service Architecture Team (SAT) is responsible for:

managing the service design step of the service orientation process;
capturing and managing the content of service definitions
- based on requirements captured during the service identification step
- to hand over to implementation projects;
contributing to the overall interoperability architecture.

Composition

The SAT involves the following roles:

Leader
- responsible for making sure the team meets and is run effectively.
- works with the architect to setup a plan for service design work e.g. taking into account dependencies.
Architect
- responsible for the service related artefacts (architecture, service definitions, etc).
- works with the leader to setup a plan for service design work e.g. taking into account dependencies.
Expert
- responsible for ensuring that the architecture and service definitions reflect the subject matter and requirements at hand.
- Thematic expert. Experts may be assigned a "theme" to research and manage at the meetings.

The SAT will have:

The SAT will use a specific workflow in order to ensure the meetings are efficient and productive. In summary:

Before the meeting
Collect themes	List of themes to be worked on.	All
Select themes	Select the themes to be worked on during this iteration. This can be done at a meeting of all members.	Leader, All
Call for interest	Once the themes have been selected a call for interest will be sent out. A thematic expert can be assigned.	Leader
Compile existing material	The existing material has to be collected by the thematic expert. This preparatory step should be done with a view to easing the work of the SAT.	Thematic expert
Preparation	In preparation for the meeting, the compiled material should be read carefully by the team members.	All
Meeting
Work on selected themes	The team meets and works on the selected themes based on the existing materials. The leader leads the meeting The thematic expert manages the discussion on a theme All experts contribute to the output The architect captures the outputs	All
After the meeting
Tidy up	Final tidy up to the outputs of the meeting takes place.	Architect
Review	The output of the meeting is reviewed by all members.	All
Implementation	The architect will complete the documents as agreed.	Architect