In this presentation we will cover:
* What is Solution Architecture and how it differs from other architectures
* What is good and what is bad for SA, tips & tricks from our experience
2. About Me
• Developer and Architect in enterprise Java
sector for many years
• Engineer and Practitioner by heart
• Solution Architect in EPAM’s Java
Competency Center
• Spare time Manager
9. Definition
The solutions architect is responsible for translating the requirements
created by functional analysts into the architecture for that solution and
describing it through the set of architecture and design artifacts.
Those artifacts are then used by the rest of the development team to
implement the solution.
The process of defining architecture by the solutions architect often involves
selection of the most appropriate technology for the problem being solved.
https://en.wikipedia.org/wiki/Solutions_Architect
12. Solution Architect
Expectations
• Understand my business needs and propose solutions
• Know trends and fill my technology knowledge gap
• Know typical and proved solutions
• Propose different options, compare them and help me chose
• Help with actual implementation planning
13. Solution Architect
Values
• Clear, completed and confirmed requirements
• Low cost of solution selection through models and prototypes
• Wide vision and expertise for educated choices
• Shared final solution understanding
• Architecture governance
14. Solution Architect
Skills
• Clarification, analysis and documentation
• Communication, negotiation and facilitation
• Visualization and explanation
• Technical Leadership
• Des of technologies and solutions
