Foreword by Dr.Vicki P.Rainey
Preface
Acknowledgments
PART I SETTING THE SCENE FOR SOFTWARE
QUALITY ASSURANCE
1 The Quality Game
1.1 Elusive Software Quality
1.1.1 Defining Quality
1.1.2 Quality and Objective Effort
1.1.3 Nature of Software
1.1.4 Assuring Quality: A Distinct Activity
1.2 Pressures on Quality
1.2.1 Budget
1.2.2 Time
1.2.3 Functionality
1.2.4 Quality
1.3 Quality Levels
1.3.1 Data Quality
1.3.2 Code Quality
1.3.3 Model Quality
1.3.4 Process Quality
1.3.5 Management Quality
1.3.6 Quality Environment
1.4 Quality Software Process
1.4.1 What Constitutes a Process?
1.4.2 A Sample Cooking Process
1.4.3 The Orthogonal Process Relationship
1.4.4 Process in Software Context
1.4.5 Software Process
1.4.6 Quality Process
1.4.7 Quality Assurance and Testing: Let's Not Confuse Them
1.5 Modeling and Quality
1.5.1 Purpose of Modeling
1.5.2 Modeling Caveats
1.5.3 Understanding Modeling Spaces in Software
1.5.4 Problem Space
1.5.5 Solution Apace
1.5.6 Background Space
1.6 UML and Quality
1.6.1 A Brief History of UML
1.6.2 Quality of UML versus Quality by UML
1.6.3 Metamodels and Quality
1.6.4 Quality by UML
1.6.5 Quality of Visualization
1.6.6 Quality of Specification
1.6.7 Quality of Construction
1.6.8 Quality of Documentation
1.6.9 Summary of UML Diagrams and Their Importance in Modeling Spaces
1.7 Quality Assurance Techniques of Syntax,Semantics, and Aesthetics
1.7.1 Quality Models-Syntax
1.7.2 Quality Models-Semantics
1.7.3 Quality Models-Aesthetics
1.8 Quality Assurance of Software Process: Necessity, Sufficiency, and Malleability
1.8.1 Quality of Process-Necessity
1.8.2 Quality of Process-Sufficiency
1.8.3 Quality of Process-Malleability
1.9 Reuse, Patterns, and Quality
1.9.1 Increasing Productivity through Reuse
1.9.2 Reusing Expert Knowledge and Experience
1.9.3 Applying Standards
1.10 Quality and Usability
1.10.1 Principles of Usability
1.10.2 Navigability of Interfaces
1.10.3 GUI Design and Quality
1.11 UNL-Based Projects-Types
1.11.1 Development
1.11.2 Integration(With Legacy)
1.11.3 Package Implementation (ERP,CRMS)
1.11.4 Outsourcing
1.11.5 Data Warehousing/Conversion
1.11.6 Educational
1.12 UML-Based Projects-Size and Scalability
1.12.1 Small Projects
1.12.2 Medium Projects
1.12.3 Large Projects
1.13 Putting it All Together(Key Points)
1.14 Bibliographic Notes
1.15 Frequently Asked Questions(FAQs)
1.16 Exercises
1.17 References
PART II ORGANIZING AND ENACTING THE PROCESS FOR QUALITY
2 Quality Environment: Managing the Quality Function
2.1 Quality Management
2.1.1 Quality Environment
2.1.2 Nontechnical Management
2.1.3 Process and Quality
2.2 Team Organization
2.2.1 Organizing the Roles in the Problem Space
2.2.2 Business Analyst
2.2.3 User
2.2.4 End User
2.2.5 Domin Expert
2.2.6 Prototyper in Problem Space
2.2.7 Organizing the Roles in the Solution Space
2.2.8 System Desingner
2.2.9 Data Modeler
2.2.10 Interface Designer
2.2.11 Programmer
2.2.12 Tester
2.2.13 Prototyper in Solution Space
2.2.14 Organizing the Roles in the Background Space
2.2.15 System Architect
2.2.16 Prototyper in Background Space
2.2.17 Database Manager
2.2.18 Common Roles
2.2.19 Project Manager
2.2.20 Steering Committee
2.2.21 Business Sponsor
2.2.22 Organizing the Qualiy Team
2.2.23 Quality Manager
2.2.24 Quality Analyst
2.2.25 Process Engineer
2.2.26 User
2.2.27 Tester
2.3 The Quality Environment
2.3.1 E-factor and Quality
2.3.2 Soft Issues Specific to UML-Based Projects
2.3.3 Communication in a Quality Environment
2.3.4 Telecommuting
2.4 ProjectSociology
2.4.1 Four Models for Project Teams
2.4.2 The Best-Fit Approach to Creating a Jomogeneous Team
2.4.3 Flattening the Pyramid
2.4.4 People in Reusability
2.4.5 Parallel Development Teams
2.5 Transactional Analysis in Software Projects
2.5.1 A Brief Jistory of TA
2.5.2 The Parent, Adult, and Child Ego States
2.5.3 The Life Positions
2.5.4 Games
2.5.5 Games in an OO Project
2.5.6 Use It or Lose It
2.5.7 Cowboy Programming
2.5.8 Flour Mix
2.5.9 Meetingitis
2.5.10 Deadline
2.6 Popular Quality Techniques
2.6.1 Walkthroughs
2.6.2 Inspections
2.6.3 Reviews
2.6.4 Audits
2.6.5 Checklists
2.6.6 Interviews
2.6.7 Workshops
2.7 Standards and Quality
2.7.1 Areas of Application of Standards
2.7.2 Project, Organizational, and Industrial Standards
2.8 Process Maturity: The CMM Standards
2.8.1 The Capability Maturity Model
2.8.2 Personal Software Process Maturity
2.8.3 Applying CMM in UML-Based Projects
2.9 Process Checks
2.9.1 Checking What Is Necessary
2.9.2 Checking What Would be Sufficient
2.9.3 Checking the Malleability of a Process
2.10 The Planning Deliveables
2.10.1 Project Organizational Plan
2.10.2 The Quality Plan
2.10.3 Test Plan
2.11 Bibliographic Notes
2.12 Frequently Asked Questions(FAQs)
2.13 Exercises
2.14 References
3 The Quality Process Architecture
3.1 The Process Backbone
3.1.1 The Three Dimensions of a Process
3.1.2 "What" of a Process
3.1.3 "How" of a Process
3.1.4 "Who" of a Process
3.2 The Process Metamodel
3.2.1 Describing the Process Metamodel
3.2.2 Process Ingredients
3.2.3 The Role Element in a Process
3.2.4 The Activity Element a Process
3.2.5 The Task Element in a Process
3.2.6 The Deliverable Element in a Process
3.2.7 A Process-Component
3.2.8 Iterations
3.2.9 Putting Together a Process-Component: A Baking Process
3.3 Quality Software Process
3.3.1 The Software Process
3.3.2 The Quality Process
3.3.3 Rigorous Process
3.3.4 Process Maturity
3.3.5 Malleable Process
3.3.6 Process Timing
3.4 The Software Process
3.4.1 Business Evaluation Process-Component
3.4.2 Roles in Business Evaluation
3.4.3 Activities and Tasks in Business Evaluation
3.4.4 Deliverables in Business Evaluation
3.4.5 Quality Comments on Business Evaluation
3.4.6 Projest Management Process-Component
3.4.7 Roles in Project Management
3.4.8 Activities and Tasks in Project Management
3.4.9 Deliverables in Project Management
3.4.10 Quality Comments on Project Management
3.4.11 Process Configuration Process-Component
3.4.12 Roles in Process Configuration
3.4.13 Activities and Tasks in Process Comfiguration
3.4.14 Deliverables in Process Configuration
3.4.15 Activities and Tasks in Process Configuration
3.4.16 Requirements Modeling Process-Component
3.4.17 Roles in Requirements Modeling
3.4.18 Activities and Tasks in Requirements Modeling
3.4.19 Deliverables in Requirements Modeling
3.4.20 Quality Comments on Requirements Modeling
3.4.21 Interface Modeling and Design Process-Component
3.4.22 Roles in Interface Modeling
3.4.23 Activities and Tasks in Interface Modeling
3.4.24 Deliverables in Interface Modeling
3.4.25 Quality Comments on Interface Modeling
3.4.26 System Design Process-Component
3.4.27 Roles in System Design
3.4.28 Activities and Tasks in System Design
3.4.29 Deliverables in System Design
3.4.30 Quality Comments on System Design
3.4.31 Persistence Design Process-Component
3.4.32 Roles in Persistence Design
3.4.33 Activities and Tasks in Persistence Design
3.4.34 Deliverables in Persistence Design
3.4.35 Quality Comments on Persistence Design
3.4.36 Implementation Process-Component
3.4.37 Roles in Implementation
3.4.38 Activities and Tasks in Implementation
3.4.39 Deliverables in Implementation
3.4.40 Quality Comments on Implementation
3.4.41 Prototyping Process-Component
3.4.42 Roles in Prototyping
3.4.43 Activities and Tasks in Prototyping
3.4.44 Change Management Process-Component
3.4.45 Roles in Change Management
3.4.46 Activities and Tasks in Change Management
3.4.47 Deliverables in Change Management
3.4.48 Quality Comments on Change Management
3.4.49 Deliverables in Change Management
3.4.50 Quality Comments on Change Management
3.4.51 Enterprise Architecture Process-Component
3.4.52 Roles in Enterprise Architecture
3.4.53 Activities and Tasks in Enterprise Architecture
3.4.54 Deliverables in Enterprise Architecture
3.4.55 Quality Comments on Enterprise Architecture
3.4.56 System Architecture Process-Component
3.4.57 Roles in System Architecture
3.4.58 Activities and Tasks in System Architecture
3.4.59 Deliverables in System Architecture
3.4.60 Quality Comments on System Architecture
3.4.61 Deployment Process-Component
3.4.62 Roles in Deployment
3.4.63 Activities and Tasks in Deployment
3.4.64 Deliverables in Deployment
3.4.65 Quality Comments on Deployment
3.4.66 Training Process-Component
3.4.67 Roles in Training
3.4.68 Activities and Tasks in Training
3.4.69 Deliverables in Training
3.4.70 Quality Comments on Training
3.4.71 Reuse process-Component
3.4.72 Roles in Reuse
3.4.73 Activities and Tasks in Reuse
3.4.74 Deliverables in Reuse
3.4.75 Quality Comments on Reuse
3.5 The Quality Process
3.5.1 Quality Management Process-Component
3.5.2 Roles in Quality Management
3.5.3 Activities and Tasks in Quality Management
3.5.4 Deliverables in Quality Management
3.5.5 Quality Comments on Quality Management
3.5.6 Quality Assurance Process-Component
3.5.7 Roles in Quality Assurance
3.5.8 Activities and Tasks in Quality Assurance
3.5.9 Delverables in Quality Assurance
3.5.10 Quality Comments on Quality Assurance
3.5.11 Quality Control Process-Component
3.5.12 Roles in Quality Control
3.5.13 Activities and Tasks in Quality Control
3.5.14 Deliverables in Quality Control
3.5.15 Quality Comments on Quality Control
3.6 Bibliographic Notes
3.7 Frequently Asked Questions(FAQs)
3.8 Exercises
3.9 References
4 Enacting the Quality Software Process
4.1 Configuration of a process
4.1.1 The Waterfall-Based SDLC
4.1.2 The Spiral-Based SDLC
4.1.3 The Fountain-Based SDLC
4.2 The Iterative, Incremental, and Parallel Development Process
4.2.1 Need for Iterations and Increments
4.2.2 Initial
4.2.3 Major
4.2.4 Final
4.2.5 Parallel Developments within a Lifecycle
4.2.6 Maintenance or Ongoing Iteration
4.3 Adoption of the Software Process
4.3.1 Ascertain Current Process State
4.3.2 Crucial Pilot Project
4.3.3 Point of Adoption
4.3.4 Separating UML from the Process
4.3.5 Keeping ALL CASE Tool Implementations Separate
4.3.6 Training and Mentoring
4.3.7 Access to the Process
4.4 Enacting the Quality Process
4.4.1 Creating Iterations and Increments in Lucky Insurance's Development
4.4.2 An Iterative Project Task Plan
4.4.3 Iterative Project Management Tools
4.5 Tracking Quality throughout the Process
4.5.1 Importance of Road Factors in Process Enactment
4.5.2 Quality Activities at the End of the Initial Iteration
4.5.3 Quality Activities at the End of the Major Iteration
4.5.4 Quality Activities at the End of the Final Iteration
4.6 Frequently Asked Questions(FAQs)
4.7 Exercises
4.8 References
5 Estimates and Metrics for UML-Based Projects
5.1 About Estimates and Measures in Softwaer Projects
5.1.1 Relating Estimates to Quality
5.1.2 Measurements and Estimates
5.1.3 Measuring the Technological Dimension
5.1.4 Measuring the Methodological Dimension
5.1.5 Measuring the Sociological Dimension
5.2 Project Metrics and Estimates
5.2.1 Project Size and Type
5.2.2 Project Time, Budgets, and People
5.2.3 Caveats in Project Estimates
5.3 Measurement of Processes
5.3.1 Why Measure Processes?
5.3.2 Measuring Process-Components in Deployment
5.3.3 Measuring Process-Components in Enactment
5.3.4 Refining the Project Estimations at the End of Each Iteration
5.4 Quality Metrics
5.5 Measuring Size of Software
5.5.1 Traditional Measures of Software
5.5.2 Additional Measures of Software
5.5.3 Object-Oriented Measures of Software
5.6 Measures of UML Artifacts, Diagrams, and Models
5.6.1 Measuring Size and Complexity of Use Cases and Use Case Diagrams
5.6.2 Measuring Size and Complexity of Classes
5.6.3 Measurement of a Component
5.6.4 Testing Metrics
5.7 Applying Metrics and Estimates to Lucky Insurance's Project
5.7.1 Considering Metrics and Estimates Specific to Lucky Insurance's Project
5.7.2 Project and Process Metrics in Enactment
5.7.3 Measuring Process-Components for Enactment
5.7.4 Applying Process and Project Metrics to Lucky Insurance's Project
5.7.5 Arriving at the Productivity Factor for Lucky Insurance's Project
5.7.6 Refining Estimates Based on the Productivity Factor for Subsequent Iterartions
5.8 Prophetic Statements on Estimates and Metrics
5.9 Bibliographic Notes
5.10 Frequently Asked Questions(FAQs)
5.11 Exercises
5.12 References
PART III: TESTING THE PRODUCT: QUALITY CONTROL
6 Quality Control of Software Products
6.1 Testing in Context
6.2 Testing Approaches in UML-Based Projects
6.2.1 Black Box
6.2.2 White Box
6.2.3 Manual Testing
6.2.4 Automated Testing
6.2.5 Vertical Testing
6.2.6 Horizontal Testing
6.2.7 Equivalence Partitioning
6.2.8 Boundary Valuv
6.3 Testing Architecture
6.3.1 Unit Test
6.3.2 Component Test
6.3.3 System Test
6.3.4 Acceptance Test
6.3.5 Regression Test
6.3.6 Operational Testing
6.3.7 Performance(Stress and Volume)Testing
6.3.8 Security Testing
6.3.9 Scalability Testing
6.4 Test Planning
6.4.1 A Good Test Plan
6.4.2 Analyzing Risks in Testing
6.4.3 Test Environment
6.4.4 Test Schedules
6.4.5 Test Cycles
6.4.6 Reusability in Testing
6.4.7 Test Design
6.4.8 Description of Test Designs
6.4.9 Sources for Test Designs
6.5 Test Design
6.5.1 Description of Test Designs
6.5.2 Sources for Test Designs
6.5.3 Format for Test Designs
6.6 Test Cases
6.6.1 Description of Test Cases
6.6.2 Designing the Test Cases
6.6.3 Format for Test Cases
6.6.4 Example Test Cases
6.6.5 Verifying the Test Cases
6.6.6 Modifying the Test Cases
6.7 Test Execution
6.7.1 Getting Ready
6.7.2 Acceptance Criteria
6.7.3 Execute Test Suites
6.7.4 Record Incident Reports
6.8 Recording and Analyzing Test Results
6.8.1 Software Incidents
6.8.2 Recording Test Results
6.8.3 Analyzing Results
6.8.4 Reporting
6.9 Bibliographic Notes
6.10 Frequently Asked Questions(FAQs)
6.11 Exercises
6.12References
Glossary of Acronyms and Important Terms
Bibliography
UML CASE Tools
Process Tools Using UML
CD-ROM Contents
Epilogue
Index
鄂公网安备 42010302001612号 