Today I’d like to report in a multinational study I’m involved (in this case, still as part of the French team 🙂 ) targeting the study of how non-functional requirements (NFRs) are handled in model-driven developpment processes.
Very few MDD approaches have been reported to deal with NFRs (and they do it in a limited way). However, it is clear that NFRs need to be considered somehow in the final product of the MDD process. To better understand how NFRs are integrated into the existing MDD approaches, we have initiated the NFR4MDD project, a multi-national empirical study, based on interviews with companies working on MDD projects. The study involves about 20 researchers from 8 countries and is expected to involve around 30 companies whose experiences and perceptions will be surveyed using semi-structured interviews
Our project aims at surveying the state of the practice for this topic. I believe this will be a very useful complement to our previous work on how NFRs affected the choice of software architectures (see this and this)
More specifically, the research questions we hope to answer in this study are the following:
RQ1 In which context is MDD adopted by companies?
- RQ1.1 What factors motivate the adoption of MDD?
- RQ1.2 Which types of NFRs are linked to these motivating factors?
- RQ1.3 To what extent are NFRs relevant for those projects that adopt MDD?
RQ2 To what extent do MDD approaches adopted by companies support NFRs?
- RQ2.1 Which types of NFRs are supported by the adopted MDD approaches?
- RQ2.2 Which characteristics do these NFRs exhibit?
- RQ2.3 Which notations and tools are used for the supported types of NFRs?
- RQ2.4 At which stages of the adopted MDD approach are these NFRs handled?
RQ3 How do companies deal with NFRs when the adopted MDD approach does not support them?
- RQ3.1 How are MDD approaches customized to take into account the previously unsupported types of NFRs?
- RQ3.2 How do companies deal with an NFR which is not supported by MDD?
- RQ3.3 To what extent do the drawbacks of dealing with unsupported types of NFRs compensated by the benefits of adopting MDD?
For more details on this study you can come to see the presentation of this study at the next Requirements Engineering Conference (RE: Next! track) or read right now the paper where we give more details on the methodology and context of the study. Needless to say any feedback will be highly appreciated.