Lesson 188 - Identifying Architectural Characteristics

Out of the hundreds of architectural characteristics out there, how do you know which ones are important to your particular system? Is scalability critical? How about responsiveness, or availability, or even testability? In this lesson I discuss various techniques for identifying which architectural characteristics are important to your system, and how to communicate those to your product team and business stakeholders.

[Rcrdslns]

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?

[sant]

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.

[gogolglaus]

If you ask the business about which *ilities are crucial they will choose all... 😮