Business users and architects must use a common language to properly communicate business goals and objectives. However, architects talk in “-ilities”, or non-functional quality attributes, and business users talk in terms of business needs. Using these two languages leads to confusion, and ultimately business goals that are not met by the architecture. In this lesson Mark Richards answers a question from a recent software architecture training class - how does an architect translate non-functional quality attributes (“-ilities”) to business users? Mark shows how the “-ilities” architects use do in fact translate to business needs and what those mappings are.
Reference Links:
Software Architecture Monday: https://bit.ly/3dadEe3
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2