FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W4997652> ?p ?o ?g. }

• W4997652 abstract "T term reactive system describes a system that needs to continuously react to inputs coming from the environment. Finite state machines are a widely used concept for specifying the behavior of such systems. Since finite state machines allow the rigorous capture of functional aspects of system behavior, they offer several advantages over informal specifications. For example, they provide the ability to automatically generate code or test cases, and they enable formal verification and validation (V&V). Generally, a finite state machine is an appropriate representation when a problem or solution has the following characteristics: • Finite and discrete set of states (e.g., on, off, and standby). • Discrete and manageable set of inputs. • Change of state is only performed in response to an input (e.g., if a button is pressed, then the machine transitions from state off to state on). State machines are used for specifying functional properties for a wide variety of systems, such as control systems and user interfaces. For example, Siemens uses state machines to precisely specify the circuitry in mail sorting systems and the controls in car radios. They are also the paradigm of choice for software compiler design and programmatic interpretation of natural language. Numerous graphical notations for state machines have been developed and are commonly used today, such as state transition diagrams, Harel statecharts [1], and UML state machine diagrams [2]. Graphical notations are often preferred by developers, analysts, and testers over textual information, since diagrams allow the visualization of complex relationships. Tabular notations for state machines (commonly also referred to as state tables or state transition tables) offer complementary advantages to these graphical notations. For example, the incompleteness of a specification, i.e., the actions of the system in a specific state in response to a specific event that are not addressed by the specification, can easily be identified as empty cells in the table. In addition, tabular notations are relatively compact and have shown to scale well to practical systems [3]. Due to these reasons, tabular notations for state machines are preferred in some domains over graphical notations for the rigorous specification of system behavior. For instance, Siemens Automotive commonly receives system requirements in the form of state tables, captured in either Excel sheets or proprietary databases. While a tabular representation is relatively compact and the completeness of the requirements specification can easily be determined, it has been shown to cause numerous difficulties. For instance, the requirements specification for a system of realistic size is often quite large and of considerable complexity, consisting of numerous large tables. As a result, precisely understanding the required behavior solely through visual inspection is difficult. Moreover, requirements captured in simple Excel sheets are difficult to analyze for consistency and adherence to critical properties. This article presents and evaluates several state machine-based tabular notations that can address some of the aforementioned problems. For instance, some notations enhance the understandability of the specification by offering a complementary graphical representation. In addition, hierarchical composition is used by several notations to keep the specification tractable and some provide tool support for V&V. The remainder of this article is organized as follows: the Background section provides an overview of finite state machines and Harel statecharts. The Tabular Notations for State Machines section describes five approaches using tabular notations for state machine-based specifications. We conclude by evaluating these notations for use in software development with respect to several factors." @default.
• W4997652 created "2016-06-24" @default.
• W4997652 creator A5040270000 @default.
• W4997652 date "2008-01-01" @default.
• W4997652 modified "2023-10-01" @default.
• W4997652 title "Tabular Notations for State Machine-Based Specifications" @default.
• W4997652 cites W1516334706 @default.
• W4997652 cites W1528204541 @default.
• W4997652 cites W1987800038 @default.
• W4997652 cites W1994299079 @default.
• W4997652 cites W2002089154 @default.
• W4997652 cites W2061420542 @default.
• W4997652 cites W2099529102 @default.
• W4997652 cites W2113657174 @default.
• W4997652 cites W2147880466 @default.
• W4997652 cites W85669259 @default.
• W4997652 cites W2259762335 @default.
• W4997652 hasPublicationYear "2008" @default.
• W4997652 type Work @default.
• W4997652 sameAs 4997652 @default.
• W4997652 citedByCount "4" @default.
• W4997652 countsByYear W49976522013 @default.
• W4997652 countsByYear W49976522014 @default.
• W4997652 countsByYear W49976522015 @default.
• W4997652 crossrefType "journal-article" @default.
• W4997652 hasAuthorship W4997652A5040270000 @default.
• W4997652 hasConcept C145644426 @default.
• W4997652 hasConcept C16671368 @default.
• W4997652 hasConcept C167822520 @default.
• W4997652 hasConcept C169590947 @default.
• W4997652 hasConcept C177264268 @default.
• W4997652 hasConcept C181062253 @default.
• W4997652 hasConcept C199360897 @default.
• W4997652 hasConcept C207953454 @default.
• W4997652 hasConcept C25344961 @default.
• W4997652 hasConcept C2777904410 @default.
• W4997652 hasConcept C33923547 @default.
• W4997652 hasConcept C41008148 @default.
• W4997652 hasConcept C45357846 @default.
• W4997652 hasConcept C48103436 @default.
• W4997652 hasConcept C80444323 @default.
• W4997652 hasConcept C94375191 @default.
• W4997652 hasConceptScore W4997652C145644426 @default.
• W4997652 hasConceptScore W4997652C16671368 @default.
• W4997652 hasConceptScore W4997652C167822520 @default.
• W4997652 hasConceptScore W4997652C169590947 @default.
• W4997652 hasConceptScore W4997652C177264268 @default.
• W4997652 hasConceptScore W4997652C181062253 @default.
• W4997652 hasConceptScore W4997652C199360897 @default.
• W4997652 hasConceptScore W4997652C207953454 @default.
• W4997652 hasConceptScore W4997652C25344961 @default.
• W4997652 hasConceptScore W4997652C2777904410 @default.
• W4997652 hasConceptScore W4997652C33923547 @default.
• W4997652 hasConceptScore W4997652C41008148 @default.
• W4997652 hasConceptScore W4997652C45357846 @default.
• W4997652 hasConceptScore W4997652C48103436 @default.
• W4997652 hasConceptScore W4997652C80444323 @default.
• W4997652 hasConceptScore W4997652C94375191 @default.
• W4997652 hasLocation W49976521 @default.
• W4997652 hasOpenAccess W4997652 @default.
• W4997652 hasPrimaryLocation W49976521 @default.
• W4997652 hasRelatedWork W1487225934 @default.
• W4997652 hasRelatedWork W1540509245 @default.
• W4997652 hasRelatedWork W1576918130 @default.
• W4997652 hasRelatedWork W158025640 @default.
• W4997652 hasRelatedWork W1854334421 @default.
• W4997652 hasRelatedWork W1974243210 @default.
• W4997652 hasRelatedWork W1980484906 @default.
• W4997652 hasRelatedWork W2004588499 @default.
• W4997652 hasRelatedWork W2073177110 @default.
• W4997652 hasRelatedWork W20858747 @default.
• W4997652 hasRelatedWork W2109559392 @default.
• W4997652 hasRelatedWork W2348327441 @default.
• W4997652 hasRelatedWork W2561224100 @default.
• W4997652 hasRelatedWork W2774310838 @default.
• W4997652 hasRelatedWork W3023976393 @default.
• W4997652 hasRelatedWork W76722835 @default.
• W4997652 hasRelatedWork W918914145 @default.
• W4997652 hasRelatedWork W946204309 @default.
• W4997652 hasRelatedWork W1861216056 @default.
• W4997652 hasRelatedWork W2287668299 @default.
• W4997652 isParatext "false" @default.
• W4997652 isRetracted "false" @default.
• W4997652 magId "4997652" @default.
• W4997652 workType "article" @default.