Category Archives: requirements

Non-functional Requirements in Architectural Decision Making at InfoQ


Our IEEE software paper Non-functional Requirements in Architectural Decision Making is now also available for everybody at InfoQ . I’m quite happy with this paper (to be honest, I can’t say the same about quite a few others, but that’s another story, more for my “My Research Rants” blog) so I’m sure you’ll find interesting.

Enabling the Collaborative Definition of DSMLs (slides)

Check this summary of Collaboro, our proposal to the collabortive definition of domain-specific languages to be presented tomorrow at the CAiSE conference. Abstract: Software development processes are collaborative in nature. Neglecting the key role of end-users leads to software that does not satisfy their needs. This collaboration becomes specially important when creating Domain-Specific Modeling Languages

How do software architects deal with non-functional requirements?


The full results of our exploratory study on how software architects deal with non-functional requirements (based on a set of interviews with software architects) were presented at the RE’12 conference (full paper is available here and the summary/slides can be browsed below) What was the motivation of this work? Research papers on software architecture often

Architecture Quality revisited


Together with X. Franch, D. Ameller and C. Ayala (all members of the GESSI group), I’ve been recently interested in exploring to what extend the huge amount of elicitation, documentation, validation, … techniques for non-functional requirements (NFRs) were useful and used in practice. The full results of our empirical study can be read here but

Conceptual modelling for the rest of us with ConML


César Gonzalez-Perez from the Institute of Heritage Sciences (Incipit) / Spanish National Research Council (CSIC) talks today about ConML, a conceptual modeling language suited for non-technical people. Enter César. Conceptual modelling is usually associated with the discipline of software engineering. But the truth is that modelling is a useful technique for shaping, exploring, documenting, understanding

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.

Powered by WordPress