Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
Inserting ilities by controlling communications
Communications of the ACM - Internet abuse in the workplace and Game engines in scientific research
Automating Support for Software Evolution in UML
Automated Software Engineering
Introducing Context-Based Constraints
FASE '02 Proceedings of the 5th International Conference on Fundamental Approaches to Software Engineering
From Dalang to Kava - The Evolution of a Reflective Java Extension
Reflection '99 Proceedings of the Second International Conference on Meta-Level Architectures and Reflection
Component Metadata for Software Engineering Tasks
EDO '00 Revised Papers from the Second International Workshop on Engineering Distributed Objects
Continuous Engineering of Information and Communication Infrastructures (Extended Abstract)
FASE '99 Proceedings of the Second Internationsl Conference on Fundamental Approaches to Software Engineering
Defining the context of OCL expressions
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Component-Based Software Development - A Practitioner'S View
Journal of Integrated Design & Process Science - Component-Based System Development
A survey of component based system quality assurance and assessment
Information and Software Technology
| Hi-index | 0.00 |
Software evolution is a major challenge to software development. When adapting a component-based system to new, altered or deleted requirements, existing requirements should not accidentally be violated. Invariant conditions are usually specified via constraint languages like OCL on a high precision level close to source code. On the contrary, this paper uses a new constraint mechanism. One context-based constraint (CoCon) specifies one requirement for a group of indirectly associated components that share a context. This paper proposes a 'Rule Manager' approach to monitor a system's compliance with requirements automatically at runtime. The approach is compatible with modern middleware technologies and allows the transparent integration of requirement validation in legacy systems or COTS.