| Preface | 5 |
---|
| Organization | 9 |
---|
| Table of Contents | 11 |
---|
| Building a Narrative Based Requirements Engineering Mediation Model | 13 |
---|
| Introduction | 13 |
| Conflict Resolution in RE | 14 |
| A Brief Overview of Narrative Mediation | 15 |
| Narrative Mediation’s Applicability to RE | 16 |
| NREMM | 17 |
| Model Translation Method | 18 |
| NREMM | 18 |
| Conclusion and Future Work | 23 |
| References | 23 |
| Problems Encountered When Implementing Agile Methods in a Very Small Company | 25 |
---|
| Introduction | 25 |
| Why Agile Methods? | 26 |
| Employing Agile Methods | 27 |
| Research Methodology | 27 |
| Case Study | 28 |
| Project Instigation | 29 |
| Effect of Implementing Agile Methods | 29 |
| Problems Encountered | 30 |
| Benefits Derived | 33 |
| So What Went Wrong? | 34 |
| Conclusion | 35 |
| References | 35 |
| A Process Asset Library to Support Software Process Improvement in Small Settings | 37 |
---|
| Introduction | 37 |
| Process Asset Library Goals and Implementation Benefits | 39 |
| The Process Asset Library Goals | 39 |
| Process Asset Library Implementation Benefits | 39 |
| Web-Based Process Assets Library Application Structure | 40 |
| CMMI Model Components Descriptions | 42 |
| Process Assets Library Structure Using CMMI Model Components as a Reference | 43 |
| Components of the Web-Based Process Assets Library for Small Settings | 45 |
| Conclusions | 46 |
| References | 46 |
| Criteria for Estimating Effort for Requirements Changes | 48 |
---|
| Introduction | 48 |
| Literature Review | 49 |
| Empirical Evidence Based on a Collection of Change Request Forms | 51 |
| Proposed Framework | 55 |
| Conclusions and Future Work | 56 |
| References | 57 |
| Productivity of Pair Programming in a Distributed Environment – Results from Two Controlled Case Studies | 59 |
---|
| Introduction | 59 |
| Research Background | 60 |
| SoPro Project | 60 |
| Pair Programming | 60 |
| Productivity | 60 |
| Research Design | 61 |
| Research Method | 61 |
| Data Collection | 61 |
| Research Setting | 61 |
| Projects and Developers | 62 |
| Productivity Factors | 62 |
| Analyses | 65 |
| Results | 66 |
| Validity | 67 |
| Discussion | 68 |
| Conclusions and Future Work | 68 |
| References | 69 |
| Software Functional Size: For Cost Estimation and More | 71 |
---|
| Introduction | 71 |
| Related Research | 72 |
| Uses of Functional Size Measures in Project Management Knowledge Areas | 74 |
| Conclusions | 78 |
| References | 80 |
| Process Reference Guides – Support for Improving Software Processes in Alignment with Reference Models and Standards | 82 |
---|
| Introduction | 82 |
| ASPEI/MSC | 83 |
| Introducing Process Reference Guides | 85 |
| First Experiences | 89 |
| Discussion | 90 |
| Conclusions | 91 |
| References | 91 |
| Practical SPI Planning | 94 |
---|
| Introduction | 94 |
| State of the Art | 95 |
| IDEAL Model | 95 |
| DMAIC Model | 96 |
| Analysis of Project Management of SPI Models | 96 |
| P4SPI Description | 97 |
| Overview | 97 |
| Initiation Phase | 97 |
| Planning Phase | 98 |
| Control and Monitoring | 99 |
| Closure Phase | 99 |
| P4SPI Components | 100 |
| Case Study of CMMI Implementation Using P4SPI | 102 |
| Conclusions | 104 |
| References | 104 |
| Analysis of Dependencies between Specific Practices in CMMI Maturity Level 2 | 106 |
---|
| Introduction | 106 |
| Work Products of CMMI Specific Practices | 107 |
| Work Product-Based CMMI Specific Practice Dependencies | 108 |
| Methodology | 108 |
| Specific Practice Dependencies within Process Areas | 108 |
| Specific Practices Dependencies Across Process Areas | 113 |
| Discussion | 113 |
| Interpreting the Model | 113 |
| Validation | 113 |
| Problems with Completeness and Terminology in the CMMI Specification | 114 |
| Discussion of Specific Practice Dependencies and Process Area Relationships | 115 |
| Conclusion | 115 |
| References | 116 |
| A Solution for Establishing the Information Technology Service Management Processes Implementation Sequence | 118 |
---|
| Introduction | 118 |
| Organization and Structure of the ITSM Processes | 119 |
| OPreSSD: Organizational Procedure for Service Support and Service Delivery | 120 |
| Establish Dependency Relationships | 120 |
| Generate Sequence | 123 |
| Summary | 127 |
| References | 128 |
| Modeling and Assessment in IT Service Process Improvement | 129 |
---|
| Introduction | 129 |
| Capability Assessments | 130 |
| Process Assessment Models for IT Service Management | 130 |
| Process Modeling | 133 |
| Experiences of Combined Modeling and Assessment | 135 |
| Integration of the Approaches | 136 |
| Conclusions | 138 |
| References | 139 |
| A Software Engineering Lifecycle Standard for Very Small Enterprises | 141 |
---|
| Introduction | 141 |
| Very Small Enterprises | 142 |
| Characteristics of a VSE | 143 |
| History of the ISO/IEC Working Group for VSEs | 144 |
| Gathering VSE Requirements | 145 |
| Categorization of the Sample According to the Size Criterion | 146 |
| General Characteristics | 147 |
| Use of Standards | 147 |
| The WG24 Approach | 148 |
| Recent Developments | 151 |
| Conclusion and Future Work | 151 |
| References | 152 |
| Lightweight Process Documentation: Just Enough Structure in Automotive Pre-development | 154 |
---|
| Introduction | 154 |
| Related Work | 156 |
| Study Design | 156 |
| Information Flow Basics | 156 |
| Elicitation
|