When to break out requirements

Amir Rosenblatt · Messages: 4 Offline

So, it seems that the main issue I'm running into is attempting to determine when I should break the requirements for a given step of the process out into a Requirements element and when they should just be part of the descriptive text for the activity. Regulatory issues are being broken out but as for other areas I'm just not certain.

E Keyes · Messages: 18 Offline

For my project, most of my requirements are software related (meaning you have to have version 2.0 of a program, etc). Perhaps for your project, you may want to put it in the description instead of making a separate requirement. I think it would be clearer than trying to find a requirement type that fits your project. It's mainly up to you, but I would make sure if you do it one way, you do it that way consistently to avoid confusion later on.