Soft Ware 2002

Software professionals and companies live in a new world today. Increasingly complex systems need to be built faster and cheaper. While many of the est- lished approaches in software quality are still valid, the software quality c- munity is going through a paradigm shift that requires a re-assessment of our current method and tool portfolio, as well as creating new and more e?ective solutions. We have selected two themes for this conference to highlight this paradigm shift. Our ?rst theme, “production of attractive and reliable software at Internet speed” sums up the dilemma many software organisations face. In order to be competitive, software should contain advanced features and run reliably – yet it should be developed quickly and cost e?ectively for the right market window. Finding the right balance between these objectives is a critical question that will determine business success in the years to come. Our second theme, “production of software with a dynamic partnership n- work” highlights the current trend of using partnerships and subcontractors as integral players in the software development process. Partnerships sometimes need to be created quickly to respond to a market opportunity, yet the costs and speed of cooperation must be competitive. Di?erent companies have di?erent processes, quality tools and cultures, yet they should cooperate seamlessly for the best result.

"This book provides the research and instruction used to develop and implement software quickly, in small iteration cycles, and in close cooperation with the customer in an adaptive way, making it possible to react to changes set by the constant changing business environment. It presents four values explaining extreme programming (XP), the most widely adopted agile methodology"--Provided by publisher.

Software is the essential enabler for the new economy and science. It creates new markets and new directions for a more reliable, flexible, and robust society. It empowers the exploration of our world in ever more depth. However, software often falls short behind our expectations. Current software methodologies, tools, and techniques remain expensive and not yet reliable for a highly changeable and evolutionary market. Many approaches have been proven only as case-by-case oriented methods. This book presents a number of new trends and theories in the direction in which we believe software science and engineering may develop to transform the role of software and science in tomorrow’s information society. This publication is an attempt to capture the essence of a new state of art in software science and its supporting technology. Is also aims at identifying the challenges such a technology has to master.

This volume examines proven software configuration management strategies to allow professionals to deliver quality software systems with the least amount of wasted effort. It is designed to help managers build and foster a development environment focused on producing optimal teamwork.

This book constitutes the thoroughly refereed post-conference proceedings of the 6th International Haifa Verification Conference, HVC 2010, held in Haifa, Israel in October 2010. The 10 revised full papers presented together with 7 invited papers were carefully reviewed and selected from 30 submissions. The papers address all current issues, challenges and future directions of verification for hardware, software, and hybrid systems and have a research focus on hybrid methods and the migration of methods and ideas between hardware and software, static and dynamic analysis, pre- and post-silicon.

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, processes, and software systems, which would in turn give rise to more appropriate techniques and higher-quality systems. Following an introductory chapter that provides an exploration of key issues in requirements engineering, the book is organized in three parts. Part 1 presents surveys of state-of-the art requirements engineering process research along with critical assessments of existing models, frameworks and techniques. Part 2 addresses key areas in requirements engineering, such as market-driven requirements engineering, goal modeling, requirements ambiguity, and others. Part 3 concludes the book with articles that present empirical evidence and experiences from practices in industrial projects. Its broader perspective gives this book its distinct appeal and makes it of interest to both researchers and practitioners, not only in software engineering but also in other disciplines such as business process engineering and management science.

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).