SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Defining Software Components: Concepts and Specifications in System Engineering

elaine-skinner avatar
elaine-skinner
6 diapositives · 190 Views · Nov 30, 2014

This document explores the fundamental principles of software components in system and software engineering, emphasizing definitions, interfaces, validation, and interaction within component systems. It outlines how a component serves as an independent unit of composition with specified interfaces, capable of integration within defined architectures. The content also addresses the nuances of packaging, API behavior, and quality of service, essential for seamless deployment and composition by third parties. Insight is drawn from notable industry examples and academic contributions, providing a comprehensive view.

Defining Software Components: Concepts and Specifications in System Engineering - slide 1
01 / 6Defining Software Components: Concepts and Specifications in System Engineering
1 / 17

Télécharger la présentation

Defining Software Components: Concepts and Specifications in System Engineering
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Components Programming Technology Lab (PROG) System & Software Engineering Lab (SSEL) Dept. of Computer Sciences (DINF) Vrije Universiteit Brussel (VUB) Werner Van Belle (WVB) Tom Toutenel (TT) SEESCOA

  2. Components & Industrial Partners • “A nontrivial piece of software, that fulfills a clear function, has a clear boundary and can be integrated in a well-defined architecture. The component can, but need not be reusable.” Alcatel CDD • “A unit of packaging that includes an implementation, a specification of interfaces provided and required, validation code, and the design (incl. documents and source).” Alcatel RCD SEESCOA

  3. Components & Industrial Partners (ctd) • “Has an API that describes behaviour, not implementation.” Agfa (Portex presentation) . • “Clear interface. Self supporting, independent from other components.Component is a collection of routines, classes.” Barco Graphics . • “Obeys to the rules of its Component System.” Laszlo Huray . SEESCOA

  4. A Software Component Definition “A software component is a unit of composition with contractually specified interfaces and explicit context dependencies only. A software component can be deployed independently and is subject to composition by third parties” Szyperski & Pfister, ECOOP 1996 SEESCOA

  5. A Component • Independent entity  own code/data space  own control flow • Has an interface (API)  provided/required interface  describes expected interaction • Documented semantics • Quality of Service  Memory, Resources • Needs a component system • Validation code • Documented design & source SEESCOA

  6. A Component System • Handles the interaction between components allows specification of real-time behaviour • Support for asynchronous/synchronous events • Ensures interfaces are used correctly(as specified by the interacting components) • Provides glue components to connect ‘different’ components allows for example grouping of components • Platform transparency (seen from the components) SEESCOA