Current practices in the use of UML
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
An empirical study of the nesting level of composite states within UML statechart diagrams
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Utilizing a multimedia UML framework for an image database application
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Object class or association class? testing the user effect on cardinality interpretation
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Organizing and managing use cases
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
A comparative analysis of use case relationships
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Applying transformations to model driven development of web applications
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
A UML 2 profile for business process modelling
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
| Hi-index | 0.00 |
The Unified Modeling Language (UML) has been widely accepted as the standard object-oriented (OO) modeling language for modeling various aspects of software and information systems. The UML is an extensible language, in the sense that it provides mechanisms to introduce new elements for specific domains if necessary, such as web applications, database applications, business modeling, software development processes, data warehouses and so on. Furthermore, the latest work of the Object Management Group (OMG) on UML [1] resulted in a larger and more complicated specification, with even more diagrams for some good reasons. Although providing different diagrams for modeling specific parts of a software system, not all of them need to be applied in most cases. Therefore, heuristics, design guidelines, and lessons learned from experiences are extremely important for the effective use of UML and to avoid unnecessary complication.