Designing object-oriented software
Designing object-oriented software
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Inferring Declarative Requirements Specifications from Operational Scenarios
IEEE Transactions on Software Engineering
Generating statechart designs from scenarios
Proceedings of the 22nd international conference on Software engineering
A workbench for synthesising behaviour models from scenarios
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Detecting implied scenarios in message sequence chart specifications
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Scenarios in System Development: Current Practice
IEEE Software
LSCs: Breathing Life into Message Sequence Charts
Proceedings of the IFIP TC6/WG6.1 Third International Conference on Formal Methods for Open Object-Based Distributed Systems (FMOODS)
Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
Use Case Maps for the Capture and Validation of Distributed Systems Requirements
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Distributed reactive systems are hard to synthesize
SFCS '90 Proceedings of the 31st Annual Symposium on Foundations of Computer Science
The application of use cases in systems analysis and design specification
Information and Software Technology
Practical experience of eliciting classes from use case descriptions
Journal of Systems and Software
Capturing business transaction requirements in use case models
Proceedings of the 2008 ACM symposium on Applied computing
The application of use cases in systems analysis and design specification
Information and Software Technology
Hi-index | 0.00 |
This paper begins by reviewing the application of use cases in the analysis and design phases of software development. At present, a use case derived in analysis is generally mapped into design through the synthesis of object behaviour for all scenarios associated with the use case. Hence the use case level of abstraction is not directly used in this process and a semantic gap exists between analysis and design. With informal textually based use case definitions this is to be expected, however, if the use cases themselves are given a more concrete structure, for example in the form of a statechart, then their direct use becomes more feasible. In this paper we therefore investigate the application of use case structures in the initial design phases of software development. A novel approach is proposed that applies a state based use case model directly to each object in the design architecture. This requires the derivation of a set of repeatable refinement procedures, which remove redundancy and allow the assignment of behaviour to objects with respect to their responsibilities. It is then shown how such procedures may be used in design, filling the semantic gap between analysis and design. By applying the procedures to a case study we identify and evaluate the characteristics of the mapping from use case model to object behaviour and review our approach with respect to other methods. It is concluded that state based use case structures not only represent a succinct analysis format, but may also be used to map analysis models directly into the design process.