How to Design an IT Solution Architecture
The Stronger the WHY, the easier the HOW becomes — Jim Rohn
--
Every time here and then, there are always questions like,
“How do you corporate as both Sales and Pre-Sales roles” or
“How do you work closely with Pre-sales as a Sales without the technical know-how?”
This step-by-step guide is intended to guide you through the processes of how a proper IT solution is constructed from my experience.
It boils down to 5 steps,
- Business Architecture — Creativity and Consistency on Business Objective
- Application Architecture — Concerning “Concerns”
- Data Architecture — Understanding Needed Data Model and Design
- Infrastructure Consideration — Based on the above Architecture
- Summary Sheet — All things needed in one place
It takes the journey from Requirements gathering to final quotation and Scope of Work.
Such Practice is common to a Sales, Pre-Sales and Business Analyst. Below, I will be going through the responsible roles involved in each section.
Business Architecture
The Creativity and Consistency on Business Objective
Whenever there is a discussion of a project, there’s already a Business Objective aligned with it. With the right questions to ask and unveil to the clients, we can start drafting a Business Architecture.
Business Architecutre is referring to “a describable level of processes and logic within the architecture.” From mapping the requirements into a high level of Products/Services.
This is intended to provide a quick capture of business requirements and propositions.
Goal: Stand out the pain points and deliverables (outcomes)
Roles Involved: Sales (80%), Pre-Sales (20%)
Application Architecture
Concerning “Concerns”
A Product/Service level of processes and logic within the architecture.
