Something for Everyone at SATURN 2012

Whether you are an aspiring software architect or an experienced practitioner, the SATURN 2012 Conference offers courses, presentations, tutorials, and talks tailored to your level of knowledge and experience.

Relative newcomers to architecture-centric engineering and development can take the introductory course in the SEI Software Architecture Curriculum, Software Architecture: Principles and Practices (SAPP) on Monday and Tuesday, May 7-8 at a discounted price. This popular course, offered each year at SATURN and taught this year by Rob Wojcik of the SEI, introduces participants to the essentials of software architecture. Also offered at SATURN this year is a half-day tutorial on Tuesday, May 8 by Peter Eeles of IBM Rational titled Software Architect 101. This tutorial (T1) provides attendees with a solid grounding in all aspects of software architecture and a framework on which they can build a deeper understanding of the role of the architect. Other Tuesday tutorials cover effective stakeholder collaboration (T2), integration of software architecture-centric methods into object-oriented analysis and design (T3), and architectural implications of cloud computing (T4).

Webinar, Architecting Software the SEI Way: Now Available on Demand

More than 630 people from 68 countries joined the Carnegie Mellon Software Engineering Institute (SEI) three-hour, live virtual event entitled Architecting Software the SEI Way: Essential Steps Toward Mastery on February 28, 2012. The three hour-long webinars from the event are now available for on-demand viewing at http://www.sei.cmu.edu/go/architecting-software-the-sei-way/.

In the three webinars, SEI researchers Rob Wojcik, Felix Bachmann, and John Klein share insights from their work, including

• what software architecture is and why it is important
• why architecture evaluation methods can continuously ensure the creation of successful systems
• how a system-of-systems perspective improves the analysis of enterprise architectures

To watch the webinar recordings, download the webinar slides, and get more information about software architecture, please visit http://www.sei.cmu.edu/go/architecting-software-the-sei-way/.

SATURN 2011 Keynote: Dave Thomas, The Intimate Relationship Between Architecture and Code: Architecture Experiences of a Playing Coach

Notes by Bill Pollak, Peter Foldes, and Jack Chen

Dave Thomas, CEO, Bedarra Research Labs
The Intimate Relationship Between Architecture and Code: Architecture Experiences of a Playing Coach

We have architects, but there is still a problem. This can’t be us, because we’re all great. We went to a conference.

No one wants their software to stink. I’ll talk about things I think are wrong.

Why does our architecture smell?

Observations from the WICSA/ECSA 2009 Conference

Last month I attended the Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture (WICSA/ECSA 2009).

This was the eighth WICSA offering in a series of conferences beginning in 1999.  

Architecture Competence Session

Why is it that some organizations have very talented architects, but they are not consistently successful producing architectures and systems? Isn’t it enough to have the best people working on these hard architecture problems? Maybe, but maybe not…

Panel: Exploring Boundaries Among Enterprise, Systems, and Software Architecture

Facilitator: Paul Clements, SEI

Panelists: Mark W. Maier, Rebecca Wirfs-Brock, John A. Zachman, and Randy Case (Raytheon)

Panel: Exploring Boundaries Among Enterprise, Systems, and Software Architecture

Wednesday, May 6, 2009, 1:00 pm

View Panel abstract >

Zachman Framework for Software Architecture?

Just heard the very interesting keynote from Zachman at the conference, and there is one thought I cannot get out of my mind.

The Zachman framework is about architecting the enterprise in terms of What?, How?, Where?, Who?, When?, and Why? from several different perspectives, such as the owners, architects, engineers, etc.

I see several similarities that software architecture tries to answer, therefore would it make sense to use the Zachman framework for software only products? I could see for example to structure the architecture documentation in this way. It might help to easily extract the information needed for the different stakeholders, such as the management, the developers, etc.

Any one with experience in this topic? Any thoughts?

- Felix Bachmann, SEI

SATURN Keynote: John A. Zachman, Architecture Is Architecture

John A. Zachman

John A. Zachman, Zachman International, USA

Architecture Is Architecture

Wednesday, May 6, 2009, 9:00 am

View keynote abstract >

Introduced by Rolf Siegers of Raytheon. Siegers introduces Zachman Framework as a thinking tool for enterprise architecture.

Welcome to the SATURN Network Blog!

As we kick-off the fifth annual SATURN conference, we’re also excited to announce a new effort to engage architecture experts and practitioners: the SATURN Network Blog.