Content in the Blogs Category
In this blog post, Jürgen Wüst discusses the size and complexity of UML sequence diagrams. He describe and define a basic set of simple size and complexity measures for UML 2.x sequence diagrams.
In this blog post, Anthony Chen compares the usage of Unified Modeling Language (UML) and Requirements Modeling Language (RML) in the business analysis activity. RML® is a language for modeling software requirements to organize and communicate large quantities of information, help identify missing requirements, give context to individual details within the overall collection of requirements, and represent different views of requirements details. Anthony Chen identifies two main issues with UML.
This blog post explains how to use Obeo UMLDesigner to create your first UML model with a custom UML profile. UML Designer is an open source Eclipse plugin for the Unified Modeling Language. It provides a set of common diagrams to work with UML 2.1 models. The intent is to provide an easy way to make the transition from UML to domain specific modelling. This way users can continue to manipulate legacy UML models and start working with DSL.
This blog post discusses the role of primary and secondary actors in UML use cases. Primary Actors are actor(s) using the system to achieve a goal. The Use Case documents the interactions between the system and the actors to achieve the goal of the primary actor. Secondary Actors are actors that the system needs assistance from to achieve the primary actor’s goal.
Geert Bellekens proposes five rules to draw better Unified Modeling Language diagrams. The best practices discussed in this blog post are
to avoid large diagrams with too many items
avoid any two lines in your diagram crossing each other
lines in a diagram should go only horizontal or vertical with only right angles
parent elements are higher then the child elements in generalization or realization hierarchies
diagrams should be nice and clean
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 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 …
In this small blog post, Kobi Sasson who is the development manager for SAP NetWeaver Visual Composer explains why he thinks that modeling is the next generation of programming languages and presents the different aspects of a good modeling tool: a robust modeling language, a simple modeling tool, user interface extension points, connectivity to various backend and the ability to deliver the applications from development to production or to enable to work on the applications with multiple users.
Clear use cases are a key success factor to understand what you want to develop. Having a good use cases template is another important condition to explain your requirements. This blog post provide 10 tips to developing, automating and publishing a great template that will improve your use cases documentation.
This blog post explains that generating code from UML can be very useful, although the usefulness of the result depends on what type of UML diagrams you use. For structural models, the autor prefers UML class diagrams as he thinks feel that they convey information in a much better way than pure textual DSLs.