2003.bib

@mastersthesis{becker2003a,
  abstract = {Diese Diplomarbeit besch\"{a}ftigt sich mit Fragen des Konfigurationsmanagements bei der betrieblichen Anwendungsentwicklung mit Softwarekomponenten. Besondere Schwerpunkte liegen dabei in der Generierung von Konfigurationen und deren systematischer Bewertung im Bezug auf ihre Nutzen und ihre Kosten. Die wichtigsten Elemente bei der Durchf\"{u}hrung des Konfigurationsmanagements werden in Form von Prozessen dargestellt, darunter ein Prozess zur Suche nach Konfigurationen sowie deren Nutzenbewertung mit Hilfe des AHP.},
  author = {Becker, Steffen},
  school = {TU Darmstadt},
  title = {{K}onfigurationsmanagement komponentenorientierter betrieblicher {A}nwendungen},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/becker2003a.pdf},
  year = {2003}
}

@misc{becker2003b,
  author = {Becker, Steffen and Ortner, Erich and Overhage, Sven},
  issn = {1434-7768},
  journal = {Thema Forschung, TU Darmstadt},
  pages = {16--21},
  title = {{D}er {K}omponentenansatz - ein {R}iesenschritt f{\"u}r unsere geistige {E}ntwicklung},
  volume = {1},
  year = {2003}
}

@inproceedings{becker2003c,
  abstract = {In diesem Beitrag wird ein Konzept f\"{u}r das Konfigurationsmanagement komponentenorientierter Anwendungen dargestellt. Dabei wird zun\"{a}chst der Begriff �Konfigura-tionsmanagement� n\"{a}her erl\"{a}utert und anschlie{\ss}end die St\"{u}cklistenorganisation als eine geeignete Methode f\"{u}r das Konfigurationsmanagement beschrieben. Der Beitrag konzentriert sich auf die Entwicklung einer Vorgehensweise zur (automatisierten) Unterst\"{u}tzung der Komponentenaus-wahl, die auf St\"{u}cklisten, einem einheitlichen Spezifikationsrahmen und einer multiattributiven Entscheidungsfindung basiert. Abschlie{\ss}end wird das \"{a}nderungsmanagement beschrieben, das ebenfalls zum Konfigurationsmanagement zu z\"{a}hlen ist.},
  author = {Becker, Steffen and Overhage, Sven},
  booktitle = {Tagungsband 5. Workshop Komponentenorientierte betriebliche Anwendungssysteme},
  editor = {Turowski, Klaus},
  pages = {17--32},
  publisher = {Universit{\"a}t Augsburg},
  title = {{S}t{\"u}cklistenbasiertes {K}omponenten-{K}onfigurationsmanagement},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/becker2003c.pdf},
  year = {2003}
}

@inproceedings{becker2003d,
  abstract = {We discuss the specification of signatures, protocols (behaviour) and quality of service within software component specification frameworks. In particular we focus on (a) contractually used components, (b) the specification of components with variable contracts and interfaces, and (c) of quality of service. Interface descriptions including these aspects allow powerful static interoperability checks. Unfortunately, the specification of constant component interfaces hinders the specification of quality attributes and impedes automated component adaptation. This is because, especially quality attributes heavily depend on the components context. To enable the specification of quality attributes, we demonstrate the inclusion of parameterised contracts within a component specification framework. These parameterised contracts compute adapted, context-dependent component interfaces (including protocols and quality attributes). This allows to take context dependencies into account while allowing powerful static interoperability checks.},
  author = {Becker, Steffen and Reussner, Ralf H. and Firus, Viktoria},
  booktitle = {Proceedings of the First International Workshop on Component Engineering Methodology},
  editor = {Turowski, Klaus and Overhage, Sven},
  title = {{S}pecifying {C}ontractual {U}se, {P}rotocols and {Q}uality {A}ttributes for {S}oftware {C}omponents},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/becker2003d.pdf},
  year = {2003}
}

@misc{boehringer2003a,
  abstract = {Today users often have problems to work with complex Web Applications and Web Portals. Although most the Web Applications provide online help, the users often need human support to solve their problems. Today this can be achieved by using telephone support or an external remote administration software. Both options have serious limitations. The telephone support is provided by an operator who cannot see what happens on the user�s screen. The external remote administration software is not always available on the Client side and can introduce security vulnerabilities and adds more complexity.},
  author = {Boehringer, J. and P.Fischer and Koziolek, H. and U.Maurer and Schulze, S.},
  title = {{M}ethod and system for session sharing},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/boehringer2003a.pdf},
  year = {2003}
}

@inproceedings{bruggemann2003a,
  author = {Br{\"u}ggemann, Stefan and Happe, Jens and Hildebrandt, Stefan and Olliges, Sascha and Koziolek, Heiko and Krohs, Florian and Sandhaus, Philipp and Starke, Rico and Storm, Christian and Warns, Timo and Willer, Stefan},
  booktitle = {BTW Studierenden-Programm, Dresden, Germany, September, 2003},
  pages = {56--58},
  title = {{K}omponentenmarktplatz f{\"u}r {E}nterprise {J}ava {B}eans},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/bruggemann2003a.pdf},
  year = {2003}
}

@inproceedings{matevskameyer2003a,
  abstract = {To reduce the down-time of software systems and maximise the set of available services during reconfiguration, we propose exploiting component protocol information. This is achieved by knowing the state of a running system and determining the component dependencies for the time interval from receiving a reconfiguration request until reconfiguration completion. For this forecast we use the architectural descriptions that specify static dependencies, as well as component protocol information. By considering only component interactions for the time interval of reconfiguration we can exclude past and future dependencies from our runtime dependency graphs. We show that such change-request-specific runtime dependency graphs may be considerably smaller than the corresponding static architecture based dependency graphs; this way, we are speeding up runtime reconfiguration of component-based systems while maximising the set of available services.},
  author = {Matevska-Meyer, Jasminka and Hasselbring, Wilhelm and Reussner, Ralf H.},
  booktitle = {Proceedings of the Eigth International Workshop on Component-Oriented Programming (WCOP'03)},
  editor = {Weck, Wolfgang and Bosch, Jan and Szyperski, Clemens},
  month = {June},
  title = {{E}xploiting {P}rotocol {I}nformation for {S}peeding up {R}untime {R}econfiguration of {C}omponent-{B}ased {S}ystems},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/matevskameyer2003a.pdf},
  year = {2003}
}

@inproceedings{poernomo2003a,
  author = {Poernomo, I. and Reussner, Ralf H. and Schmidt., H. -W.},
  booktitle = {Euromicro 2003, IEEE, Antalya - Turkey, September 3rd-5th, 2003},
  editor = {Chroust, Gerhard},
  title = {{A}rchitectural {C}onfiguration with {EDOC} and .{NET} {C}omponent {S}ervices},
  year = {2003}
}

@inproceedings{reussner2003f,
  author = {Reussner, Ralf H.},
  booktitle = {Proceedings of the Eighth International Workshop on Component-Oriented Programming (WCOP'03)},
  editor = {Weck, Wolfgang and Bosch, Jan and Szyperski, Clemens},
  month = {June},
  title = {{C}ontracts and {Q}uality {A}ttributes of {S}oftware {C}omponents},
  year = {2003}
}

@article{reussner2003b,
  abstract = {The purpose of this tutorial is to provide concepts and historical background of the �network integration testing� (NIT) methodology. NIT is a �grey box� testing technique that is aimed at verifying the correct behaviour of interconnected networks (operated by different operators) in provisioning services to end users, or the behaviour of a complex network operated by a unique operator. The main technical concepts behind this technique are presented along with the history of some International projects that have contributed to its early definition and application. European Institute for Research and Strategic Studies in Telecommunication (EURESCOM) has actually been very active, with many projects, in defining the NIT basic methodology and providing actual NIT specifications (for narrow-band and broad-band services, covering both voice and data). EURESCOM has also been acting as a focal point in the area, e.g., encouraging the Industry in developing commercial tools supporting NIT. In particular, the EURESCOM P412 project (1994�1996) first explicitly defined the NIT methodology (the methodological aspects include test notation, test implementation, test processes, distributed testing and related co-ordination aspects). P412 applied the methodology to ISDN whilst another project, P410, applied NIT to data services. The P613 project (1997�1999) extended the basic NIT methodology to the broad band and GSM. More into details, the areas covered currently by NIT test specifications developed by EURESCOM projects include N-ISDN, N-ISUP, POTS, B-ISDN, B-ISUP, IP over ATM, ATM/FR, GSM, focusing also on their �inter-working� cases (e.g., ISDN/ISDN, ISDN/GSM, etc.). ETSI, the European Telecommunication Standards Institute, also contributed to NIT development (e.g., the definition of the TSP1+ protocol, used for the functional co-ordination and timing synchronisation of all tools involved in a distributed testing session). The paper also discusses NIT in relation to the recent major changes (processes) within the telecommunication (TLC) community. Beyond the new needs coming from the pure technical aspects (integration of voice and data, fixed mobile convergence, etc.) the full deregulation of the TLC sector has already generated new processes and new testing needs (e.g., Interconnection Testing) that had a significant influence on the methodology. NIT is likely to continue to develop further in the future according to the needs of telecom operators, authorities, user�s associations and suppliers.},
  author = {Reussner, Ralf H.},
  journal = {Future Generation Computer Systems},
  number = {5},
  pages = {627--639},
  title = {{A}utomatic {C}omponent {P}rotocol {A}daptation with the {C}o{C}o{N}ut {T}ool {S}uite},
  volume = {19},
  year = {2003}
}

@article{reussner2003e,
  author = {Reussner, Ralf H.},
  issn = {0167-739X},
  journal = {Future Generation Computer Systems},
  number = {5},
  pages = {749--759},
  title = {{U}sing {SK}a{MPI} for {D}eveloping {H}igh-{P}erformance {MPI} {P}rograms with {P}erformance {P}ortability},
  volume = {19},
  year = {2003}
}

@incollection{reussner2003a,
  abstract = {One of the motivations for specifying software architectures explicitly is the better prediction of system quality attributes. In this chapter we present an approach for determining the reliability of component-based software architectures. Our method is based on RADL (Rich Architecture Definition Language), an extension of DARWIN [16]. RADL places special emphasis on component interoperation and, in particular, on accounting for the effects of interoperation on system reliability. To achieve this, our methods use a notion of design-by-contract [19] for components, called parameterized contracts [26]. Our contracts involve finite state machines that allow software architects to define how a componentrsquos reliability will react to a deployment environment. We show how a system, built from contractually specified components, can be understood in terms of Markov models, facilitating system reliability analysis. We illustrate our approach with an e-commerce example and report about empirical measurements which confirm our analytical reliability prediction by means of monitoring in our reliability testbed.},
  author = {Reussner, Ralf H. and Poernomo, Iman H. and Schmidt, Heinz W.},
  booktitle = {Component-Based Software Quality: Methods and Techniques},
  editor = {Cechich, A. and Piattini, M. and Vallecillo, A.},
  pages = {287--325},
  publisher = {Springer-Verlag Berlin Heidelberg},
  series = {Lecture Notes in Computer Science},
  title = {{R}easoning on {S}oftware {A}rchitectures with {C}ontractually {S}pecified {C}omponents},
  volume = {2693},
  year = {2003}
}

@inproceedings{reussner2003c,
  abstact = {We argue that quality attributes of a component are most often not a constant property. Muchmore, the quality of a component heavily depends on the specific usage context. Therefore, we present a specification method for contractually specified components which does not specify quality attributes as constants but as functions to be evaluated at deployment. The contribution of this paper is threefold: (a) We clarify the term �contractual use of components�, a term which is often misstated or used inconsistently in current literature. We therefore translate the �design-by-contract�-principle to components. (b) We generalise component contracts to parameterised contracts, taking the mentioned context-dependencies of components into account. (c) We finally demonstrate how parameterised contracts are used to compute the reliability of software components. Results from an empirical evaluation confirm the strong context-dependency of a component�s reliability but also show that parameterised contracts for reliability prediction are easy to specify by automated control-flow analysis.},
  author = {Reussner, Ralf H. and Poernomo, Iman H. and Schmidt, Heinz W.},
  booktitle = {Proceedings of the Eigth International Workshop on Component-Oriented Programming (WCOP'03)},
  editor = {Weck, Wolfgang and Bosch, Jan and Szyperski, Clemens},
  month = {June},
  title = {{C}ontracts and {Q}uality {A}ttributes for {S}oftware {C}omponents},
  url = {http://sdqweb.ipd.uka.de/publications/pdfs/reussner2003c.pdf},
  year = {2003}
}

@article{reussner2003d,
  abstract = {Due to the increasing size and complexity of software systems, software architectures have become a crucial part in development projects. A lot of effort has been put into defining formal ways for describing architecture specifications using Architecture Description Languages (ADLs). Since no common ADL today offers tools for evaluating the performance, an attempt to develop such a tool based on an event-based simulation engine has been made. Common ADLs were investigated and the work was based on the fundamentals within the field of software architectures. The tool was evaluated both in terms of correctness in predictions as well as usability to show that it actually is possible to evaluate the performance using high-level architectures as models.},
  author = {Reussner, Ralf H. and Schmidt, Heinz W. and Poernomo, Iman},
  journal = {Journal of Systems and Software -- Special Issue of Software Architecture -- Engineering Quality Attributes},
  number = {3},
  pages = {241--252},
  title = {{R}eliability {P}rediction for {C}omponent-{B}ased {S}oftware {A}rchitectures},
  volume = {66},
  year = {2003}
}

@mastersthesis{trifu03a,
  author = {Mircea Trifu},
  month = {September},
  school = {"Politehnica" University of Timi{\c s}oara, Romania},
  title = {Architecture-Aware Adaptive Clustering of Object-Oriented Systems},
  year = {2003}
}