Search

Your search keyword '"Software Technology Group [Darmstadt]"' showing total 7 results
Start Over Author "Software Technology Group [Darmstadt]" Topic software
7 results on '"Software Technology Group [Darmstadt]"'

1. Detecting missing method calls as violations of the majority rule

Author

Martin Monperrus, Mira Mezini, Software Technology Group [Darmstadt], Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt), Adaptive Distributed Applications and Middleware (ADAM), Laboratoire d'Informatique Fondamentale de Lille (LIFL), Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe, and Institut National de Recherche en Informatique et en Automatique (Inria)

Subjects
FOS: Computer and information sciences, Majority rule, Information retrieval, business.industry, Computer science, Best practice, Code smell, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], Software Engineering (cs.SE), Set (abstract data type), Computer Science - Software Engineering, Software, Key (cryptography), Code (cryptography), business
Abstract

International audience; When using object-oriented frameworks it is easy to overlook certain important method calls that are required at particular places in code. In this paper, we provide a comprehensive set of empirical facts on this problem, starting from traces of missing method calls in a bug repository. We propose a new system that searches for missing method calls in software based on the other method calls that are observable. Our key insight is that the voting theory concept of majority rule holds for method calls: a call is likely to be missing if there is a majority of similar pieces of code where this call is present. The evaluation shows that the system predictions go further missing method calls and often reveal different kinds of code smells (e.g. violations of API best practices).

Published
2013
Full Text
View/download PDF

2. What should developers be aware of? An empirical study on the directives of API documentation

Author

Elif Tekes, Martin Monperrus, Mira Mezini, Michael Eichberg, Adaptive Distributed Applications and Middleware (ADAM), Laboratoire d'Informatique Fondamentale de Lille (LIFL), Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe, Institut National de Recherche en Informatique et en Automatique (Inria), Software Technology Group [Darmstadt], and Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt)

Subjects
FOS: Computer and information sciences, Application programming interface, business.industry, Computer science, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], Reuse, Software Engineering (cs.SE), Computer Science - Software Engineering, Software, Empirical research, Order (business), Taxonomy (general), Software engineering, business
Abstract

Application Programming Interfaces (API) are exposed to developers in order to reuse software libraries. API directives are natural-language statements in API documentation that make developers aware of constraints and guidelines related to the usage of an API. This paper presents the design and the results of an empirical study on the directives of API documentation of object-oriented libraries. Its main contribution is to propose and extensively discuss a taxonomy of 23 kinds of API directives., Comment: Empirical Software Engineering (2011)

Published
2011
Full Text
View/download PDF

3. Abmash: Mashing Up Legacy Web Applications by Automated Imitation of Human Actions

Author

Mira Mezini, Martin Monperrus, Alper Ortac, Darmstadt University of Technology [Darmstadt], Adaptive Distributed Applications and Middleware (ADAM), Laboratoire d'Informatique Fondamentale de Lille (LIFL), Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe, Institut National de Recherche en Informatique et en Automatique (Inria), Software Technology Group [Darmstadt], and Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt)

Subjects
FOS: Computer and information sciences, Ajax, SIMPLE (military communications protocol), business.industry, Computer science, media_common.quotation_subject, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], computer.software_genre, Software Engineering (cs.SE), Computer Science - Software Engineering, Human–computer interaction, Code (cryptography), Web application, Mashup, business, Imitation, computer, Composition (language), Software, Graphical user interface, computer.programming_language, media_common
Abstract

Many business web-based applications do not offer applications programming interfaces (APIs) to enable other applications to access their data and functions in a programmatic manner. This makes their composition difficult (for instance to synchronize data between two applications). To address this challenge, this paper presents Abmash, an approach to facilitate the integration of such legacy web applications by automatically imitating human interactions with them. By automatically interacting with the graphical user interface (GUI) of web applications, the system supports all forms of integrations including bi-directional interactions and is able to interact with AJAX-based applications. Furthermore, the integration programs are easy to write since they deal with end-user, visual user-interface elements. The integration code is simple enough to be called a "mashup"., Comment: Software: Practice and Experience (2013)

Published
2013
Full Text
View/download PDF

4. Automated Measurement of Models of Requirements

Author

Benoit Baudry, Joël Champeau, Jean-Marc Jézéquel, Martin Monperrus, Brigitte Hoeltzener, Software Technology Group [Darmstadt], Technische Universität Darmstadt (TU Darmstadt), Reliable and efficient component based software engineering (TRISKELL), Institut de Recherche en Informatique et Systèmes Aléatoires (IRISA), Université de Rennes 1 (UR1), Université de Rennes (UNIV-RENNES)-Université de Rennes (UNIV-RENNES)-Institut National des Sciences Appliquées - Rennes (INSA Rennes), Institut National des Sciences Appliquées (INSA)-Université de Rennes (UNIV-RENNES)-Institut National des Sciences Appliquées (INSA)-Institut National de Recherche en Informatique et en Automatique (Inria)-Centre National de la Recherche Scientifique (CNRS)-Université de Rennes 1 (UR1), Institut National des Sciences Appliquées (INSA)-Université de Rennes (UNIV-RENNES)-Institut National des Sciences Appliquées (INSA)-Institut National de Recherche en Informatique et en Automatique (Inria)-Centre National de la Recherche Scientifique (CNRS)-Inria Rennes – Bretagne Atlantique, Institut National de Recherche en Informatique et en Automatique (Inria), Lab-STICC_ENSTAB_CACS_MOCS, Laboratoire des sciences et techniques de l'information, de la communication et de la connaissance (UMR 3192) (Lab-STICC), Université européenne de Bretagne - European University of Brittany (UEB)-Université de Bretagne Sud (UBS)-Université de Brest (UBO)-Institut Brestois du Numérique et des Mathématiques (IBNM), Université de Brest (UBO)-Télécom Bretagne-Institut Mines-Télécom [Paris] (IMT)-Centre National de la Recherche Scientifique (CNRS)-Université européenne de Bretagne - European University of Brittany (UEB)-Université de Bretagne Sud (UBS)-Université de Brest (UBO)-Institut Brestois du Numérique et des Mathématiques (IBNM), Université de Brest (UBO)-Télécom Bretagne-Institut Mines-Télécom [Paris] (IMT)-Centre National de la Recherche Scientifique (CNRS), Département STIC [Brest] (STIC), École Nationale Supérieure de Techniques Avancées Bretagne (ENSTA Bretagne), Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt), Université de Rennes (UR)-Institut National des Sciences Appliquées - Rennes (INSA Rennes), Institut National des Sciences Appliquées (INSA)-Institut National des Sciences Appliquées (INSA)-Institut National de Recherche en Informatique et en Automatique (Inria)-Centre National de la Recherche Scientifique (CNRS)-Université de Rennes (UR)-Institut National des Sciences Appliquées - Rennes (INSA Rennes), Institut National des Sciences Appliquées (INSA)-Institut National des Sciences Appliquées (INSA)-Institut National de Recherche en Informatique et en Automatique (Inria)-Centre National de la Recherche Scientifique (CNRS)-Inria Rennes – Bretagne Atlantique, Université européenne de Bretagne - European University of Brittany (UEB)-Université de Bretagne Sud (UBS)-Université de Brest (UBO)-Télécom Bretagne-Institut Brestois du Numérique et des Mathématiques (IBNM), Université de Brest (UBO)-Institut Mines-Télécom [Paris] (IMT)-Centre National de la Recherche Scientifique (CNRS)-Université européenne de Bretagne - European University of Brittany (UEB)-Université de Bretagne Sud (UBS)-Université de Brest (UBO)-Télécom Bretagne-Institut Brestois du Numérique et des Mathématiques (IBNM), and Université de Brest (UBO)-Institut Mines-Télécom [Paris] (IMT)-Centre National de la Recherche Scientifique (CNRS)

Subjects
Requirements management, 021103 operations research, Non-functional requirement, Requirements traceability, business.industry, Computer science, 0211 other engineering and technologies, Software requirements specification, 020207 software engineering, System requirements specification, 02 engineering and technology, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], computer.software_genre, Requirement prioritization, 0202 electrical engineering, electronic engineering, information engineering, Non-functional testing, Data mining, Safety, Risk, Reliability and Quality, Software engineering, business, Requirements analysis, computer, Software
Abstract

update for BASE on Sep 08 2018 22:43:36; International audience; On way to formalize system requirements is to express them using the object-oriented paradigm. In this case, the class model representing the structure of requirements is called a requirements metamodel, and requirements themselves are object-based models of natural-language requirements. In this paper, we show that such object-oriented requirements are well-suited to support a large class of requirements metrics. We define a requirements metamodel and use an automated measurement approach proposed in our previous work to specify requirements metrics. We show that it is possible to integrate 78 metrics from 11 different papers in the proposed framework. The software that computes the requirements metric values is fully generated from the specification of metrics.

Published
2013
Full Text
View/download PDF

5. Querying source code with natural language

Author

Mira Mezini, Martin Monperrus, Markus Kimmig, Software Technology Group [Darmstadt], Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt), Adaptive Distributed Applications and Middleware (ADAM), Laboratoire d'Informatique Fondamentale de Lille (LIFL), Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe, Institut National de Recherche en Informatique et en Automatique (Inria), and Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)

Subjects
FOS: Computer and information sciences, Source code, business.industry, Computer science, Programming language, media_common.quotation_subject, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], computer.software_genre, Task (project management), Software Engineering (cs.SE), Computer Science - Software Engineering, Software, business, computer, Natural language, media_common
Abstract

International audience; One common task of developing or maintaining software is searching the source code for information like specific method calls or write accesses to certain fields. This kind of information is required to correctly implement new features and to solve bugs. This paper presents an approach for querying source code with natural language.

Published
2011
Full Text
View/download PDF

6. Product line implementation with ECaesarJ

Author

Jacques Noyé, Vaidas Gasiunas, Angel Núñez, Mira Mezini, Software Technology Group [Darmstadt], Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt), Laboratoire d'Informatique de Nantes Atlantique (LINA), Mines Nantes (Mines Nantes)-Université de Nantes (UN)-Centre National de la Recherche Scientifique (CNRS), Aspect and composition languages (ASCOLA), Mines Nantes (Mines Nantes)-Université de Nantes (UN)-Centre National de la Recherche Scientifique (CNRS)-Mines Nantes (Mines Nantes)-Université de Nantes (UN)-Centre National de la Recherche Scientifique (CNRS)-Département informatique - EMN, Mines Nantes (Mines Nantes)-Inria Rennes – Bretagne Atlantique, Institut National de Recherche en Informatique et en Automatique (Inria)-Institut National de Recherche en Informatique et en Automatique (Inria), Awais Rashid and Jean-Claude Royer and Andreas Rummler, European Project: 33573,AMPLE, Jacques, Noyé, and AMPLE: Aspect-oriented, model-driven, product line engineering - AMPLE - 33573 - OLD

Subjects
Theoretical computer science, Finite-state machine, ACM: D.: Software/D.2: SOFTWARE ENGINEERING/D.2.13: Reusable Software, [INFO.INFO-PL]Computer Science [cs]/Programming Languages [cs.PL], business.industry, Programming language, Computer science, [INFO.INFO-SE] Computer Science [cs]/Software Engineering [cs.SE], Mixin, Inversion of control, ACM: D.: Software/D.3: PROGRAMMING LANGUAGES/D.3.3: Language Constructs and Features, [INFO.INFO-SE]Computer Science [cs]/Software Engineering [cs.SE], computer.software_genre, [INFO.INFO-PL] Computer Science [cs]/Programming Languages [cs.PL], Feature (linguistics), Software, Product (mathematics), Decomposition (computer science), Late binding, business, computer
Abstract

International audience; This chapter takes a closer look at the difficulties of feature-oriented modularisation of product lines and demonstrate how a better modularisation can be achieved with the ECaesarJ programming language, through a type-safe and stable decomposition of a broad spectrum of software abstractions: classes, methods, events, and state machines, based on late binding and mixin composition.

Published
2011

7. A model curriculum for aspect-oriented software development

Author

Jacques Noyé, Johan Brichau, Awais Rashid, Ruzanna Chitchyan, Siobhán Clarke, M. Haupt, Ellie D'Hondt, Alessandro Garcia, Mario Südholt, Wouter Joosen, Shmuel Katz, Centre Leo Apostel, Informatics and Applied Informatics, Software Languages Lab, Weaving of Software Components (JACQUARD), Laboratoire d'Informatique Fondamentale de Lille (LIFL), Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe, Institut National de Recherche en Informatique et en Automatique (Inria), Computing Department [Lancaster], Lancaster University, Department of Computer Science - Trinity College Dublin, University of Dublin, Center Leo Apostel (CLEA), Vrije Universiteit Brussel (VUB), Software Technology Group [Darmstadt], Technische Universität Darmstadt (TU Darmstadt), Distributed Systems and Computer Networks (DistriNet), Catholic University of Leuven - Katholieke Universiteit Leuven (KU Leuven), Department of Computer Science [Haifa], University of Haifa [Haifa], Objects, aspects and components (OBASCO), Mines Nantes (Mines Nantes)-Inria Rennes – Bretagne Atlantique, Institut National de Recherche en Informatique et en Automatique (Inria)-Institut National de Recherche en Informatique et en Automatique (Inria), Laboratoire d'Informatique de Nantes Atlantique (LINA), Mines Nantes (Mines Nantes)-Université de Nantes (UN)-Centre National de la Recherche Scientifique (CNRS), NoE AOSD-Europe, and Technische Universität Darmstadt - Technical University of Darmstadt (TU Darmstadt)

Subjects
Social software engineering, Software Engineering Process Group, Engineering, [INFO.INFO-PL]Computer Science [cs]/Programming Languages [cs.PL], Software engineering, business.industry, 4. Education, Software development, 020207 software engineering, 02 engineering and technology, aspect-oriented software development, curricula development, Software development process, ComputingMilieux_GENERAL, 020204 information systems, Software construction, Personal software process, 0202 electrical engineering, electronic engineering, information engineering, ComputingMilieux_COMPUTERSANDEDUCATION, Package development process, business, Software
Abstract

Special issue on Software Engineering Curriculum Development; International audience; As new software engineering techniques emerge, there's a cognitive shift in how developers approach a problem's analysis and how they design and implement its software-based solution. Future software engineers must be appropriately and effectively trained in new techniques' fundamentals and applications. With techniques becoming more mature, such training moves beyond specialized industrial courses into postgraduate curricula (as advanced topics) and subsequently into undergraduate curricula. A model curriculum for aspect-oriented software development provides guidelines about fundamentals, a common framework, and a step toward developing a body of knowledge.

Published
2006
Full Text
View/download PDF

Catalog

Books, media, physical & digital resources
See catalog results