Muutke küpsiste eelistusi

Software Maintenance Management: Evaluation and Continuous Improvement [Pehme köide]

3.00/5 (8 hinnangut Goodreads-ist)
(Université du Québec), (Université du Québec)
  • Formaat: Paperback / softback, 336 pages, kõrgus x laius x paksus: 236x155x25 mm, kaal: 567 g, Drawings: 10 B&W, 0 Color; Tables: 23 B&W, 0 Color; Graphs: 10 B&W, 0 Color
  • Sari: Practitioners
  • Ilmumisaeg: 20-May-2008
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 0470147075
  • ISBN-13: 9780470147078
Teised raamatud teemal:
  • Pehme köide
  • Hind: 120,63 €*
  • * saadame teile pakkumise kasutatud raamatule, mille hind võib erineda kodulehel olevast hinnast
  • See raamat on trükist otsas, kuid me saadame teile pakkumise kasutatud raamatule.
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Lisa soovinimekirja
  • Raamatukogudele
Software Maintenance Management: Evaluation and Continuous ImprovementSuurem pilt
  • Formaat: Paperback / softback, 336 pages, kõrgus x laius x paksus: 236x155x25 mm, kaal: 567 g, Drawings: 10 B&W, 0 Color; Tables: 23 B&W, 0 Color; Graphs: 10 B&W, 0 Color
  • Sari: Practitioners
  • Ilmumisaeg: 20-May-2008
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 0470147075
  • ISBN-13: 9780470147078
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780470147078.html
Märksõnad:
This book explores the domain of software maintenance management and provides road maps for improving software maintenance organizations. It describes full maintenance maturity models organized by levels 1, 2, and 3, which allow for benchmarking and continuous improvement paths. Goals for each key practice area are also provided, and the model presented is fully aligned with the architecture and framework of software development maturity models of CMMI and ISO 15504. It is complete with case studies, figures, tables, and graphs.

Arvustused

"The book is a fresh approach to an often otherwise dull and boring subject area." (Ubiquity, June 10-16, 2008)

Foreword xiii
Thomas Pigoski
Foreword xv
Ned Chapin
Preface xvii
Maintenance Issues and Related Management Approaches
1(40)
Introduction
1(1)
Issues in Software Maintenance
2(6)
Users' Perceptions of Software Maintenance Issues
2(2)
Maintainers' Perceptions of Software Maintenance Issues
4(4)
Software Maintenance Body of Knowledge
8(2)
Software Maintenance Definition
10(1)
Differences Between Operations, Development, and Maintenance
10(5)
Which Organization is Responsible for Software Maintenance?
15(1)
Software Maintenance Standards
15(6)
Software Maintenance Process and Activities
21(2)
Software Maintenance Categories
23(1)
Maintenance Measurement
23(6)
Maintenance Process Measurement
23(5)
Software Product Measurement
28(1)
Service Measurement
29(6)
Internal Service-Level Agreement
30(2)
Maintenance Service Contracts---External Service Agreement
32(2)
Outsourcing Agreements
34(1)
Software Maintenance Benchmarking
35(2)
Summary
37(1)
Exercises
38(3)
Maturity Models in Software Engineering
41(28)
Introduction
41(1)
Overview of Basic Concepts (Process and Maturity)
42(3)
Does CMMi Cover Software Maintenance Adequately?
45(1)
Difference Between Maturity Model, Quality Standards, and Evaluation Method
46(6)
Chosing Between ISO9001 and CMMi
46(2)
The Evaluation Method
48(3)
Evaluation Types
51(1)
How is a Maturity Model Designed?
52(3)
The Trillium Design Process
52(2)
ISO 15504 Design Process
54(1)
CMMi for Services Design Process
55(1)
Summary
55(1)
Initial Validation of a Maturity Model
55(2)
IT Service CMM Model---Initial Validation Approach
56(1)
CM3® Model---Initial Validation Approach
56(1)
ISO 15504 Model---Initial Validation Approach
57(1)
CMMI for Services Model---Initial Validation Approach
57(1)
Maturity Model Validation, Conclusion
57(1)
What is the Typical Architecture of Maturity Models?
57(5)
CMMi Model Architecture
58(2)
The ISO 15504 (SPICE) Model
60(2)
An Inventory of Software Engineering Maturity Models
62(3)
Summary
65(1)
Exercices
66(3)
Foundations of the S3m® Process Model
69(14)
Introduction
69(2)
Context of Software Maintenance
71(2)
Proposed Classification of Software Maintenance Processes
73(3)
Software Maintenance Operational Processes
75(1)
Software Maintenance Support Processes
76(1)
Software Maintenance Organizational Processes
76(1)
Identification of Process Domains and Key Process Areas in Software Maintenance
76(5)
Summary
81(1)
Exercises
81(2)
Process Management Domain
83(12)
Overview
83(3)
Maintenance Process Focus KPA
86(1)
Goals of this KPA
86(1)
Links with Other KPAs
86(1)
Expected Results of this KPA
87(1)
Maintenance Processes/Services Definition KPA
87(1)
Goals of this KPA
87(1)
Links with Other KPAs
88(1)
Expected Results from this KPA
88(1)
Maintenance Training KPA
88(2)
Goals of this KPA
89(1)
Links with Other KPAs
89(1)
Expected Results from this KPA
89(1)
Maintenance Process Performance KPA
90(1)
Goals of this KPA
90(1)
Links with Other KPAs
90(1)
Expected Results from this KPA
91(1)
Maintenance Innovation and Deployment KPA
91(2)
Goals of this KPA
91(1)
Links with Other KPAs
92(1)
Expected Results from this KPA
92(1)
Summary
93(1)
Exercises
93(2)
Event/Request Management Domain
95(12)
Overview
95(2)
Event/Request Management KPA
97(1)
Goals of this KPA
97(1)
Links with Other KPAs
98(1)
Expected Results from this KPA
98(1)
Maintenance Planning KPA
98(2)
Goals of this KPA
99(1)
Links with Other KPAs
99(1)
Expected Results from this KPA
100(1)
Request/Software Monitoring and Control KPA
100(1)
Goals of this KPA
100(1)
Links with Other KPAs
101(1)
Expected Results from this KPA
101(1)
SLA and Supplier Agreement Management KPA
101(2)
Goals of this KPA
102(1)
Links with Other KPAs
102(1)
Expected Results from this KPA
102(1)
Summary
103(1)
Exercises
103(4)
Evolution Engineering Domain
107(10)
Overview
107(2)
Predelivery and Transition Services KPA
109(2)
Goals of this KPA
109(1)
Links with Other KPAs
110(1)
Expected Results from this KPA
110(1)
Operational Support Services KPA
111(1)
Goals of this KPA
111(1)
Links with Other KPAs
111(1)
Expected Results from this KPA
111(1)
Software Evolution and Correction Services KPA
112(1)
Goals of this KPA
112(1)
Links with Other KPAs
113(1)
Expected Results of this KPA
113(1)
Verification and Validation KPA
113(2)
Goals of this KPA
114(1)
Links with Other KPAs
114(1)
Expected Results of this KPA
114(1)
Summary
115(1)
Exercises
115(2)
Support for the Evolution Engineering Domain
117(12)
Overview
117(3)
Configuration and Version Management KPA
120(2)
Goals of this KPA
121(1)
Links with Other KPAs
121(1)
Expected Results of this KPA
122(1)
Process, Service, and Software Quality Assurance KPA
122(1)
Goals of this KPA
122(1)
Links with Other KPAs
123(1)
Expected Results of this KPA
123(1)
Maintenance Measurement and Analysis KPA
123(1)
Goals of this KPA
124(1)
Links with Other KPAs
124(1)
Expected Results of this KPA
124(1)
Causal Analysis and Problem Resolution KPA
124(1)
Goals of this KPA
125(1)
Links with Other KPAs
125(1)
Expected Results of this KPA
125(1)
Software Rejuvenation, Migration, and Retirement KPA
125(2)
Goals of this KPA
126(1)
Links with Other KPAs
126(1)
Expected Results of this KPA
126(1)
Summary
127(1)
Exercises
127(2)
Exemplary Practices---Process Management
129(20)
Maintenance Process Focus---Detailed Exemplary Practices
130(5)
Level 0
130(1)
Level 1
130(1)
Level 2
131(4)
Maintenance Process/Service Definition---Detailed Exemplary Practices
135(3)
Level 0
135(1)
Level 1
136(1)
Level 2
136(2)
Maintenance Training---Detailed Exemplary Practices
138(6)
Level 0
138(1)
Level 1
138(1)
Level 2
139(5)
Maintenance Process Performance---Detailed Exemplary Practices
144(2)
Level 0
144(1)
Level 1
144(1)
Level 2
145(1)
Maintenance Innovation and Deployment---Detailed Exemplary Practices
146(3)
Level 0
146(1)
Level 1
147(1)
Level 2
147(2)
Exemplary Practices---Event/Request Management Domain
149(20)
Event/Request Management KPA---Detailed Exemplary Practices
150(1)
Level 0
150(1)
Level 1
150(1)
Level 2
150(1)
Maintenance Planning KPA---Detailed Exemplary Practices
151(8)
Level 0
151(1)
Level 1
151(1)
Level 2
152(7)
Requests/Software Monitoring and Control KPA---Detailed Exemplary Practices
159(3)
Level 0
159(1)
Level 1
159(1)
Level 2
159(3)
SLA and Supplier Agreements Management KPA---Detailed Exemplary Practices
162(7)
Level 0
162(1)
Level 1
162(1)
Level 2
163(6)
Exemplary Practices---Evolution Engineering Domain
169(18)
Predelivery and Transition to Software Maintenance KPA---Detailed Exemplary Practices
170(5)
Level 0
170(1)
Level 1
170(1)
Level 2
170(5)
Operational Support Services KPA---Detailed Exemplary Practices
175(3)
Level 0
175(1)
Level 1
175(1)
Level 2
176(2)
Software Evolution and Correction Services KPA---Detailed Exemplary Practices
178(4)
Level 0
178(1)
Level 1
178(1)
Level 2
179(3)
Verification and Validation KPA---Detailed Exemplary Practices
182(5)
Level 0
182(1)
Level 1
182(1)
Level 2
183(4)
Exemplary Practices---Support to Evolution Domain
187(16)
Configuration and Change Management---Detailed Exemplary Practices
188(2)
Level 0
188(1)
Level 1
188(1)
Level 2
189(1)
Process, Service, and Software Quality Assurance---Detailed Exemplary Practices
190(3)
Level 0
191(1)
Level 1
191(1)
Level 2
191(2)
Maintenance Measurement and Analysis---Detailed Exemplary Practices
193(2)
Level 0
193(1)
Level 1
194(1)
Level 2
194(1)
Causal Analysis and Problem Resolution---Detailed Exemplary Practices
195(2)
Level 0
195(1)
Level 1
195(1)
Level 2
196(1)
Software Rejuvenation, Migration, and Retirement---Detailed Exemplary Practices
197(6)
Level 0
197(1)
Level 1
197(1)
Level 2
198(5)
Assessment Process, Assessment Tool, and Case Studies of the Use of S3m®
203(20)
Evaluation Process and Support Tools
203(3)
Example of Evaluation Results
206(4)
Four Case Studies Using S3m®
210(11)
Contributions to the Definition of Software Maintenance
210(1)
Contributions to the Definition of the Service Level Agreement (SLA)
210(1)
Contributions to Software Product Quality Assessment During Predelivery and Transition
211(2)
Contributions to the Improvement of a Very Small Maintenance Function
213(8)
Summary
221(2)
Summary
223(4)
The Maintenance Issues Revisited
224(1)
Questions 1 and 2---Is Maintenance a Specific Domain of Software Engineering?
224(1)
Question 3---Does the CMMi Adequately Address Software Maintenance?
225(1)
Question 4---What Would the Architecture of a Software Maintenance Maturity Model Look Like?
225(1)
Question 5---How Can Such a Model be Used in Practice?
225(1)
Lessons Learned and Contributions
225(1)
Further Reading
226(1)
Appendix A Maintenance Standards Models and Enhancement Proposal
227(4)
Software Maintenance Standards
227(4)
Appendix B Term Assignment for Students
231(4)
Appendix C Acronyms and Glossary
235(50)
References 285(16)
Index 301(12)
About the Authors 313
Alain April, PhD, is Professor of Software Engineering at Université du Québec (Canada). His research interests include software maintenance, software quality assurance, and multimedia databases. Dr. April has worked in the telecommunications industry for more than twenty years, has contributed to the internal measurement of software of ISO 9126-3, and is an Editor of The Guide to Software Engineering Body of Knowledge (SWEBOK) chapters on software maintenance and software quality. Alain Abran, PhD, is Professor and the Director of the Software Engineering Research Laboratory at Université du Québec (Canada). Dr. Abran is the Co-Executive Editor of the SWEBOK project. He has been actively involved in software engineering standardization as the International Secretary for ISO/IEC JTC SC7 Software and System Engineering and as co-manager for the Common Software Measurement International Consortium (COSMIC). Dr. Abran's research interests include software productivity and estimation models, software engineering foundations, software quality, software functional size measurement, software risk management, and software maintenance management.