Skip to main content Accessibility help
×
Hostname: page-component-848d4c4894-x5gtn Total loading time: 0 Render date: 2024-04-30T14:20:52.482Z Has data issue: false hasContentIssue false

18 - Designing Concurrent and Real-Time Software Architectures

from PART III - Architectural Design

Published online by Cambridge University Press:  05 June 2012

Hassan Gomaa
Affiliation:
George Mason University, Virginia
Get access

Summary

This chapter describes the design of concurrent and real-time software architectures. Real-time software architectures are concurrent architectures that usually have to deal with multiple streams of input events. They are typically state-dependent, with either centralized or decentralized control. Thus, the design of finite state machines, as described in Chapter 10, state-dependent interaction modeling, as described in Chapter 11, and the control patterns, as described in this chapter, are very important in the design of real-time software architectures.

Section 18.1 describes concepts, architectures, and patterns for designing concurrent and real-time software architectures. Section 18.2 describes the characteristics of real-time systems. Section 18.3 describes control patterns for real-time software architectures. Section 18.4 describes the concurrent task structuring criteria. Section 18.5 describes the I/O task structuring criteria, and Section 18.6 describes the internal task structuring criteria. Section 18.7 describes the steps in developing the concurrent task architecture. Section 18.8 describes designing the task interfaces using task communication and synchronization. Section 18.9 describes documenting task interface and behavior specifications. Section 18.10 describes concurrent task implementation in Java using threads.

CONCEPTS, ARCHITECTURES, AND PATTERNS FOR CONCURRENT AND REAL-TIME SOFTWARE ARCHITECTURES

An important activity in designing real-time software architectures is to design concurrent objects, which are referred to as concurrent tasks in this chapter. Chapter 14 described the design of passive objects, which do not have threads of control. Concurrency concepts were introduced in Chapter 4.

Type
Chapter
Information
Software Modeling and Design
UML, Use Cases, Patterns, and Software Architectures
, pp. 318 - 343
Publisher: Cambridge University Press
Print publication year: 2011

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
×