Applying use cases: a practical guide
Applying use cases: a practical guide
Software for use: a practical guide to the models and methods of usage-centered design
Software for use: a practical guide to the models and methods of usage-centered design
Wisdom—Whitewater interactive system development with object models
Object modeling and user interface design
Structure and style in use cases for user interface design
Object modeling and user interface design
Software Engineering Economics
Software Engineering Economics
The obstacles and myths of usability and software engineering
Communications of the ACM - The Blogosphere
Estimating software based on use case points
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
About Face 3.0: The Essentials of Interaction Design
About Face 3.0: The Essentials of Interaction Design
Use cases modeling and software estimation: applying use case points
ACM SIGSOFT Software Engineering Notes
Towards a UML profile for interaction design: the wisdom approach
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Proceedings of the 5th ACM SIGCHI symposium on Engineering interactive computing systems
| Hi-index | 0.00 |
This paper describes an approach to adapt the use-case point estimation method to fit the requirements of agile development of interactive software. Creating product cost estimates early in the development lifecycle is a challenge for the software industry, they require substantial data from past projects and constant feedback and fine-tuning, which are rarely available or consistent through interactive software development. In addition, the profusion of incremental and evolutionary development methods (like Scrum and XP) produced new challenges with estimating frequent releases. Here we propose several changes to the original use-case point estimation method, in particular to take advantage of the enhanced information that can be extracted from usage-centered design (usageCD) that devotes particular attention to critical aspects like weighting actors and uses-cases for complexity. We propose to exploit user-roles, essential use-cases and the usageCD architecture to enhance the weighting heuristics for assigning complexity factors to actors and use-cases required to calculate the unadjusted use-case point reflecting the complexity of the requirements for a given iteration or evolution. We propose to exploit user-roles as the main basis for weighting complex actors, which originally are grouped in the highest weight factor. Conversely we propose to extract the complexity of use-cases from essential use case steps depicted through user intentions and system responsibilities and also the analysis classes extract from those for the usageCD architecture. Detailing this approach the paper presents a contribution, not only to leverage more accurate early lifecycle software estimation, but also to bridge the gap between SE and HCI enabling cross-fertilization between the two disciplines.