Español
Subscribe Ads
Why this modeling portal?
Modeling is supposed to be one of the most important activities in any software development process. At least this is the general understanding within the software engineering research community. However, in the day-to-day practice, modeling is usually regarded as, basically, a waste of time.
Novulo interview highlights
For the lazy (or busy) ones, some highlights of the interview:
- With Novulo, application modeling finally reaches the business domain.
- We want to deliver software that supports the business and not software that is a headache for the business.
- Modeling starts from the user perspective. First thing we do is to model the user interface
- We are eager to integrate and combine domain specific knowledge in submodels that then can be reused in other projects for the same domain
Competition: Best modeling notation for Requirements Engineering (II)
Some time ago we talked about a competition to find the Best Modeling Notation for Requirements Engineering held as part of the RE'09 Conference. As you all know, there is a huge number of different notations/approaches for modeling stakeholders' requirements such as: plain text specifications, structured text templates, goal-oriented requirement approaches (e.g.
Impact of having a blog post appearing in DZone (and similars)
Dzone is quite popular among the developer community (the RSS feed for the popular links category has around 25000 subscribers) so you may wonder how big is the effect of having a link to your site appearing there.
Top 5 posts in February 2010
According to your votes (number of votes = number of clicks on the post), the five most popular blog entries in February 2010 are (in this order):
Using Balsamiq mock-ups to create UML models in your iPhone (updated)
We have blogged before ( here and here ) about UML tools for the iPhone but those two tools were NOT modeling tools but a reference guide for the UML you could consult when drawing UML diagrams.
Some thoughts on simplifying the OCL
Jonathan Musset has just written a blog post on "Simple OCL" where he summarizes our discussion (by "our" I mean: Martin Gogolla, Jonathan Musset, Frédéric Jouault and myself) about possible ways to simplify the OCL. In particular, we focused on how to change the language to be able to write shorter OCL expressions. We tried to propose solutions that
would not break the language semantics and compatibility (e.g. by extending and overloading the OCL standard library)