Roeland posted a response (Requirements vs Process and Rules) to my recent post that made me realize how important capitalization can be!
Roeland points out that the process definition you need and the decisions and rules you need are all part of the requirements of the system you are trying to deliver. This is, of course, true. What I was trying to get at was that I do not believe that process definitions or decision definitions should be managed like Requirements. Documenting them in Use Cases or Requirements tools is much less efficient than managing them as their own artifacts. Clearly they are requirements, they are just not Requirements.














Thanks for your comment!
Posted more on
http://process-transformation.blogspot.com/2007/10/james-triggered-me-again-around.html
Regards,
Roeland