Object-oriented software engineering
Object-oriented software engineering
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
Use cases: requirements in context
Use cases: requirements in context
Advanced use case modeling: software systems
Advanced use case modeling: software systems
Writing Effective Use Cases
Replicating the CREWS Use Case Authoring Guidelines Experiment
Empirical Software Engineering
Acquiring COTS Software Selection Requirements
IEEE Software
Task Descriptions as Functional Requirements
IEEE Software
Software Requirements: Styles and Techniques
Software Requirements: Styles and Techniques
User Interface Design: A Software Engineering Perspective
User Interface Design: A Software Engineering Perspective
Answering a request for proposal --- challenges and proposed solutions
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
| Hi-index | 0.00 |
[Context and motivation] Use cases are widely used as a substantial part of requirements, also when little programming is expected (COTS-based systems). [Question/problem] Are use cases effective as requirements? To answer this question, we invited professionals and researchers to specify requirements for the same project: Acquire a new system to support a hotline. [Principal ideas/results] Among the 15 replies, eight used traditional use cases that specified a dialog between users and system. Seven used a related technique, task description, which specified the customer's needs without specifying a dialog. [Contribution] It turned out that the traditional use cases covered the customer's needs poorly in areas where improvement was important but difficult. Use cases also restricted the solution space severely. Tasks didn't have these problems and allowed an easy comparison of solutions.