Muutke küpsiste eelistusi

E-raamat: Software Engineering Quality Practices [Taylor & Francis e-raamat]

(Jet Propulsion Laboratory, Pasadena, California, USA)
  • Formaat: 280 pages, 14 Tables, black and white; 18 Illustrations, black and white
  • Sari: Applied Software Engineering Series
  • Ilmumisaeg: 01-Nov-2005
  • Kirjastus: Auerbach
  • ISBN-13: 9780429118975
Teised raamatud teemal:
  • Taylor & Francis e-raamat
  • Hind: 166,18 €*
  • * hind, mis tagab piiramatu üheaegsete kasutajate arvuga ligipääsu piiramatuks ajaks
  • Tavahind: 237,40 €
  • Säästad 30%
  • Formaat: 280 pages, 14 Tables, black and white; 18 Illustrations, black and white
  • Sari: Applied Software Engineering Series
  • Ilmumisaeg: 01-Nov-2005
  • Kirjastus: Auerbach
  • ISBN-13: 9780429118975
Teised raamatud teemal:
The integrated software development approach presented in this book outlines practices for hiring and retaining the best people, and recommends efficient procedures for them to use. Separate chapters describe guidelines for developing configuration management, requirements engineering, design, project management, and measurement procedures that support an iterative software development life cycle. Topics include providing a suitable workplace, controlling changes to software artifacts, reducing large system into modules, minimizing the use of "goto" statements, reusability, and defect estimation techniques. Distributed by CRC. Annotation ©2006 Book News, Inc., Portland, OR (booknews.com)

Learn how to attract and keep successful software professionals
Software Engineering Quality Practices describes how software engineers and the managers that supervise them can develop quality software in an effective, efficient, and professional manner. This volume conveys practical advice quickly and clearly while avoiding the dogma that surrounds the software profession. It concentrates on what the real requirements of a system are, what constitutes an appropriate solution, and how you can ensure that the realized solution fulfills the desired qualities of relevant stakeholders. The book also discusses how successful organizations attract and keep people who are capable of building high-quality systems.

The author succinctly describes the nature and fundamental principles of design and incorporates them into an architectural framework, enabling you to apply the framework to the development of quality software for most applications. The text also analyzes engineering requirements, identifies poor requirements, and demonstrates how bad requirements can be transformed via several important quality practices.
Preface xvii
Acknowledgments xxi
Introduction
1(20)
Qualities
2(5)
Characteristic Qualities of Products
3(3)
Characteristic Process Qualities
6(1)
Quality Drivers
7(4)
Common Approaches to Developing Quality Software
11(2)
Software Automation
11(1)
Software Modeling Methodologies
11(1)
Software Process Improvement
12(1)
Software Reuse
13(1)
An Integrated Approach for Developing Quality Software
13(3)
Summary
16(5)
References
17(4)
Organizational Change Management
21(30)
Practices for Management Personnel to Follow
22(11)
Practices for Software Engineering Process Groups to Follow
33(6)
A Procedure for Making Change Happen
39(5)
Summary
44(7)
References
46(5)
Personnel Management
51(22)
Practices for Staffing an Organization
53(9)
Practices for Developing Individual Skills
62(1)
Practices for Rewarding Performance
63(1)
Practices for Providing a Suitable Workplace
64(3)
A Procedure for Hiring and Retaining Good People
67(2)
Summary
69(4)
References
70(3)
Project Management
73(16)
Practices for Planning a Project
73(5)
Practices for Managing a Project
78(3)
A Procedure for Planning a Project
81(5)
Summary
86(3)
References
86(3)
Configuration Management
89(14)
Practices for Managing Versions of Software Artifacts
90(2)
Practices for Controlling Changes to Software Artifacts
92(1)
Practices for Building Software Systems
93(1)
Practices for Releasing Software Systems
94(1)
Practices for Maintaining the Integrity of Software Artifacts
95(1)
A Procedure for Creating a Configuration Management System
96(2)
A Baseline Procedure for Managing Software Configurations
98(3)
Summary
101(2)
References
101(2)
Requirements Engineering
103(36)
Practices for Eliciting Requirements
105(10)
Practices for Analyzing the Problem Domain and Application Needs
115(5)
Practices for Specifying Requirements
120(7)
Practices for Validating Requirements
127(4)
Practices for Managing the Definition of Requirements
131(1)
A Procedure for Engineering Requirements
132(3)
Summary
135(4)
References
136(3)
Design
139(30)
Fundamental Principles of Design
141(5)
Separation of Concerns
141(2)
Coupling and Cohesion
143(2)
Conceptual Modeling
145(1)
Practices for Designing Architectures
146(8)
Practices for Adding Detailed Design Information
154(3)
Practices Affecting the Design Process
157(3)
A Unified Framework for System Architectures
160(3)
A Procedure for Designing Software
163(2)
Summary
165(4)
References
165(4)
Programming
169(8)
Practices for General-Purpose Programming
169(7)
Summary
176(1)
References
176(1)
Verification
177(22)
Inspections
178(3)
Practices for Inspecting Artifacts
179(1)
A Procedure for Inspecting an Artifact
180(1)
Testing
181(9)
Practices for Testing Code
181(6)
Testing Heuristics
187(1)
A Procedure for Testing a System
188(2)
A Procedure for Planning the Verification Procedure
190(3)
A Baseline Procedure for Verifying Software Systems
193(3)
Summary
196(3)
References
196(3)
Remaining Quality Practices and Issues
199(14)
Practices for Writing Useful User Documentation
199(4)
Reusability
203(3)
The Relationship between Abstraction and Reuse
204(1)
Approaches to Reuse
205(1)
Defect Estimation Techniques
206(3)
Historical Techniques
207(1)
Halstead's Technique
207(1)
Detection Profile Method
208(1)
Capture-Recapture Techniques
208(1)
Summary
209(4)
References
210(3)
Competing Approaches
213(24)
Extreme Programming
214(6)
The Rational Unified Process
220(5)
Cleanroom Software Engineering
225(4)
Capability Maturity Model-Integrated
229(4)
Summary
233(4)
References
235(2)
Summary
237(16)
Software Development
237(9)
Comparison to Competing Approaches
246(2)
Early Thoughts of the Software Pioneers
248(2)
My Final Thoughts
250(3)
References
251(2)
Index 253


Ronald Kirk Kandt