3. Methodology used

3.1. Methodology

The architecture of the system and design were created in an iterative way – from outline in the DOW, through the meeting discussions within consortium and with User Board, to this deliverable. We took into account also previous development of components of the system, as some of them existed before the COMSODE project started or before work on this deliverable started.

The project uses internal collaborative space - called wiki - based on Atlassian Confluence technology with access of all members of the project team. There was established a dedicated space in the internal wiki for collection of inputs to the architecture and design from consortium members and from members of User Board. Also input (obtained by means other than wiki) from possible users of the platform was included in use cases.

ODN platform is planed to reuse, integrate and extend open source components, and architecture is based on the current status of those components and also on what additional features are possible to be included in those components.

It is expected, that the deliverable will be updated when significant design changes are required due to changes in existing components or when a new component that better fits the project needs becomes available and can replace the currently selected component.

3.2. Partner contributions

The architecture and design document was prepared under management of consortium member - EEA, LTD.

Tomas Knap and Peter Hanečák are architects of ODN and UnifiedViews and DSE CUNI provided main input to Use cases.

Project coordinator UNIMIB, DSE CUNI and ADDSEN have reviewed the pre-final version of the document.