Software Process Definition and Management
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
- PDF / 7,579,997 Bytes
- 254 Pages / 439.37 x 666.142 pts Page_size
- 3 Downloads / 172 Views
Editorial Board W. Rance Cleaveland II Reinhold E. Achatz Helmut Krcmar
.
J€ urgen M€ unch • Ove Armbrust • Martin Kowalczyk • Martı´n Soto
Software Process Definition and Management
Ju¨rgen Mu¨nch University of Helsinki Department of Computer Science Helsinki Finland
Ove Armbrust Alpine Electronics Research of America Torrance, CA USA
Martin Kowalczyk Fraunhofer IESE Kaiserslautern Germany
Martı´n Soto eleven GmbH Berlin Germany
ISBN 978-3-642-24290-8 ISBN 978-3-642-24291-5 (eBook) DOI 10.1007/978-3-642-24291-5 Springer Heidelberg New York Dordrecht London Library of Congress Control Number: 2012936487 ACM Codes: D.2, K.6 # Springer-Verlag Berlin Heidelberg 2012 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein. Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)
Foreword
One of the most significant contributions of the agile methods community has been to put to rest the mistaken belief that there could be a one-size-fits-all software process by which all software systems could be developed. The agilists not only produced a family of process models that were clearly different from the traditional single-pass, sequential, requirements-first models, and their attendant baggage, but also they provided evidence of their successful application, often in situations in which the traditional approaches had failed
Data Loading...
