Technical architecture is the finest of detail
Once the solution has been decided, the technical architects can start to build the designs for the individual components that will form the solution. This is where integrations between each component, including the users, third party systems, and external parties begins to take shape. Up until this stage of the design, it has all been fluffy clouds and ideas, linked back to the business.
How detailed the technical architecture will depend on where the technologies will be deployed. For example, if a majority of your systems are on-premises, then rack designs, power consumption figures calculated to ensure supplies are not breached, server designs, and detailed software configurations are documented. On the other hand, if your new system is cloud-based, VPC configurations, deployment scripts, SaaS enrolment, environmental build scripts (plus software configuration details) are all created.
Techniques to get the configuration right vary but they all have the same aim which is to develop a Minimum Viable Product, or MVP. This MVP will be the first step in creating something concrete for the users and the first opportunity they will have to see the new system. Technical Architects will be key to supplying engineering with exactly what needs to be built. Infrastructure details, software configurations, application architecture, scripts, deployment configurations, all to bring together the whole solution.
Technical Architects will work on areas of the solution to which they are most experienced. It would be difficult to find a single technical who would be fully knowledgeable about every aspect of the solution. They would have a broad knowledge-base, yes, but they will specialise in one or two technical areas, such as Oracle data base, Microsoft Active Directory, Amazon Web Services, desktop services, Salesforce, etc.
Building a solution can be likened to building a new housing estate. The council (the business) will have a vision for housing to keep pace with population needs (the board will know what the future of the business will need to be), and therefore will need to know where the best location to build a new housing estate (the Enterprise Architect will guide the board where best to invest to increase value). Once the council has identified a location, an architect (solution architect) will draw up plans for what the housing estate (solution) will look like. The architect will be constrained by things like roads, school, medical, telecommunications, electricity, water, and gas capacity (guardrails, local capacities, legislative, and government requirements, and do on). As the design is approved by the council and other authorities (design authorities), the specialists of building houses (technical architects) are brought in. The technical designs will be supplied to builders (engineering) who will use the designs to build the houses (system components).
Thinking of the context of the technical architect in this way highlights the significance of them. Being the subject matter expert, means they are a rich source of design information to the solution architect, and the more they work together, the more likely will the solution be successful.
Provantage Technical Architecture
Technical Architecture can take many forms, from in-depth knowledge of one or two particular complex applications, to understanding networks, security, identity, Zero Trust Architectures, and so on. Provantage has those skills, having created many technical architecture designs for our clients.
If you need that extra bit of help with technical design, please call today to discuss your issues.