Abstract
In a use case-driven process, classes in the class diagram need to be identified from use cases in the use case diagram. Current object modelling approaches identify classes either from use case descriptions, or using classic categories. Both ways are inefficient when use cases can be described with many scenarios in different words. This paper represents a new approach that identifies classes based on goals of use cases without descriptions. The approach produces use case-entity diagrams as a vehicle for deriving classes from use cases and to show the involvement of classes in use cases of a system.
| Original language | English |
|---|---|
| Pages (from-to) | 83-93 |
| Number of pages | 11 |
| Journal | Information and Software Technology |
| Volume | 45 |
| Issue number | 2 |
| DOIs | |
| Publication status | Published - 1 Feb 2003 |
Keywords
- Object modelling
- Use case
- Use case's goal
- Class
- UML
Fingerprint
Dive into the research topics of 'From use cases to classes: a way of building object model with UML'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver