This post and this conceptual model has me thinking.
I know how busy you are and I know you are writing requirements but are you writing too much detail in the wrong places?
Does this model help you? Does it affect the detail you are writing in your requirements documents? Can you use it to help you write more effective requirements? Can you use it to align better your resources with respect to what they are supposed to contribute to this model?
I do struggle a bit with the model because the arrows seem to indicate flow and because of that I am not sure if I am supposed to start at the bottom and work up or at the top and work down. Or maybe I am missing the point. Maybe at the end of the day - you need to make sure you have addressed all the boxes. Thoughts anyone?
Stewart, thanks for linking to the conceptual model and opening it up for discussion.
The model is intended merely to describe how the concepts relate to each other without prescribing a sequence or process. For help reading the diagram, read this post.
I will be giving a webinar January 17th to explain the model in more detail.
Good to know - I'll be sure to listen your webinar. Have you announced it on your blog? - Stewart
Hi Stewart Rogers thanks for providing us most important information on "Software Development Deliverables"it's reallly useful for Software Development.
Thanks
MAG Studios
mag-corp.com