1992
DOI: 10.1109/32.120312
|View full text |Cite
|
Sign up to set email alerts
|

Introducing Objectcharts or how to use Statecharts in object-oriented design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
56
0
4

Year Published

1995
1995
2015
2015

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 127 publications
(64 citation statements)
references
References 4 publications
0
56
0
4
Order By: Relevance
“…An instance of the scenarios defined above can be found in the alarm clock described in Objectcharts [30], an incremental way to extend state machines. Figure 2, reproduced from that paper, depicts two state machines mainSM and timeSM for the class AlarmClock.…”
Section: A Concrete Examplementioning
confidence: 99%
See 1 more Smart Citation
“…An instance of the scenarios defined above can be found in the alarm clock described in Objectcharts [30], an incremental way to extend state machines. Figure 2, reproduced from that paper, depicts two state machines mainSM and timeSM for the class AlarmClock.…”
Section: A Concrete Examplementioning
confidence: 99%
“…State machines control the behavior of instances of classes; it is a key way that UML envisions using state machines [117]. There is considerable literature focusing on such state machines and also on code generation from such machines [30,34,79,95,96] to avoid the need for manual coding of their logic.…”
Section: State Machinesmentioning
confidence: 99%
“…All these fundamental classes have behavior, based on modal programming. We used ObjectCharts as the formalism to specify behavior [4]. ObjectCharts are a well-suited tool to describe environments based on events and actions as in hyperstories.…”
Section: The Modelmentioning
confidence: 99%
“…These are Provided-services, Required-services, and Clauses. Provided and required services can be regarded as input and output ports (gates) (i.e., IO-model by Coleman et al (1992')). …”
Section: A 1 External Class Descriptionmentioning
confidence: 99%
“…TOOMS is based on an object-oriented formal language and model named TROL (Nesi, 1993;Bucci et al, 1994). TROL adopts a dual model which is capable of integrating the operational and the descriptive formalism; its operational or descriptive features are similar to other IO-based objectoriented specification languages and methodse.g., TRIO + by Morzenti and SanPietro (1992); ObjectCharts by Coleman et al (1992); ObjectOriented version of SDL (OSDL) by Braek and Haugen (1993); Object-Time by Northern Telecom (1993). Most of these approaches have the capabilities of specifying system behavior, structure, and functionality and allow the verification and validation of composition/decomposition mechanisms.…”
Section: Introductionmentioning
confidence: 99%