Developers focus on functional requirements, but once you step into the architect role, your world is increasingly inhabited by the “-ilities”—the nonfunctional or quality attributes of a software system. But which “-ilities” matter and which don’t? As much as we may want to turn every knob up to 11, many “-ilities” are inversely related; maximize one, and you by definition minimize another.
Nathaniel Schutta explores approaches to architectural problems and explains how to best document the inevitable decisions we arrive at. Along the way, you’ll get the opportunity to try and balance nonfunctional requirements yourself.
Nathaniel T. Schutta is a software architect focused on cloud computing and building usable applications. In addition to his day job, he’s an adjunct professor at the University of Minnesota, where he teaches students to embrace dynamic languages. A proponent of polyglot programming, Nate has written multiple books, including Presentation Patterns, with Neal Ford and Matthew McCullough, written to rid the world of bad presentations. He’s also appeared in various videos and is a seasoned speaker, regularly presenting at conferences worldwide, No Fluff Just Stuff symposia, meetups, universities, and user groups.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org