The Role of a Solution Architect in a Software Project

Transcript

1. Role of a Solution Architect in a Software Project 1/51 EPAM Systems
2. 2/51 EPAM Systems
3. About me 3/51 EPAM Systems
4. About me • Vladimir Ivanov 3/51 EPAM Systems
5. About me • Vladimir Ivanov • Working as a Solution Architect 3/51 EPAM Systems
6. About me • Vladimir Ivanov • Working as a Solution Architect • Certified Google Cloud Architect 3/51 EPAM Systems
7. About me • Vladimir Ivanov • Working as a Solution Architect • Certified Google Cloud Architect • Speaker 3/51 EPAM Systems
8. About me • Vladimir Ivanov • Working as a Solution Architect • Certified Google Cloud Architect • Speaker • PC of Mobius 3/51 EPAM Systems
9. Let's get to know each other! 4/51 EPAM Systems
10. What is the motivation of our work? 5/51 EPAM Systems
11. Helping business to grow by solving their problems with technology 6/51 EPAM Systems
12. The way we do it is completing projects 7/51 EPAM Systems
13. 8/51 EPAM Systems
14. RFI Request for information 9/51 EPAM Systems
15. RFI 10/51 EPAM Systems
16. RFI • Answer the questions 10/51 EPAM Systems
17. RFI • Answer the questions • Contact the architects of related fields 10/51 EPAM Systems
18. RFI • Answer the questions • Contact the architects of related fields • Perform the required research 10/51 EPAM Systems
19. RFP Request for proposal 11/51 EPAM Systems
20. RFP 12/51 EPAM Systems
21. RFP • Understand the business value 12/51 EPAM Systems
22. RFP • Understand the business value • Create a solution architecture 12/51 EPAM Systems
23. RFP • Understand the business value • Create a solution architecture • Understand which teams are necessary to implement that solution 12/51 EPAM Systems
24. RFP • Understand the business value • Create a solution architecture • Understand which teams are necessary to implement that solution • Come up with the resource plan 12/51 EPAM Systems
25. RFP • Understand the business value • Create a solution architecture • Understand which teams are necessary to implement that solution • Come up with the resource plan • Present a proposal 12/51 EPAM Systems
26. 13/51 EPAM Systems
27. Discovery 14/51 EPAM Systems
28. 15/51 EPAM Systems
29. First steps 16/51 EPAM Systems
30. First steps • Getting to know the organization and key people 16/51 EPAM Systems
31. First steps • Getting to know the organization and key people • Getting to know the business and it's goals 16/51 EPAM Systems
32. First steps • Getting to know the organization and key people • Getting to know the business and it's goals • Build trust 16/51 EPAM Systems
33. Requirements gathering 17/51 EPAM Systems
34. Requirements gathering • Functional 17/51 EPAM Systems
35. Requirements gathering • Functional • Non-functional 17/51 EPAM Systems
36. Requirements gathering • Functional • Non-functional • Constraints 17/51 EPAM Systems
37. Functional requirements! 18/51 EPAM Systems
38. Functional requirements! • The system should allow an administrator to login 18/51 EPAM Systems
39. Functional requirements! • The system should allow an administrator to login • The system should show the list of users 18/51 EPAM Systems
40. Non-functional requirements 19/51 EPAM Systems
41. Non-functional requirements • The application should use TLS 1.2 for all connections involving user-data 19/51 EPAM Systems
42. Non-functional requirements • The application should use TLS 1.2 for all connections involving user-data • The application should open the page under 0.5 second 19/51 EPAM Systems
43. Non-functional requirements • The application should use TLS 1.2 for all connections involving user-data • The application should open the page under 0.5 second • The application may not be available 1 hour per year 19/51 EPAM Systems
44. Constraints 20/51 EPAM Systems
45. Constraints • The app should be deployed to customers' Azure cloud 20/51 EPAM Systems
46. Constraints • The app should be deployed to customers' Azure cloud • The app should implement 152 federal law 20/51 EPAM Systems
47. Constraints • The app should be deployed to customers' Azure cloud • The app should implement 152 federal law • The app should be developed with Xamarin technology 20/51 EPAM Systems
48. Some of them will change the architecture of the solution. 21/51 EPAM Systems
49. Every additional 9 of availability doubles the complexity of a target system. 22/51 EPAM Systems
50. 23/51 EPAM Systems
51. Source of requirements 24/51 EPAM Systems
52. Source of requirements • Stakeholders 24/51 EPAM Systems
53. Stakeholders are the people who have an interest in the project 25/51 EPAM Systems
54. Stakeholders are the people who have an interest in the project • Customer business representatives 25/51 EPAM Systems
55. Stakeholders are the people who have an interest in the project • Customer business representatives • Delivery organization business representatives 25/51 EPAM Systems
56. Stakeholders are the people who have an interest in the project • Customer business representatives • Delivery organization business representatives • Technical folks from both sides 25/51 EPAM Systems
57. Stakeholders are the people who have an interest in the project • Customer business representatives • Delivery organization business representatives • Technical folks from both sides • End-users 25/51 EPAM Systems
58. Stakeholders are the people who have an interest in the project • Customer business representatives • Delivery organization business representatives • Technical folks from both sides • End-users • Competitors 25/51 EPAM Systems
59. In order to gather requirements you need to talk to stakeholders. The stakeholders identification is one of the main responsibilities of a Solution Architect. 26/51 EPAM Systems
60. 27/51 EPAM Systems
61. What’s an architecture? The set of structures needed to reason about the system, which comprises software elements, relations among them, and properties of both. 2 2 Software Architecture in Practice, 3rd Edition, Bass, Clements, Kazman, Addison-Wesley 28/51 EPAM Systems
62. What the hell it means? 29/51 EPAM Systems
63. What the hell it means? • Architecture is a key to the system properties, an end user is concerned about 29/51 EPAM Systems
64. What the hell it means? • Architecture is a key to the system properties, an end user is concerned about • Or product owner thinks so 29/51 EPAM Systems
65. What the hell it means? • Architecture is a key to the system properties, an end user is concerned about • Or product owner thinks so • There are no bad or good architectures; there are ones that fit the target system properties 29/51 EPAM Systems
66. ASRs Target system properties which affects architecture are unsurprisingly called architecturally significant requirements. 30/51 EPAM Systems
67. 31/51 EPAM Systems
68. How to identify ASR? 32/51 EPAM Systems
69. How to identify ASR? • From requirements documents 32/51 EPAM Systems
70. How to identify ASR? • From requirements documents • By interviewing stakeholders 32/51 EPAM Systems
71. How to identify ASR? • From requirements documents • By interviewing stakeholders • By understanding the business goals 32/51 EPAM Systems
72. How to identify ASR? • From requirements documents • By interviewing stakeholders • By understanding the business goals • Utility tree! 32/51 EPAM Systems
73. Utility tree 33/51 EPAM Systems
74. 34/51 EPAM Systems
75. 35/51 EPAM Systems
76. 36/51 EPAM Systems
77. How to document architecture? 37/51 EPAM Systems
78. How to document architecture? • Non-formal notations with general purpose diagramming 37/51 EPAM Systems
79. How to document architecture? • Non-formal notations with general purpose diagramming • Semi-formal notations with standardized notation 37/51 EPAM Systems
80. How to document architecture? • Non-formal notations with general purpose diagramming • Semi-formal notations with standardized notation • Formal notations with precise semantics 37/51 EPAM Systems
81. 38/51 EPAM Systems
82. 39/51 EPAM Systems
83. 40/51 EPAM Systems
84. 41/51 EPAM Systems
85. Documenting the architecture is the third most important activity for an SA. 42/51 EPAM Systems
86. 43/51 EPAM Systems
87. Construction 44/51 EPAM Systems
88. Construction • Bootstrap the development 44/51 EPAM Systems
89. Construction • Bootstrap the development • Define and setup quality gates 44/51 EPAM Systems
90. Construction • Bootstrap the development • Define and setup quality gates • Create PoCs 44/51 EPAM Systems
91. Construction • Bootstrap the development • Define and setup quality gates • Create PoCs • Share knowledge 44/51 EPAM Systems
92. 45/51 EPAM Systems
93. Transition 46/51 EPAM Systems
94. Transition • To production 46/51 EPAM Systems
95. Transition • To production • To other team 46/51 EPAM Systems
96. So... The person who identifies stakeholders, gathers ASRs, builds the architecture, shares it and bootstraps some of the systems components is usually called Solution Architect. 47/51 EPAM Systems
97. 48/51 EPAM Systems
98. 49/51 EPAM Systems
99. Links 50/51 EPAM Systems
100. Links • Books is Software Architecture: https:/ /medium.com/@nvashanin/books-in-software- architecture-6ad974e524ce 50/51 EPAM Systems
101. Links • Books is Software Architecture: https:/ /medium.com/@nvashanin/books-in-software- architecture-6ad974e524ce • Amazon Cloud Architect Associate: https:/ /www.udemy.com/aws-certified-solutions-architect- associate/ 50/51 EPAM Systems
102. Links • Books is Software Architecture: https:/ /medium.com/@nvashanin/books-in-software- architecture-6ad974e524ce • Amazon Cloud Architect Associate: https:/ /www.udemy.com/aws-certified-solutions-architect- associate/ • Google Cloud Architect Professional: https:/ /www.coursera.org/specializations/gcp-architecture 50/51 EPAM Systems
103. Me 51/51 EPAM Systems
104. Me • https:/ /twitter.com/vvsevolodovich ! 51/51 EPAM Systems
105. Me • https:/ /twitter.com/vvsevolodovich ! • https:/ /medium.com/@dzigorium " 51/51 EPAM Systems
106. Me • https:/ /twitter.com/vvsevolodovich ! • https:/ /medium.com/@dzigorium " • https:/ /mobiusconf.com/ 51/51 EPAM Systems
107. Me • https:/ /twitter.com/vvsevolodovich ! • https:/ /medium.com/@dzigorium " • https:/ /mobiusconf.com/ • Vladimir_Ivanov4@epam.com 51/51 EPAM Systems