(Have you noticed a change from solution model? Solution design creates system models.)
What's in a system model? Everything! Everything "I" am interested in modelling. That may sound so obvious... but it wasn't always; and in fact is still not the case in many methods today in which there are many different models for different aspects of the system; several for requirements modelling, more for software design, and even more for deployment considerations, almost everyone of which is called the "XYZ Model Work Product". And that's just one perspective - carve things up in other ways and you'll find security models, infrastructure models, and risk models... All of the same system.
So what? To repeat an earlier phrase - so what a lot!
First of all, imagine making a change to the name of something... How many models will you need to edit? Will you make those changes?
Or "So how does this model relate to that one? Not just at this moment, but after I've made this change?" Any idea?
Or "We've had a budget cut, and need to descope all of this" Gulp.
Far, far easier if there is one and only one system model embracing all aspects and perspectives of all that "I" am interested in... and since I am a Solution Designer, I know "all" for me covers a well understood spectrum of stuff.
Oh boy, that's a lot of stuff... All those aspects and dimensions! I couldn't possibly... Oh yes you can, if you adopt the right approach: "Views and Viewpoints" and Something of Everything".
No comments:
Post a Comment