Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
More Buying Choices
Have one to sell? Sell yours here
The Project Manager's Guide to Software Engineering's Best Practices
 
 

The Project Manager's Guide to Software Engineering's Best Practices [Paperback]

Mark Christensen , Richard H. Thayer
5.0 out of 5 stars  See all reviews (1 customer review)
List Price: CDN$ 131.99
Price: CDN$ 101.75 & this item ships for FREE with Super Saver Shipping. Details
You Save: CDN$ 30.24 (23%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Usually ships within 1 to 3 weeks.
Ships from and sold by Amazon.ca. Gift-wrap available.

Product Details


Product Description

Product Description

Since the earliest days of the computer industry, managing a software project has been a complex and demanding activity. While the technical content of software products and the technical methods used to build them have changed over time, the fundamental issues that determine the success or failure of software projects have remain fairly constant. That is, the same fundamental management mistakes continue to be made. To cite a few examples; requirements are unclear at the beginning of projects and are not managed during the project, the product is not tested adequately, schedules are misestimated or not tracked in sufficient detail. The contents of this book, together with the underlying IEEE Standards, are dedicated to helping the reader in their work: The continuing quest to produce quality software products in a predictable manner.

This book, containing all original material, is based on the proposition that the IEEE Software Engineering Standards capture many of the fundamental 'best practices' of software project management. It is written to assist the reader in applying those standards to their projects and company. To meet this goal, the authors discuss and elaborate the standards that bear on the three key management areas of: Software systems engineering, Processes for developing software products, Planning and control of software project activities.

The body of the book is correspondingly organized into three parts. Software Systems Engineering, which argues that software development projects are most successful when developed using a systems level viewpoint. Process Management and Control, which describes the key activities needed to define, support, and manage a project's software development processes. Project Planning and Management completes the book, integrating the elements of cost and schedule estimation and control, risk management, and the role metrics play in performing those tasks.

From the Back Cover

Since the earliest days of the computer industry, managing a software project has been a complex and demanding activity. While the technical content of software products and the technical methods used to build them have changed over time, the fundamental issues that determine the success or failure of software project have remained fairly constant. The contents of this book, together with the underlying IEEE Standards, are dedicated to helping the reader in their ongoing task to produce quality software products in a conventional manner.

This book, containing all original material, is built on the proposition that the IEEE Software Engineering Standards capture many of the fundamental "best practices" of software project management. It will assist the reader in successfully applying those standards to their projects and their organization. To meet this goal, the authors discuss and elaborate on the standards covering these three key management areas:

  • Software systems engineering
  • Process for developing software products
  • Planning and control of software project activities

The body of the text is correspondingly organized into three important parts: Software Systems Engineering; Process Management and Control; and Project Planning and Management.


Inside This Book (Learn More)
First Sentence
This chapter describes the application of systems engineering principles to the development of a computer software system. Read the first page
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Tag this product

 (What's this?)
Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items.
Your tags: Add your first tag
 

 

Customer Reviews

1 Review
5 star:
 (1)
4 star:    (0)
3 star:    (0)
2 star:    (0)
1 star:    (0)
 
 
 
 
 
Average Customer Review
5.0 out of 5 stars (1 customer review)
 
 
 
 
Share your thoughts with other customers:
Most helpful customer reviews

5.0 out of 5 stars Lives up to its title - best practices and sound approach, Aug 1 2002
By 
Mike Tarrani "Jazz Drummer" (Deltona, FL USA) - See all my reviews
(REAL NAME)   
This review is from: The Project Manager's Guide to Software Engineering's Best Practices (Paperback)
This is a completely updated book that departs from the earlier "Software Engineering Project Management" by Thayer (1997) in that it's more anchored in software engineering standards than in project management. To be sure, this book is about project management, but takes a more holistic view.

The best practices, predicated upon the view that the common thread is software engineering standards and practices, are presented in three sections:

(1)Software Systems Engineering - a critical success factor for any software project.
(2) Process Management and Control - what must be done in order to effectively scope, support and manage the development process itself.
(3) Project Planning and Management - standard fare, including estimation, risk management, and metrics.

Each of these sections contain papers that discuss aspects of the topic area, which include: Software Systems Engineering, Concept of Operations, Software Requirements Specification, Software User Documentation, Software Verification and Validation, Software Life Cycle Process Management, Software Process Improvement, Software Reviews, Software Configuration Management, Software Quality Assurance, Maintenance, Software Engineering Project Management, Software Cost and Schedule, Software Risk Management and Software Metrics.

Personally I completely agree with the book's approach (standards and processes are critical to successful development projects). However, even if taken as individual papers, each chapter presents excellent advice and insights that will benefit not only project managers, but all members of a development team. If you do agree with me that the overall approach is valid you will also find " SWEBOK: Guide to the Software Engineering Body of Knowledge" by Alain Abran(ISBN 0769510000) will complement this book by providing more foundation material about key areas of the software engineering process.

Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 5.0 out of 5 stars (1 customer review)

13 of 13 people found the following review helpful
5.0 out of 5 stars Lives up to its title - best practices and sound approach, Aug 1 2002
By Mike Tarrani "Jazz Drummer" - Published on Amazon.com
This review is from: The Project Manager's Guide to Software Engineering's Best Practices (Paperback)
This is a completely updated book that departs from the earlier "Software Engineering Project Management" by Thayer (1997) in that it's more anchored in software engineering standards than in project management. To be sure, this book is about project management, but takes a more holistic view.

The best practices, predicated upon the view that the common thread is software engineering standards and practices, are presented in three sections:

(1)Software Systems Engineering - a critical success factor for any software project.
(2) Process Management and Control - what must be done in order to effectively scope, support and manage the development process itself.
(3) Project Planning and Management - standard fare, including estimation, risk management, and metrics.

Each of these sections contain papers that discuss aspects of the topic area, which include: Software Systems Engineering, Concept of Operations, Software Requirements Specification, Software User Documentation, Software Verification and Validation, Software Life Cycle Process Management, Software Process Improvement, Software Reviews, Software Configuration Management, Software Quality Assurance, Maintenance, Software Engineering Project Management, Software Cost and Schedule, Software Risk Management and Software Metrics.

Personally I completely agree with the book's approach (standards and processes are critical to successful development projects). However, even if taken as individual papers, each chapter presents excellent advice and insights that will benefit not only project managers, but all members of a development team. If you do agree with me that the overall approach is valid you will also find " SWEBOK: Guide to the Software Engineering Body of Knowledge" by Alain Abran(ISBN 0769510000) will complement this book by providing more foundation material about key areas of the software engineering process.

 Go to Amazon.com to see the review  5.0 out of 5 stars 
 
 
Only search this product's reviews



Listmania!

Create a Listmania! list

Look for similar items by category


Look for similar items by subject


Feedback


Amazon.ca Privacy Statement Amazon.ca Shipping Information Amazon.ca Returns & Exchanges