Object-oriented specification of reactive systems
ICSE '90 Proceedings of the 12th international conference on Software engineering
ACM Transactions on Programming Languages and Systems (TOPLAS)
A practical approach to object-oriented state modeling
Software—Practice & Experience
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Scenario-Based Analysis of Software Architecture
IEEE Software
Idioms and Patterns as Architectural Literature
IEEE Software
Aspect-Oriented Modeling: Bridging the Gap between Implementation and Design
GPCE '02 Proceedings of the 1st ACM SIGPLAN/SIGSOFT conference on Generative Programming and Component Engineering
A Model for Change Propagation Based on Graph Rewriting
ICSM '97 Proceedings of the International Conference on Software Maintenance
Abstractions of Distributed Cooperation, their Refinement and Implementation
PDSE '98 Proceedings of the International Symposium on Software Engineering for Parallel and Distributed Systems
Managing Software Evolution with a Formalized Abstraction Hierarchy
ICECCS '02 Proceedings of the Eighth International Conference on Engineering of Complex Computer Systems
Validating UML models against architectural profiles
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
On horizontal specification architectures and their aspect-oriented implementations
Transactions on Aspect-Oriented Software Development II
Global software development using the 24-Hour Knowledge Factory paradigm
International Journal of Computer Applications in Technology
Hi-index | 0.01 |
Complex computer systems are seldom implemented from scratch, but they contain significant amounts of legacy code, which is under continuous pressure for evolution. We propose a management method for reactive and distributed systems, based on creating a formal abstraction hierarchy to model the system with abstractions that exceed those that are used as implementation facilities. The hierarchy is used to estimate an effort needed for implementing a modification by associating the modification to abstractions in the hierarchy and by determining the abstractions that need to be revised to retain the hierarchy consistency.