Service Demand

training for SOA

veryard projects > so > training

we offer

soa

available workshops

links

consultancy

management briefings

independent advice on tools and methods

	Modelling for SOA - Concepts and Governance A 1-day workshop for senior IT planners and business architects
	Modelling for SOA - Techniques A 3-day workshop providing practical instruction in the modeling and design techniques.
	Information Modelling for SOA A 4-day workshop providing practical instruction in the modeling and design of document structures and schemas within an SOA context.

Each workshop is aimed at a different audience. Although similar topics are included in each workshop, these topics are covered at different levels of detail and practicality.

recent material

Modelling for SOA - Concepts and Governance

veryard projects > so > training > concepts

Objectives, Approach, Timing

This is a high-level 1-day workshop, concentrating on the strategic vision and opportunities of SOA.

Participants will gain an understanding of SOA through modeling, and an understanding of the role of modeling in the planning, development, implementation and management of SOA. They will gain an awareness of the available modeling and design techniques for the development and management of services and systems.

Audience

Business/System Architects

Agenda

Introduction	Innovation and Challenge of SOA – Business Adaptability and Alignment. Adding Value to Business Services – Smart Services, Differentiated Services, Context-Aware Services, Services on Demand
Service Concepts	Basic Types of Business Service. Basic Patterns of Service Delivery and Aggregation. Distributed Design-by-Contract.
Service Design	Service Identification. Partitioning & Clustering, Service Bundling & Unbundling. Service Specification & Policy.
Modelling for Service Design	Development and Use of Business Process Models, Business Asset Models & Business Rule Models. Identification of Usage Scenarios.
System Design & Governance	Architectural Frameworks, Service Socket Identification, Service Policy Identification, System Policy Identification, Distributed System Management, Dynamic System Behavior
Modelling for System Design and Governance	Development and Use of Business Process Models, Business Asset Models, Business Risk Models and System Dynamics Models.
Conclusions	Ownership & Governance Issues Technological Review Business Case Framework SOA Roadmap

Modelling for SOA - Techniques

veryard projects > so > training > techniques

Objectives, Approach, Timing

This is a 3-day hands-on workshop, providing an opportunity to learn practical skills for the development and management of SOA. Participants will gain an understanding of SOA through modeling, and an understanding of the role of modeling in the planning, development, implementation and management of SOA. They will gain experience of the available modeling and design techniques for the development and management of services and systems.

Audience

Architects, Business/Project Analysts

Agenda

Introduction	Basic Concept of SOA. Overview of the SOA Lifecycle.
Service Concepts	Basic Types of Business Service. Basic Patterns of Service Delivery and Aggregation. Distributed Design-by-Contract.
Service Design Techniques	Service Identification. Partitioning & Clustering, Service Bundling & Unbundling. Service Specification & Policy. Usage Scenarios for Web Service design and implementation
Business Process Modelling for Service Design	Concepts notations, development and use. Includes practical session.
Business Asset Modelling for Service Design	Concepts notations, development and use. Includes practical session.
Business Rule Modelling for Service Design	Concepts notations, development and use. Includes practical session.
Extended Exercise	A simple case study to decompose a business scenario into a set of business services. Each team will be supported in using a different modeling approach, allowing the results to be compared.
Further Modelling Topics	Granularity, Generality, Performance, Versioning
Generalized Service Design	Ownership, Generality, Performance,
Extended Exercise II	A realistic case study to create a set of shared business services.
System Design & Governance	Contract design, Design traceability, Trust frameworks, Policy Frameworks
SOA Lifecycle	Taking a more detailed look at the development and management of SOA, showing how the modeling techniques learned on this workshop fit into the overall process.

Information Modelling for SOA

veryard projects > so > training > info model

Objectives, Approach, Timing

This is a 4-day hands-on workshop, providing an opportunity to learn practical skills for the development and management of information exchange within an SOA context.

Whereas traditional modeling courses present students with a blank sheet of paper and require the construction of a simple model, our approach is more realistic. We present students with existing models, conflicting requirements and clashing perspectives, and help them to use the techniques of information modeling to negotiate ways of linking together heterogeneous systems and services.

Traditional data modeling techniques concentrate on the design of data storage – such as corporate databases. For SOA, the focus is on the design of the information structure and semantics at the service interface, and on the design of documents and schemas that are passed around a complex network of services. There is also a need to pay attention to the ownership and protection of information assets.

Audience

Information Architects, Business/Project Analysts

Agenda

Introduction Motivation, Overview & Context

Basic Concepts

Exercise 1: Simple Modeling In this exercise, the students are given a simple scenario and required to model it. Among other things, this exercise helps to highlight the different ways each group interprets the scenario, and the investigation (fact-finding and negotiation) that would be needed to choose between or reconcile different interpretations.

Exercise 2: Model Review In this exercise, the students are given an existing model, challenged to identify its strengths and weakness, and recommend improvements.

Using the Data Model Data Storage Design / Enhancement - Persistent Data and Data Integrity
Information Services – Virtual Management Information, Distributed Data Warehousing & Mining, Information Grid

Refining the Data Model

Rescoping / Incorporating New Requirements

Refactoring / Rechunking

Exercise 3: Start from the Information Needs In this exercise, the students are given some business information needs, and challenged to support them from an existing data store (whose logical model is provided).
The exercise is then reversed, and students develop scenarios that can/cannot be supported by a given data store, to understand the degree of flexibility implicit in the data structures.

Quality Goals: What The Data Modeller is Trying to Achieve

Just Enough Detail?

Just Enough Accuracy?

Corporate/Domain Consistency?

Quality Data Modelling Patterns and Pitfalls

Managing the Data Model(s) Coordination Issues

Exercise 4: Evolving an Existing Model In this exercise, the students are presented with a series of increasingly complex demands. The task is to evolve and extend the data model to accommodate these requirements, and also to clearly articulate the implications of any changes that they make.

Mapping from one data model to another

Tables and Views

Transition: AS-IS to TO-BE

Data Migration & Aggregation

Data Interfaces, Web Services, APIs and Exchange Protocols

Data and Component Services

Commercial background to XML and industry models

Exercise 5: Negotiating Information Exchange In this exercise, each team is given a different problem, with a different perspective, and required to develop a data model from this perspective. The teams then negotiate interfaces and protocols for the exchange of information, while each preserving the integrity of their own model.

Close Brief Recapitulation and Review

veryard projects - innovation for demanding change

[top]

[home page]

[contact us]

in asssociation with

Introduction	Motivation, Overview & Context
Basic Concepts
Exercise 1: Simple Modeling	In this exercise, the students are given a simple scenario and required to model it. Among other things, this exercise helps to highlight the different ways each group interprets the scenario, and the investigation (fact-finding and negotiation) that would be needed to choose between or reconcile different interpretations.
Exercise 2: Model Review	In this exercise, the students are given an existing model, challenged to identify its strengths and weakness, and recommend improvements.
Using the Data Model	Data Storage Design / Enhancement - Persistent Data and Data Integrity Information Services – Virtual Management Information, Distributed Data Warehousing & Mining, Information Grid
Refining the Data Model	Rescoping / Incorporating New Requirements Refactoring / Rechunking
Exercise 3: Start from the Information Needs	In this exercise, the students are given some business information needs, and challenged to support them from an existing data store (whose logical model is provided). The exercise is then reversed, and students develop scenarios that can/cannot be supported by a given data store, to understand the degree of flexibility implicit in the data structures.
Quality Goals: What The Data Modeller is Trying to Achieve	Just Enough Detail? Just Enough Accuracy? Corporate/Domain Consistency?
Quality Data Modelling	Patterns and Pitfalls
Managing the Data Model(s)	Coordination Issues
Exercise 4: Evolving an Existing Model	In this exercise, the students are presented with a series of increasingly complex demands. The task is to evolve and extend the data model to accommodate these requirements, and also to clearly articulate the implications of any changes that they make.
Mapping from one data model to another	Tables and Views Transition: AS-IS to TO-BE Data Migration & Aggregation
Data Interfaces, Web Services, APIs and Exchange Protocols	Data and Component Services Commercial background to XML and industry models
Exercise 5: Negotiating Information Exchange	In this exercise, each team is given a different problem, with a different perspective, and required to develop a data model from this perspective. The teams then negotiate interfaces and protocols for the exchange of information, while each preserving the integrity of their own model.
Close	Brief Recapitulation and Review