Corpus ID: 9753848

The Context-Based Constraint Language CCL for Components

@inproceedings{Bubl2002TheCC,
  title={The Context-Based Constraint Language CCL for Components},
  author={Felix Bubl},
  year={2002}
}
Software evolution is a major challenge to software development. When adapting a systems to new, altered or deleted requirements, existing requirements should not unintentionally be violated. One requirement can affect several possibly unassociated components that do not invoke each other directly or do not even run on the same platform. A context-based constraint (CoCon) can indirectly select the constrained components via their metadata even if they are not associated or do not invoke each… Expand
Enhancing ArgoUML by the Context-Based Component Constraint Language CCL
TLDR
A CCL plugin for ArgoUML is planned, which will add new diagrams and enhance the design critique mechanism, and compliance with requirements can be verified automatically when modells are modified. Expand
Introducing Context-Based Constraints
TLDR
A new constraint technique is introduced in this paper: One context-based constraint (CoCon) specifies a requirement for those system (model) elements that belong to the related context that are indirectly selected via their meta-information. Expand
External Requirements Validation for Component-Based Systems
TLDR
A 'Rule Manager' approach to monitor a system's compliance with requirements automatically at runtime is proposed, compatible with modern middleware technologies and allows the transparent integration of requirement validation in legacy systems or COTS. Expand
Tracing crosscutting requirements for component based systems via context based constraints
TLDR
This thesis presents algorithms for detecting both violated and contradicting CoCons automatically in UML models of component-based systems and presents a new notion of constraints: a context-based constraint (CoCon) expresses a condition on how its constrained elements must relate to each other. Expand
Tracing cross-cutting requirements via context-based constraints
  • Felix Bübl, M. Balser
  • Computer Science
  • Ninth European Conference on Software Maintenance and Reengineering
  • 2005
TLDR
This article presents a new approach for expressing and validating a requirement even if the authors don't precisely know which system elements are involved: a context-based constraint (CoCon) can identify the involved elements according to their context. Expand
What Must (Not) Be Available Where?
Arranging the distribution of data, objects or components is a critical task that can ultimately affect the performance, integrity and reliability of distributed system. This paper suggests to writeExpand
Integrating Container Services with Pluggable System Extensions
A common problem in today’s software is the lack of separation of concerns, which results in intertwined code, that is di.cult to maintain. In order to make a component-based system adaptive to newExpand

References

SHOWING 1-10 OF 80 REFERENCES
Introducing Context-Based Constraints
TLDR
A new constraint technique is introduced in this paper: One context-based constraint (CoCon) specifies a requirement for those system (model) elements that belong to the related context that are indirectly selected via their meta-information. Expand
External Requirements Validation for Component-Based Systems
TLDR
A 'Rule Manager' approach to monitor a system's compliance with requirements automatically at runtime is proposed, compatible with modern middleware technologies and allows the transparent integration of requirement validation in legacy systems or COTS. Expand
Component Metadata for Software Engineering Tasks
TLDR
A framework that lets a component developer provide a component user with different kinds of information, depending on the specific context and needs, based on presenting this information in the form of metadata is presented. Expand
Validating UML Models and OCL Constraints
TLDR
This work presents an approach for the validation of UML models and OCL constraints that is based on animation and enabled a thorough and systematic check of the OCL well-formedness rules in the UML standard. Expand
A Classification and Comparison Framework for Software Architecture Description Languages
TLDR
A definition and a classification framework for architecture description languages are presented and the utility of the definition is demonstrated by using it to differentiate ADLs from other modeling notations, enabling us, in the process, to identify key properties ofADLs. Expand
Modular Architecture for a Toolset Supporting OCL
TLDR
A flexible modular architecture for a UML/OCL toolset is proposed and the first results of an ongoing project which aims at the provision of such an OCL toolset for the public domain are reported. Expand
The object constraint language: precise modeling with UML
TLDR
This book discusses modeling with Constraints in a UML Model, using Package Names in Navigations, using Pathnames in Inheritance Relations, and treating Instances as Collections. Expand
Automatic Generation of Simulation Models for the Evaluation of Performance and Reliability of Architectures Specified in UML
TLDR
This paper introduces an approach for the evaluation of non-functional requirements in UML models, using simulation techniques, and associates results to objects, classes, states, operations, actors, system resources and other UML elements. Expand
Constraint Diagrams: A Step Beyond UML
TLDR
This work describes a notation, constraint diagrams, which were introduced as a visual technique intended to be used in conjunction with the UML for object-oriented modelling. Expand
Automating Support for Software Evolution in UML
TLDR
This paper generalises the reuse contracts formalism, and integrates it into the UML metamodel, so that support for evolution becomes readily available for many kinds of UML models, ranging from requirements to the implementation phase. Expand
...
1
2
3
4
5
...