Skip to main content

A Blueprint for Success

Article

A Blueprint for Success

Implementing an architectural review system

Article by Daniel Starr, Gus Zimmerman | Comments: (0) | Thu, 08/01/2002 - 12:33pm
Summary:

The most costly product defects are often a problem of software architecture. Testing your architecture is a crucial, but often overlooked, step in product development. Learn how to apply Lucent's model to implementing your own architectural review process.

You run a good software development shop. You validate your system design with reviews. You inspect your code and test the finished product, using a carefully specified test set. Still, you sometimes uncover a defect so serious and so fundamental that you have to start over from scratch, wondering "What were we thinking?"

Perhaps it's time to take a closer look at your architecture. Much like civil (building) architecture, systems architecture provides a conceptual design solution to a specific problem.

Editor's Note: 
ALM changed from paid to free because this was featured free on www.stqemagazine.com
About The Author: Daniel Starr

After twenty-six years in telecommunications, Daniel Starr retired from Bell Labs in 2001. He now is writing, riding motorcycles, and learning to play the bagpipe. He also consults in reviews, retrospectives, and "thinking like a systems architect." You can reach the kilted biker/piper/consultant at dcstarr@ntsource.com.

About The Author: Gus Zimmerman

Gus Zimmerman is the Director of the SARB at Lucent Technologies, Naperville, Illinois. After twenty-two years developing telecommunications systems, he is now responsible for providing system architecture education services and reviews for Lucent Technologies R&D projects worldwide. Email: ghzimmerman@lucent.com