Thanks Sir, really appreciate your videos! Thinking as a solution consultant (technical implementer) that aspires to become an architect, What would you do to seek growth into such role if instead of a developer, you were an implementer to become an architect? How would your methodology adapt if we have fixed vendor (think of SAP / Workday/ Salesforce etc) or those large systems that are as implementers we are fixed? Is there any difference in Your analysis?
I'm so happy you asked this question! Understanding your business needs and translating those needs to architectural characteristics is just as important when using large systems like you mentioned and also for doing a more effective product evaluation. A company may try to sell you on their product because "it's the fastest one on the market", but maybe performance isn't important to you - data integrity is. The approach is the same for custom development as well as product selection and configuration.
I think in the list of the "user satisfaction" related architecture characteristics - the "usability" should be one of the most important. Strange I don't see it in the list.
Usability is often a design consideration rather than an architectural one, particularly as it relates to the user interface and web design. Usability becomes architectural when it changes the *structure* of the system - for example, adding other kinds of UIs (apple watch, mobile app, web, etc.) and the use of patterns such as the BFF pattern.
As always, super helpful. Thank you
Glad you found it useful!
Thanks Sir, really appreciate your videos! Thinking as a solution consultant (technical implementer) that aspires to become an architect, What would you do to seek growth into such role if instead of a developer, you were an implementer to become an architect?
How would your methodology adapt if we have fixed vendor (think of SAP / Workday/ Salesforce etc) or those large systems that are as implementers we are fixed? Is there any difference in Your analysis?
I'm so happy you asked this question! Understanding your business needs and translating those needs to architectural characteristics is just as important when using large systems like you mentioned and also for doing a more effective product evaluation. A company may try to sell you on their product because "it's the fastest one on the market", but maybe performance isn't important to you - data integrity is. The approach is the same for custom development as well as product selection and configuration.
I think in the list of the "user satisfaction" related architecture characteristics - the "usability" should be one of the most important. Strange I don't see it in the list.
Usability is often a design consideration rather than an architectural one, particularly as it relates to the user interface and web design. Usability becomes architectural when it changes the *structure* of the system - for example, adding other kinds of UIs (apple watch, mobile app, web, etc.) and the use of patterns such as the BFF pattern.
If you ask the business about which *ilities are crucial they will choose all... 😮
So true!!!!
1st view
Congrats! 🙂