Service Oriented Communications

https://noppa.lut.fi/noppa/opintojakso/ct30a8901

Task: Design and implement an SOA based solution with the following aspects considered:

Topic: Group management solution

• For example doing practical works in universities or a facebook or a linkedin or wiki or … type of an approach (these are just examples of the solution area)

Requirements:

• Implemented with .NET (or with Java but in that case no support is offered)
• Client for the use of services (to be used for the checking the working implementation)

Evaluation:

• Number of services (max 3 points)
  • max points with 5
• Types of services (max 4 points)
  • not only client-service but also service-service (composition)
  • max points with 3
• Level of implementation (max 3 points)
  • XML-WSDL-SOAP (minimum)
  • WS-extensions (maximum points with tre use of 2 WS-*)
• SOA compatibility (max 6 points)
  • how well the approach follows the SOA principles

In addition to implementation the groups need to provide a report that explais the selected problem, design of the solution, implementation details and the explanations fot the evaluation criteria.

SOA Design Principles. primitive SOA.

1. Loose Coupling – Services maintain a relationship that minimizes dependencies
2. Service Contract – Services adhere to a communications agreement defined by one or more service descriptions and related documents
3. Autonomy – Services have control over the logic they encapsulate
4. Abstraction – Beyond what is described in the service contract, services hide logic from the outside world
5. Reusability – Logic is divided into services with the intention of promoting reuse
6. Composability – Collections of services can be coordinated and assembled to form composite services
7. Statelessness – Services minimize retaining information specific to an activity
8. Discoverability – Services are designed to be outwardly descriptive so they can be found and accessed via discovery mechanisms

Contemporary SOA