Communicating sequential processes
Communicating sequential processes
Safety analysis of timing properties in real-time systems
IEEE Transactions on Software Engineering - Special issue on reliability and safety in real-time process control
Statecharts: A visual formalism for complex systems
Science of Computer Programming
Communications of the ACM
Augmented state-transition diagrams for reactive software
ACM SIGSOFT Software Engineering Notes
STATEMATE: A Working Environment for the Development of Complex Reactive Systems
IEEE Transactions on Software Engineering
On the development of reactive systems
Logics and models of concurrent systems
Introducing Objectcharts or How to Use Statecharts in Object-Oriented Design
IEEE Transactions on Software Engineering
Object-oriented modeling and design
Object-oriented modeling and design
A compositional axiomatization of Statecharts
Theoretical Computer Science - Selected papers of the International BCS-FACS Workshop on Semantics for Concurrency, Leicester, UK, July 1990
Using Harel statecharts to model object-oriented behavior
ACM SIGSOFT Software Engineering Notes
Communicating Real-Time State Machines
IEEE Transactions on Software Engineering - Special issue: specification and analysis of real-time systems
Real-time object-oriented modeling
Real-time object-oriented modeling
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Requirements Specification for Process-Control Systems
IEEE Transactions on Software Engineering
Modechart: A Specification Language for Real-Time Systems
IEEE Transactions on Software Engineering
Communicating sequential processes
Communications of the ACM
Programming-in-the large versus programming-in-the-small
Proceedings of the international conference on Reliable software
Hi-index | 0.00 |
A software behavioral pattern is a typical pattern of event interaction at the level of modules up to independent software components. Behavioral patterns are specified using a form of D. Harel's Statecharts, and we call them type-charts . They provide a semantic basis for presenting software architecture and configuration from a behavioral point of view.We introduce the notation for typecharts and discuss the uses to which they will be put. A catalogue of formally specified behavioral patterns (basic architectural "plans") is envisaged from which a software requirements engineer can select and refine to produce further plans, and present and record the software behavioral requirements. An example of this process is presented.