Site Sponsor
Go WordPress
Category Archives: requirements
Two surveys on modeling are waiting for your input
MDE researchers kindly request your help: “In the course of the project MOLIZ, a research project together with the Vienna University of Technology, we kindly invite you to participate in an online survey about the usage of models in practice and requirements for model execution. The questionnaire is targeted at people who work with models
Choosing the right names for modeling elements
Because picking names is not only hard when it comes to babies…. On 2011, Raúl García-Ranea implemented an Eclipse plugin to validate the names of a conceptual model as his final carreer project [ESP], at BarcelonaTech (UPC), Spain. This work was presented as a Demo entitled An Eclipse Plugin for Validating Names in UML Conceptual
Dealing with Non-Functional Requirements in Model-Driven Development
In a joint work with David Ameller and Xavier Franch (presented at the RE’10 conference) we have investigated the support FOR non-functional requirements (NFRs) IN model-driven development (MDD).
Best modeling notation for Requirements Engineering (III) – all material online
We have commented before the competition to choose the best notation the Best Modeling Notation for Requirements Engineering held as part of the RE’09 Conference (see this post FOR the competition description AND this other post FOR a summary OF the results).
Integrating MDD with Goal-oriented Requirements Engineering methods
During my 2-YEAR postdoc IN Toronto, I did SOME WORK WITH Eric Yu about the integration OF GORE (Goal-Oriented Requirements Engineering) AND model-driven development methods.
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.
Best modeling notation for Requirements Engineering – Competition at RE’09
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.
