An Architectural Perspective of Real-Time Ada Applications
While there are appear to be many ways in which real-time Ada systems can be designed, it is observed that they can be described using four architectural families: the Timeline, Event-Driven, Pipeline, and Client-Server architectures. This paper describes the principal characteristics of each of these architecture families with respect to their ability to provide bounded application response times, their cost, and safety at a high level. In addition, the use of important Ada constructs for each architecture family is discussed, and examples of application domains that use each of these architectures are identified.
KeywordsPipeline Architecture Protected Object Output Manager Architectural Perspective Deadline Monotonic
Unable to display preview. Download preview PDF.
- 1.The Common Object Request Broker: Architecture and Specification, Revision 2.0, July 1996, Object Management Group, Framingham, Massachusetts, USAGoogle Scholar
- 2.The Joint Revised Realtime CORBA Submission, March, 1999, Object Management Group, Framingham, Massachusetts, USAGoogle Scholar
- 4.Locke, C. D., Software Architecture for Hard Real-Time Applications: Cyclic Executives vs. Fixed Priority Executives, Real-Time Systems Journal, Kluwer Publishers, vol 4, 1992Google Scholar
- 5.The Ravenscar Tasking Profile for High Integrity Real-Time Programs, A. Burns, B. J. Dobbing, G. Romanski, in Reliable Software Technologies — Ada-Europe’ 98, Lecture Notes in Computer Science, Springer-Verlag, June, 1998Google Scholar
- 6.Sprunt, H. M. B., Sha, L., Lehoczky, J.P., Aperiodic Task Scheduling on Hard Real-Time Systems, Real-Time Systems Journal, Kluwer Publishers, 1989Google Scholar