copy code,drag or close
Solution Architecture.
Existing systems are the systems we are often trying to improve upon, and so often they dictate many aspects of the final solution architecture.
By assumming a similar approach to that used in science, physics being the one I am most failiure with, we can imagine starting with the data, then the software models and then the hardware and communications required.
That way we can design the system from concept to concrete but all within a simulation.
This approach is akin to how the Gas Laws were arrived at, by imagining an ideal world where molecules had particular properties and that temperature stayed constant allowing the effect that pressure had on volume.
With a similar approach, by ignoring certain constraints an ideal database application solution architecture can be arrived at.
Once that is achieved, and not before, then the ideal Web Application solution architecture can be visualized.
There's not shortage of visualisation and modelling tools to help at this stage.
Once you've arrived at an ideal solution architecture you can usefully compaire to the exsiting system then you can map the ground out between where you are and where you want to get to, and what the actual deliverable solution architecture will be.