Generalization of requirements

[GBeutler]

Hi,

in EA it is possible to model generalization of requirements.
i.e. a requirement hast to fulfill all of another requirement AND something else. Is it a good idea to model this as generalization? A composite dependency would work also but i am not clear about what would be the correct way of modeling this. Is generalization of requirements part of the uml standard?

thanks in advance and best regards,

Guido

[thomaskilian]

bruce did write a bit about "structured" requirements. I would summarize as follows. Requirements need to be flat. Each one must be independent of the other. However, during capturing phase you will find requirements that are alike. What I do is to use aggregation. That does give a clearer picture and you can continue to remove redundant requirements. I definitely would avoid using generalization.

[«Midnight»]

Like Thomas says...

There is an example of aggregation of requirements in the EAExample project.