A scenario-based approach to hierarchical state machine design

Bordeleau, Francis; Corriveau, Jean-Pierre; Selić, Bran

doi:10.1109/isorc.2000.839514

Cited by 15 publications

(10 citation statements)

References 9 publications

(23 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This constitutes an important nonfunctional requirement that must be considered by designers. The transition between scenario models and hierarchical state machines constitutes the focus of our work [4,9]. Our standpoint is that in order to successfully proceed from scenarios to state machines, it is not sufficient to grasp the details of individual scenarios, but also to understand the relationships that exist between these scenarios.…”

Section: Scenarios Of Different Typesmentioning

confidence: 99%

“…In order to integrate a role state machine of scenario S1 with f, the designer must establish the pair-wise relationships that exist between S1 and the scenarios already handled by f. Each relationship, we repeat, must suggest a specific behavior integration pattern [9]. Fig.…”

Section: Proposed Approachmentioning

confidence: 99%

“…We are suggesting that the exact inter-scenario relationship between two scenarios determine how these scenarios are to be integrated into a hierarchical state machine [4,9]. Our goal here is not to be exhaustive, but instead to demonstrate the importance of each of the four inter-scenario dependency relationships we introduce namely: containment, alternative, temporal and functional.…”

Section: On Scenario Relationships and Integration Of Behaviormentioning

confidence: 99%

“…More specifically, in order to integrate scenarios contained in different clusters, we use the State Machine Integration pattern of 0. This pattern (see [9] and [4] for details) suggests that each aspect in which a component participates be given its own hierarchical state in the behavior of that component. For example, after analyzing the overall set of ATM scenarios, scenarios have been partitioned into four subsets: normal operation, control, maintenance, configuration, and secure communication.…”

Section: Functional Dependencymentioning

confidence: 99%

See 3 more Smart Citations

On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design

Bordeleau

Corriveau

2001

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. One of the most crucial and complicated phases of system development lies in the transition from system behavior (generally specified using scenario models) to the detailed behavior of the interacting components (typically captured by means of communicating hierarchical finite state machines). This transition constitutes the focus of this paper. Our standpoint is that in order to succeed with this transition, it is not sufficient to grasp the details of individual scenarios, but also to understand the relationships that exist between the scenarios. Our claim is that different types of scenario relationships result in different hierarchical state machine structures. We identify and describe four different types of scenario relationships: containment dependency, alternative dependency, temporal dependency, and functional dependency. We also illustrate how such scenario relationships can be expressed in UML using stereotypes and how they guide the design of the corresponding hierarchical state machines.

show abstract

Section: Scenarios Of Different Typesmentioning

confidence: 99%

Section: Proposed Approachmentioning

confidence: 99%

Section: On Scenario Relationships and Integration Of Behaviormentioning

confidence: 99%

Section: Functional Dependencymentioning

confidence: 99%

See 2 more Smart Citations

On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design

Bordeleau

Corriveau

2001

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…In HiraishiÕs method, a safe Petri net is constructed from a dependency relation extracted from the firing sequences. Bordeleau et al proposed an approach which takes a traceable progression from use cases to object-based state machines (Bordeleau and Buhr, 1997;Bordeleau et al, 2000).…”

Section: Introductionmentioning

confidence: 99%

A petri-net-based synthesis methodology for use-case-driven system design

Cheung

Chow

2006

Journal of Systems and Software

View full text Add to dashboard Cite

Model‐based protocol specification

Mordecai

2019

Systems Engineering

View full text Add to dashboard Cite

We propose a holistic Model-Based Protocol Specification (MBPS) framework. Standards, procedures, and protocols are important anchors for interconnected systems: they facilitate the connectivity of billions of devices around the world, commodify advanced technologies and solutions, and enable efficient services involving trillions of transactions in aviation, medicine, e-commerce, transportation, infrastructure, and other domains. Domain protocols allow for conventional interactions within a domain among ecosystem entities and humans (eg, airline ticketing, financial transactions, etc). Protocol specifications must be formal, consistent, and verifiable. Nevertheless, most current standard protocols are text-based, unverifiable, and often inconsistent with themselves and with other standards. Text-based standards are difficult to manage, track, control, and adopt. MBPS includes three critical enablers: a modeling language, a modeling process, and a model-supported standardization process. This paper employs Object-Process Methodology (OPM), a model-based systems engineering framework, endorsed as ISO-19450, for modeling and simulation of the generic protocol specification process and for two examples: (a) a Kerberos authentication protocol revision based on a previous Kerberos model and on a recently discovered vulnerability and (b) a domain-specific Publish-Subscribe protocol application for selective information distribution. K E Y W O R D S formal protocol specification, Kerberos, model-based systems engineering (MBSE), objectprocess methodology (OPM), publish-subscribe INTRODUCTIONThe ISO 9000 revolution in the world of business process management and quality led to clear definitions of the terms standard and procedure. 1 A standard is a specification of requirements, guidelines, or characteristics that can be used consistently to ensure that materials, products, processes, and services are fit for their purpose. As this definition implies, standards are nonbinding, often informal documents, yet broadly accepted, adopted, and applied, even if they lack in formality. Standards often include or constitute specifications of procedures and protocols, among other elements such as conventions, attributes, and quality requirements. A procedure is a specification of an activity or process. The term protocol, which originated from the domains of law and diplomacy, has become a common term in computer and communication technology for formal conventions. Large standardization bodies publish standards for common practices, industry-wide conventions, solution integration, compatibility, exchangeability, and interoperability. The International Organization for Standardization (ISO), the Institute of Electrical and Electronics Engineers (IEEE), the US Federal Drug Administration (FDA), the Inter-net Engineering Task Force (IETF) and the Object Modeling Group (OMG) are major standardization bodies. Standards are sometimes premature, when they are formed for emerging domains, such as Internet of Things (IoT) 2,3 and electric v...

show abstract

A scenario-based approach to hierarchical state machine design

Cited by 15 publications

References 9 publications

On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design

On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design

A petri-net-based synthesis methodology for use-case-driven system design

Model‐based protocol specification

Contact Info

Product

Resources

About