The Model Driven Software Network

Raise your level of abstraction

Dealing with Non-Functional Requirements in Model-Driven Development

The impact of non-functional requirements (NFRs) over software systems
has been widely documented; especially regarding the choice of the right
software architecture for the system (two different sets of NFRs may
need two different system implementations even if the functional
requirements are the same).

Consequently, cost-effective software production methods shall provide means to integrate this type of
requirements into the development process. Unfortunately this is not the
case in MDD processes that mainly focus on the functional aspects of
the system. Therefore, the software implementation generated as part of
the MDD processes must be manually adapted by programmers to comply with
the NFRs of the stakeholders. Needless to say this is not an ideal
scenario.

How to solve this? See our (theoretical) proposal and join the discussion here

Views: 64

Add a Comment

You need to be a member of The Model Driven Software Network to add comments!

Join The Model Driven Software Network

Badge

Loading…

© 2018   Created by Mark Dalgarno.   Powered by

Badges  |  Report an Issue  |  Terms of Service