Task 8: e-Service Middleware Design

Activity: development

Description: The task is to define an architecture of the e-service-supporting middleware software - its components and how they are arranged to work together - to realise the behaviour specified formally during Task 7. The architecture also defines the interface of all middleware-conforming e-services, but avoids concrete implementation decisions, as they are subject of the following Task 9. Design decisions are expressed with object-oriented concepts, using a programming language-neutral notation such as UML.

Purpose: To make design decisions concering the components of the system and their relationships, as needed to deliver the fuctionality specified during Task 7. As a result, to bring the formal specification closer to the actual implementation.

Report: See Implementation