Requirements Elicitation and Validation with Real World Scenes
IEEE Transactions on Software Engineering
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Cascaded refactoring for framework
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
A Survey of Agent-Oriented Methodologies
ATAL '98 Proceedings of the 5th International Workshop on Intelligent Agents V, Agent Theories, Architectures, and Languages
Towards a Common Semantic Foundation for Use Cases and Task Models
Electronic Notes in Theoretical Computer Science (ENTCS)
Applying MAS-CommonKADS methodology in knowledge management problem in call centers
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Systems Analysis For Collaborative System By Use Case Diagram
Journal of Integrated Design & Process Science
Identifying vulnerabilities and critical requirements using criminal court proceedings
Proceedings of the 2009 ACM symposium on Applied Computing
Application patterns for computer-based systems design reuse
ECBS'99 Proceedings of the 1999 IEEE conference on Engineering of computer-based systems
UCM-ROOM modelling: from use case maps to communicating state machines
ECBS'97 Proceedings of the 1997 international conference on Engineering of computer-based systems
ATVA'10 Proceedings of the 8th international conference on Automated technology for verification and analysis
| Hi-index | 0.00 |
Use case modeling is gaining increasing interest in computer-based systems engineering, especially in the earliest stages of system development, where requirements are elicited, documented and validated. This paper presents a conceptual framework for use case modelling and a new use case model with graphical representation, including support for different abstraction levels and mechanisms for managing large use case models. Current application of use cases in requirements engineering is discussed, as well as ontological and methodological issues related to use case modelling. The presented use case model has three levels of abstraction: Environment Level, relating use cases with actors and services; Structure Level, describing the episode structure of each use case; Event Level, describing stimuli, responses and system actions of each episode. All levels have graphical representation, and the paper gives examples of each level and explains the notation. The event level is described by an extension of Message Sequence Charts [ITU-T recommendation Z.120], with operators for alternative, repetition, exception and interrupt. Conclusions are given together with a discussion on further research.