Publication List of EMPRESS-related Papers
-
Jewgenij botaschanjan, andreas fleischmann, markus pister,
a conceptual model for requirements engineering and management for
change-intensive software,
IASTED
international conference on software engineering (SE2004), Innsbruck, Austria,
http://www.iasted.org/conferences/2004/Innsbruck/se.htm.
-
Jason Xabier Mansell, David Sellier,
Decision Model and Flexible Component Definition based on XML Technology,
5th International Workshop on Product Family Engineering (PFE-5), Siena, Italy, November 4-6 2003.
-
Hannes Omasreiter, Ramin Tavakoli Kolagari,
Ziel- und kundenorientierte Anforderungserstellung mit
Abstraktionsebenen als zentraler Erfolgsfaktor bei der Entwicklung von
Kfz-Software,
EUROMOTIVE, Softwaretechnolgie für Automobile Nürnberg, Germany.
-
Adam Trendowicz and Teade Punter,
Quality Modeling for Software Product Lines,
in F. Brito e Abreu (ed.) Proceedings of 7th ECOOP Workshop on Quantitative Approaches in Object-Oriented Software Engineering, QAOOSE, Darmstadt, 2003.
-
A. Wils, J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
Flexible component contracts for local resource awareness,
ECOOP 2003 Workshop on resource aware computing,
Darmstadt, Germany, 21 July 2003,
http://cui.unige.ch/~ecoopws
-
H. W. Pohl and J. Gerlach,
Using the Bridge Design Pattern for OSGi Service Update,
EuroPlop 2003,
http://hillside.net/patterns/EuroPLoP/
.
-
D. Kerkow, A.Von Knethen, B. Paech, J.Doerr,
Eliciting Efficiency Requirements with Use Cases,
Refsq '03
.
-
Isabel John, Jörg Dörr,
Elicitation of Requirements from User Documentation,
Refsq '03
.
-
Jan Philipps, Oscar Slotosch et.al.,
Model-Based Test Case Generation for Smart Cards,
FMICS 2003,
.
-
J. Mansell,
La variabilidad en el software ¿Cómo identificarla y gestionarla para conseguir mayor eficiencia en el desarrollo? (The variability within software. How to identify and to manage it for improving the software development efficiency?), ESI, Zamudio, Spain.
-
B. Paech, A.Von Knethen, J.Doerr, J.Bayer, D. Kerkow, R. Kolb,
A Trendowicz, T. Punter and A. Dutoit,
An Experience-Based Approach for Integrating Architecture and
Requirements Engineering,
ICSE'03 Workshop "From Software Requirements to Architectures",
.
-
H.-G. Groß, N. Mayer, Built-in Contract Testing in Component Integration Testing, TACoS-ETAPS 2003 Workshop, Warsaw, Poland.
-
V. Del Bianco, L. Lavazza, M. Mauri and G. Occorso,
Towards UML-based formal specificiations of component-based real-time software,
ETAPS 2003 Workshop FASE,
Warsaw, Poland, 9-11 April 2003,
http://www.lta.disco.unimib.it/fase2003/.
-
J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
Managing quality of service during evolution using component contracts,
ETAPS 2003 Workshop on Unanticipated Software Evolution (USE2003)
G. Kniesel, P. Costanza and J. L. Fiadeiro (eds.),
Warsaw, Poland, 5-6 April 2003,
http://joint.org/use2003/.
-
J. Dörr, D. Kerkow, A. von Knethen and B. Paech,
Auf dem Weg zumessbaren Wartungsanforderungen,
GI-Softwaretechnik-Trends, Mitteilungen der Gesellschaft für Informatik, Band 23, Heft 1,
February 2003.
-
Teade Punter, Adam Trendowics and Peter Kaiser,
Evaluating evolutionary software systems,
Profes 2002, Rovaniemi, Finland, December 9-11 2002.
-
H.-G. Gross and N. Mayer,
Search-based Execution Time Analysis in Component-oriented Real-Time Application Development,
ISSRE 2002, Annapolis, MD, USA,
November 12-15 2002.
-
E.E.Roubtsova, H.B.M. Jonkers and R.Kuiper,
Interface Suites as Contracts. Composition of Contracts in UML,
Proceedings of 3d Workshop on Embedded
Systems, PROGRESS 2002, 24 October 2002, The Netherlands. STW, pp.203-210.
-
EMPRESS Project Posters, Profile Sheet & Software Engineering Session Presentation, 3rd ITEA Symposium, Amsterdam, The
Netherlands, October 10-11 2002.
-
E.E. Roubtsova and R. Kuiper,
Process semantics for UML component specifications to assess inheritance,
Proceedings of the International Workshop on
Graph Transformation and Visual Modeling Techniques (GT&VMT'02),
Paolo Bottoni and Mark Minas (eds.),
Elsevier Journal,
Electronic Notes in Theoretical Computer Science 72(4), 2002,
Barcelona, Spain, 7-12 October 2002,
http://www.elsevier.nl/locate/entcs/volume72.html.
-
I. John and D. Muthig,
Tailoring Use Cases for Product Line Modeling,
International Workshop on Requirements Engineering for Product Lines,
REPL'02,
Avaya Labs Research Report ALR-2002-033 ISBN 0-9724277-0-8,
Essen, Germany, September 9-13 2002,
http://www.research.avayalabs.com/REPL02/.
-
E.E. Roubtsova, L.C.M. van Gool, R. Kuiper and H.M. Jonkers,
Consistent
Specification of Interface Suites in UML,
Journal on Software & System Modeling (SoSym ) 1(2), Special Issue UML 2001, Springer, 2002, pp.98-112,
http://link.springer.de/link/service/journals/10270/tocs/t2001002.htm.
-
A. von Knethen,
Integrated refinement of non-functional requirements,
Dagstuhl-Seminar No. 02361, Report No. 352, September 2002.
-
B. Paech, A.H. Detroit, D. Kerkow and A. von Knethen,
Functional requirements, non-functional requirements, and
architecture should not be separated - A position paper,
REFSQ' 2002, Essen, Germany, September 9-10 2002,
http://panoramix.univ-paris1.fr/CRINFO/REFSQ/02/.
-
I. John and D. Muthig,
Product Line Modeling with Generic Use Cases,
SPLC-2 Workshop on
Techniques for Exploiting Commonality Through Variability Management,
Second Software Product Line Conference,
San Diego, USA, August 19-22 2002,
http://trese.cs.utwente.nl/splc2-variability/.
-
E.E. Roubtsova, H.B.M. Jonkers and R. Kuiper,
Component Specification and Composition in a UML-based tool,
The 6th World Multiconference on Systemics,
Cybernetics and Informatics (SCI 2002), International Conference on Information Systems, Analysis and Synthesis,
Nagib Callaos, Rong Zhao, Belkis Sanchez and William Lesso (eds.),
Orlando, Florida, USA,
14-18 July 2002,
volume XVII, Information Systems Development III, pp. 85-90.
-
H.-G. Gross and N. Mayer,
Evolutionary Testing in Component-based Real-time System Construction,
GECCO 2002, New York, NY, USA,
July 8-14 2002.
-
J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
EMPRESS: Component Based Evolution for Embedded Systems,
ECOOP 2002 Workshop on Unanticipated Software Evolution (USE2002)
G. Kniesel, P. Costanza and M. Dimitriev (eds.),
Malaga, Spain, June 10-14 2002,
http://joint.org/use2002/.
Abstracts & Full Papers
-
Jewgenij Botaschanjan, Andreas Fleischmann, Markus Pister,
a conceptual model for requirements engineering and management for
change-intensive software,
IASTED
international conference on software engineering (SE2004),
http://www.iasted.org/conferences/2004/Innsbruck/se.htm
.
-
Abstract:
In the development of software with evolving require-ments,
activities of requirements-engineering and manage-ment
are present through the whole software development
process and affect most of the actors involved. This paper
presents a conceptual model which aims to an efficient
requirements management by offering a central data
structure for requirements that integrates requirements,
design and implementation workflow. This conceptual
model was developed for change-intensive embedded
systems, but can be easily adapted to other domains. This
paper presents the model itself, techniques to adapt this
model to specific needs, and demonstrates its usage.
-
Full Paper (PDF format)
back
-
Jason Xabier Mansell, David Sellier,
Decision Model and Flexible Component Definition based on XML Technology,
5th International Workshop on Product Family Engineering (PFE-5), Siena, Italy, November 4-6 2003.
-
Abstract:
Not available yet
-
Full Paper
Not available yet
back
-
Hannes Omasreiter, Ramin Tavakoli Kolagari,
Ziel- und kundenorientierte Anforderungserstellung mit Abstraktionsebenen als zentraler Erfolgsfaktor bei der Entwicklung von Kfz-Software, EUROMOTIVE Conference
- Abstract:
Die Nützlichkeit einer Herangehensweise bei der Erstellung von Software-Anforderungen, die sich an den Kunden des zu entwickelnden Systems und an deren Zielen orientiert, ist in der Theorie anerkannt. In der Praxis trifft man allerdings häufig auf Systementwickler, die stark technik- und lösungsorientiert denken und daher bei der Anforderungserstellung oft direkt Lösungswege beschreiben, ohne die Frage nach den Kunden und deren Bedürfnissen zu vertiefen. Das Ergebnis dieses Verhaltens sind im schlechtesten Fall Softwarefunktionen, die den Anwenderwunsch nicht treffen. In diesem Artikel wird ein Ansatz zur Erstellung von Anforderungen vorgestellt und an einem konkreten Beispiel eines Drehzahlmessers eines Kombiinstruments erörtert, bei dem basierend auf Abstraktionsebenen eine zielgerichtete und kundenorientierte Vorgehensweise unterstützt wird. Dabei wurde ein besonderes Augenmerk darauf gelegt, dieses Konzept möglichst einfach und damit praktikabel zu halten.
-
Full Paper (PDF format)
back
-
Adam Trendowicz and Teade Punter,
Quality Modeling for Software Product Lines,
in F. Brito e Abreu (ed.) Proceedings of 7th ECOOP Workshop on Quantitative Approaches in Object-Oriented Software Engineering, QAOOSE, Darmstadt, 2003
-
Abstract:
In today's embedded software systems development, non-functional
requirements (e.g., dependability, maintainability) become more and more
important. Simultaneously the increasing pressure for developing software in
shorter time and at a lower cost pushes software industry towards product lines
solutions. To support product lines for high quality embedded software, quality
models are needed. In this paper we investigate to which extent existing quality
modelling approaches facilitate high quality software product lines. First, we
define several requirements for an appropriate quality model. Then, we use
those requirements to review the existing quality modelling approaches. We
conclude from the review that no single quality model fulfils all of our
requirements. However, several approaches contain valuable characteristics.
Based upon those characteristics we propose the Prometheus approach.
Prometheus is a goal-oriented method that integrates qualitative and qualitative
approaches to quality control. The method starts quality modelling early in the
software lifecycle and is reusable across product lines.
-
Full Paper (PDF format)
back
-
A. Wils, J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
Flexible component contracts for local resource awareness,
ECOOP 2003 Workshop on resource aware computing
Darmstadt, Germany, 21 July 2003,
http://cui.unige.ch/~ecoopws.
- Abstract:
Ubiquitous and pervasive computing paradigms tend to shift towards open service-oriented platforms, in which carelessly written services can undermine the general stability of the whole system. We propose a component-contract based approach to solve these challenges. Resource contracts, combined with an intelligent resource broker and monitoring system, will efficiently deal with the local resource aspects of dynamically reconfigurable component systems.
-
Full Paper (PDF format)
back
-
H. W. Pohl and J. Gerlach,
Using the Bridge Design Pattern for OSGi Service Update,
EuroPlop 2003, http://hillside.net/patterns/EuroPLoP/,
.
-
Abstract:
In the OSGi framework, components cooperate by sharing service
objects. The suggested way to replace a service by a newer version
consists of updating its containing components which requires a tem-porary
shutdown of the component. Special care must be taken to
avoid dangling references to old service instances.
As this appears to be an overly expensive strategy, we describe
the use of the well-known Bridge design pattern to decouple service
replacement from component updates. Instead of registering services
only references to instances of automatically generated bridge classes
are registered. This solves not only the problem of dangling references
but also avoids stopping and starting dependent bundles.
-
Full Paper (PDF format)
back
-
Daniel Kerkow, Kirstin Kohler and Jörg Dörr,
Usability and Other Quality Aspects Dervied from Use Cases,
forUse 2003,
.
-
Abstract:
Usability is one of several quality aspects (also named non-functional requirements) according to ISO 9126. The elicitation of those during an early phase of the development is crucial in information systems as well as in embedded systems. Despite the practical importance of usability and additional aspects like performance and maintainability, and so forth, there is rarely any guidance on the elicitation of these requirements. We present an approach to elicit usability requirements in concert with supplementary requirements based on a use case based specification of functional behavior.
-
Full Paper (PDF format)
back
-
Isabel John, Jörg Dörr,
Elicitation of Requirements from User Documentation,
Refsq '03,
.
-
Abstract:
This paper describes an approach for elicitation of
requirements based on existing user documentation. The
approach we describe in this paper supports capturing of
the information found in user documentation of legacy
systems, e.g., user manuals, and the specification of this
information in requirements specifications, using, e.g.,
Use Cases. We propose a conceptual model describing
the transition from user documentation to requirements
artifacts describing common and variable elements of a
product line model or requirements specification. We
present heuristics that allow an easy identification of text
elements in user documents that are then used to create a
significant part of the requirements specification and
product line model, respectively.
-
Full Paper (PDF format)
back
-
Jan Philipps, Oscar Slotosch et.al.,
Model-Based Test Case Generation for Smart Cards,
FMICS 2003,
.
-
Abstract:
Testing denotes a set of activities that aim at discovering discrepancies between
actual and intended behaviors of a system. Often, the intended behavior is known
only implicitly, which renders the process of testing unstructured, unmotivated in
its details, and barely reproducible. The use of explicit and executable models to
describe the intended behavior promises to solve these problems. We use an industrial
case study - a smart card application - to present a method for automatically
generating test cases from such explicit models. The test cases are used both to
validate the model and verify the actual card.
-
Full Paper (PDF format)
back
-
J. Mansell,
La variabilidad en el software ¿Cómo identificarla y gestionarla para conseguir mayor eficiencia en el desarrollo? (The variability within software. How to identify and to manage it for improving the software development efficiency?), ESI, Zamudio, Spain
-
Abstract:
Not available yet
-
Full Paper (PDF format)
back
-
B. Paech, A.Von Knethen, J.Doerr, J.Bayer, D. Kerkow, R. Kolb,
A Trendowicz, T. Punter, A. Dutoit,
An Experience-Based Approach for Integrating Architecture and
Requirements Engineering,
ICSE'03 Workshop "From Software Requirements to Architectures",
.
-
Abstract:
Deriving requirements and architecture in concert
implies the joint elicitation and specification of the
problem and the structure of the solution. In this paper
we argue that such an integrated process should be
fundamentally based on experience. We sketch an
approach developed in the context of the EMPRESS
project that shows how different kinds of experience-based
artifacts, such as checklists, patterns, and
rationale, can beneficially be applied.
-
Full Paper (PDF format)
back
-
H.-G. Groß, N. Mayer, Built-in Contract Testing in Component Integration Testing, TACoS-ETAPS 2003 Workshop, Warsaw, Poland.
-
Abstract:
Assembling new software systems from prefabricated components
is an attractive alternative to traditional software engineering
practices which promises to increase reuse and reduce development
costs. However, these benefits will only occur if separately
developed components can be made to work effectively together
with reasonable effort. Lengthy and costly in-situ verification
and acceptance testing directly undermines the benefits of
independent component fabrication and late system integration.
This position paper outlines and introduces an approach
for reducing manual system verification effort
by equipping components with the ability
to check their execution environments at run-time. When deployed
in new systems, built-in tester components check the
contract-compliance of their server components, including
the run-time system, and thus automatically verify their
ability to fulfill their own obligations. This comprises
functional/behavioural contracts as well as quality-of-service
contracts between individual components.
Enhancing traditional component-based development
methods with built-in contract testing in this way
reduces the costs associated with component
assembly, and thus makes the "plug-and-play"
vision of component-based development
closer to practical reality.
-
Full Paper (PDF format)
back
-
V. Del Bianco, L. Lavazza, M. Mauri and G. Occorso,
Towards UML-based formal specificiations of component-based real-time software,
ETAPS 2003 Workshop FASE,
Warsaw, Poland, 9-11 April 2003,
http://www.lta.disco.unimib.it/fase2003/.
-
Abstract:
UML-RT is achieving increasing popularity as a modeling language for real-time
applications. Unfortunately UML-RT is not formally well defined and it is not well
suited for supporting the specification stage: e.g., it does not provide native constructs to
represent time and non-determinism. UML+ is an extension of UML that is formally well
defined and suitable for expressing the specifications of real-time systems (e.g., the prop-erties
of a UML+ model can be formally verified). However, UML+ does not support de-sign
and development. This article addresses the translation of UML+ into UML-RT, thus
posing the basis for a development framework where UML+ and UML-RT are used to-gether,
thus removing each other~Rs limitations. Specifications are written using UML+,
they are verified by means of formal methods, and are then converted in an equivalent
UML-RT model that becomes the starting point for the implementation.
-
Full Paper (PDF format)
back
-
J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
Managing quality of service during evolution using component contracts,
ETAPS 2003 Workshop on Unanticipated Software Evolution (USE2003)
Warsaw, Poland, 5-6 April 2003,
http://joint.org/use2003/.
-
Abstract:
In this paper we propose a methodolody to guarantee resource contracts and increase reliability across updates in embedded soft real-time systems. We present the roadmap to a solution based on the verification of component updates using update contracts. In our system the behaviour of all components is modelled in detail. Relying on a resource aware component system which has full control over all resources we will be able to guarantee that an update will not cause resource constraint violations for components that are not updated. We also lay out a tool which helps the software developer in estimating the maximal resource consumption of a certain update and determining the impact of a that update on the running program.
-
Full Paper (PDF format)
back
-
J. Dörr, D. Kerkow, A. von Knethen and B. Paech,
Auf dem Weg zumessbaren Wartungsanforderungen,
GI-Softwaretechnik-Trends, Mitteilungen der Gesellschaft für Informatik, Band 23, Heft 1,
February 2003.
-
Abstract:
Dieser Artikel beschreibt, wie
nichtfunktionale Anforderungen verfeinert und
messbar beschrieben werden können. Dabei werden
einerseits Abhängigkeiten zu funktionalen
Anforderungen und der Architektur explizit gemacht.
Andererseits werden Erfahrungen aus bereits
durchgeführten Projekten in Form von Verfeinerungs-graphen
und Checklisten genutzt.
-
Full Paper (PDF format)
back
-
Teade Punter, Adam Trendowics, Peter Kaiser,
Evaluating evolutionary software systems,
Profes 2002, Rovaniemi, Finland, December 9-11 2002.
-
Abstract:
Non-functional requirements (NFRs) of software-intensive systems
that are under continuous evolution should be evaluated during early develop-ment
phases in order to be able to improve those systems and achieve ‘time-to-market’.
However, current evaluations are often done during late stages, like
coding and testing. In this paper we propose an approach to evaluate NFRs ear-lier.
The requirements for this approach are the use of flexible and reusable
quality models, which can deal with little data, that are transparent and meas-urement-
based. Our approach, called Prometheus, is a way of modeling NFRs
that should cope with those requirements. Prometheus applies the quality mod-eling
concept from the SQUID approach, the probability concept of Bayesian
Belief Nets (BBNs) and the specification concepts of the Goal Question Metric
(GQM) approach.
-
Full Paper (PDF format)
back
-
H.-G. Gross and N. Mayer,
Search-based Execution Time Analysis in Component-oriented Real-Time Application Development,
ISSRE 2002, Annapolis, MD, USA,
November 12-15 2002.
-
Abstract:
One of the most important motivations for the
application of object technology and subsequently
component-based software engineering techniques in
practice is that new applications can be created with significantly less effort than in traditional approaches,
simply by assembling the appropriate prefabricated
parts. However, contemporary object and
component technologies are still some way from realizing
this vision, especially when component-based
real-time applications are considered. The late
integration implied by the assembly of deployable
objects or components means there is little opportunity
to verify the correct functional and non-functional operation of the resultant application before
deployment in the run-time environment. This
problem is compounded when non-functional requirements
are considered, for example the compliance
of the application to a real-time schedule.
Such real-time requirements are not only affected by
individual objects, but by the entirety of all objects
that make up the application. Timing verification
can only be performed when components are assembled and put together into a new configuration. Although,
the effort involved in plugging components
together may be relatively small, therefore, the effort
involved in verifying that the resulting assembly of
components works as expected, and shows the expected
run-time behaviour, may be much greater.
The savings that are promised by object and component
technologies may thus be wiped out by the
extra effort needed at integration and deployment time to verify that the run-time behaviour of the resultant
application is acceptable.
-
Full Paper (>PDF format)
back
-
E.E.Roubtsova, H.B.M. Jonkers and R.Kuiper,
Interface Suites as Contracts. Composition of Contracts in UML,
Proceedings of 3d Workshop on Embedded
Systems, PROGRESS 2002, 24 October 2002, The Netherlands. STW, pp.203-210.
-
Abstract:
We present a tool for composition of compo-nent
specifications. The tool uses UML diagrams to model
the composition. A fixed component specification is a con-tract
between some roles communicating via interfaces. A
contract has a specific underlying model that we present.
Composition of contracts is a contract that extends con-tracts
of composites, but does not change them. To guar-antee
this feature we built some rules of the composition
into our tool. Our tool is an ADD-IN of the Rational Rose
that allows to produce consistent interface suite specifica-tions
in form of UML diagrams and documentation and to
reuse such specifications in system design by composition.
-
Full Paper (PDF format)
back
-
EMPRESS Project Posters, Profile Sheet and Software Engineering Session Presentation, 3rd ITEA Symposium, Amsterdam, The
Netherlands, October 10-11 2002.
-
EMPRESS Presentation on Software Engineering Session
(PDF format)
-
EMPRESS Profile Sheet
(PDF format)
-
EMPRESS Posters
(PDF format)
back
-
E.E. Roubtsova and R. Kuiper,
Process semantics for UML component specifications to assess inheritance,
Proceedings of the International Workshop on
Graph Transformation and Visual Modeling Techniques (GT&VMT'02),
Paolo Bottoni and Mark Minas (eds.),
Elsevier Journal,
Electronic Notes in Theoretical Computer Science 72(4), 2002,
Barcelona, Spain, 7-12 October 2002,
http://www.elsevier.nl/locate/entcs/volume72.html.
-
Abstract:
We define a component specification as a process. The starting point is the specifi-cation
of a component in a UML profile. The process of the component is a derivable
feature from the component specification. We define the inheritance of component
specifications as inheritance of processes. Process semantics of the UML profile
allows to check inheritance of specifications using a process algebra with renaming
functions, we have presented.
-
Full Paper (PDF format)
back
-
I. John and D. Muthig,
Tailoring Use Cases for Product Line Modeling,
International Workshop on Requirements Engineering for Product Lines,
REPL'02,
Avaya Labs Research Report ALR-2002-033 ISBN 0-9724277-0-8,
Essen, Germany, September 9-13 2002,
http://www.research.avayalabs.com/REPL02/.
-
Abstract:
Use cases are used for single system requirements engineering to capture
requirements from an external point of view. When utilizing use cases for
product line modeling they cannot be used as is but they have to be extended
with a variability mechanism. Stereotypes can be used as this variability
mechanism for use case diagrams and tags can be used for textual use cases.
In this paper we describe how to tailor use cases for product line modeling,
describe in which situations the approach can be applied and illustrate the
use case approach by an example.
-
Full Paper (PDF format)
back
-
E.E. Roubtsova, L.C.M. van Gool, R. Kuiper and H.M. Jonkers,
Consistent
Specification of Interface Suites in UML,
Journal on Software & System Modeling (SoSym ) 1(2), Special Issue UML 2001, Springer, 2002, pp.98-112,
http://link.springer.de/link/service/journals/10270/tocs/t2001002.htm.
-
Abstract:
The paper motivates and describes a model oriented approach for consistent specification of interface suites in UML. An interface suite is a
coherent collection of interfaces defining interactions that transcend component boundaries. The specification of interface suites contains diagrammatic views
and documentation, but it is extended with templates for structured specifications deriving from the ISpec approach. To guarantee that the specification
views, documentation and templates are consistent, a specification model has been constructed. The model contains both structural and behavioural
information, represented in the form of sequences of carefully designed tuples. The model provides the underlying structure for the tool supporting the
design process. The tool directs the designer to specify all elements of the model in a consistent way. The specification is collected both by customized
specification templates and by diagrams. The documentation and the diagram elements - both derived from the template information - are automatically
generated. This prevents errors and provides specification consistency.
-
Full Paper: (PDF format)
back
-
A. von Knethen,
Integrated refinement of non-functional requirements,
Dagstuhl-Seminar No. 02361, Report No. 352, September 2002.
-
Abstract:
The goal of this workshop was to discuss how non-functional requirements,
such as maintainability or performance, could be described quantitatively
under consideration of different viewpoints (i.e., customer, supplier) and
different abstraction levels (i.e., system, software). Non-functional
requirements have to be investigated together with functional requirements
and architectural decisions because there are different types of dependencies
between them. Non-functional requirements constrain, for example,
architectural decisions, whereas the architecture realizes functional and non-functional
requirements and constraints functional requirements.
-
Full Paper: (PDF format)
back
-
B. Paech, A.H. Detroit, D. Kerkow and A. von Knethen,
Functional requirements, non-functional requirements, and
architecture should not be separated - A position paper,
REFSQ' 2002, Essen, Germany, September 9-10 2002,
http://panoramix.univ-paris1.fr/CRINFO/REFSQ/02/
-
Abstract:
Requirements engineering approaches have for a long time
mainly focused on functional requirements. During the last 5 years,
several approaches dealing specifically with non-functional requirements
have emerged. They support the elicitation, documentation, verification
and validation of non-functional requirements: sometimes only
concentrating on the non-functional requirements, sometimes in
conjunction with functional requirements, and sometimes in conjunction
with architecture. The position we put forward in this paper is that
functional requirements, non-functional requirements, and architecture
must be treated together.
-
Full Paper
(PDF format)
back
-
I. John and D. Muthig,
Product Line Modeling with Generic Use Cases,
SPLC-2 Workshop on
Techniques for Exploiting Commonality Through Variability Management,
Second Software Product Line Conference,
San Diego, USA, August 19-22 2002,
http://trese.cs.utwente.nl/splc2-variability/.
-
Abstract:
Use cases are used for single system requirements engineering to capture
requirements from an customer/user point of view. When utilizing use cases
for product line modeling they have to be extended with a variability
mechanism. Stereotypes can be used as this variability mechanism for use
case diagrams and textual use cases. This early and explicit variability in
the product line lifecycle supports the domain experts in establishing a
variability mindset and supports explicit instantiation during application
analysis
-
Full Paper (PDF format)
back
-
E.E. Roubtsova, H.B.M. Jonkers and R. Kuiper,
Component Specification and Composition in a UML-based tool,
The 6th World Multiconference on Systemics,
Cybernetics and Informatics, International Conference on Information Systems, Analysis and Synthesis,
Nagib Callaos, Rong Zhao, Belkis Sanchez and William Lesso (eds.),
Orlando, Florida, USA,
14-18 July 2002,
volume XVII, Information Systems Development III, pp. 85-90.
-
Abstract:
We present a tool that supports both specification of
a component and composition of a system from com-ponents.
A component is specified as a set of roles
communicating via interfaces, named an interface-suite-
contract. The composition of interface-suites-contracts
is defined as an inheritance of roles and a
specialization of the contract by an interface-suite. A
user of the tool defines and chooses in forms elements
of UML diagrams corresponding to the interface-suite
definition and the composition definition. The
tool draws UML diagrams and generates the corre-spondent
documentation using the information from
forms. The tool is implemented as an extension of
the Rational Rose UML-based tool.
-
Full Paper (PDF format)
back
-
H.-G. Gross and N. Mayer,
Evolutionary Testing in Component-based Real-time System Construction,
GECCO 2002, New York, NY, USA,
July 8-14 2002.
-
Abstract:
Execution time analysis is an essential verification
activity during real-time system
development. This activity can be performed
dynamically through optimisation-based analysis
techniques such as evolutionary testing. Evolutionary
testing is already successfully used
under the traditional procedural development
paradigm. This paper is an initial attempt in
making evolutionary testing also applicable
under the more recent object-oriented, component-
based software development paradigm.
Here, the application of evolutionary testing is
more difficult compared with the traditional
procedural development approches because
component-based architectures are inherently
encapsulated, and often represent state machines.
This work proposes a solution that makes
evolutionary testing available in component-based
real-time system construction. It is based
on built-in testing interfaces and on the execution
of an object's invocation history through evolutionary
testing.
-
Full Paper: (PDF format)
back
-
J. Gorinsek, S. Van Baelen, Y. Berbers and K. De Vlaminck,
EMPRESS: Component Based Evolution for Embedded Systems,
ECOOP 2002 Workshop on Unanticipated Software Evolution (USE2002)
G. Kniesel, P. Costanza and M. Dimitriev (eds.),
Malaga, Spain, June 10-14 2002, http://joint.org/use2002/.
-
Abstract:
In this paper we present our work in the field of component based evolution for
embedded systems. Our focus is on the necessary properties of the underlying system
supporting evolution. We discuss the requirements of such a system, which address
both the dynamic updating of components and the embedded nature of our target
platform. Based on these requirements we propose a new approach to design such a system.
-
Keywords: component based development, embedded systems, software evolution
-
Full paper (PDF format)
back