4,951 papers · page 161 of 248
Frank Keenan
Developing software using a well-defined, well-understood process improves the likelihood of delivering a product with the required quality. Enhancing that process to meet recognised process standards, such as CMMI and ISO 9000, can further facilitate the development of complex s…
Rohit Khare, Richard N. Taylor
Because it takes time and trust to establish agreement, traditional consensus-based architectural styles cannot safely accommodate resources that change faster than it takes to transmit notification of that change, nor resources that must be shared across independent agencies. Th…
Diana Kirk
The development of software products is a complex activity with a large number of factors involved in defining success. As real-world experimentation is difficult and costly, researchers have used various techniques in an attempt to model the development process. This field of so…
Barbara A. Kitchenham, Tore Dybå, Magne Jørgensen
Our objective is to describe how software engineering might benefit from an evidence-based approach and to identify the potential difficulties associated with the approach. We compared the organisation and technical infrastructure supporting evidence-based medicine (EBM) with the…
John C. Knight
It is important that computer engineers, software engineers, project managers, and users understand the major elements of current technology in the field of dependability, yet this material tends to be unfamiliar to researchers and practitioners alike. Researchers are often conce…
Jyrki Kontio, Magnus Höglund, Jan Rydén, Pekka Abrahamsson
Software development is always a challenging undertaking and it requires high commitments from individuals who participate in it. Software development often involves new technology, challenging or unknown requirements, and tight schedules - making it particularly prone to several…
Axel van Lamsweerde
Caring for security at requirements engineering time is a message that has finally received some attention recently. However, it is not yet very clear how to achieve this systematically through the various stages of the requirements engineering process. The paper presents a const…
Rogério de Lemos, Cristina Gacek, Alexander B. Romanovsky
Wee Kheng Leow, Siau-Cheng Khoo, Yi Sun
Most research on automated specification-based software testing has focused on the automated generation of test cases. Before a software system can be tested, it must be set up according to the input requirements of the test cases. This setup process is usually performed manually…
Karl J. Lieberherr
Our research has focused on identifying techniques to develop software that is amenable to refactoring and change. The Law of Demeter (LoD) was one contribution in this effort. But it led to other problems. With the current state of the art focused on aspect-oriented software dev…
Ronald van der Lingen, André van der Hoek
Building a configuration management (CM) system is a difficult endeavor that regularly requires tens of thousands of lines of code to be written. To reduce this effort, several experimental infrastructures have been developed that provide reusable repositories upon which to build…
Annabella Loconsole
The goal of this research is to demonstrate that a subset of a set of 38 requirements management measures are good predictors of stability and volatility of requirements and change requests. At the time of writing we have theoretically validated ten of these 38 measures. We are c…
Jeffrey Ka-Hing Mak, Clifford Sze-Tsan Choy, Daniel Pak-Kong Lun
Prior research attempts to formalize the structure of object-oriented design patterns for a more precise specification of design patterns. It also allows automation support to be developed for user-defined design patterns in the future CASE tools. Targeting to a particular type o…
Peter Manhart, Kurt Schneider
A software engineering department in a Daimler-Chrysler business unit was highly professional at developing embedded software for busses and coaches. However, customer specific add-ons were a regular source of hassle. Simple as they are, those individual requirements have to be i…
Mika Mäntylä
This research abstract presents two approaches for utilizing the developers' subjective design quality evaluations during the software lifecycle. In process-based approach developers study and improve their system's structure at fixed intervals. Tool-based approach uses subjectiv…
Leonardo Mariani
Mari Matinlassi
Product line architectures (PLAs) have been under continuous attention in the software research community during the past few years. Although several methods have been established to create PLAs there are not available studies comparing PLA methods. Five methods are known to answ…
Atif M. Memon, Adam A. Porter, Cemal Yilmaz, Adithya Nagarajan, Douglas C. Schmidt, Balachandran Natarajan
Quality assurance (QA) tasks, such as testing, profiling, and performance evaluation, have historically been done in-house on developer-generated workloads and regression suites. Since this approach is inadequate for many systems, tools and processes are being developed to improv…
Parastoo Mohagheghi, Reidar Conradi, Ole M. Killi, Henrik Schwarz
The paper describes results of an empirical study, where some hypotheses about the impact of reuse on defect-density and stability, and about the impact of component size on defects and defect-density in the context of reuse are assessed, using historical data (data mining) on de…
Nachiappan Nagappan
The field reliability is measured too late for affordably guiding corrective action to improve the quality of the software. Software developers can benefit from an early warning of their reliability while they can still affordably react. This early warning can be built from a col…