Annotation Best practice management and development of Visual Studio .NET 2005 applications with this easy-to-use SCM tool from Microsoft * SCM fundamentals and strategies clearly explained * Real-world SOA example: a hotel reservation system * SourceSafe best practices across the complete lifecycle * Multiple versions, service packs and product updates.

This textbook describes the approaches used by software engineers to build quality into their software. The fundamental principles of software quality management and software process improvement are discussed in detail, with a particular focus on the CMMI framework. Features: includes review questions at the end of each chapter; covers both theory and practice, and provides guidance on applying the theory in an industrial environment; examines all aspects of the software development process, including project planning and tracking, software lifecycles, software inspections and testing, configuration management, and software quality assurance; provides detailed coverage of software metrics and problem solving; describes SCAMPI appraisals and how they form part of the continuous improvement cycle; presents an introduction to formal methods and the Z specification language; discusses UML, which is used to describe the architecture of the system; reviews the history of the field of software quality.

This textbook presents a concise introduction to the fundamental principles of software engineering, together with practical guidance on how to apply the theory in a real-world, industrial environment. The wide-ranging coverage encompasses all areas of software design, management, and quality. Topics and features: presents a broad overview of software engineering, including software lifecycles and phases in software development, and project management for software engineering; examines the areas of requirements engineering, software configuration management, software inspections, software testing, software quality assurance, and process quality; covers topics on software metrics and problem solving, software reliability and dependability, and software design and development, including Agile approaches; explains formal methods, a set of mathematical techniques to specify and derive a program from its specification, introducing the Z specification language; discusses software process improvement, describing the CMMI model, and introduces UML, a visual modelling language for software systems; reviews a range of tools to support various activities in software engineering, and offers advice on the selection and management of a software supplier; describes such innovations in the field of software as distributed systems, service-oriented architecture, software as a service, cloud computing, and embedded systems; includes key learning topics, summaries and review questions in each chapter, together with a useful glossary. This practical and easy-to-follow textbook/reference is ideal for computer science students seeking to learn how to build high quality and reliable software on time and on budget. The text also serves as a self-study primer for software engineers, quality professionals, and software managers.

Project initiation; Project planning; Project execution and termination.

C. Amting Directorate General Information Society, European Commission, Brussels th Under the 4 Framework of European Research, the European Systems and Soft ware Initiative (ESSI) was part of the ESPRIT Programme. This initiative funded more than 470 projects in the area of software and system process improvements. The majority of these projects were process improvement experiments carrying out and taking up new development processes, methods and technology within the software development process of a company. In addition, nodes (centres of exper tise), European networks (organisations managing local activities), training and dissemination actions complemented the process improvement experiments. ESSI aimed at improving the software development capabilities of European enterprises. It focused on best practice and helped European companies to develop world class skills and associated technologies to build the increasingly complex and varied systems needed to compete in the marketplace. The dissemination activities were designed to build a forum, at European level, to exchange information and knowledge gained within process improvement ex periments. Their major objective was to spread the message and the results of experiments to a wider audience, through a variety ofdifferent channels. The European Experience Exchange (tUR~X) project has been one ofthese dis semination activities within the European Systems and Software Initiative.~UR~X has collected the results of practitioner reports from numerous workshops in Europe and presents, in this series of books, the results of Best Practice achieve ments in European Companies over the last few years.

InfoWorld is targeted to Senior IT professionals. Content is segmented into Channels and Topic Centers. InfoWorld also celebrates people, companies, and projects.

Anne Mette Jonassen Hass explains the principles and benefits of a sound configuration management strategy. This volume is designed to help the professional put that strategy into action.

This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often. Whether as a full-time position or just because they are helpful, all projects have toolsmiths: making choices about tools, installing them, and then maintaining the tools that everyone else depends upon. This book is especially for everyone who ends up being a toolsmith for his or her group.