𝔖 Scriptorium
✦   LIBER   ✦

πŸ“

Software Process Definition and Management

✍ Scribed by Jürgen Münch, Ove Armbrust, Martin Kowalczyk, Martín Soto (auth.)


Publisher
Springer-Verlag Berlin Heidelberg
Year
2012
Tongue
English
Leaves
253
Series
The Fraunhofer IESE Series on Software and Systems Engineering
Edition
1
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


The concept of processes is at the heart of software and systems engineering. Software process models integrate software engineering methods and techniques and are the basis for managing large-scale software and IT projects. High product quality routinely results from high process quality.

Software process management deals with getting and maintaining control over processes and their evolution. Becoming acquainted with existing software process models is not enough, though. It is important to understand how to select, define, manage, deploy, evaluate, and systematically evolve software process models so that they suitably address the problems, applications, and environments to which they are applied. Providing basic knowledge for these important tasks is the main goal of this textbook.

MΓΌnch and his co-authors aim at providing knowledge that enables readers to develop useful process models that are suitable for their own purposes. They start with the basic concepts. Subsequently, existing representative process models are introduced, followed by a description of how to create individual models and the necessary means for doing so (i.e., notations and tools). Lastly, different possible usage scenarios for process management are highlighted (e.g. process improvement and software process simulation).

Their book is aimed at students and researchers working on software project management, software quality assurance, and software measurement; and at practitioners who are interested in process definition and management for developing, maintaining, and operating software-intensive systems and services.

✦ Table of Contents


Front Matter....Pages i-xx
Introduction....Pages 1-18
Prescriptive Process Models....Pages 19-77
Descriptive Process Models....Pages 79-110
Process Modeling Notations and Tools....Pages 111-138
Process Improvement....Pages 139-176
Empirical Studies....Pages 177-186
Software Process Simulation....Pages 187-210
Glossary....Pages 211-215
Authors....Pages 217-218
Back Matter....Pages 219-235

✦ Subjects


Software Engineering; Management of Computing and Information Systems; Project Management


πŸ“œ SIMILAR VOLUMES


Software Process Quality: Management and
✍ Alexander Soifer, Branko GrΓΌnbaum, Peter Johnson, Cecil Rousseau πŸ“‚ Library πŸ“… 1999 πŸ› CRC Press, Marcel Dekker 🌐 English

<P>Using actual examples of software process improvement from the private sector and government, this work demonstrates how quality systems, measurement techniques and performance evaluations work. It presents a methodology for analyzing an ongoing software development process and establishing a rat

Managing the Software Process
✍ Watts S. Humphrey πŸ“‚ Library πŸ“… 1990 πŸ› Publishing Company 🌐 English

The author, drawing on years of experience at IBM and the SEI, provides here practical guidance for improving the software development and maintenance process. He focuses on understanding and managing the software process because this is where he feels organizations now encounter the most serious pr

Management, Labour Process and Software
✍ Rowena Barrett πŸ“‚ Library πŸ“… 2005 πŸ› Routledge 🌐 English

This revealing book is about software development, the developers themselves, and how their work is organized and managed. The latest original research from Australia, Europe, and the UK is used to examine the differences between the image and reality of work in this industry. Chapters also cover is

Process-Based Software Project Managemen
✍ F. Alan Goodman πŸ“‚ Library πŸ“… 2006 πŸ› Auerbach Publications, CRC Press 🌐 English

Not connecting software project management (SPM) to actual, real-world development processes can lead to a complete divorcing of SPM to software engineering that can undermine any successful software project. By explaining how a layered process architectural model improves operational efficiency, <b