Well, it's Solution Modelling! Based on the previous post, the word "design" is superfluous! Design is modelling!! So I could equally say "it's Solution Design"!
So what's "Solution"? In some contexts (language is all about context!) it labels the work done to create a plan to profitably realise, you might say implement an answer to a problem: "if we do this and this to understand the challenge, then decide which package fits best and how to implement it in a phased way while keeping the existing system running... all signed of by our sponsors and users by next Christmas and within budget.. then we have a solution!!!"
Yes, that's a perfectly OK use of the word, and is in fact one I find attractive. A solution design may therefore include many models, including a system model, financial model and project model (plus loads of other things like stakeholder management and contracts) that taken together should deliver profitably a working solution.
But in the context of my "tribe", that's more likely to be called programme design, at the heart of which (for us!) is the design... sorry, model of the business/IT that shows how we expect to solve the business (or IT) problem with a combination of human and IT components - in other words, our solution model is more narrowly defined to show the structure of the system's parts (some based on silicon, some on carbon) and how they work together, how they behave to safely and profitably satisfy the requirements.
We're getting there: to solve is to design, to design is to model, and to model is to think about structure and behaviour... What do solution designers think about when they think about their system's structure and behaviour?
Yes, I know I should have said "their solution's structure and behaviour"! But I did say I liked that other tribe's terminology!
No comments:
Post a Comment