Your "What" Is My "How": Iteration and Hierarchy in System Design

Whalen, Michael W.; Gacek, Andrew; Cofer, Darren; Murugesan, Anitha; Heimdahl, Mats P. E.; Rayadurgam, Sanjai

doi:10.1109/ms.2012.173

Cited by 60 publications

(31 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Often, the physical constraints drove our revision (de-idealization) of the requirements. Whalen et al, report similar experience with large avionic systems, in which the requirements were as likely to be wrong as the models [52]. They found, as we did, that the analysis of formal models was e↵ective in uncovering inconsistencies between the requirements and implicit assumptions about the environment in which the system was to be deployed.…”

Section: Related Worksupporting

confidence: 68%

Automated requirements analysis for a molecular watchdog timer

Ellis

Henderson

Klinge

et al. 2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

View full text Add to dashboard Cite

Dynamic systems in DNA nanotechnology are often programmed using a chemical reaction network (CRN) model as an intermediate level of abstraction. In this paper, we design and analyze a CRN model of a watchdog timer, a device commonly used to monitor the health of a safety critical system. Our process uses incremental design practices with goal-oriented requirements engineering, software verification tools, and custom software to help automate the software engineering process. The watchdog timer is comprised of three components: an absence detector, a threshold filter, and a signal amplifier. These components are separately designed and verified, and only then composed to create the molecular watchdog timer. During the requirements-design iterations, simulation, model checking, and analysis are used to verify the system. Using this methodology several incomplete requirements and design flaws were found, and the final verified model helped determine specific parameters for biological experiments.

show abstract

Section: Related Worksupporting

confidence: 68%

Automated requirements analysis for a molecular watchdog timer

Ellis

Henderson

Klinge

et al. 2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

View full text Add to dashboard Cite

show abstract

“…While constructing models of a system -by exploring the solution domain -an engineer adds architectural and design detail not specifically stated in requirements, architectural and design information that helps clarify existing requirement as well as discover missing ones [6,27]. Similarly, as requirements are modified and added, the models evolve to accommodate the new constraints.…”

Section: A Model Based Development Approachmentioning

confidence: 99%

From Requirements to Code: Model Based Development of a Medical Cyber Physical System

Murugesan

Heimdahl

Whalen

et al. 2017

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

The advanced use of technology in medical devices has improved the way health care is delivered to patients. Unfortunately, the increased complexity of modern medical devices poses challenges for development, assurance, and regulatory approval. In an e ort to improve the safety of advanced medical devices, organizations such as FDA have supported exploration of techniques to aid in the development and regulatory approval of such systems. In an ongoing research project, our aim is to provide effective development techniques and exemplars of system development artifacts that demonstrate state of the art development techniques.In this paper we present an end-to-end model-based approach to medical device software development along with the artifacts created in the process. While outlining the approach, we also describe our experiences, challenges, and lessons learned in the process of formulating and analyzing the requirements, modeling the system, formally verifying the models, generating code, and executing the generated code in the hardware for generic patient controlled analgesic infusion pump (GPCA). We believe that the development artifacts and techniques presented in this paper could serve as a generic reference to be used by researchers, practitioners, and authorities while developing and evaluating cyber physical medical devices. Abstract. The advanced use of technology in medical devices has improved the way health care is delivered to patients. Unfortunately, the increased complexity of modern medical devices poses challenges for development, assurance, and regulatory approval. In an effort to improve the safety of advanced medical devices, organizations such as FDA have supported exploration of techniques to aid in the development and regulatory approval of such systems. In an ongoing research project, our aim is to provide effective development techniques and exemplars of system development artifacts that demonstrate state of the art development techniques. In this paper we present an end-to-end model-based approach to medical device software development along with the artifacts created in the process. While outlining the approach, we also describe our experiences, challenges, and lessons learned in the process of formulating and analyzing the requirements, modeling the system, formally verifying the models, generating code, and executing the generated code in the hardware for generic patient controlled analgesic infusion pump (GPCA). We believe that the development artifacts and techniques presented in this paper could serve as a generic reference to be used by researchers, practitioners, and authorities while developing and evaluating cyber physical medical devices.

show abstract

“…This system can be of any domain, e.g., SW, HW, mechanical, electrical, etc, and also a heterogeneous system, i.e., a system composed of parts from multiple domains. Structuring the specifications for a system in accordance with its architecture is an established idea [11,79] that is also advocated in FuSa standards such as ISO 26262.…”

Section: Application Context: Authoring Specificationsmentioning

confidence: 99%

Providing tool support for specifying safety-critical systems by enforcing syntactic contract conditions

Westman

Nyberg

2017

Requirements Eng

View full text Add to dashboard Cite

Functional safety standards such as IEC 61508 and ISO 26262 advocate a particularly stringent requirements engineering where safety requirements must be structured in a hierarchical manner and specified in accordance with the system architecture. In contrast to the stringent requirements engineering in functional safety standards, according to previous studies, requirements engineering in industry is in general of poor quality. Contracts theory has been previously shown to be suitable for supporting such a stringent requirements engineering effort; this support has also been implemented in tools. However, to use these contract-based tools, requirements must be formalized, which is a major challenge in industry. Therefore, to support current industrial requirements engineering practice and the stringent requirements engineering in functional safety standards, it is shown how tool support can be provided even when requirements, and also architectures, are not formalized. This is achieved by enforcing syntactic, yet formal, conditions in contracts theory. Despite the need for further validation, initial findings in an industrial case study indicate high potential in realizing the proposed support in an industrial setting.

show abstract

Your "What" Is My "How": Iteration and Hierarchy in System Design

Cited by 60 publications

References 9 publications

Automated requirements analysis for a molecular watchdog timer

Automated requirements analysis for a molecular watchdog timer

From Requirements to Code: Model Based Development of a Medical Cyber Physical System

Providing tool support for specifying safety-critical systems by enforcing syntactic contract conditions

Contact Info

Product

Resources

About