Software metrics: establishing a company-wide program
Software metrics: establishing a company-wide program
Tutorial programming productivity: issues for the eighties, 2nd ed.
Tutorial programming productivity: issues for the eighties, 2nd ed.
Software Process Evolution at the SEL
IEEE Software
Software product-line engineering: a family-based software development process
Software product-line engineering: a family-based software development process
Software assessments, benchmarks, and best practices
Software assessments, benchmarks, and best practices
Does Code Decay? Assessing the Evidence from Change Management Data
IEEE Transactions on Software Engineering
Software Engineering Economics
Software Engineering Economics
The Data Warehouse Lifecycle Toolkit: Expert Methods for Designing, Developing and Deploying Data Warehouses with CD Rom
Software Maintenance Management
Software Maintenance Management
Interval quality: relating customer-perceived quality to process quality
Proceedings of the 30th international conference on Software engineering
Assessing the capability and maturity of capstone software engineering projects
ACE '08 Proceedings of the tenth conference on Australasian computing education - Volume 78
Assessing the state of software in a large enterprise
Empirical Software Engineering
Goal alignment in process improvement
Journal of Systems and Software
| Hi-index | 0.00 |
Companies that engage in multi-site, multi-project software development continually face the problem of how to understand and improve their software development capabilities. We have defined and applied a goal-oriented process that enables such a company to assess the strengths and weaknesses of those capabilities. Our goals are to help a) to decrease the time and cost to develop software, b)to decrease the time needed to make changes to existing software, c) to improve software quality, d) to attract and retain a talented engineering staff, and e) to facilitate more predictable management of software projects. In response to the variety of product requirements, market needs, and development environments, we selected a goal-oriented process, rather than a criteria-oriented process, to advance our strategy and ensure relevance of the results. We describe the design of the process, discuss results achieved, and present vulnerabilities of the methodology. The process includes both interviews with projects' personnel and analysis of change data. Several common issues have emerged from the assessments across multiple projects, enabling strategic investments in software technology. Teams report satisfaction with the outcome in that they act on the recommendations, ask for additional future assessments, and recommend the process to sibling organizations.