SEESCOA stands
for Software Engineering for Embedded Systems using a Component
Oriented Approach. The project runs from October 1999 till September
2003. It is a project with a total budget of EUR 2'000'000, after it
has been classified as a top project. It is carried out by 4 academic
partners:
The Programming Technology Lab (PROG) at the Vrije Universiteit
Brussel (VUB)
Research group PARIS of the 'RijksUniversity Ghent' (RUG)
Research group DISTRINET of the Katholieke Universiteit Leuven
(KUL)
Research Group 'Centrum of Expertise for Digital Media' (EDM) of
the 'Limburgs Universitair Centrum' (LUC)
SEESCOA is
funded by the IWT (Flemish Institue of Science and Technology) and 6
industrial partners. These are: Siemens,
Barco-graphics, Agfa Gevaert, Imec, Philips and Alcatel.
Highlights of this period:
In the beginning of the project company visits were organized.
During these visits all the different companies explained how they were
developing their embedded systems.
With a plethora of component definitions wandering around, we had
to define what a component was. Therefore I injected the Borg
definition, of agents into the project. In essense it is a hybrid of
process based systems and event based systems. A component is an
autonomous entity. It does not share data with other components.
Components can receive messages and react upon them, but they do not
have a thread associated with them.
During the project I was responsible for the development of the
entire Java runtime architecture for components. The runteime
architecture has been extensively tested and is vcurrently being used
in other projects.
The SEESCOA runtime architecture allows component based
applications to be made distributed without any changes to the
underlying components. The resulting applications run peer to peer.
Error handling is done at a central place.
Deliverables
Some
deliverables written by me might help clarifying what components are
and how the component system can be used.
1. Philips
Visiation Report (24 pages); 25 April 2000 -- Werner Van Belle 2. Common Test
Case (10 pages) -- all members of the team 3. Working Definition of
Components
(19 pages) -- Werner Van Belle & David Urting 4. Real Time UML (26 pages) -- Werner
Van Belle & Tom Toutenel 5. The Component System (62 pages) --
Werner
Van Belle 6. Refinement of the
Component Architecture (36 pages) -- Werner
Van Belle 7. Component
Oriented Design of Common Test Case (126 pages) -- all members of the
team
