A laboratory for teaching object oriented thinking
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Communications of the ACM - Special issue on analysis and modeling in software development
Inquiry-Based Requirements Analysis
IEEE Software
Generating object-oriented design representations via scenario queries
Scenario-based design
ICSE '93 Proceedings of the 15th international conference on Software Engineering
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Scenario-based requirements analysis
Requirements Engineering
Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Conceptual modeling through linguistic analysis using LIDA
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Writing Effective Use Cases
Uml and the Unified Process: Practical Object-Oriented Analysis and Design
Uml and the Unified Process: Practical Object-Oriented Analysis and Design
Exploring Requirements: Quality Before Design
Exploring Requirements: Quality Before Design
An Evaluation of Applying Use Cases to Construct Design versus Validate Design
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track 9 - Volume 9
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
Investigating the Role of Use Cases in the Construction of Class Diagrams
Empirical Software Engineering
Assessing the quality of use case descriptions
Software Quality Control
The application of use cases in systems analysis and design specification
Information and Software Technology
| Hi-index | 0.00 |
In moving from requirements analysis to design, use cases are often recommended as the starting point for the derivation of classes. However, exactly how classes are to be found within the use case is not entirely obvious. Typical approaches suggest a simple noun/verb search or brainstorming. Recent work is moving towards an interrogation of the use case diagram as a means of validation and of the description (and scenario) to elicit objects in the problem domain. This paper presents a set of Elicitation Questions that enables the interrogation of descriptions from the perspectives of specification, software architecture and design. This qualitative 'interrogation' teases out design issues. The Elicitation Questions were trialled through application to a real industrial project at a financial services company. Feedback from practitioners shows that the Elicitation Questions are important in raising design and testing issues from the use case descriptions but the organisational culture in how software is developed would impact its uptake.