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 solution architect focused on making usable applications. A proponent of polyglot programming, Nate has written two books on Ajax and speaks regularly at various worldwide conferences, No Fluff Just Stuff symposia, universities, and Java user groups. In addition to his day job, Nate is an adjunct professor at the University of Minnesota, where he teaches students to embrace dynamic languages. Most recently, Nate coauthored Presentation Patterns with Neal Ford and Matthew McCullough.
Comments on this page are now closed.
©2017, 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. • email@example.com