Best practice to implement requirements planning

[Stanislaw Tristan]

I have a hierarchy of functional requirements categorized in packages by specific domain areas.
How to implement the scenario when I have a set of iterations and I need to assign some of requirements to specified iterations?
What is the best practice to do this in EA?
Other words I want to implement the agile development process via EA to make requirements defining, managing and planning in one program.

[Eve]

I don't think there's a best practice.

I would recommend using keywords or a tagged value to define grouping of requirements. Then use packages to define the target iteration (with one package being the pool of unassigned requirements)

You can then use the package list grouping by the tag defined.

[Stanislaw Tristan]

I think may be the next solution:
1. Create a hierarchy of iterations
2. Create the Requirement stereotype that adds a tagged value of Iteration type
3. For each requirement assign the needed iteration through tagged value.
4. For requirements with unresolved iteration - simply do nothing.
What is the pros and cons can be?
Thank you!

[qwerty]

Usually we just group requirements in packages. Functional ones in a package structure that resembles use case sub-domains. Then for each use case we create a composite diagram where the relevant requirements are related. To check whether all requirements are used a little query/script helps. Non-functional requirements are a bit more tricky. First we group them, according to "usual" categories (legal, performance, etc.). Since you might be forced to attach them to almost everything they can be linked to a whole package and/or they receive some explanatory text.

q.

[Stanislaw Tristan]

Thanks, Querty, for sharing your experience!
Any others opinions for my last post?
Thanks!