25 April 2000

S

E

E

S

C

O

A STWW - Programma

Software Engineering for

Embedded Systems using a

Component-Oriented Approach

Yolande BerbersDistriNet, KULeuven

S

E

E

S

C

O

A

Outline

Project overview

Project management

Short term task overview

Agenda of today

S

E

E

S

C

O

A

The current software technology cannot always fulfill these higher requirements

too late too expensive too many errors

The current software technology cannot always fulfill these higher requirements

too late too expensive too many errors

Context and problem statement

Embedded systems

functionality and complexity are ever increasing (communication, multi-media, …)

quality requirements are growing (ISO 900x)

time-to-market is getting smaller and smaller

S

E

E

S

C

O

AOur proposal: adaptation of successful methodologies for the specific requirements of embedded software

Our proposal: adaptation of successful methodologies for the specific requirements of embedded software

Context and problem statement

Administrative systems

an even bigger increase in functionality and complexity during the last 10 years

a comparable increase in quality requirements

focussed on methodological aspects of software production

modern methodologies have proven benefits

clear increase of productivity and quality improvement

S

E

E

S

C

O

A General methodology: case driven

SEESCOA is generic, conceptual basic research.All developed software is to be considered as proof-of-concept.

General methodology: case driven

SEESCOA is generic, conceptual basic research.All developed software is to be considered as proof-of-concept.

Innovative method for component-based software-development for ES, supported by

General purpose

a notation for component modeling, with emphasis on RT aspects, memory and power consumption, and supported by a development environment

a component architecture and method

a generic architecture for the realization of user interfaces for ES

improving the observability of the dynamic behavior of ES (debugging, profiling)

S

E

E

S

C

O

A

Consortium

Computer science departments of four Flemish universities, each with their own competence

VUB Component modeling

KULeuven Component architecture

LUC User interfaces

RUG Enhancing observability

S

E

E

S

C

O

A

User commission

6 companies, all members of the Vlaams Software Platform (VSP)

Agfa

Alcatel

Barco

Imec

Philips

Siemens Atea

cofinancing for 10%

S

E

E

S

C

O

A

WP

7:

fin

al v

alid

atio

n(s

econ

d c

ase

stu

dy)

WP

7:

fin

al v

alid

atio

n(s

econ

d c

ase

stu

dy)

Overview projectWP 1WP 1

WP6: Coordination and project managementWP6: Coordination and project management

WP2: component modelingWP2: component modeling

WP3: component architecture WP3: component architecture

WP4: user interfacesWP4: user interfaces

WP5: observabilityWP5: observability

0 6 12 18 24 30 36 42 48

S

E

E

S

C

O

A

WP 1: Orientation

purpose:

describing the state-of-the-art of development of embedded systems in Flemish companies

choice of example applications and a common case

choice of a common platform

first working definition of component

methodology:

visitation of the user members of the user commission

literature study

S

E

E

S

C

O

A

WP 2: component modelling

purpose:

design of a component modeling notation

component-composer environment that allows for cooperation and timing checks (static as well as dynamic)

modeling evolution and version control of components

methodology:

enhancing traditional IDL or UML-like notations with semantic information: synchronization, real-time and memory consumption aspects, dependencies between components

S

E

E

S

C

O

A

WP 3: component architecture

purpose:

method for component-based software development for embedded systems

definition of a suitable component architecture

integration of results from the other work packages in the common case

dynamic updates of components

methodology:

gradually improving the component architecture on examples

design and implementation of a common case integrating the results from the other work packages

S

E

E

S

C

O

A

WP 4: user interfaces

purpose:

evaluation of existing systems for UI

development of component technology for UI

improving the look-and-feel of UI by adding multimedia

increasing the productivity of UI development

assess feasibility of adaptable UI

methodology:

development of a UI for different cases, based on our component technology

building an environment to realize interfaces

S

E

E

S

C

O

A

WP 5: observability

purpose:

adding observability to components while limiting the computing and memory resources

development of a debugger component for external or embedded use

develop remote service technology

methodology:

specification of a debug interface for components

development of an external debugger and integration in our common case

S

E

E

S

C

O

A

WP 6: coordination and project management

purpose:

administrative support for the project

supporting and stimulating interaction between partners

interface to the user commission

timely delivery and dissemination of results

proposing, if needed, of “corrective”actions

methodology:

setup of a communication structure, including a web-site

organization of meetings and seminars

follow-up of commitments

follow-up of trends and evolutions in embedded systems

S

E

E

S

C

O

A

Contacts with user commission

visitations during the first months

project meetings every 6 months

presentations, demonstrations and reports

feedback by the user commission

a web-site with results, only accessible by members of the user commission and partners of the project

bilateral contacts between the members of the user commission and the academic partners for specific problems or additional projects

after 2 and after 4 year a broad seminar for the members of the VSP

S

E

E

S

C

O

A

Outline

Project overview

Project management

Short term task overview

Agenda of today

S

E

E

S

C

O

A

task 6.1: development of communication tools

web site for SEESCOA project with public and private (partners & user group only) pages:

General documents like the Project Proposal etc.Partner information: home pages, people, e-mailMeeting information: agendas, minutes,locationThe project timetable with milestones and deliverablestemplates for documents and presentationsPer work package: deliverables, intermediate resultsLatest news about the SEESCOA-projectEvents: conferences, meetings, ...Mailing list information, archives, ...

WP 6: coordination and project management

S

E

E

S

C

O

A

task 6.1: development of communication tools

mailing lists:seescoa project partners:

• list intended for the researchers involved in SEESCOA in the 4 universities

seescoa user group: • list intended for the members of the user group

(not operational yet)alias for seescoa project partners and user group

• intended to reach all involved parties (not operational yet)

WP 6: coordination and project management

S

E

E

S

C

O

A

task 6.2: organization of internal informal meetings

see progress report for details

kick-off meeting

meeting with reports from conference

meetings to discuss user group visits

meetings to discuss deliverables

WP 6: coordination and project management

S

E

E

S

C

O

A

task 6.3: use of progress monitoring tools

project timetable with milestones and deliverables is available on line for partners in Ms-project form

task 6.4: organization of project meetings every 6 months

task 6.5: open eye on related developments

several project partners attended Embedded Systems Conference Europe, and gave presentations for partners

task 6.6: support for dissemination of results

WP 6: coordination and project management

S

E

E

S

C

O

A

Outline

Project overview

Project management

Short term task overview

Agenda of today

S

E

E

S

C

O

A

Short term: months 7-15

T 2.2: Reuse contracts for component-based embedded software

T 3.2: Development of component architecture for first case

T 4.2: Implementation of component-based UIs

T 5.2: Specification and implementation of a generic debug interface for components

S

E

E

S

C

O

A

Medium term: months 16-24

T 2.3: Component composer + static consistency checking

T 3.3: refinement of architecture

T 3.4: design of common test case using components

T 4.3: Generalization of component-based UIs

T 5.3: Implementation of external debugger component

S

E

E

S

C

O

A

planning of next project meetings

according to STWW: every 6 months

after month 12

after month 18

after month 24

in line with milestones of project:

after month 15

after month 24

when ??

S

E

E

S

C

O

A

Outline

Project overview

Project management

Short term task overview

Agenda of today

S

E

E

S

C

O

A

Agenda

9.30: General project presentation

Yolande Berbers

10.00: Overview visitations

Koen De Bosschere

10.45: Coffee

11.00: Case and platform

Koen De Bosschere

11.30: definition of component

David Urting

12.15: Lunch

S

E

E

S

C

O

A

Agenda

14.00: Real-Time UML Tom Toutenel

14.30: Components in protocol stacks Yolande Berbers

15.00: Coffee

15.15: Evaluation of existing UI Realization Systems Karin Coninx & Jan Van den Bergh

15.45: Evaluation of on-chip debugging techniques Michiel Ronsse

16.15: Conclusion