 |
| |
During this session at the Jazoon Conference, Rokas Bartkevičius from the NoMagic company presented some UML modeling anti-patterns. They then serve as a basis for discussing Unified Modeling Language best practices that could correct them.
Read the full story »
News about the Unified Modeling Language (UML)
Articles on Unified Modeling Language (UML)
Blog posts about Unified Modeling Language (UML)
Videos and tutorials on the Unified Modeling Language (UML)
Unified Modeling Language (UML) tools, books, web sites and other resources
This article presents a tool for the reuse of use case diagrams by storing their information in OWL ontology and the use of Semantic Web technologies. Software reuse is defined as the use on a new project of any artifact created before. This practice has significant benefits in reducing costs and increasing quality and productivity in software development. Numerous approaches have been proposed aimed mostly at the source code reuse, but this type of reuse has its limitations because development platforms and technologies are constantly changing. It is necessary to …
This blog post discusses how and when to use UML use cases in Agile Scrum projects. Use cases are more specific and they describe how your system will act. User stories are focused on the result and the benefit of the thing you’re describing. According to the author use cases shouldn’t be used in Agile software projects unless the team really feel the need for them.
This video explains how you can use tools like the Architecture Explorer to better understand and comprehend complex systems before making any changes to them. You will see how graphically modeling the code makes it easier to understand the impact of a potential change. The video explains also how you can use modeling tools for UML and layer diagramming to describe and communicate the design of a new system—including how these tools can be used to validate the software being developed against its intended architecture.
Many applications are built around a single data model, typically persisted to a data store via an object-relational mapper (ORM) tool. Sometimes you want to have more flexibility, which requires multiple models. Understanding when one model of data just doesn’t fit all use cases is the challenge for the architect. This article discusses some strategies you can use to handle these situations and develop more layered and robust applications, using objects for data modeling.
ISLANDIA, N.Y., Feb. 1, 2012 – CA Technologies announced new CA ERwin products and releases that help a wider audience of stakeholders accurately visualize data assets across the enterprise, from on-premise platforms to the cloud.
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 worsening the situation. The ACU or “Actors Call Use cases” conjecture, which is actually against the definition of a use case, is found buried in OOSE. It distorts the features of use-case objects and is …
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 considers the behavior of the system as a whole, leading to behavioral specification of the application automatically from the machine state of each connected component. It is performed the convertion of the state machines of …
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 merged PIM and PSMs. The model is designed by reverse engineering of the legacy code in a Test Driven Development fashion.
“Just Enough Software Architecture” is book that provides guidelines and models on how to include just enough architecture in your software development activities, following an Agile approach and using risk as the main criteria on how much architecture to include in your current activity.
This blog post presents some improvements of the existing features of Acceleo. Acceleo is a pragmatic implementation of the Object Management Group (OMG) MOF Model to Text Language (MTL) standard. You do not need to be an expert to start using the plug-ins and create your first code generator. One of the improvement is the traceability for each line of code of which part of the generation template generated it, and which model element triggered its generation. This feature is intensively used in the UML to Java generator, an …
RSS Feed
Twitter