The Unified Modeling Language user guide
The Unified Modeling Language user 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
Structure and style in use cases for user interface design
Object modeling and user interface design
Writing Effective Use Cases
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
UPi: a software development process aiming at usability, productivity and integration
CLIHC '05 Proceedings of the 2005 Latin American conference on Human-computer interaction
Tailoring UML activities to use case modeling for web application development
CASCON '06 Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research
A transformational approach to produce web application prototypes from a web requirements model
International Journal of Web Engineering and Technology
Business Process Modelling and Purpose Analysis for Requirements Analysis of Information Systems
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Introducing requirements traceability support in model-driven development of web applications
Information and Software Technology
BPMN-Based Specification of Task Descriptions: Approach and Lessons Learnt
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
Use cases versus task descriptions
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
| Hi-index | 0.00 |
Many IT systems fail to satisfy business goals or support users efficiently, even when the system meets written requirements. Why? Usually because the requirements rather arbitrarily specify what a system shall do, and barely consider its context. Stakeholders cannot check that such requirements meet expectations. To remedy this situation, the Tasks & Support approach uses task descriptions that specify what the user and computer shall accomplish together without being explicit about who performs which parts of a task. The requirement is simply to support the identified tasks. Stakeholders can easily validate and later verify such requirements. This approach is just as successful for product development and large-scale work restructuring as it is for buying commercial off-the-shelf products. Although the resulting requirements are of higher quality than traditional requirements, they are much faster to produce.