Temporal analysis and object-oriented real-time software development: a case study with ROOM/ObjecTime

New generation methodologies and CASE tools are making possible increasing "automation" by addressing software development in terms of executable models. We describe one such methodology, ROOM, along with its CASE tool, ObjecTime, for which systems are modelled in terms of hierarchically organised communicating objects whose behavior is defined in terms of finite state machines. In particular, we present the results of a Rate Monotonic Analysis inspired temporal analysis which makes evident some of the runtime limitations associated with ROOM semantics and the way in which the ROOM model is cast as an executable for the intended embedded platform.

[1]  Bran Selic.  Periodic tasks in ROOM , 1995 .

[2]  D Dooling.  TECHNOLOGY 1995 - TRANSPORTATION , 1995 .

[3]  Bran Selic,et al.  Real-time object-oriented modeling , 1994, Wiley professional computing.

[4]  D. M. Johnson.  The systems engineer and the software crisis , 1996, SOEN.

[5]  Maarten Boasson,et al.  Control Systems Software , 1993, Fifth Euromicro Workshop on Real-Time Systems.

[6]  Mark Klein,et al.  A practitioner's handbook for real-time analysis - guide to rate monotonic analysis for real-time systems , 1993, The Kluwer international series in engineering and computer science.

[7]  Gul Agha,et al.  RTsynchronizer: language support for real-time specifications in distributed systems , 1995 .

[8]  Mary Shaw,et al.  Comparing Architectural Design Styles , 1995, IEEE Softw..

[9]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[10]  Gul A. Agha,et al.  RTsynchronizer: language support for real-time specifications in distributed systems , 1995, Workshop on Languages, Compilers, & Tools for Real-Time Systems.

[11]  David Harel,et al.  Executable object modeling with statecharts , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.