Each of the eight "portholes" into the box offer a viewpoint that is tailor made to a particular responsibility in the solution's system design. (I'll talk bout viewpoints and other stuff in a short while)
For example, the front/top/left corner... sorry... hole is looking into the box from the functional/application/logical viewpoint, the most abstract view point we use - and an amazingly powerful way for a software engineer to focus on what matters to them, removing all extraneous information from their mind as they work out the shape and structure of "their application", without worrying (too much!) about it's deployment, implementation technologies and technical services needed to keep it going.
Compare that to the back/bottom/right hole - the operational/technical/physical viewpoint, in which all those "previously ignored" issues have to be grappled with - by the systems engineer, things such as "how will we make sure the data's where it needs to be?" and "where will we run the application - here or there?"
But hold on - surely the software engineer also worries about these things?
YES!
But from different perspectives to that of the systems engineer - they look into the box from the left hand side's four holes - so if they choose to think about how their application will be supported by "infrastructure", they'll use the (bottom/left/front) technical/functional/logical viewpoint as a way of understanding the technical implications and functional requirements placed on the infrastructure by their application and data design - such as specifying the behaviour of the underlying infrastructure needed to supply, backup and maintain their data, or to maintain their application's transaction integrity.
No comments:
Post a Comment