Live sequence charts applied to hardware requirements specification and verification

Bunker, A.S.; Gopalakrishnan, Ganesh; Slind, Konrad

doi:10.1007/s10009-004-0145-x

Cited by 24 publications

(17 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this paper, we build upon the basis of scenario-based programming as established by LSCs, and the experience gained from experimenting with it in several application areas [2,4,5,9,15,33]. We first identify and provide formal definitions for the essence of the ideas (which we more generally call behavioral programming [17]).…”

Section: Introductionmentioning

confidence: 99%

Programming Coordinated Behavior in Java

Harel¹,

Marron²,

Weiss³

2010

ECOOP 2010 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Following the scenario-based approach to programming which centered around live sequence charts (LSCs), we propose a general approach to software development in Java. A program will consist of modules called behavior threads (b-threads), each of which independently describes a scenario that may cross object boundaries. We identify a protocol and a coordination mechanism that allow such behavioral programming. Essentially, runs of programs are sequences of events that result from three kinds of b-thread actions: requesting that events be considered for triggering, waiting for triggered events, and blocking events requested by other b-threads. The coordination mechanism synchronizes and interlaces b-threads execution yielding composite, integrated system behavior. The protocol idioms and the coordination mechanism of b-threads are implemented as a Java library called BPJ. Throughout the exposition we illustrate benefits of the approach and discuss the merits of behavioral programming as a broad, implementation-independent paradigm.

show abstract

Section: Introductionmentioning

confidence: 99%

Programming Coordinated Behavior in Java

Harel¹,

Marron²,

Weiss³

2010

ECOOP 2010 – Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…The versatility of the LSC language and of the Java and Erlang implementation versions has been demonstrated in several ways including: the Play-Engine and PlayGo development environments [23,31], language packages [32,51]; application in various domains, including hardware, telecommunication, production control, tactical simulators, and biological modeling [6,15,16,21,29,47]; tools for compilation [30]; smarter execution using lookahead [25,28]; learning [19], model-checking (for discovering and handling conflicts and underspecification in incremental development) [33]; and, trace visualization and comprehension [20,43].…”

Section: Overviewmentioning

confidence: 99%

Behavioral programming, decentralized control, and multiple time scales

Harel

Marron

Wiener

et al. 2011

Proceedings of the Compilation of the Co-Located Workshops on DSM'11, TMC'11, AGERE! 2011, AOOPES'11, NEAT'11, &Amp; VMIL'11

View full text Add to dashboard Cite

Behavioral programming is a recently proposed approach for nonintrusive incremental software development. We propose that behavioral programming concepts, such as behavioral decomposition, synchronized execution of independent behaviors, and event blocking, can help in the incremental and natural coding of complex decentralized systems, complementing actor-oriented and agentoriented approaches. We also contribute to the existing research on behavioral programming a method for coordinating behaviorallyprogrammed components which, due to different time scales or interaction with the external environment, cannot synchronize and thus cannot employ event blocking. We show that the resulting decentralized system retains many of the advantages present in a purely behavioral, fully synchronized system.

show abstract

“…All non-accepting states, i.e., states with outgoing hot transitions, have an additional outgoing transition to a rejecting sink state labeled M \ mh, where mh is the set of enabled events in the state. 3 Finally, the initial state, representing the minimal legal cut, has a self transition labeled , quantified universally with all the minimal occurrence specifications. The partition of the state space is induced naturally from the partial order of legal cuts.…”

Section: The Basicsmentioning

confidence: 99%

“…Thus, formal methods and tools can take advantage of scenario-based specifications throughout the development cycle of systems, from requirements capture and analysis, to design and specification, implementation, testing, formal verification, and system execution (see, e.g., [8,16,22,25,27,31]). Initial projects that use LSC have been carried out recently in the automotive, telecommunication, and hardware domains (see, e.g., [3,6]). …”

Section: Introductionmentioning

confidence: 99%

Assert and negate revisited: Modal semantics for UML sequence diagrams

2007

View full text Add to dashboard Cite

Live Sequence Charts (LSC) extend Message Sequence Charts (MSC), mainly by distinguishing possible from necessary behavior. They thus enable the specification of rich multi-modal scenario-based properties, such as mandatory, possible and forbidden scenarios. The sequence diagrams of UML 2.0 enrich those of previous versions of UML by two new operators, assert and negate, for specifying required and forbidden behaviors, which appear to have been inspired by LSC. The UML 2.0 semantics of sequence diagrams, however, being based on pairs of valid and invalid sets of traces, is inadequate, and prevents the new operators from being used effectively.We propose an extension of, and a different semantics for this UML language-Modal Sequence Diagrams (MSD)-based on the universal/existential modal semantics of LSC. In particular, in MSD assert and negate are really modalities, not operators. We define MSD as a UML 2.0 profile, thus paving the way to apply formal verification, synthesis, and scenario-based execution techniques from LSC to the mainstream UML standard.

show abstract

Live sequence charts applied to hardware requirements specification and verification

Cited by 24 publications

References 15 publications

Programming Coordinated Behavior in Java

Programming Coordinated Behavior in Java

Behavioral programming, decentralized control, and multiple time scales

Assert and negate revisited: Modal semantics for UML sequence diagrams

Contact Info

Product

Resources

About