I'm currently struggling with some basic requirement management:
Given a set of stakeholder requirements I refine them by an equal set of use cases to identify underlying activities/functional requirements satisfied by a set of functions to fulfill the initial stakeholder requirements. These use cases may lead to a redundancy in the identified activities which i guess is okay, but should not lead to redundant functional requirements but be covered by an unique requirement for all the redundant use case activities.
Is there a certain way how to structure/relate functional requirements and the belonging stakeholder requirements? How do I handle the 1:n relation between a functional requirement and the stakeholder requirements?
Thanks in advance!
