Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Lessons Learned from Architecture Reviews

Lessons Learned from Architecture Reviews



In this presentation, Rebecca Wirfs-Brock presents some practical lessons she has learned from doing architectural reviews. Many times projects are not delivered in time, or have quality problems or have an incomplete set of features due to architectural flaws. The reviews are meant to highlight existing risks and strengths of the architecture, and to reveal issues initially neglected.


Rebecca Wirfs-Brock invented the way of thinking about objects known as Responsibility-Driven Design. She is lead author of the classic Designing Object-Oriented Software, and Object Design: Roles, Responsibilities and Collaborations. She is the design columnist for IEEE Software and past board member of the Agile Alliance.

About the conference

JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.

Recorded at:

Jul 29, 2008

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Thanks for sharing the experiences

    by Dinkar Gupta,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Thanks rebecca for sharing these lessons with us. I have noted all of these and am going to consider these while I undertake reviews of architecture or present my own architecture designs for review. we have also experienced some of these things mentioned by you - especially the first one. Majority of people consider architecture review (audit) as a means of validating the technology choices.

    it would be great if you can also share some of your experiences of design reviews of object oriented applications! This would be of great value considering majority of architects are regularly engaged in application designs using object oriened paradigm.

  • Cost versus good architecture

    by Prasanna Nippani,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This is a very good presentation. I have been looking for something like this for quite some time. I would like to learn from your experience on how to effectively deal with the situations where cost becomes a barrier to architecture.

  • Painful

    by Randall Cook,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    There was about 20 minutes of content in this presentation, if that. The presentation style was poor, with the speaker exuding tension and nervousness. If the unit test I was running had finished sooner, I wouldn't have watched the whole thing.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p