Object-oriented development in an industrial environment
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
A laboratory for teaching object oriented thinking
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Object-oriented modeling and design
Object-oriented modeling and design
Designing object-oriented software
Designing object-oriented software
Communications of the ACM - Special issue on analysis and modeling in software development
Information modeling: an object-oriented approach
Information modeling: an object-oriented approach
Object-oriented analysis and design with applications (2nd ed.)
Object-oriented analysis and design with applications (2nd ed.)
Requirements specification: learning object, process, and data methodologies
Communications of the ACM
The object advantage: business process reengineering with object technology
The object advantage: business process reengineering with object technology
Object models: strategies, patterns, applications
Object models: strategies, patterns, applications
Object solutions: managing the object-oriented project
Object solutions: managing the object-oriented project
Object-oriented systems analysis and design
Object-oriented systems analysis and design
ACM Computing Surveys (CSUR)
Succeeding with the Booch and OMT methods: a practical approach
Succeeding with the Booch and OMT methods: a practical approach
Developing object-oriented software: an experience-based approach
Developing object-oriented software: an experience-based approach
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Object-oriented modeling and design for database applications
Object-oriented modeling and design for database applications
Using objects for systems analysis
Communications of the ACM
Understanding UML: the developer's guide: with a Web-based application in Java
Understanding UML: the developer's guide: with a Web-based application in Java
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The unified software development process
The unified software development process
Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
Requirements analysis and system design: developing information systems with UML
Requirements analysis and system design: developing information systems with UML
Applying use cases (2nd ed.): a practical guide
Applying use cases (2nd ed.): a practical guide
Advanced use case modeling: software systems
Advanced use case modeling: software systems
Structure and style in use cases for user interface design
Object modeling and user interface design
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process
Writing Effective Use Cases
Sams Teach Yourself Uml in 24 Hours
Sams Teach Yourself Uml in 24 Hours
Rational Rose Essentials: Using the Booch Method
Rational Rose Essentials: Using the Booch Method
Systems Analysis and Design and the Transition to Objects
Systems Analysis and Design and the Transition to Objects
Object-Oriented Approach: Concepts, Modeling, and System Development
Object-Oriented Approach: Concepts, Modeling, and System Development
Schaum's Outline of Uml
Using UML: Software Engineering with Objects and Rules
Using UML: Software Engineering with Objects and Rules
Use Cases: Requirements in Context
Use Cases: Requirements in Context
Cognitive fit in requirements modeling: a study of object and process methodologies
Journal of Management Information Systems - Special section: Strategic and competitive information systems
Toward formalized object-oriented management information systems analysis
Journal of Management Information Systems
Hi-index | 0.00 |
A use case is a description of a sequence of actions constituting a complete task or transaction in an application. Use cases were first proposed by Jacobson (1987) and have since been incorporated as one of the key modeling constructs in the UML(Booch, Jacobson, & Rumbaugh, 1999) and the Unified Software Development Process(Jacobson, Booch, & Rumbaugh, 1999). This chapter traces the development of use cases, and identifies a number of problems with both their application and theoretical underpinnings. From an application perspective, the use-case concept is marked by a high degree of variety in the level of abstraction versus implementation detail advocated by various authors. In addition, use cases are promoted as a primary mechanism for identifying objects in an application, even though they focus on processes rather than objects. Moreover, there is an apparent inconsistency between the so-called naturalness of object models and the commonly held view that use cases should be the primary means of communicating and verifying requirements with users. From a theoretical standpoint, the introduction of implementation issues in use cases can be seen as prematurely anchoring the analysis to particular implementation decisions. In addition, the fragmentation of objects across use cases creates conceptual difficulties in developing a comprehensive class diagram from a set of use cases. Moreover, the role of categorization in human thinking suggests that class diagrams may serve directly as a good mechanism for communicating and verifying application requirements with users. We conclude by outlining a framework for further empirical research to resolve issues raised in our analysis.