Theory-W Software Project Management Principles and Examples
IEEE Transactions on Software Engineering
Evolving and packaging reading technologies
Journal of Systems and Software - Special issue on achieving quality in software
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Measuring and Managing Knowledge
Measuring and Managing Knowledge
When Good Enough Software Is Best
IEEE Software
Software Quality: The Elusive Target
IEEE Software
IEEE Software
Incremental return on incremental investment: Engenio's transition to software product line practice
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
A product management challenge: Creating software product value through requirements selection
Journal of Systems Architecture: the EUROMICRO Journal
Expert Systems with Applications: An International Journal
Business value is not only dollars – results from case study research on agile software projects
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Software quality trade-offs: A systematic map
Information and Software Technology
Alignment of software product quality goals in two outsourcing relationships
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
| Hi-index | 0.00 |
The long-term sustainability of a software product depends on more than developing features. Priorities are placed on aspects that support the development of software, like software product quality (eg. ISO 9126), project constraints — time and cost, and even the development of intellectual capital (IC). A greater focus on any one aspect takes priority from another, but as each aspects delivers a different type of value managers have trouble comparing and balancing these aspects. This paper presents a method to help determine the balance between key priorities in the software development process. The method is applied to a new case study, that also combines with results from previous studies. The results show it is possible to compare features, quality, time, cost and IC in a comprehensive way, with the case study showing that participants perceive a change from a shorter-term product perspective to a longer-term organisation beneficial to the business.