A benchmark text on software development and quantitative software
engineering
"We all trust software. All too frequently, this trust is
misplaced. Larry Bernstein has created and applied quantitative
techniques to develop trustworthy software systems. He and C. M.
Yuhas have organized this quantitative experience into a book of
great value to make software trustworthy for all of us."
-Barry Boehm
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.
Specifically, it helps developers identify customer requirements,
develop software designs, manage a software development team, and
evaluate software products to customer specifications. Students
learn "magic numbers of software engineering," rules of thumb that
show how to simplify architecture, design, and
implementation.
Case histories and exercises clearly present successful software
engineers' experiences and illustrate potential problems, results,
and trade-offs. Also featuring an accompanying Web site with
additional and related material, Trustworthy Systems Through
Quantitative Software Engineering is a hands-on, project-oriented
resource for upper-level software and computer science students,
engineers, professional developers, managers, and professionals
involved in software engineering projects.
An Instructor's Manual presenting detailed solutions to all the
problems in the book is available from the Wiley editorial
department.
An Instructor Support FTP site is also available.
Autorentext
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.
Klappentext
A benchmark text on software development and quantitative software engineering
"We all trust software. All too frequently, this trust is misplaced. Larry Bernstein has created and applied quantitative techniques to develop trustworthy software systems. He and C. M. Yuhas have organized this quantitative experience into a book of great value to make software trustworthy for all of us."
—Barry Boehm
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.
Specifically, it helps developers identify customer requirements, develop software designs, manage a software development team, and evaluate software products to customer specifications. Students learn "magic numbers of software engineering," rules of thumb that show how to simplify architecture, design, and implementation.
Case histories and exercises clearly present successful software engineers' experiences and illustrate potential problems, results, and trade-offs. Also featuring an accompanying Web site with additional and related material, Trustworthy Systems Through Quantitative Software Engineering is a hands-on, project-oriented resource for upper-level software and computer science students, engineers, professional developers, managers, and professionals involved in software engineering projects.
Zusammenfassung
A benchmark text on software development and quantitative software engineering
"We all trust software. All too frequently, this trust is misplaced. Larry Bernstein has created and applied quantitative techniques to develop trustworthy software systems. He and C. M. Yuhas have organized this quantitative experience into a book of great value to make software trustworthy for all of us."
-Barry Boehm
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.
Specifically, it helps developers identify customer requirements, develop software designs, manage a software development team, and evaluate software products to customer specifications. Students learn "magic numbers of software engineering," rules of thumb that show how to simplify architecture, design, and implementation.
Case histories and exercises clearly present successful software engineers' experiences and illustrate potential problems, results, and trade-offs. Also featuring an accompanying Web site with additional and related material, Trustworthy Systems Through Quantitative Software Engineering is a hands-on, project-oriented resource for upper-level software and computer science students, engineers, professional developers, managers, and professionals involved in software engineering projects.
An Instructor's Manual presenting detailed solutions to all the problems in the book is available from the Wiley editorial department.
An Instructor Support FTP site is also available.
Inhalt
Preface xvii
Acknowledgment xxv
Part 1 Getting Started 1
1. Think Like an EngineerEspecially for Software 3
1.1 Making a Judgment 4
1.2 The Software Engineer's Responsibilities 6
1.3 Ethics 6
1.4 Software Development Processes 11
1.5 Choosing a Process 12
1.5.1 No-Method Code and Fix Approach 15
1.5.2 Waterfall Model 16
1.5.3 Planned Incremental Development Process 18
1.5.4 Spiral Model: Planned Risk Assessment-Driven Process 18
1.5.5 Development Plan Approach 23
1.5.6 Agile Process: an Apparent Oxymoron 25
1.6 Reemergence of Model-Based Software Development 26
1.7 Process Evolution 27
1.8 Organization Structure 29
1.9 Principles of Sound Organizations 31
1.10 Short Projects4 to 6 Weeks 33
1.10.1 Project 1: Automating Library Overdue Book Notices 33
1.10.2 Project 2: Ajax Transporters, Inc. Maintenance Project 34
1.11 Problems 35
2. People, Product, Process, ProjectThe Big Four 39
2.1 People: Cultivate the Guru and Support the Majority 40
2.1.1 How to Recognize a Guru 41
2.1.2 How to Attract a Guru to Your Project 42
2.1.3 How to Keep Your Gurus Working 43
2.1.4 How to Support the Majority 43
2.2 Product: Buy Me! 45
2.2.1 Reliable Software Products 46
2.2.2 Useful Software Products 47
2.2.3 Good User Experience 48
2.3 Process: OK, How Will We Build This?…