UNICOS Application Builder

Architecture Review

18/01/2013

UAB Model

FESA Editor

Plugin Base

S7IG S7LG WinCCOA

CPC Wizard

Bootstrap Bootstrap Installer

Type Builder

Wizard Components

Ext Config Utils

OLPROC++ Ext Config Plugin

CIET FE CIET WinCCOA

CIET Wizard

UAB Modules & Dependencies

UAB Model

FESA Editor

Plugin Base

S7IG S7LG WinCCOA

CPC Wizard

Bootstrap Bootstrap Installer

Type Builder

Wizard Components

Ext Config Utils

OLPROC++ Ext Config Plugin

CIET FE CIET WinCCOA

CIET Wizard

UAB Core

CPCCIET

SURVEY CRYO

OLPROC++

Bootstrap

TCT

Development & Maintenance Responsibles

AdrienAlexey

Bart

Ivan

Ext Config

SVN Layout

UAB Components

UAB Plug-ins

Current Layout Alternative Layout

Grouped byComponents

Current approach• Only one person is responsible of releasing the UAB components

× Time consuming× Low flexibility

• The release of a UAB component implies releasing all the dependencies All the UAB modules are linked to the latest development version (always up to date) Less effort required to maintain the dependencies× Some components are released even if there are no changes since the previous release

• Modifications in the core can be applied to all dependent modules Refactoring allowed

Alternative approach• The responsible of each UAB Component will do the release

Time consuming: spread among component responsibles More flexible× Total effort required for releases and update dependencies is bigger

• A module should be linked to released dependencies only× Risk of having dependencies with very old modules× The responsible of each module will manage the dependencies× New features are not available until the dependency is released

• Modifications in the core can not be applied to all dependent modules× Refactoring not allowed

Release Procedure

• Requirements for redundant PLCs

• Versioning

To discuss …