| 145 |
|
Many software systems are now being designed as a set of discrete, interacting components, instead of monolithic structures. Component interfaces specify the syntax of these interactions, and type models can define their semantics. In order to build a successful software system, however, an additional set of rules governing component interaction, the component architecture, is needed.
Layering is an important part of the architecture, but is not dealt with in component standards such as EJB and COM. A good layering of components promotes flexibility by limiting interaction. The rules by which components can communicate within and between layers should be stated and justified.
The purpose of this session is to examine the question of component architecture by considering a simple system, dividing it into components, creating a set of layers and assigning components to these layers. A set of rules governing interaction within and between layers should also be derived. This will then form the component architecture.
|
Sapient Ltd | Anthony Willoughby works as a technical architect for an internet consultancy, designing e-commerce applications. Previously he was an independent consultant for 8 years, specialising in object and component technology.
|
| Session: Think Tank 75 minutes | Level: Advanced |
|
Audience:
An understanding of objects and components. Useful for system designers and architects.
| Max 30 approx |
A poster summarising the conclusons of the session. I will prepare this afterwards.
Mixture of plenary sessions and group work (in groups of 3 - 5). Groups will produce posters summarising their ideas, for review by other groups. Some groups will also be encouraged to present one or two key ideas briefly.
| 145 |
|