PATTERN LANGUAGE

Modeling, Managing, Making it Right.

June 2006

Between Dr. Dobb's coverage of the Ruby RailsConf 2006 conference and the Dr. Dobb's Architecture and Design world, we have Chicago covered like the dew in Dixie.

As its name suggests, Dr. Dobb's Architecture and Design conference, which kicked off July 17 at McCormick Place in Chicago, is designed with software architects, senior developers, modeling professionals, and usability experts in mind. All in all, the conference will have more than 70 sessions, taught by some of the industry's foremost experts.

I recently had a chance to sit down with conference manager Tamara Carter to find out more about the event.

DDJ: Tami, what's new this year?
TC: For starters, we've revamped the tracks. The UML track has transformed into Modeling, covering the entire process of transforming requirements into a roadmap that developers can use to build software. The track is jam-packed with sessions. For instance, Bran Selic, IBM distinguished engineer and OMG chair for UML 2.0, is teaching a tutorial on the modeling language's latest evolution; Stephen Mellor's offering several classes on MDA and embedded development; and Scott Ambler's teaching a tutorial on Agile Model-Driven Development.

Another new track is Usability: Hugh Beyer, Jeff Patton, Larry Constantine, and James Hobart will be speaking in panels, keynotes, classes, and half-day tutorials.

We also have more than 30 sessions in the Process & Methods and Architecture & Design tracks, focusing on issues such as SOA, object-oriented design, software factories, test-driven development, architecture best practices for Ruby development, and much more.

DDJ: Who's keynoting?
TC: Okay, Hugh Beyer, co-inventor of the contextual design process, kicks off the keynotes on Monday, July 17, speaking on architecting usability. IBM distinguished engineer Murray Cantor will speak on modeling and governance ("Good Modeling, Good Governance"), and security expert Herbert Thompson will talk about securing software architecture.

DDJ: Herb Thompson, eh? He's a great guy and has written some great security articles for Dr. Dobb's Journal. Who else is speaking?
TC: Well, Ed Yourdon rounds out the week, giving a keynote speech on the changes the next decade will bring to modeling ("Beyond UML, ERDs and DFDs"). Ed's always controversial and compelling; it's one keynote I wouldn't miss.

DDJ: What other speakers and courses come to mind?
TC: Robert Martin's half-day tutorial on test-driven development is filling up fast; Terry Quatrani's intro to UML is always popular; and Elliotte Rusty Harold's "Human Factors in API Design" class consistently gets high marks. There are also sessions on aspects, embedded systems, SysML, peer-to-peer technology, and the like.

DDJ: What else?
TC: We have two great panels this year. "The Model-Driven Development Face-Off" was a heated debate at last year's conference, and promises to generate controversy again this year. Also, Scott Ambler, Hugh Beyer, Larry Constantine, and Michael Rosen will be joining Jeff Patton on the Usability panel: "Software Design, Interaction Design: The View Across the User Interface Divide."

DDJ: For more information, what's that URL again?
TC: That's www.sdexpo.com/2006/archdesign/

DDJ: Thanks for your time, and I'll see you there.
TC: Thanks.

Posted by Jon Erickson at 03:52 PM  Permalink |

The International Association of Software Architects (IASA), a global non-profit association for professional IT architects that is vendor and technology agnostic, is set to deliver the first IT Architecture standard ever developed, controlled, and owned by IT architects.

This standard, entitled the "Foundations Reference Model" (FRM), represents a fundamental shift in the IT industry away from vendor initiated and managed standards, towards best practices controlled and operated by the professionals using them.

The FRM is currently undergoing the first peer review by participating senior architects from IASA chapters around the world. Once this Alpha review is complete, the FRM will then be open for review by all IASA members and once approved it will be released to the public.

The ultimate goal of the FRM is to drive stability in the architecture profession by providing the missing "big picture" for large, long term IT efforts. The FRM addresses the entire scope of an architect’s role including the organizational, time-line and evolutionary perspectives to provide guidance that is otherwise missing in large institutions and projects. It strives to provide a common approach to architectural endeavors while being applicable to any type of design and at any level in an IT organization.

"What the FRM is doing is mapping out the very basics of our profession. From terminology to role descriptions and activities, the FRM provides the common understanding necessary for communication between architects and their employers," explains Paul Preiss, president and founder of IASA.

"How many times have architects had to justify their positions? How much time have we spent just developing and describing basic principles within our organizations? These activities represent massive fiscal waste and a significant source of frustration with our profession. The FRM solves all of that," according to Preiss.

Posted by Jon Erickson at 01:31 PM  Permalink |

Microsoft has launched a new peer-review board certification program called the Microsoft Certified Architect (MCA).

The certification process to consists of five steps:

• You apply for the program by completing the program application and paying the application fee.
• Your application is assessed relative to the established criteria, such as years and type of experience, architectural knowledge, and complexity of technical solutions to determine whether the candidate will advance in the application process. If you do advance, the next step is a telephone screening with an MCA who will determine whether the candidate is accepted into the program.
• Upon acceptance into the program, you work with mentors to prepare for your review board interview. Additionally, you continue to work on your documentation. The documentation consists of a dossier that includes a work history, an architectural solution case study, and a document specifying instances in which you have displayed the program competencies.
• As soon as a mentor determines that the candidate is ready, you submit your final documentation and schedules the review board interview.
• At the conclusion of the interview and a positive vote from the review board, you are awarded the MCA credential.

The certifcation recognizes two types of architects--Infrastructure Architects and Solutions Architects. Certification candidates are evaluated on several criteria, including:

• Leadership (you must demonstrate that you can develop partnerships with stakeholders both inside and outside the organization on your projects, that you can mentor others, that you develop and form strong teams, and that you achieve successful results)
• Communication (you must demonstrate that you can maintain well-written and accurate project documentation, and that you can present information about a technical subject in a concise and measured manner)
• Organizational dynamics (you must demonstrate that you can recognize the key stakeholders on a project and that you can work with those stakeholders to drive the project to a successful conclusion)
• Strategy (you apply your knowledge of technology to further organizational goals within your vertical industry and understand the principles of project management and interact with project managers to complete projects successfully).
• Process and tactics (you demonstrate that you can gather and refine project requirements from both a technical and a business perspective. You design, create, maintain, and verify models of the deployed infrastructure)
• Technology breadth (you understand architectural best practices and can apply them across a breadth of technologies to solve an organizational problem)
• Technology depth (you demonstrate that you have a detailed knowledge of the concepts, application, and issues of at least two depth competencies. You must also demonstrate the ability to quickly assimilate information about new technologies)

To apply for Architect certification, go to http://www.microsoft.com/learning/mcp/architect/archapp/default.mspx.

Posted by Jon Erickson at 10:07 AM  Permalink |