Applying use cases: a practical guide
Applying use cases: a practical guide
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Use cases: requirements in context
Use cases: requirements in context
Writing Effective Use Cases
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Use Case Modeling
Empirical Software Engineering
A Framework for Object Identification and Refinement Process in Object-Oriented Analysis and Design
ICCI '02 Proceedings of the 1st IEEE International Conference on Cognitive Informatics
Quality and Understandability of Use Case Models
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
Guiding Use Case Authoring: Results of an Empirical Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
OOA Metrics for the Unified Modeling Language
CSMR '98 Proceedings of the 2nd Euromicro Conference on Software Maintenance and Reengineering ( CSMR'98)
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
IEEE Transactions on Software Engineering
Investigating the Role of Use Cases in the Construction of Class Diagrams
Empirical Software Engineering
Perspective-Based Reading: A Replicated Experiment Focused on Individual Reviewer Effectiveness
Empirical Software Engineering
Communications of the ACM - Two decades of the language-action perspective
Assessing the quality of use case descriptions
Software Quality Control
Improving the quality of use case descriptions: empirical assessment of writing guidelines
Software Quality Control
MODELS '09 Proceedings of the 12th International Conference on Model Driven Engineering Languages and Systems
Supporting use case based requirements engineering
Information and Software Technology
The impact of structural complexity on the understandability of UML statechart diagrams
Information Sciences: an International Journal
Object-Oriented Software Engineering Using UML, Patterns, and Java
Object-Oriented Software Engineering Using UML, Patterns, and Java
A systematic review of transformation approaches between user requirements and analysis models
Requirements Engineering
Automated transition from use cases to UML state machines to support state-based testing
ECMFA'11 Proceedings of the 7th European conference on Modelling foundations and applications
Automatically deriving a uml analysis model from a use case model
Automatically deriving a uml analysis model from a use case model
An automated approach to transform use cases into activity diagrams
ECMFA'10 Proceedings of the 6th European conference on Modelling Foundations and Applications
Complementary use case scenario representations based on domain vocabularies
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
Functional requirements validation by transforming use case models into Abstract State Machines
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Hi-index | 0.00 |
Use case modeling, including use case diagrams and use case specifications (UCSs), is commonly applied to structure and document requirements. UCSs are usually structured but unrestricted textual documents complying with a certain use case template. However, because Use Case Models (UCMods) remain essentially textual, ambiguity is inevitably introduced. In this article, we propose a use case modeling approach, called Restricted Use Case Modeling (RUCM), which is composed of a set of well-defined restriction rules and a modified use case template. The goal is two-fold: (1) restrict the way users can document UCSs in order to reduce ambiguity and (2) facilitate the manual derivation of initial analysis models which, when using the Unified Modeling Language (UML), are typically composed of class diagrams, sequence diagrams, and possibly other types of diagrams. Though the proposed restriction rules and template are based on a clear rationale, two main questions need to be investigated. First, do users find them too restrictive or impractical in certain situations? In other words, can users express the same requirements with RUCM as with unrestricted use cases? Second, do the rules and template have a positive, significant impact on the quality of the constructed analysis models? To investigate these questions, we performed and report on two controlled experiments, which evaluate the restriction rules and use case template in terms of (1) whether they are easy to apply while developing UCMods and facilitate the understanding of UCSs, and (2) whether they help users manually derive higher quality analysis models than what can be generated when they are not used, in terms of correctness, completeness, and redundancy. This article reports on the first controlled experiments that evaluate the applicability of restriction rules on use case modeling and their impact on the quality of analysis models. The measures we have defined to characterize restriction rules and the quality of analysis class and sequence diagrams can be reused to perform similar experiments in the future, either with RUCM or other approaches. Results show that the restriction rules are overall easy to apply and that RUCM results into significant improvements over traditional approaches (i.e., with standard templates, without restrictions) in terms of class correctness and class diagram completeness, message correctness and sequence diagram completeness, and understandability of UCSs.