You may have to Search all our reviewed books and magazines, click the sign up button below to create a free account.
Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The...
Following an introductory chapter that provides an exploration of key issues in requirements engineering, this book is organized in three parts. It presents surveys of requirements engineering process research along with critical assessments of existing models, frameworks and techniques. It also addresses key areas in requirements engineering.
Nowadays, societies crucially depend on high-quality software for a large part of their functionalities and activities. Therefore, software professionals, researchers, managers, and practitioners alike have to competently decide what software technologies and products to choose for which purpose. For various reasons, systematic empirical studies employing strictly scientific methods are hardly practiced in software engineering. Thus there is an unquestioned need for developing improved and better-qualified empirical methods, for their application in practice and for dissemination of the results. This book describes different kinds of empirical studies and methods for performing such studies, e.g., for planning, performing, analyzing, and reporting such studies. Actual studies are presented in detail in various chapters dealing with inspections, testing, object-oriented techniques, and component-based software engineering.
Software quality is a generalised statement difficult to agree or disagree with until a precise definition of the concept of "Software Quality" is reached in terms of measurable quantities. Unfortunately, for the software technology the basic question of: • what to measure; • how to measure; • when to measure; • how to deal with the data obtained are still unanswered and are also closely dependant on the field of application. In the past twenty years or more there have been a number of conferences and debates focusing on the concept of Software Quality, which produced no real industrial impact. Recently, however, the implementation of a few generic standards (ISO 9000, IEEE etc.) has...
It is my belief that software engineers not only need to know software engineering methods and processes, but that they also should know how to assess them. Conse quently, I have taught principles of experimentation and empirical studies as part of the software engineering curriculum. Until now, this meant selecting a text from another discipline, usually psychology, and augmenting it with journal or confer ence papers that provide students with software engineering examples of experi ments and empirical studies. This book fills an important gap in the software engineering literature: it pro vides a concise, comprehensive look at an important aspect of software engineer ing: experimental ana...
This book constitutes the refereed proceedings of the 9th International Conference on Model Driven Engineering Languages and Systems (formerly UML conferences), MoDELS 2006. The book presents 51 revised full papers and 2 invited papers. Discussion is organized in topical sections on evaluating UML, MDA in software development, concrete syntax, applying UML to interaction and coordination, aspects, model integration, formal semantics of UML, security, model transformation tools and implementation, and more.
The dependence on quality software in all areas of life is what makes software engineering a key discipline for today’s society. Thus, over the last few decades it has been increasingly recognized that it is particularly important to demonstrate the value of software engineering methods in real-world environments, a task which is the focus of empirical software engineering. One of the leading protagonists of this discipline worldwide is Prof. Dr. Dr. h.c. Dieter Rombach, who dedicated his entire career to empirical software engineering. For his many important contributions to the field he has received numerous awards and recognitions, including the U.S. National Science Foundation’s Pres...
By bringing together various current directions, Software Project Management in a Changing World focuses on how people and organizations can make their processes more change-adaptive. The selected chapters closely correspond to the project management knowledge areas introduced by the Project Management Body of Knowledge, including its extension for managing software projects. The contributions are grouped into four parts, preceded by a general introduction. Part I “Fundamentals” provides in-depth insights into fundamental topics including resource allocation, cost estimation and risk management. Part II “Supporting Areas” presents recent experiences and results related to the managem...
The IFIP International Working Conference on Intelligent Networks '95 was held at the Technical University of Denmark (DTU) in Copenhagen. The conference was organised jointly by the Center for Tete-Information at DTU and Tele Danmark Research! during August 30-31 1995 and was hosted by the Center for Tete-Information. The conference was sponsored by IFIP TC6. The papers contained in this book are edited versions of the papers from the conference and some of the tutorial presentations that were arranged prior to the conference. The mixture of tutorial papers and conference papers gives a broad and yet thorough coverage of activities and central areas of development in the IN world at this po...
The IT community has always struggled with questions concerning the value of an organization’s investment in software and hardware. It is the goal of value-based software engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule – such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extend...