Trustworthy Systems Through Quantitative Software Engineering / Edition 1

Hardcover (Print)
Buy New
Buy New from
Used and New from Other Sellers
Used and New from Other Sellers
from $31.15
Usually ships in 1-2 business days
(Save 79%)
Other sellers (Hardcover)
  • All (5) from $31.15   
  • New (2) from $127.28   
  • Used (3) from $31.15   


Trustworthy Systems Through Quantitative Software Engineering proposes a novel, reliability-driven software engineering approach, and discusses human factors in software engineering and how these affect team dynamics. This practical approach gives software engineering students and professionals a solid foundation in problem analysis, allowing them to meet customers' changing needs by tailoring their projects to meet specific challenges, and complete projects on schedule and within budget.
Read More Show Less

Editorial Reviews

From the Publisher
"In a study, the book was found to be successful at significantly increasing the students' willingness and competency in using good software engineering processes." (Computing, May 10, 2006)

"…the book is an excellent and very readable guide to the development of reliable software, augmented with humor, case studies, useful tidbits…highly recommended for all software engineers." (CHOICE, March 2006)

Read More Show Less

Product Details

  • ISBN-13: 9780471696919
  • Publisher: Wiley
  • Publication date: 10/5/2005
  • Series: Quantitative Software Engineering Series , #1
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 464
  • Product dimensions: 6.44 (w) x 9.35 (h) x 1.10 (d)

Meet the Author

LAWRENCE BERNSTEIN is the Series Editor for the Quantitative Software Engineering Series, published by Wiley. Professor Bernstein is currently Industry Research Professor at the Stevens Institute of Technology. He previously pursued a distinguished executive career at Bell Laboratories. He is a Fellow of IEEE and ACM.

C. M. YUHAS is a freelance writer who has published articles on network management in the IEEE Journal on Selected Areas in Communication and IEEE Network. She has a BA in English from Douglass College and an MA in communications from New York University.

Read More Show Less

Table of Contents

1 Think like an engineer - especially for software 3
2 People, product, process, project - the big four 39
3 Software requirements 75
4 Prototyping 107
5 Architecture 137
6 Estimation, planning, and investment 173
7 Design for trustworthiness 223
8 Identifying and managing risk 277
9 Human factors in software engineering 309
10 Implementation details 344
11 Testing and configuration management 372
12 The final project : by students, for students 404
Read More Show Less

Customer Reviews

Average Rating 5
( 2 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 2 Customer Reviews
  • Anonymous

    Posted February 27, 2006

    a wonderful text/reference book

    This book is about to deliver trustworthy systems through quantitative software engineering methodologies, which is unfortunately rare to be implemented well in the real world. I believe Professor Bernstein has placed 'trust' as the foremost aspect of this book is a landmark decision and it precisely describes the ultimate goal of software development--to make a system that is trusted by customers. As far as I can tell, all aspects and concerns in software development have been covered and provided with solutions and even real-life examples. The concepts of simplification, trustworthiness, risk assessment, and architecture are stressed. It is fun to read. Each aspect is clearly stated with background, objectives and how to achieve or avoid it. This book is well illustrated with graphs, charts and examples. Quantitative aspects are always easy to be mentioned but hard to be understood and implemented. Following this book, either developers or managers can analyze the project methodically throughout the full life-cycle of the software development to help to improve the system and project performance, especially, as emphasized in this book, at the planning and designing phase. This book is as well designed as it is well written. If there is anything that I think the author missed a bit, it would be the 'Magic Numbers', which is a writing trick for making important things stand out, by giving it a 'name' and putting it in a box. This is effective but when the quantity of 'Magic Numbers' gets accumulated, it makes it hard to find the ones that reader needs. However, this is only a minor issue. This book is written as a textbook. It is well suited for senior design semesters, as being used at Stevens Institute of Technology, for computer major students to gain experiences with teamwork skills, learn to tradeoff and communicate with other team members, learn to face conflicts and search for solutions. Most importantly, learn to find the good software engineering practice for their own project through quantitative analysis, which is provided in this book. It is also good for experienced software professionals and managers who's trying to understand software engineering technologies. I would very much recommend this book to everyone who is interested in Software Engineering.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted November 4, 2005

    An Instant Classic

    This book is a must read for every professional having responsibility for some aspect of a software development project. It presents the tools and techniques necessary to develop software systems on time and within budget, using quantitative, well-defined techniques. These quantitative techniques are clearly described in the text. The information and insight that the authors ¿Magic Numbers¿ give us is worth the price of the book! ¿Magic Numbers¿ are rules of thumb (developed from analysis of many past software projects) that give numerical insight to many phases of the software development project. An additional important element is the discussion of ethical behavior in a variety of situations. The case studies presented serve as real life examples of the pressures and problems that can plague a software project. The several projects discussed with which I have first hand knowledge are perceptively and accurately portrayed. The writing is clear, to the point and engaging. This is the book I wish I had at the beginning of my career in software development. I feel it belongs in the library of all software professionals and students alike. I love this book!

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 2 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)