Deliverable D3.2 SPIKE system components and functional descriptions

Abstract

This report outlines functional characteristics of main system components called managers. Since the managers have already been briefly defined in the architecture report, this report complements the architecture report and extends its functional view. Functional descriptions of all managers are provided on two levels – the level of particular managers as well as their constituents. In addition to the description of expected functionality, the report provides information on functional dependencies of constituents as well as a preliminary idea about APIs of the components. In order to document non-linearity of the development process, the report outlines also changes to the architecture report accepted after its publication.

The presented report is one of documents in a series of documents describing a system to be designed and implemented within the SPIKE project. This report is a functional description of main system components – it outlines ideas of a group of the project developer partners on what functionality the SPIKE system is going to be provided regarding its internal component structure. It complements the architecture report and extends it in the functional area. Thus, it represents a link between an overall functional view of the architectural description [D3.1] and a more technical description of the system's components to be provided in the upcoming deliverables D4.1 (Specification of components for Portal system) and D5.1 (Specification of components for the Service Bus subsystem). The aim is to define system managers’ functionality, to break the managers down into architectural pieces (so called modules), to define the functionality of these modules and mutual dependencies. This deliverable forms one of the pillars on which the work to be accomplished in the work packages 4 and 5 will be based. The deliverable structure is quite straightforward. In addition to a section listing all system managers, it consists of seventeen more parts – each part dedicated to one manager. The functionality of the following managers is described in the report:

Alliance Manager, Communication Manager, Content Manager, Display Manager, Identity Manager, Interface Manager, Intra Portlet Manager, Notification Manager, Platform Manager, Process Manager, Report Manager, Search Manager, Security Manager, Semantic Manager, Service Manager, Session Manager, and Wrapper Manager.

Each of these seventeen chapters provides information on a particular manager. The information incorporates:

-Context of the manager - defines relationships of the manager with those other managers which are in some way dependent on the given manager (are interested in the functionality offered by the manager) or which provide functionality consumed by the given manager.
-Use cases - describe the functionality offered by the manager. The functionality is presented in the form of use cases supported by the manager. 
-Structure of the manager - breaks down the manager into more fine-grained modules offering specific functional subtasks.
-Module functional description - defines the functionality offered by each module the manager consists of. The information includes description of module's goal and functionality, functional definition of module's API, and dependencies between the module and other modules of the manager and/or other managers.
-Module dependencies - illustrate dependencies of modules of a particular manager. The information is presented in the form of sequence diagrams.

You can download a short version of this document here:

D.3.2. SPIKE System Components

In order to obtain the full content of this document, please use the contact form below: