Articles on Unified Modeling Language (UML), Software Architecture and Data Modeling
UML 1.3 has made a pair of changes concerning the use case relationships; one is to move include and extend that used to be stereotypes of the generalization into those of the dependency, and the other is to introduce a true generalization. A use-case generalization, however, is practically useless and therefore the changes are rather …
This article proposes to automate the process of structural and behavior analysis of component-oriented software fully specified in UML. The structural specification uses component, class and deployment diagrams, and the behavior specification, state machine diagram. The produced structural analysis tool analyzes a connection between pairs of components at a time. The produced behavioral analysis tool …
Component-Oriented Software Development with UML Read More »
This article explains how with the application of Agile and Lean principles on model-driven development, we will get an Agile approach for constructing the architecture of a new Market Server Capability (MSC)definition which will eliminate the duplication and inconsistency, while still maintaining a short implementation phase. The resulting architecture has a single modeling level, with …
The main reason enterprise system solutions become hard to understand, maintain is that development teams do not apply best practices in a disciplined way when they perform use cases realizations. A use cases realization describes in terms of collaborating objects how a particular use case is realized within the design model. Its goal is to …
In this interview, Michael Blaha discusses the relationship between use cases gathering and database modeling. His opinion is that it is fine to capture requirements with use cases, but they should be dependend of the class model, which defines the domain of knolwedge that can be referenced by use cases. For database applications it is …