scispace - formally typeset
Search or ask a question

Real-Time Design Patterns

TL;DR: In this paper, the authors present a policy abstract for policy-making in the context of health care this paper..., and discuss the following topics:Healthcare.Healthcare
Abstract: Policy Abstract Policy

Content maybe subject to copyright    Report

Citations
More filters
Book
01 Jan 2007
TL;DR: The proposed book will provide an introduction to SysML, and instruction on how to implement it, for all these new users, and is likely to be the first available book on Sys ML in English.
Abstract: UML, the Universal Modeling Language, was the first language designed to fulfill the requirement for "universality." However, it is a software-specific language, and does not support the needs of engineers designing from the broader systems-based perspective. Therefore, SysML was created. It has been steadily gaining popularity, and many companies, especially in the heavily-regulated Defense, Automotive, Aerospace, Medical Device and Telecomms industries, are already using SysML, or are plannning to switch over to it in the near future. However, little information is currently available on the market regarding SysML. Its use is just on the crest of becoming a widespread phenomenon, and so thousands of software engineers are now beginning to look for training and resources. The proposed book will provide an introduction to SysML, and instruction on how to implement it, for all these new users. *The first available book on SysML in English *Insider information! The author is a member of the SysML working group and has written sections of the specification *Special focus comparing SysML and UML, and explaining how both can work together

457 citations

Proceedings ArticleDOI
03 Dec 2007
TL;DR: This paper introduces the simplex reference model which is distinguished by: a plant being controlled in an external context, a machine performing the control, a domain model that estimates the plant state, and the safety requirements that must be met.
Abstract: Cyber-physical systems are networked, component-based, real-time systems that control and monitor the physical world. We need software architectures that limit fault-propagation across unreliable components. This paper introduces our simplex reference model which is distinguished by: a plant being controlled in an external context, a machine performing the control, a domain model that estimates the plant state, and the safety requirements that must be met. The simplex reference model assists with constructing CPS architectures which limit fault-propagation. We present a representative case study to highlight the ideas behind the model and our particular decomposition.

122 citations


Cites background from "Real-Time Design Patterns"

  • ...Recent design patterns, such as [17] and [18], address issues faced by real-time domains....

    [...]

  • ...The “Safety Executive” [17] is one pattern which describes how a component should enter its fail-safe state....

    [...]

Book
22 Mar 2010
TL;DR: The introduced Coupled Transformations method uses this relationship to automatically include implementation details which increases their prediction accuracy, and is validated in several case studies showing the increased accuracy as well as the applicability of the overall approach by third parties.
Abstract: Component-based software engineering aims at developing software systems by assembling pre-existing components to build applications. One advantage gained from this is an increased predictability of the system's performance based on its constituting components. As models are used during software design but performance is a run-time attribute, the necessary abstraction in models from implementation details might remove performance-relevant aspects resulting in a loss of prediction accuracy. The solution presented in this thesis introduces the Palladio Component Model for component-based software design with predictable performance attributes. Transformations map instances of this model into implementations resulting in a deterministic relationship between the model and its implementation. The introduced Coupled Transformations method uses this relationship to automatically include implementation details which increases their prediction accuracy. The approach is validated in several case studies showing the increased accuracy as well as the applicability of the overall approach by third parties.

69 citations


Cites methods from "Real-Time Design Patterns"

  • ...However, after starting the behaviours it uses the Barrier pattern (Douglass, 2002) to wait for all threads to terminate before returning....

    [...]

Journal ArticleDOI
TL;DR: The application of object-oriented modeling techniques to control software development for complex manufacturing systems, with particular focus on case studies taken from the packaging industry and design patterns that can be abstracted from such case studies are presented.

65 citations

Journal ArticleDOI
TL;DR: This research investigates how an approach similar to the well-known design patterns can be applied in the analysis phase of embedded systems development, prior to design and coding, and explores how object-oriented modeling notations can be used to represent structural and behavioral information as part of commonly occurring object analysis patterns.
Abstract: Some of the most challenging tasks in building a software system are capturing, refining, and analyzing requirements. How well these tasks are performed significantly impacts the quality of the developed software system. The difficulty of these tasks is greatly exacerbated for the software of embedded systems as these systems are commonly used for critical applications, have to operate reliably for long periods of time, and usually have a high degree of complexity. Current embedded systems software development practice, however, often deals with the (requirements) analysis phase in a superficial manner, instead emphasizing design and implementation. This research investigates how an approach similar to the well-known design patterns, termed object analysis patterns, can be applied in the analysis phase of embedded systems development, prior to design and coding. Specifically, our research explores how object-oriented modeling notations, such as the Unified Modeling Language (UML), can be used to represent structural and behavioral information as part of commonly occurring object analysis patterns. This work also investigates how UML-based conceptual models of embedded systems, based on the diagram templates in the object analysis patterns, can be automatically analyzed using the Spin model checker for adherence to properties specified in linear-time temporal logic (LTL) using a previously developed UML formalization framework. We have applied these patterns to several embedded systems applications obtained from the automotive industry. This paper describes one of our case studies and illustrates how our approach facilitates the construction of UML-based conceptual models of embedded systems and the analysis of these models for adherence to functional requirements.

61 citations


Cites background from "Real-Time Design Patterns"

  • ...Current embedded systems software development practice, however, often deals with the (requirements) analysis phase in a superficial manner, instead emphasizing design and implementation....

    [...]

  • ...Index Terms—Object-oriented modeling, embedded systems, requirements, patterns, conceptual modeling, object analysis, formal specification, model checking....

    [...]

  • ...Additionally, use scenarios to capture behavioral information (using sequence charts) about the interaction between actors and system....

    [...]

References
More filters
Book
01 Jan 1997
TL;DR: This concise overview introduces you to UML, highlighting the key elements of its notation, semantics, and processes and offers the first look at the emerging Objectory Software Development Process derived from the methodologies of Grady Booch, Ivar Jacobson, and James Rumbaugh.
Abstract: Today, a software designer or architect who seeks to represent the design of a software system can choose from a wide variety of notational languages, each aligned with a particular analysis and design methodology. Ironically, this wide variety of choice is one impediment to the significant benefits promised by software reuse. The emergence of the Unified Modeling Language (UML) -- created by the joint efforts of leading object technologists Grady Booch, Ivar Jacobson, and James Rumbaugh with contributions from many others in the object community -- represents one of the most significant developments in object technology. Supported by a broad base of industry-leading companies, the UML merges the best of the notations used by the three most popular analysis and design methodologies, Booch, OOSE (use-cases), and OMT, to produce a single, universal modeling language that can be used with any method.Written for those already grounded in object-oriented analysis and design, this concise overview introduces you to UML, highlighting the key elements of its notation, semantics, and processes. Included is a brief explanation of UML's history, development, and rationale, as well as discussions on how UML can be integrated into the object-oriented development process. In addition, the book profiles various modeling techniques associated with UML -- use cases, CRC cards, design by contract, dynamic classification, interfaces, and abstract classes -- along with concise descriptions of notation and semantics and numerous insightful tips for effective use based on the authors' experience. In addition, the authors offer the first look at the emerging Objectory Software Development Process derivedfrom the methodologies of Grady Booch, Ivar Jacobson, and James Rumbaugh. To give you a feel for the UML in action, the book includes a Java programming example that outlines the implementation of a UML-based design.You will come away with an excellent understanding of UML essentials, insight into how UML functions within the software development process, and a firm foundation upon which to expand and build your knowledge of the Unified Modeling Language.

883 citations

Book
31 Aug 1993
TL;DR: In this article, the authors present a framework for describing real-time systems with RMA and rate-monotonic analysis, as well as a set of rules of thumb.
Abstract: Preface. Part 1: Introduction. 1. About this Handbook. 2. Fundamentals of RMA. Part 2: Concepts and Techniques. 3. A Framework for Describing Real-Time Systems. 4. Techniques for Analyzing Timing Behavior. Part 3: Analyzing Real-Time Systems. 5. Basic Real-Time Situations. 6. Advanced Real-Time Situations. 7. Effects of Operating System and Runtime Services on Timing Analysis. Part 4: Using the Handbook on Realistic Systems. 8. Analyzing Complex Systems. 9. Designing with Rate Monotonic Analysis. Part 5: Appendices. A. Rules of Thumb. B. Notation Used in this Handbook. C. Bibliography. D. Glossary. E. Index.

579 citations