Pattern-based control systems engineering

Sanz, Ricardo; Zalewski, Janusz

doi:10.1109/mcs.2003.1200245

Cited by 34 publications

(1 citation statement)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Because of that, some experience researchers on patternbased control engineering point out main benefits to motivate the application of pattern-based design approach in the control engineering field. Sanz and Zalewski (2003) defines the pattern-based approach as "a method of generating solutions based on existing design knowledge". They stress that the pattern-based control engineering is not a control design method in the classic sense but a new way of managing and exploiting existing design knowledge for control systems, leading to better solutions.…”

Section: Design Patterns In Control Engineeringmentioning

confidence: 99%

Safe-Guarded Agent Design Pattern for Mechatronic Systems

Dao

Vries

Amerongen

2010

IFAC Proceedings Volumes

View full text Add to dashboard Cite

Section: Design Patterns In Control Engineeringmentioning

confidence: 99%

Safe-Guarded Agent Design Pattern for Mechatronic Systems

Dao

Vries

Amerongen

2010

IFAC Proceedings Volumes

View full text Add to dashboard Cite

The Concept of Reference Architectures

Cloutier

Müller²,

Verma

et al. 2009

Systems Engineering

174

129

View full text Add to dashboard Cite

The concept of Reference Architectures is novel in the business world. However, many architects active in the creation of complex systems frequently use the term Reference Architecture. Yet, these experienced architects do not collectively have a consistent notion of what constitutes a Reference Architecture, what is the value of maintaining the Reference Architecture, what is the best approach to visualizing a Reference Architecture, what is the most appropriate level of abstraction, and how should an architect make use of the Reference Architecture in their work? This paper examines current Reference Architectures and the driving forces behind development of them to come to a collective conclusion on what a Reference Architecture should truly be. It will be shown that a Reference Architecture captures the accumulated architectural knowledge of thousands man-years of work. This knowledge ranges from why (market segmentation, value chain, customer key drivers, application), what (systems, key performance parameters, system interfaces, functionality, variability), to how (design views and diagrams, essential design patterns, main concepts). The purpose of the Reference Architecture is to provide guidance for future developments. The Reference Architecture incorporates the vision and strategy for the future. The Reference Architecture is a reference for the hundreds of teams related to ongoing developments. By providing this reference all these teams have a shared baseline of why, what and how. It is the authors' goal that this paper will facilitate further research in the concepts and ideas presented herein.

show abstract