Content tagged with: model
Ever seen technical drawings you just couldn’t make any sense of, even though you know very well what they were supposed to show? Sometimes a picture is worth a thousand words, but sometimes a thousand words can’t repair the damage done by a bad drawing.
This article by Tanya Wolff provides an overview of using models for designing business processes and services, the roles and tools involved and workflows that software architects can use for this activity. It highlights advantages of assembling the participants and services in a business process or service and provides examples to demonstrate the effects that different models have on the tools used to generate deployable artifacts. The article explains techniques to use to achieve good results, even from incomplete models and summarizes the SoaML modeling practices to use when assembling …
Business application development often starts with business process modeling to discover and document the key business requirements necessary to meet business objectives. Tasks in these processes can be implemented using a variety of techniques. However, there are many cases where simple functional decomposition leading to workflow based applications are not enough. In these cases other architectural styles may be used to develop applications in order to better manage complexity, achieve more reuse, and to facilitate change.
Graphical general-purpose modeling languages like UML dominate the modeling activity, because textual modeling languages are not as popular though they have a big potential. This article defines the important features of textual modeling languages and then compares existing general-purpose textual modeling languages according to these criteria to show if they meet their potential. Based on the comparison results, the article proposes a new modeling language called Earl Grey whose basics are presented with the experience from creating this language.
This article discusses the usage of modeling activities in agile approaches. It explains that agile modeling is aligned with Agile values and principles. Modeling should be included in your Agile toolkit, a models support communication and understanding. It recommends to create simple models using simple tools. As requirements are going to change, you should embrace change as you create models. Remember that the focus is to deliver software and not models. Use models when and where they add value.
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 presents a classification of models for software applications. This proposed classification divide all models into two group: the models in applied domain and the models in application system domain.
Modeling is not reserved to plan-driven methods, and the problems sometimes encountered lie not with modeling but with overdosing on models and failing to use modeling as an opportunity for communication. Models that become an end in themselves and are drawn up by individuals in isolation from one another are often the culprit. Typically, the secret to effective modeling is more in the -ing than the model.