Software Engineering Risk Management (Practitioners) [Hardcover]

Dale Walter Karolak (Author)

Book Description

Publication Date: November 27, 1995 | ISBN-10: 0818671947 | ISBN-13: 978-0818671944 | Edition: 1

This book is designed for those who manage software development projects. It explores software and risk management both from a technology and a business perspective. Issues regarding costs, schedules, technical performance, and strategies for software development are discussed.

The author approaches software development from a just-in-time viewpoint and details strategies for implementing and planning development plans in a cost-effective and timely manner. The book presents a significant discussion of software risk issues pertaining to organizational costs and schedules. It also identifies metrics and presents several models for measuring and predicting risk.

The information featured in the book is supported by actual proven case studies derived from the author's experience. The text addresses many different concepts, strategies, and tools that could make the management of your next software development project less of a guess and more predictable.

Also available is the SERIM Software Tool. This interactive, easy-to-use Windows application gives you an automated way to determine the risks of your software project. The product is based on the SERIM model detailed in this bestselling book.

Editorial Reviews

From the Back Cover

This book explores software and risk management both from a technology and a business perspective. Dale Karolak approaches software development from a just-in-time viewpoint and presents strategies that you can use to implement and plan software projects in a cost-effective and timely manner. This book discusses vital issues and, in particular, their costs, schedules, technical performance, and risk-based approaches for software development. It is especially designed to assist those who manage software development projects.

The book provides

• A significant discussion of software risk issues pertaining to technical performance, costs, and schedules
• Metrics and several models for measuring and predicting risk
• Information supported by actual proven case studies derived from the author's experience
• Many different concepts, strategies, and tools that can make the management of your next software development project less of a guess and more predictable

About the Author

Karl Karolak is currently a Design Engineering Manager at TRW Automotive Electronics Group. He received the BS degree in computer science from Central Michigan University, the PhD degree in software engineering from Union Institute in Cincinnati, Ohio, and the MBA degree from the University of Phoenix. His research interests include software engineering management, software process development, software architectures, and software verification/validation.
Karolak is a member of the IEEE Computer Society and the ACM. He has published papers for IEEE, ACM, SERF, and NSIA and has a patent pending on a Software Architecture for a Communications (Network) Management System.

Product Details

• Hardcover: 182 pages
• Publisher: Wiley-IEEE Computer Society Pr; 1 edition (November 27, 1995)
• Language: English
• ISBN-10: 0818671947
• ISBN-13: 978-0818671944
• Product Dimensions: 9.3 x 6.2 x 0.6 inches
• Shipping Weight: 1 pounds (View shipping rates and policies)
• Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
• Amazon Best Sellers Rank: #2,668,378 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

8 of 9 people found the following review helpful:

5.0 out of 5 stars Unique, effective approach to risk management, July 6, 2001

By 

Mike Tarrani "www.tarrani.com" (Deltona, FL USA) - See all my reviews
(COMMUNITY FORUM 04)    (REAL NAME)   

This review is from: Software Engineering Risk Management (Practitioners) (Hardcover)

This book contains 170 information-packed pages that describe a comprehensive and effective approach to managing software development risks.

The approach is based on a just-in-time (JIT) strategy. Key elements of this strategy include (1) strategic planning and operational planning, the former is focused on product-line based software and makes a distinction between the software under development being the product itself or a part of the product, and the latter is focused on project planning and controls; (2) early risk identification, and (3) parallel development. When this book was first published parallel development was a complex goal; however, with component-based development strategies the approach is ideal. Perhaps the author was ahead of his time.

Some of the best chapters in this book are: Chapter 4 - provides excellent insights and advice on managing the strategic and operational elements of the JIT strategy, Chapter 5 - comprehensive list of software risk elements and Chapter 7 - another comprehensive list that covers risk metrics.

Chapter 8 describes the JIT method as it applies to each phase in the software development life cycle. This chapter contains valuable tables that can be used as checklists in your own project, and is full of useful information that can be applied to project risk management regardless of whether or not you implement the JIT approach described in this book. Chapter 9 shows how to apply the JIT approach to a project. This chapter is short is really a brief summary of the software engineering risk model (SERIM) from which the JIT approach was derived. Chapter 10 is a collection of JIT examples that can easily be recast into patterns. I especially like the way these examples clarify the information in preceding nine chapters. I recommend that you refer to this chapter as you read through the book because there will almost certainly be an example that will illustrate any fuzzy areas.

This is one of my favorite books on risk management in general and software risk management in particular. The information and approach are not limited to software engineering, although the book was obviously written for that technical domain. I have borrowed techniques from this book and have successfully applied them in other kinds of projects, as I am sure you will. I give it 5 stars and a strong recommendation.