The path to become a Solution Architect

A Solutions Architect is an expert in many categories. They should have hands-on experience in multiple industries and across several disciplines. They can master a variety of hardware platforms including mainframes, distributed platforms, desktops, and mobile devices. Akin to that, they should also possess skill and understanding of a variety of Operating Systems. A broad and deep understanding of Databases is also require. Solution Architect is the High level Solution designer that juggle around information, infrastructure, software, and business

Yes. I have taken TOGAF certification, IASA Architect ( Foundation), IASA Business Architect, ugggh. Now IASA Solution Architect. What does that do for me, in terms of upgrading of my skill level?

What is Solution Architect Job Role?

Solutions architect must have strong leadership and communication skills, as well as?both technical and business knowledge.

1. "Bridging the current state to the future state of the solution ecosystem." Yes. I have done more than 30 projects using Artificial Intelligence each one worth 100k to 200k in a span of 7 months.
2. Manage the alignment with other specialisation architects (Business, Software, Infra, Info)
3. Proficient in producing documentations & artifacts that reflect the value of the tech strategy & value. Yes. Lots of documentation work has been created to have a reusable technology model for scalability and availability.
4. Collaborating with other professionals to determine functional and non-functional requirements for new software or applications
5. Using tools and methodologies to create representations for functions and user interface of desired product
6. Developing high-level product specifications with attention to system integration and feasibility
7. Solves complex problems in an organization by designing or modifying technology architecture and testing the integration of software in these designs for correct functionality

Key Activites of a Solution Architect

1. BA – Analysis of As-Is Business Technology Strategy and start planning for the To-Be State in relevance to business goals
2. SA – Start getting acquainted, engaging in key projects, assessment of as-is solutions and how to improve them
3. IA – Collate resources list of data storage for governance and compliance.

Hope that this little activity list can excite you to join our ranks of solution architecturing.

The Key Takeaway from the course is the ability to better tool or artefact[TOGAF] or model [IASA]. to represent view and viewpoint of an architecture. and qualify the best model for the appropriate stakeholder.

Second Takeaway is to choose projects base on business values that the project contribute to the company objective, and to make use a domain experts into defining the problems and create a stakeholder viewpoint that will excite them to say YES.

Working on the Workshop on a fictional Ticklebank, this series of models are our reply to the workshop requirement.

Architecture of a 5g IOT fridge-wearable eWallet - Solution.

Creation of different viewpoints for different stakeholders. namely logical view, development view, physical or deployment view and process view.

Business Architecture - Using the Benefit Dependency Network to define and map the Business objective to Business benefit to Business changes, and Change enabler.

Architecture Viewpoint and Perspective

Process Viewpoint

Functional Viewpoint

Development Viewpoint

Information Viewpoint or Information diagram of a IOT fridge Solution

Actually in the 4 days workshop, we created more than 30 diagrams surrounding the fictional project. and all the diagrams are timeboxed in 10 minutes.

Extremely intensive course for Architect, and intensive for me cos I have to juggle between working and studying at the same time. But It is extremely helpful in creating documentation relevant to the various stakeholder, regarding the solutioning.

Insight in the 4 Day Course.

ATDSOLUTION IASA SOLUTION ARCHITECTURE

The role of an architect is to be the technology and business leader that make technology work for the business, by bridging the current state to the future state, and get the solutioning as the business driver.

One insight to me was: There is (almost) always a tool. The answer is not in knowing A tool all the time, nor being scared of a new unknown tool. The key is to see through, find out what problem the tool is there to solve. Identify the purpose of the tool in the current context, how it satisfies the problem it's there for. If it's unsatisfactory, one might find out how the tool was selected, why it was selected. Then work out the gaps between current and satisfactory. Finally - if the tool does not fit, don't make the problem to fit it. There is always guidelines, but there is no answer. the answer is always base on the most relevance and brings highest business value.

The Key Takeaway from the course is the ability to better tool or artefact[TOGAF] or model [IASA]. to represent view and viewpoint of an architecture. and qualify the best model for the appropriate stakeholder.

Second Takeaway is to choose projects base on business values that the project contribute to the company objective, and to make use a domain experts into defining the problems and create a stakeholder viewpoint that will excite them to say YES.

About Me

I have completed Business Architect pathway and learning, I took the certification for both ScaledAgile Lean Portfolio Management and Solution Architect pathway. And this article will be my first evolving attempt to identify the differences, integrate the differences and attempt to bring traditional architecturing into agile architecturing.

See what I have done in the last 6 months.