Results 11 - 20
of
207
Deriving Behavior Specifications from Textual Use Cases
- Oesterreichische Computer Gesellschaft
, 2004
"... The design of a software system or component starts with specifying its requirements; traditionally, use cases written in natural language are used for this task. While this makes use cases easily readable, it neither permits reasoning on requirement specifications (written as use cases), nor employ ..."
Abstract
-
Cited by 18 (1 self)
- Add to MetaCart
(Show Context)
The design of a software system or component starts with specifying its requirements; traditionally, use cases written in natural language are used for this task. While this makes use cases easily readable, it neither permits reasoning on requirement specifications (written as use cases), nor employing the use cases in deriving an initial design in an automated way. While employing linguistic tools to analyze use cases has already been considered, such efforts usually attempted to utilize all the information possibly contained in a use case specification, thus facing the complexity of a natural language. Yet, in a use case, the sentence describing a use case step adheres to a simple prescribed structure, and describes an action, which is either a communication action (among entities involved in the use case), or an internal action.
Specification and Generation of Environment for Model Checking of Software Components
, 2007
"... Model checking of isolated software components is inherently not possible because a component does not form a complete program with an explicit starting point. To overcome this obstacle, it is typically necessary to create an environment of the component which is the intended subject to model checki ..."
Abstract
-
Cited by 17 (9 self)
- Add to MetaCart
Model checking of isolated software components is inherently not possible because a component does not form a complete program with an explicit starting point. To overcome this obstacle, it is typically necessary to create an environment of the component which is the intended subject to model checking. We present our approach to automated environment generation that is based on behavior protocols [9]; to our knowledge, this is the only environment generator designed for model checking of software components. We compare it with the approach taken in the Bandera Environment Generator tool [12], designed for model checking of sets of Java classes.
Model-Based Monitoring of Component-Based Software Systems
"... The development of component-based software systems opens the possibility of using model-based diagnosis techniques for large software systems. We have developed a simple monitoring system based on the modeling of the external behavior of software components by Petri nets. With each component is ass ..."
Abstract
-
Cited by 15 (0 self)
- Add to MetaCart
The development of component-based software systems opens the possibility of using model-based diagnosis techniques for large software systems. We have developed a simple monitoring system based on the modeling of the external behavior of software components by Petri nets. With each component is associated a local controller which observes the messages received and sent by the component and compares them with the specified behavior. As the components interact, information is collected on error emission and time constraint violation to infer indicators about the state of components.
Java Implementation of a Component Model with Explicit Symbolic Protocols
- In Proceedings of the 4th International Workshop on Software Composition (SC’05), volume 3628 of LNCS
, 2005
"... Component-Based Software Engineering (CBSE) has now emerged as a discipline for system development. Important issues in CBSE such as composition incompatibility detection and (dynamic) adaptation can only be addressed with the help of formal component models with Behavioural Interface Descriptio ..."
Abstract
-
Cited by 15 (2 self)
- Add to MetaCart
(Show Context)
Component-Based Software Engineering (CBSE) has now emerged as a discipline for system development. Important issues in CBSE such as composition incompatibility detection and (dynamic) adaptation can only be addressed with the help of formal component models with Behavioural Interface Description Languages (BIDLs) and explicit protocols. The issue is then to fill the gap between such high-level models and implementation. This paper suggests to do so by relying on Symbolic Transition Systems (STSs). It describes a component model with explicit symbolic protocols based on STSs, and its implementation in Java. This implementation is based on controllers that encapsulate protocols and channels devoted to (possibly remote) communications between components.
Checking Component Composability
- 5TH INTERNATIONAL SYMPOSIUM ON SOFTWARE COMPOSITION, VIENNE: AUSTRIA
, 2006
"... Component-Based Software Engineering (CBSE) is one of the approaches to master the development of large scale software. In this setting, the verification concern is still a challenge. The current work addresses the composability of components and their services. A component model (Kmelia) is intro ..."
Abstract
-
Cited by 15 (5 self)
- Add to MetaCart
Component-Based Software Engineering (CBSE) is one of the approaches to master the development of large scale software. In this setting, the verification concern is still a challenge. The current work addresses the composability of components and their services. A component model (Kmelia) is introduced; an associated formalism, simple but expressive is introduced; it describes the services as extended LTSs and their structuring as components. The composability of components is defined on the basis of the composability of services. To ensure the correctness of component composition, we check that an assembly is possible via the checking of the composability of the linked services, and their behavioural compatibility. In order to mechanize our approach, the services and the components are translated into the Lotos formalism. Finally the Lotos CADP toolbox is used to perform experiments.
Hand-written vs. MOF-based Metadata Repositories: The SOFA Experience
- PROCEEDINGS OF ECBS 2004, BRNO, CZECH REPUBLIC, IEEE CS
, 2004
"... Metadata management is one of the key concepts of distributed interoperable systems. This paper compares two approaches to building a metadata repository for component-based distributed environment. We compare a hand-written repository and MOF-based one with respect to easiness of building and acces ..."
Abstract
-
Cited by 13 (8 self)
- Add to MetaCart
Metadata management is one of the key concepts of distributed interoperable systems. This paper compares two approaches to building a metadata repository for component-based distributed environment. We compare a hand-written repository and MOF-based one with respect to easiness of building and accessing them. The results are based on implementations of the both repositories for a real component model.
Layered Ontological Modelling for Web Serviceoriented Model-Driven Architecture
- European Conference on Model-Driven Architecture - Foundations and Applications ECMDA’2005, LNCS 3748
, 2005
"... Abstract. Modelling is recognised as an essential activity in the archi-tectural design of software systems. Model-driven architecture (MDA) is a framework implementing this idea. Ontologies are knowledge rep-resentation frameworks that are ideally suited to support modelling in this endeavour. We p ..."
Abstract
-
Cited by 13 (12 self)
- Add to MetaCart
(Show Context)
Abstract. Modelling is recognised as an essential activity in the archi-tectural design of software systems. Model-driven architecture (MDA) is a framework implementing this idea. Ontologies are knowledge rep-resentation frameworks that are ideally suited to support modelling in this endeavour. We propose here a layered ontological framework that addresses domain modelling, architectural modelling, and interoperabil-ity aspects in the development of service-based software systems. We illustrate the benefits of ontological modelling and reasoning for service-oriented software architectures within the context of the Web Services.
Model-Based Adaptation of Behavioural Mismatching Components
- IEEE TRANSACTIONS ON SOFTWARE ENGINEERING
, 2008
"... Component-Based Software Engineering focuses on the reuse of existing software components. In practice, most components cannot be integrated directly into an application-to-be, because they are incompatible. Software Adaptation aims at generating, as automatically as possible, adaptors to compensate ..."
Abstract
-
Cited by 13 (8 self)
- Add to MetaCart
(Show Context)
Component-Based Software Engineering focuses on the reuse of existing software components. In practice, most components cannot be integrated directly into an application-to-be, because they are incompatible. Software Adaptation aims at generating, as automatically as possible, adaptors to compensate mismatch between component interfaces, and is therefore a promising solution for the development of a real market of components promoting software reuse. In this article, we present our approach for software adaptation which relies on an abstract notation based on synchronous vectors and transition systems for governing adaptation rules. Our proposal is supported by dedicated algorithms that generate automatically adaptor protocols. These algorithms have been implemented in a tool, called Adaptor, that can be used through a user-friendly graphical interface.
Erroneous Architecture Is A Relative Concept
, 2004
"... The problem this paper addresses is that an architecture formed of software components can contain composition errors (introduced, for instance, as a result of the choice of a framework's parameters). The title "Erroneous architecture is a relative concept" is to emphasize that whethe ..."
Abstract
-
Cited by 12 (5 self)
- Add to MetaCart
The problem this paper addresses is that an architecture formed of software components can contain composition errors (introduced, for instance, as a result of the choice of a framework's parameters). The title "Erroneous architecture is a relative concept" is to emphasize that whether a composition error occurs in an architecture depends on the way the architecture is used in its environment. An important issue is finding a way to possibly statically verify that, for a given setup containing the architecture, no composition errors can occur in any run. The contribution of the paper is bringing an evidence that this can be done by employing behavior protocols and their consent operator.
A Formal Architectural Description Language based on Symbolic . . .
, 2006
"... Component Based Software Engineering has now emerged as a discipline for system development. After years of battle between component platforms, the need for means to abstract away from specific implementation details is now recognized. This paves the way for model driven approaches (such as MDE) bu ..."
Abstract
-
Cited by 12 (5 self)
- Add to MetaCart
Component Based Software Engineering has now emerged as a discipline for system development. After years of battle between component platforms, the need for means to abstract away from specific implementation details is now recognized. This paves the way for model driven approaches (such as MDE) but also for the more older Architectural Description Language (ADL) paradigm. In this paper we present KADL, an ADL based on the Korrigan formal language which supports the following features: integration of fully formal behaviours and data types, expressive component composition mechanisms through the use of modal logic, specification readability through graphical notations, and dedicated architectural analysis techniques.
