Skip to main content Accessibility help
×
Hostname: page-component-8448b6f56d-jr42d Total loading time: 0 Render date: 2024-04-24T10:55:33.687Z Has data issue: false hasContentIssue false

12 - Component-Based Software Architectures for Real-Time Embedded Systems

from Part II - Real-Time Software Design Method

Published online by Cambridge University Press:  05 March 2016

Hassan Gomaa
Affiliation:
George Mason University, Virginia
Get access

Summary

In earlier chapters, the term component has been used informally. This chapter describes the design of distributed component-based software architectures in which the architecture for a real-time embedded system is designed in terms of components that can be deployed to execute on different nodes in a distributed environment. It describes the component structuring criteria for designing components that can be deployed to execute in a distributed configuration. The design of component interfaces is described, with component ports that have provided and required interfaces and connectors that join compatible ports.

Components are initially designed using the subsystem structuring criteria described in Chapter 10. Additional component configuration criteria are used to ensure that components are configurable, in other words that they can be effectively deployed to distributed physical nodes in a distributed environment. Architectural structure and communication patterns described previously in Chapter 11 are also used in the design of component-based software architectures.

Components can be effectively modeled in UML with structured classes and depicted on composite structure diagrams. Structured classes have ports with provided and required interfaces. Structured classes can be interconnected through their ports via connectors that join the ports of communicating classes. Chapter 2, Section 2.10 and Chapter 10, Section 10.2.1 introduce the UML notation for composite structure diagrams. This chapter describes in detail how component-based software architectures are designed.

Section 12.1 describes concepts for distributed component-based software architectures. Section 12.2 describes the steps in designing distributed component-based software architectures. Section 12.3 describes how component interfaces are designed with provided and required interfaces. Section 12.4 describes the concepts and design of composite subsystems and components. Section 12.5 describes some examples of distributed component-based software architectures. Section 12.6 describes component structuring criteria for structuring a software architecture into configurable distributed components. Section 12.7 describes the design of sequential and concurrent service subsystems. Section 12.8 describes issues in the distribution of data in distributed systems. Section 12.9 describes component deployment to a distributed configuration. Finally, Section 12.10 describes the design of software connectors.

CONCEPTS FOR COMPONENT-BASED SOFTWARE ARCHITECTURES

A component integrates the concepts of encapsulation and concurrency. An important goal of a component-based software architecture is to provide a concurrent message-based design that is highly configurable.

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2016

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×