B. Selic et al., `ROOM: an object-oriented methodology for developing real-time systems', Proc. International Workshop on Computer-Aided Software Eng., IEEE Computer Society Press, 1992, pp. 6--10.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....inheritance, and it must still be valid when OCL is used. 8. 2 UML RT UML for Real Time (UML RT) extends the basic UML with constructs to facilitate the design of complex embedded real time software systems [Sel98, Lyo98] The constructs origin from the real time speci c modelling language ROOM [SGME92] and have been modi ed to t UML. The language focuses primarily on specifying the architecture of software systems, i.e. the major components, the externally visible properties of these, and the communication between them. It is argued that since decisions made during the architectural design ....

Bran Selic, Garth Gullekson, Jim McGee, and Ian Engelberg. ROOM: An object-oriented methodology for developing real-time systems. In Gene Forte, Nazim H. Madhavji, and Hausi A. Muller, editors, 5th Int. Work. Computer-Aided Software Engineering, pages 230-240, 6-10 July 1992.

....tools such as Concurrency Workbench [9] The Concurrency Workbench allows for the testing of equivalences and preorders and the verification of systems in the modal mu calculus; real time CCS style front ends are available. Other tools such as Modechart [21] Statemate [16] and ObjectTime [45] also use statecharts for visual system descriptions. Modechart allows for both simulation and algorithmic analysis techniques for a subset of properties expressed in a predicate real time logic [34] Statemate can be used to do reachability analysis and ObjectTime is object oriented which is ....

Selic, B., G. Gullekson, J. McGee, and I. Engelberg. "ROOM: An Object-Oriented Methodology for Developing Real-Time Systems." In CASE'92 Fifth International Workshop on Computer-Aided Software Engineering, Montreal, IEEE Computer Society Press, 230-240, 1992.

....the driving force behind design decisions such as the scheduling. Timing constraints are a direct consequence of the dynamics of the environment, hence being able to express timing constraints is of little help if they are not based on correct requirements. Other formalisms, e.g. SDL [2] and ROOM [8], suffer from the same limitations as basic UML. Several object oriented languages for modeling of physical systems have been proposed. Currently, international efforts are under way in defining the language Modelica [3] which has been a source of inspiration for this work and which contains ....

Selic, B., G. Gullekson, J. McGee, and I. Engelberg. ROOM: An Object-Oriented Methodology for Developing Real-Time Systems. Proc. 5th International Workshop on Computer-Aided Software Engineering, 1992.

....in the activity charts. The semantics of the behavioral view of a reactive system is given in terms of a restricted implementation of those of Statecharts. STATEMATE makes use of the formal semantics of Statecharts and offers dynamic analysis through step by step executions of Statecharts. ROOM [SGME92] is another attempt to build a methodology for real time system development which is based on a modified version of Statecharts. ROOM allows designers to describe the behavioral view of a real time system in an object oriented paradigm with a graphical interface. Graphical Specification and ....

B. Selic, G. Gullekson, J. McGee, and I. Engelberg. ROOM: An ObjectOriented Methodology for Developing Real-Time Systems. IEEE Proc. Fifth International Workshop on Computer-Aided Software Engineering, Montr'eal, Qu'ebec, Canada, pages 230--240, July 6-10 1992.

....[4] Enterprise [35] Polylith [31] and UNAS [33] In our software structure categories, these issues are addressed in the execution structure. Now research is progressing to higher abstraction levels. Software engineers would like to be able to compose software systems using concurrent objects [1, 38] or assemblies of components and connectors [5,8,10,26,39] We place these concerns in the conceptual structure category. In the rest of this section, we use System B as an example to discuss the typical categories of software structures across all the systems we studied. We describe the four ....

....capsules in the execution structure. Here, the guidelines are driven by requirements for performance and location independence. Code Generation Being able to automatically generate the low level code from the architectural description is a clear benefit of using a formal architectural notation [38]. In System G, application code was generated from the functional diagrams, combining the conceptual structure, the Run time Environment, and the protocols. Simple and standardized implementation techniques facilitate the automatic generation of application code. In one subsystem of System K, code ....

B. Selic, G. Gullekson, J. McGee, and I. Engelberg. ROOM: an object-oriented methodology for developing real-time systems, In Proceedings of the CASE'92 Fifth International Workshop on Computer-Aided Software Engineering, Montreal, Canada, July 1992.

....phase. In the implementation phase, the code for the system is developed or derived from the design. Although there has been a progress in automating the derivation of an implementation from a design specification, currently the derivation for complex software produces at best skeleton code [SGME92, HLNP90] that must be manually augmented to complete an implementation. This gap between a design and an implementation in turn creates a gap between requirements and an implementation. The goal of the MaC paradigm is to narrow this gap. One source of the gap is that requirements are described ....

B. Selic, G. Gullekson, J. McGee, and I. Engelberg. Room: An object-oriented methodology for developing real-time systems. IEEE Proc. Fifth International Workshop on Computer-Aided Software Engineering, Montr'eal, Qu'ebec, Canada, pages 230--240, July 6-10 1992.

....is an example of a a useful analytical technique. But many ordinary deadlock, safety and liveness properties cannot easily be captured by reachability analysis alone. Other commercial tools have been developed incorporating structured methods for specifying real time systems requirements [16,44,48]. These tools are in actual use, and have been successful on the whole in removing ambiguities in the requirements. However, these methods are at best semi formal. They lack a precise semantics and rigorous verification methods (e.g. through model checking, proof calculi or algebraic ....

....on the whole in removing ambiguities in the requirements. However, these methods are at best semi formal. They lack a precise semantics and rigorous verification methods (e.g. through model checking, proof calculi or algebraic bisimulations) An important part of tools such as Statemate, Objectime [44], and Observ [46] is the use of visual structuring techniques of state machines that are intuitively appealing to engineers. Research prototype tools such as Modechart [17,23] and ExSpect [47] also use graphical methods based on statecharts or Petri nets, and in addition support various forms of ....

Selic, B., G. Gullekson, J. McGee, and I. Engelberg. "ROOM: An Object-Oriented Methodology for Developing Real-Time Systems." In CASE'92 Fifth International Workshop on Computer-Aided Software Engineering, Montreal, IEEE Computer Society Press, 230-240, 1992.

....apparent during animation. In light of these results, the user may increase the number of over strained resources to smoothen execution (in our example, we could increase the number of Trucks , if the action Transport had low throughput) Similar to methodologies and tools in related domains [SGME92] the user may prototype the model. He or she might run, in an iterative way, animation and performance analysis, until the appropriate attribute values and configuration for a desired model behavior are found. 3.1.5 Implementation and Evaluation of Development Effort Macrotec is a Unix based ....

Bran Selic, Garth Gullekson, Jim McGee, and Ian Engelberg. ROOM: An object-oriented methodology for developing real-time systems. In Proceedings of the Fifth International Workshop on Computer-Aided Software Engineering, pages 230--240, Montreal, Canada, July 1992.

....to Statecharts, but emphasizes the timing properties of systems; a simulator for Modechart is presented in [15] Unlike CRSMs, Modechart does not allow events to have message components. Both Statecharts and Modechart use a shared memory model, whereas CRSMs present a distributed model. Reference [13] describes the ROOM methodology and its associated toolset. ROOM combines object oriented methods (including inheritance) and Statecharts. Hierarchical Multi State Machines (HMS) 4] is an executable notation that blends ideas from Petri nets, Statecharts and temporal logic. Finally, the new model ....

B. Selic et al., "ROOM: An Object-Oriented Methodology for Developing Real-time Systems", Proc. International Workshop on Computer-Aided Software Eng., July 1992.

....sequence charts(Rudolph et al. 1996) are used to represent the different scenarios of the use cases identified. An alternative graphical model are event trace diagrams as in the dynamic modelling of OMT (Rumbaugh, 1995b; Rumbaugh, 1995a; Yau et al. 1995) Scenarios in the same way than in ROOM (Selic et al. 1992) describe both how the system is used and the event sequences that occur inside the system (in this case, the different interactions between the agents) ffl Event flow diagrams are used to model the generic behaviour of the agent, including all the possible interactions and the data knowledge ....

Selic, B., Gullekson, G., McGee, J., & Engelberg, J. (1992). Room: An object-oriented methodology for developing real-time systems. In CASE'92 Fifth International Workshop on Computer-Aided Software Engineering, Montreal, Quebec, Canada.

....support for distribution. The Designer s Notepad [20] shares many of our concerns on design capture and expression, and provides flexible means for note taking, documentation and design exploration. However, being a generic design tool, it is weak in method specific automated support. ROOM [21] and its associated CASE tool ObjecTime is targeted for distributed real time systems. It embodies many of the same concepts as Darwin Regis, including the separation of system structure from its behaviour. As in Darwin, the system architecture is specified in terms of hierarchically structured ....

B. Selic et al. "ROOM: An Object-Oriented Methodology for Developing RealTime Systems", Bell-Northern Research Ltd., Ottawa, Canada.

....communications across a lossy wide area network. A second major requirement that motivated our work was the desire to integrate statecharts with the object paradigm [3] Our experience with real time system design indicated that the object paradigm was an excellent fit to the real time domain [4]. In particular, we found that most real time applications are more naturally expressed as netPaper submitted (23 10 92) to CHDL 93: IFIP Conference on Hardware Description Languages and Their Applications, April 26 28, 1993, Ottawa, CANADA 2 works of cooperating objects rather than in ....

....above. This framework is part of a system development methodology called Real Time Object Oriented Modeling or ROOM. A very brief overview of the fundamental aspects of ROOM is provided in the next section of this paper but readers interested in a more in depth view should consult reference [4]. The focus of the remainder of this paper is the particular refinement of statecharts developed in ROOM and which we shall call, for want of a better name, ROOMcharts. At this time there is a substantial body of experience in using ROOMcharts since they are supported by a commercial CASE tool ....

B. Selic, G. Gullekson, J. McGee, and I. Engelberg, "ROOM: An Object-Oriented Methodology for Developing Real-Time Systems, " in Proc. 5th Internantional Workshop on CASE, Montreal, Canada, 1992.

No context found.

B. Selic et al., `ROOM: an object-oriented methodology for developing real-time systems', Proc. International Workshop on Computer-Aided Software Eng., IEEE Computer Society Press, 1992, pp. 6--10.

No context found.

B. Selic, et al., #ROOM: An Object-Oriented Methodology for Developing Real-Time Systems," In Proceedings of the 5th International Workshop on Computer-Aided Software Engineering#CASE '92#, #July 1992#.

No context found.

B. Selic, et al. ROOM: An Object-Oriented Methodology for Developing Real-Time Systems. In Proceedings of the 5th International Workshop on Computer-Aided Software Engineering(CASE '92), July 1992.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC