Muutke küpsiste eelistusi

Practical Support for Lean Six Sigma Software Process Definition: Using IEEE Software Engineering Standards [Multiple-component retail product, part(s) enclosed]

(The Sutton Group), (IEEE SAB/IEEE SESC/MITRE), (Northrop Grumman)
  • Formaat: Multiple-component retail product, part(s) enclosed, 360 pages, kõrgus x laius x paksus: 254x179x20 mm, kaal: 733 g, Drawings: 50 B&W, 0 Color, Contains 1 Paperback / softback and 1 DVD-ROM
  • Sari: Practitioners
  • Ilmumisaeg: 11-Jul-2008
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 0470170808
  • ISBN-13: 9780470170809
Teised raamatud teemal:
  • Multiple-component retail product, part(s) enclosed
  • Hind: 159,78 €*
  • * 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
  • Formaat: Multiple-component retail product, part(s) enclosed, 360 pages, kõrgus x laius x paksus: 254x179x20 mm, kaal: 733 g, Drawings: 50 B&W, 0 Color, Contains 1 Paperback / softback and 1 DVD-ROM
  • Sari: Practitioners
  • Ilmumisaeg: 11-Jul-2008
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 0470170808
  • ISBN-13: 9780470170809
Teised raamatud teemal:
This book is geared for managers and engineers who are Lean Six Sigma novices working in organizations adept at software engineering but in need of processes, internal plans, and procedures that bring complex projects to the finish line efficiently. The need may arise from external motivations (such as a Department of Defense contract requirement) or internal motivations--such as the goals of enhanced profitability, reduced costs, and improved delivery times. Presenting an approach driven by IEEE standards, coverage includes an overview of Lean Six Sigma methodologies, detailed organizational policy examples, a set of document templates, and examples of materials that support process improvement activities and organizational delineation. The three authors all have many years of experience in the field and are affiliated, respectively, with MITRE (a not-for-profit organization), Northrop Grumman, and Lucent Technologies. Annotation ©2008 Book News, Inc., Portland, OR (booknews.com)

Practical Support for Lean Six Sigma Software Process Definition: Using IEEE Software Engineering Standards addresses the task of meeting the specific documentation requirements in support of Lean Six Sigma. This book provides a set of templates supporting the documentation required for basic software project control and management and covers the integration of these templates for their entire product development life cycle. Find detailed documentation guidance in the form of organizational policy descriptions, integrated set of deployable document templates, artifacts required in support of assessment, organizational delineation of process documentation.

Arvustused

"The book will be useful to software project managers, developers, and organizations deploying process improvement practices, because of its comprehensiveness. Students of software engineering may finds its templates useful, as they provide a simulated project environment." (Computing Reviews, December 22, 2008)

Preface xiii
Acknowledgments xv
Introduction and Overview
1(6)
Introduction
1(2)
Stimulus for Lean Six Sigma
3(1)
Using This Book
4(3)
Standards and Software Process Improvement
7(10)
What are Standards?
7(6)
IEEE S2ESC Software and Systems Engineering Standards Committee
8(1)
SWEBOK
9(3)
IEEE 12207
12(1)
Software Processes Must Exist Before They Can Be Redesigned
13(4)
Software Engineering and Training
13(1)
Software Engineering and Organizational Support
14(1)
Charter Infrastructure
14(1)
Establish Steering Committee and Process Group
14(1)
Software Engineering Processes
15(1)
Software Engineering Artifacts
15(2)
12207 Primary Life Cycle Processes
17(50)
The IEEE 12207 Process Framework
17(3)
Acquisition
20(10)
Software Acquisition Plan
20(1)
Software Acquisition Plan Document Guidance
21(2)
Concept of Operations
23(1)
Concept of Operations (ConOps) Document Guidance
24(3)
Decision Tree Analysis
27(3)
Supply
30(8)
Request for Proposal
30(1)
Request for Proposal (RFP) Document Guidance
31(1)
Joint Customer Technical Reviews
32(2)
Software Project Management Plan
34(1)
Software Project Management Plan Document Guidance
35(3)
Development
38(18)
System Requirements Analysis
40(1)
System Requirements Specification
41(1)
System Requirements Specification Document Guidance
42(3)
Software Requirements Analysis
45(1)
Software Requirements Specification
45(1)
Software Requirements Specification Document Guidance
46(2)
Software Design Document
48(2)
Software Design Document Guidance
50(3)
Interface Control Document
53(1)
Interface Control Document Guidance
53(3)
Operation
56(3)
User's Manual
56(1)
User's Manual Document Guidance
57(2)
Maintenance
59(8)
Transition Plan
59(2)
Transition Plan Document Guidance
61(6)
12207 Supporting Life Cycle Processes
67(66)
IEEE 12207 Supporting Processes
67(1)
Documentation
68(1)
Configuration Management Record
68(1)
Configuration Management
69(9)
Software Configuration Management Plan
69(1)
Software Configuration Management Plan Document Guidance
70(8)
Quality Assurance
78(8)
Software Quality Assurance Plan (SQAP)
78(1)
Software Quality Assurance Plan Document Guidance
79(7)
Verification
86(7)
Inspections
87(4)
Walk-throughs
91(2)
Validation
93(21)
Software Test Plan
94(1)
Software Test Plan Document Guidance
95(7)
System Test Plan
102(7)
System Integration Test Plan
109(5)
Joint Review
114(5)
Technical Reviews
115(2)
Management Reviews
117(2)
Audit
119(9)
Audits
120(2)
Software Measurement and Measures Plan
122(1)
Software Measurement and Measures Plan Document Guidance
123(5)
Problem Resolution
128(5)
Risk Management Plan
129(2)
Probability/Impact Risk Rating Matrix
131(2)
12207 Organizational Processes
133(28)
Management
133(18)
Software Requirements Management Plan
135(2)
Software Requirements Management Plan Document Guidance
137(6)
Software Project Management Plan
143(1)
Software Project Management Plan Document Guidance
144(4)
Stakeholder Involvement
148(1)
Work Breakdown Structure (WBS)
148(2)
Work Breakdown Structure (WBS) for Postdevelopment Stage
150(1)
Infrastructure
151(1)
Organization's Set of Standard Processes
151(1)
Improvement
152(3)
Engineering Process Group Charter
153(1)
Process Action Plan (PAP)
154(1)
Tailoring Guidelines
154(1)
Training
155(6)
Training Plan
156(5)
Lean Six Sigma Fundamentals
161(12)
What is Lean Six Sigma?
161(1)
Lean Principles
161(3)
Six Sigma Principles
164(2)
Lean Six Sigma Fundamentals
166(5)
Typical Lean Six Sigma Data
167(1)
The Laws of Lean Six Sigma
168(2)
Lean Six Sigma as Applied to Software
170(1)
What Lean Six Sigma is Not
170(1)
Six Sigma Life Cycle Variants
171(2)
Lean Six Sigma Techniques and DMAIC
173(60)
Define
173(16)
Build Sponsorship and Determine Stakeholders
173(1)
Set Priorities
174(1)
Plan Actions
175(1)
Baseline Processes
175(1)
Create a Solution
176(1)
Abstraction Tree (KJ or Affinity) Diagram
177(1)
Functional Analysis Diagrams
178(2)
Critical-to-Quality (CTQ) Tree
180(1)
Kano Model
181(1)
Project Charter
182(2)
Quality Function Deployment (House of Quality)
184(3)
Stakeholder Analysis
187(1)
Supplier, Inputs, Process, Outputs, and Customers (SIPOC) Diagram
187(1)
Voice of the Customer
188(1)
Measure
189(9)
Checksheet
189(1)
Control Charts
190(2)
FMEA (Failure Modes and Effects Analysis)/EMEA (Error Modes and Effects Analysis)
192(1)
Histograms
192(1)
Pareto Charts
193(1)
Prioritization Matrix
194(1)
Process Cycle Efficiency (PCE)
195(1)
Run Charts
196(1)
Time Value Analysis
197(1)
Analyze
198(15)
5 Whys Analysis
199(1)
Analysis of Variance (ANOVA)
199(1)
Brainstorming
200(1)
Cause-and-Effect (C&F) Diagrams
201(1)
Flowcharts---y-to-x Flowdown Diagrams
202(2)
Multivoting
204(1)
Pugh Concept Selection Matrix
205(1)
Regression Analysis
206(1)
Root Cause Analysis
207(1)
Scatter Plots (Diagrams)
208(1)
Stratification
209(1)
Value-Stream Mapping
210(1)
Waste Identification and Elimination (Seven Elements of Waste)
211(2)
Improve
213(12)
5S's Method
213(1)
Balanced Work Flow
214(1)
Cellular/Flow Manufacturing
215(1)
Jidoka (Autonomation)
215(1)
Kaizen Events
216(1)
Little's Law
216(1)
Process Stability
217(1)
Production Smoothing (Heijunka)
218(3)
Setup Time Reduction
221(1)
Takt Time
221(1)
Total Productive Maintenance (TPM)
222(2)
Visual Workplace
224(1)
Control
225(8)
Evolutionary Operation (EVOP)
225(1)
One-Piece Flow
225(1)
Measurement Systems and their Assessment
226(1)
PDCA
227(1)
Poka-yoke (Error Proofing)
228(1)
Quality Control Process Chart
228(2)
Standardized Work/Processes
230(1)
Statistical Process Control
230(3)
Applying Lean Six Sigma
233(12)
Why Should My Organization Implement Lean Six Sigma?
233(3)
Keys to Success
233(2)
The Change Context
235(1)
What If My Organization Implements Lean Six Sigma?
236(3)
Identify Your Target(s)
237(1)
Staff Responsibilities and Training
237(2)
Follow-up
239(1)
Goal-Driven Implementation
239(1)
Lean Six Sigma and Conformance
240(2)
Implementation Pitfalls
242(2)
Being Overly Prescriptive
243(1)
Documentation, Documentation
243(1)
Lack of Incentives
243(1)
Overemphasis on Certification and Not on the Lean
244(1)
Conclusion
244(1)
Appendix A. 12207 Supporting Work Products
245(112)
Acquisition
245(3)
Make/Buy Decision Matrix
245(2)
Alternative Solution Screening Criteria Matrix
247(1)
Cost-Benefit Ratio
247(1)
Supply
248(5)
Recommendations for Software Acquisition
248(1)
Organizational Acquisition Strategy Checklist
249(1)
Supplier Evaluation Criteria
250(2)
Supplier Performance Standards
252(1)
Development
253(13)
Requirements Traceability
253(1)
Software Development Standards Description
253(1)
System Architectural Design Description
254(1)
Software Architectural Design Description
255(1)
Database Design Description
255(1)
Software Architecture Design Success Factors and Pitfalls
256(1)
UML Modeling
257(1)
Unit Test Report
257(1)
Unit Test Report Document Guidance
258(5)
System Integration Test Report
263(1)
System Integration Test Report Document Guidance
263(3)
Operation
266(14)
Product Packaging Information
266(2)
Maintenance
268(1)
Change Enhancement Requests
268(1)
Baseline Change Request
269(1)
Work Breakdown Structure for Postdevelopment
270(1)
Configuration Management
271(5)
Software Change Request Procedures
276(3)
Version Description Document
279(1)
Quality Assurance
280(8)
Example Life Cycle
280(6)
Minimum Set of Software Reviews
286(1)
SQA Inspection Log
287(1)
Inspection Log Description
288(1)
Verification
288(11)
Inspection Log Defect Summary
288(1)
Inspection Log Defect Summary Description
289(1)
Inspection Report
290(1)
Inspection Report Description
291(1)
Requirements Walk-through Form
292(1)
Software Project Plan Walk-through Checklist
293(1)
Preliminary Design Walk-through Checklist
294(1)
Detailed Design Walk-through Checklist
295(1)
Program Code Walk-through Checklist
296(1)
Test Plan Walk-through Checklist
297(1)
Walk-through Summary Report
298(1)
Classic Anomaly Class Categories
298(1)
Validation
299(8)
Example Test Classes
299(2)
Types of System Testing
301(1)
Test Design Specification
302(1)
Test Case Specification
303(1)
Test Procedure Specification
304(1)
Test Item Transmittal Report
305(1)
Test Log
305(1)
Test Incident Report
306(1)
Test Summary Report
307(1)
Joint Review
307(2)
Open Issues List
307(2)
Audit
309(23)
Status Reviews
309(1)
Critical Dependencies Tracking
309(2)
List of Measures for Reliable Software
311(1)
Example Measures---Management Category
312(5)
Example Measures---Requirements Category
317(4)
Example Measures---Quality Category
321(9)
Measurement Information Model in ISO/IEC 15939
330(2)
Problem Resolution
332(6)
Risk Taxonomy
332(1)
Risk Taxonomy Questionnaire
333(3)
Risk Action Request
336(1)
Risk Mitigation Plan
337(1)
Risk Matrix Sample
337(1)
Management
338(2)
Work Breakdown Structure
338(1)
Work Flow Diagram
339(1)
Infrastructure
340(5)
Organizational Policy Examples
340(1)
Software Life Cycle (SLC) Selection and Design
341(2)
Process Definition
343(1)
Process Definition Form
343(1)
Asset Library Catalog
344(1)
Improvement
345(8)
Organizational Improvement Checklist
345(4)
Organization Process Appraisal Checklist
349(2)
Lessons Learned
351(2)
Measures Definition for Organizational Processes
353(1)
Training
353(4)
Training Log
355(2)
Appendix B. Planning For Small Projects
357(10)
Process Definition and Small Projects
357(1)
Project Management Plan---Small Projects
358(9)
Small Software Project Management Plan Document Guidance
359(8)
Appendix C. CD ROM Reference Summary
367(2)
Appendix D. IEEE Standards Abstracts
369(8)
Appendix E. Mapping From IEEE 12207 to ISO/IEC 12207:2008
377(2)
Appendix F. Acronyms
379(4)
References
383(10)
IEEE Publications
383(2)
ISO Publications
385(1)
Lean Six Sigma References
386(3)
Other References
389(4)
Index 393(18)
About the Authors 411
SUSAN K. LAND is employed by MITRE, a not-for-profit organization chartered to operate in the public interest. She has more than twenty years of industry experience in the practical application of software engineering methodologies. Ms. Land is an active volunteer supporting the IEEE Computer Society. A former vice president of the Standards Activities Board (SAB) for the Computer Society, she now serves as a member of this board and as a member of the Software and Systems Engineering Standards Committee (S2ESC). She is also the author of Jumpstart CMM/CMMI Software Process Improvement: Using IEEE Software Engineering Standards, and with John W. Walz, Practical Support for CMMI SW Software Project Documentation: Using IEEE Software Engineering Standards, and Practical Support for ISO 9001 Software Project Documentation: Using IEEE Software Engineering Standards (all published by Wiley). DOUGLAS B. SMITH is a Northrop Grumman Information Technology Technical Fellow and Program Manager of the Northrop Grumman IT Defense Group Lean Six Sigma Program. He is a Lean Six Sigma Black Belt and has been involved in process improvement since 1987. He is a member of the IEEE and IEEE Computer Society.

JOHN W. WALZ retired as senior manager of supply chain management at Lucent Technologies. His thirty-year career at Lucent & AT&T was highlighted by customer-focused and results-oriented management. Mr. Walz is Vice President of the SAB and also serves as a member of the S2ESC.