A5022214666- Software Engineering Techniques and Practices
- Software Engineering Research
- Business Process Modeling and Analysis
- Software Reliability and Analysis Research
- Software System Performance and Reliability
- Software Testing and Debugging Techniques
- Advanced Software Engineering Methodologies
- Open Source Software Innovations
- Scientific Computing and Data Management
- Advanced Malware Detection Techniques
- Model-Driven Software Engineering Techniques
- Green IT and Sustainability
- Big Data and Business Intelligence
- Web Data Mining and Analysis
- Service-Oriented Architecture and Web Services
- Complex Systems and Decision Making
- Technology Assessment and Management
- Mobile and Web Applications
- Sentiment Analysis and Opinion Mining
- Caching and Content Delivery
- Simulation Techniques and Applications
- Safety Systems Engineering in Autonomy
- E-Learning and Knowledge Management
- Cloud Computing and Resource Management
- Topic Modeling
University of Tartu
2016-2025
Beijing University of Posts and Telecommunications
2021
University of Southern California
2021
Vrije Universiteit Amsterdam
2021
University of Massachusetts Amherst
2021
University of Calgary
2007-2020
University of Oslo
2006-2013
Lund University
2011-2012
Japan External Trade Organization
1998-2009
Simula Research Laboratory
2008-2009
New knowledge in science and engineering relies increasingly on results produced by scientific software. Therefore, knowing how scientists develop use software their research is critical to assessing the necessity for improving current development practices making decisions about future allocation of resources. To that end, this paper presents a survey conducted online October-December 2008 which received almost 2000 responses. Our main conclusions are (1) required primarily acquired from...
One major problem for integrating study results into a common body of knowledge is the heterogeneity reporting styles: (1) it difficult to locate relevant information and (2) important often missing. Reporting guidelines are expected support systematic, standardized presentation empirical research, thus improving in order readers finding they looking for, understanding how an experiment conducted, (3) assessing validity its results. The objective this paper survey most prominent published...
Software developers often include available open-source software packages into their projects to minimize redundant effort. However, adding a package project can also introduce risks, which propagate through multiple levels of dependencies. Currently, not much is known about the structure ecosystems popular programming languages and extent transitive bug propagation possible. This paper analyzes dependency network evolution JavaScript, Ruby, Rust ecosystems. The reported results reveal...
Requirements Engineering (RE) has established itself as a software engineering discipline during the past decades. While researchers have been investigating RE with plethora of empirical studies, attempts to systematically derive an empirically-based theory in context just recently started. However, such is needed if we are define and motivate guidance performing high quality research practice. We aim at providing valid foundation for RE, which helps engineers establish effective efficient...
Empirical Standards are natural-language models of a scientific community's expectations for specific kind study (e.g. questionnaire survey). The ACM SIGSOFT Paper and Peer Review Quality Initiative generated empirical standards research methods commonly used in software engineering. These living documents, which should be continuously revised to reflect evolving consensus around best practices, will improve quality make peer review more effective, reliable, transparent fair.
Methods for predicting issue lifetime can help software project managers to prioritize issues and allocate resources accordingly. Previous studies on prediction have focused models built from static features, meaning features calculated at one snapshot of the issue's based data associated itself. However, during its lifetime, an typically receives comments various stakeholders, which may carry valuable insights into perceived priority difficulty thus be exploited update predictions....
Together with many success stories, promises such as the increase in production speed and improvement stakeholders' collaboration have contributed to making agile a transformation software industry which companies want take part. However, driven either by natural expected evolution or contextual factors that challenge adoption of methods prescribed their creator(s), processes practice mutate into hybrids over time. Are these still agile? In this article, we investigate question: what makes...
Evaluation, prioritization and selection of candidate requirements are tremendous importance impact for subsequent software development. Effort, time as well quality constraints have to be taken into account. Typically, different stakeholders conflicting priorities the all these balanced in an appropriate way ensure maximum value final set requirements. Trade-off analysis is needed proactively explore certain decisions terms criteria constraints. The proposed method called Quantitative...
Context: Exploratory Testing has experienced a rise in popularity the industry with emergence of agile development practices, yet it remains unclear, which domains and how is used practice.
Research collaboration between industry and academia supports improvement innovation in helps ensure the industrial relevance of academic research. However, many researchers practitioners community believe that level joint industry-academia (IAC) projects Software Engineering (SE) research is relatively low, creating a barrier practice. The goal empirical study reported this paper to explore characterize state IAC with respect needs, developed solutions, impacts also set challenges, patterns...
Software development methods are usually not applied by the book. Companies under pressure to continuously deploy software products that meet market needs and stakeholders' requests. To implement efficient effective processes, companies utilize multiple frameworks, practices, combine these into hybrid methods. A common combination contains a rich management framework organize steer projects complemented with number of smaller practices providing teams tools complete their tasks. In this...
Defining, prioritizing, and selecting requirements are problems of tremendous importance. In this paper, a new approach called Quantitative WinWin for decision support in negotiation is studied. The difference to Boehm's groupware-based the inclusion quantitative methods as backbone better more objective decisions. Like original WinWin, uses an iterative approach, with aim increase knowledge about during each iteration. novelty presented idea three-fold. Firstly, it Analytical Hierarchy...
Context: The authors wanted to assess whether the quality of published human-centric software engineering experiments was improving. This required a reliable means assessing such experiments. Aims: aims study were confirm usability evaluation checklist, determine how many reviewers needed per paper that reports an experiment, and specify appropriate process for evaluating quality. Method: With eight four papers describing experiments, we used checklist with nine questions. We conducted in...
Effort estimation is important to correctly plan the use of resources in a software project. In agile projects, correct effort helps decide which issues have be fixed or finished during next iteration. However, estimating can complex task and developers may make inaccurate estimates. Therefore, automatic approaches that aim support process worth studied. We explore predictive model developers' features assign story points issue reports. The performance compared with models based on extracted...
The development of scientific software has similarities with processes that follow the engineering "agile manifesto": responsiveness to change and collaboration are utmost importance. But how well do current software-development match practices found in agile methods, what effects using such processes?