Solution Architecture: Foundations

Thanks to the original article : https://medium.com/@yam-yam-architect/solution-architecture-foundations-fb4af948bb02

Tips for becoming a better solution architect

What is Solution Architecture?

The role of a Solution Architect (SA) is to join the dots. To be the conduit between the technical teams and the business. Liaise with technology vendors, and ensure that any emergent design aligns with the strategy.

Contrary to popular belief, the architect is?not?an expert. Their value is a broad but shallow understanding of solutions vs deep technical knowledge.

For a better explanation of breadth vs depth, check out?this post ?by Neal Ford.

The SA should facilitate conversions between specialists to identify a fit-for-purpose solution.

Responsibilities

The list below was taken from?Glassdoor’s ?SA job description.

• Analyse current technologies used within the company and determine ways to improve
• Document and monitor requirements needed to institute proposed updates
• Work closely with Information Technology professionals within the company to ensure hardware is available for projects and working properly
• Propose and establish framework for necessary contributions from various departments
• Account for possible project challenges on constraints including, risks, time, resources and scope
• Work closely with project management teams to successfully monitor progress of initiatives
• Provide detailed specifications for proposed solutions
• Define clear goals for all aspects of a project and manage their proper execution

Key Skills

• Technical breadth
• Leadership
• Ability to communicate to different stakeholders
• Strong analytical skills
• Commercial awareness
• Project management skills

Enterprise vs Solution vs Domain Architecture

A large enterprise will typically have a variety of architects, each with its area of focus and expertise.

Enterprise Architects

Enterprise Architects (EA) are responsible for ensuring that the technology aligns with the needs of the business.

Solution Architects

Solution Architects are focused on a specific business problem/solution. They’ll often (but not always) consult with Enterprise Architects to ensure that proposed solutions align with the strategic needs of the business.

Domain Architects (includes Technical Architects)

Domain Architects are specialists that operate within a particular domain.

Examples: Technical Architect, Integration Architect, Data Architect.

Tips to becoming a better Solution Architect

Here are some tips and tricks to help you become a better architect.

Communication

• When discussing a complex problem or solution, use visual aids.
• Be concise and avoid technical jargon.
• Use analogies to describe complex topics.
• Pause for questions.
• Playback understanding.
• Understand the audience and tailor the communication. For example, if you’re speaking to a delivery manager, their key concerns will be effort and cost. Don’t bore them with technical detail.

Analysis and Design

• Apply first principles thinking: Don’t assume anything; Start with the facts.
• Move from top to bottom, i.e. start with the business problem before looking at the technical solution.
• Model the solution from multiple viewpoints, e.g. capability view, application view, technology view etc.
• Validate the solution views with the relevant stakeholders. The stakeholders?must?understand the views; otherwise, you’ll be misaligned on the design.
• Apply second-order thinking: Think holistically beyond the short-term. Could there be any unintended consequences with the proposed solution?

Documentation

Many new architects (including myself) are surprised by the amount of documentation required.

Documentation is essential; it describes the?what,?how?and?why.

Documentation doesn’t need to be onerous and, if done well, can set you apart from your peers. Most people?hate?documentation.

If you wish to improve your technical writing skills, I strongly recommend checking out this free self-study course from Google:?https://developers.google.com/tech-writing .

Here are tips for improving your documentation:

• Understand the objective and audience of the document, i.e. what information does it need to convey and to who?
• Keep it concise and to the point.
• Use consistent terminology.
• Chapters should be self-contained. Most readers don’t read technical docs/books linearly; they will jump to a section they’re interested in. Ensure that each chapter has sufficient context, includes a visual and provides a brief summary. Include hyperlinks to prerequisite chapters.
• Use lists, visuals, and tables where applicable.
• Use tools like Grammarly as a writing aid.
• Use document collaboration features to elicit feedback.

Governance

If you’re an architect working in a large enterprise, you will have presented a solution to a committee of representatives from across the business. Often referred to as Architecture Review Board (ARB) or Design Authority (DA).

This is often a tedious process but an important one. Without the board’s approval, you’ll be unable to proceed to the next stage.

Here are some?tips?for getting through the process:

• Understand?who?from the committee is likely to pick holes in the solution. If possible, meet with them before the ARB/DA and walk them through the design. If they raise any concerns, you can update the design or prepare responses.
• If the solution uses a new pattern or technology, get validation from the vendor. When presented to the ARB/DA, vendor validation will add weight to the design.
• The vendor will want to ensure the customer uses their technology as intended. They can also share insights from customers who have implemented similar solutions.

Learning and Development

“You will not make any significant advances in life based on what you already know.”

-?Charlie Munger

Learning should be a life-long endeavour. The majority of people I’ve met seem to lose their zest for learning. In my opinion, this is a mistake. The more you know, the more valuable you are.

Another mistake (IMHO) I see many architects making is focusing purely on developing their technical prowess. Whilst technical skills are helpful, the role of architecture is so much more.