You may have to Search all our reviewed books and magazines, click the sign up button below to create a free account.
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...
Developing variable systems faces many challenges. Dependencies between interrelated artifacts within a product variant, such as code or diagrams, across product variants and across their revisions quickly lead to inconsistencies during evolution. This work provides a unification of common concepts and operations for variability management, identifies variability-related inconsistencies and presents an approach for view-based consistency preservation of variable systems.
Over the last decade, Method Engineering, defined as the engineering discipline to design, construct and adapt methods, including supportive tools, has emerged as the research and application area for using methods for systems development. This book contains the papers from the IFIP Working Group 8.1 conference on Situational Method Engineering.
Requirements engineering is the process by which the requirements for software systems are gathered, analyzed, documented, and managed throughout their complete lifecycle. Traditionally it has been concerned with technical goals for, functions of, and constraints on software systems. Aurum and Wohlin, however, argue that it is no longer appropriate for software systems professionals to focus only on functional and non-functional aspects of the intended system and to somehow assume that organizational context and needs are outside their remit. Instead, they call for a broader perspective in order to gain a better understanding of the interdependencies between enterprise stakeholders, processe...
This book contains most of the papers presented at the 4th International C- ference on Extreme Programming and Agile Processes in Software Engineering (XP 2003), held in Genoa, Italy, May 2003. The XP 200n series of conferences were started in 2000 to promote the - change of new ideas, research and applications in the emerging ?eld of agile methodologies for software development. Over the years, the conference has - come the main world forum for all major advances in this important ?eld. Also this year the contributions to Agile Methodologies and Extreme P- gramming were substantial. They demonstrate that the topic is continuing to gain more and more momentum. In spite of some criticism of a...
This book constitutes the refereed proceedings of the 4th Software Quality Days Conference (SWQD) held in Vienna, Austria, in January 2012. The selection of presentations at the conference encompasses a mixture of practical presentations and scientific papers covering new research topics. The seven scientific full papers accepted for SWQD were each peer-reviewed by three or more reviewers and selected out of 18 high-quality submissions. Further, six short papers on promising research directions were also presented and included in order to spark discussions between researchers and practitioners. The papers are organized into topical sections on software product quality; software engineering processes; software process improvement; component-based architectures; risk management; and quality assurance and collaboration.
This book constitutes the refereed proceedings of the 7th International Conference on Extreme Programming and Agile Processes in Software Engineering, XP 2006, held in Oulu, Finland, June 2006. The book presents 16 revised full papers together with 6 experience papers, 12 poster papers and panel summaries, organized in topical sections on foundation and rationale for agile methods, effects of pair programming, quality in agile software development, and more.
This textbook describes the theory and the pragmatics of using and engineering high-level software languages – also known as modeling or domain-specific languages (DSLs) – for creating quality software. This includes methods, design patterns, guidelines, and testing practices for defining the syntax and the semantics of languages. While remaining close to technology, the book covers multiple paradigms and solutions, avoiding a particular technological silo. It unifies the modeling, the object-oriented, and the functional-programming perspectives on DSLs. The book has 13 chapters. Chapters 1 and 2 introduce and motivate DSLs. Chapter 3 kicks off the DSL engineering lifecycle, describing h...
This book constitutes the refereed proceedings of the First International Conference on Software Process, held in Minneapolis, MN, USA, in May 2007. The 28 revised full papers presented together with the abstracts of two keynote addresses cover process content, process tools and metrics, process management, process representation, analysis and modeling, experience report, and simulation modeling.
Software and Systems Traceability provides a comprehensive description of the practices and theories of software traceability across all phases of the software development lifecycle. The term software traceability is derived from the concept of requirements traceability. Requirements traceability is the ability to track a requirement all the way from its origins to the downstream work products that implement that requirement in a software system. Software traceability is defined as the ability to relate the various types of software artefacts created during the development of software systems. Traceability relations can improve the quality of a product being developed, and reduce the time and cost of development. More specifically, traceability relations can support evolution of software systems, reuse of parts of a system by comparing components of new and existing systems, validation that a system meets its requirements, understanding of the rationale for certain design and implementation decisions, and analysis of the implications of changes in the system.