All Applications Need a Detailed Architecture

When developing a solution, there might be some sort of mechanical, compute or software element. This is the technical part of the solution. The Technical Architect will put together the software modules, describe the infrastructure the software will be hosted on, network components, and any other individual components that makes up the physical and/or virtual/cloud environments.

The Technical Architects will put together the build guides and will get deeply involved with vendors to discover the optimal operating environment and configuration to get the most out of their applications and hardware.

If the strategy is to use Cloud as much as possible, the Technical Architect will be able to select the best offering for the functions needed for the solution. In some ways, the Technical Architect has never had so much choice on tap. Working with the Solution Architect, the Technical Architect will make the decisions on the functions provided which will meet the requirements. If a function doesn’t quite fit, maybe a change to the business processes might make the function fit better at no extra charge.

There are advantages in using an independent Technical Architect. They can spend the time becoming embedded in the vendors to get the most out of the system being deployed, while fully appreciating the needs of the business. There are times when an integrator’s own people are great, but an independent Technical Architect will provide a more balanced view of the system, detaching themselves from all the shiny parts and concentrate on just what is needed. This detachment can also extend to individuals within the organisation who selected a particular application or hardware, where their thinking maybe a little biased. There is no problem with this bias as it brings enthusiasm to the project. But this needs to be tempered to allow it to be deployed smoothly, gradually, to use the functions most important to the solution.

Let's Talk Today