Feasibility is an often overlooked architectural characteristic. It identifies how feasible your solution is based on time, budget, and skillset constraints. It is also linked to requirements handed down from product owners or business stakeholders. Many times, what architects and development teams receive are not requirements, but rather solutions. Through some story telling and real-world examples, I show in this lesson how to identify real requirements, particularly when a requirement doesn’t seem feasible.
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
Watch video Lesson 181 - Feasibility and Questioning Requirements online without registration, duration hours minute second in high quality. This video was added by user Software Architecture Monday 25 February 2024, don't forget to share it with your friends and acquaintances, it has been viewed on our site 3,030 once and liked it 132 people.