InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

New Resources for the Software Architecture

Posted by Steven Robbins on Mar 20, 2008

Sections
Enterprise Architecture
Topics
Enterprise Architecture ,
Architecture
Tags
SOA Adoption ,
Business/IT Alignment ,
Documentation
Several new resources are available for the software architect. Simon Brown and Kevin Seal have made available a set of guidelines for creating software architecture documentation. Mike Kavis also put together a framework to help guide the architect in dealing with the change that new architecture can bring.

The purpose of Brown and Seal's Software Architecture Document Guidelines v0.1 is to provide:
1. An outline description of the software architecture, including major software components and their interactions.
2. A common understanding of the architectural principles used during design and implementation.
3. A description of the hardware and software platforms on which the system is built and deployed.
4. Explicit justification of how the architecture meets the non-functional requirements.
Each of the 15 sections of the document included a short description or examples of the content to be included in the section along with a checklist for the architect. The authors created the guidelines as part of a tutorial they delivered at QCon London 2008. The document is available in PDF form.

Mike Kavis said "Most articles that I have read discuss two critical elements: the technology and governance. Not enough people are talking about change management." He used John Kotter's 8 steps from "Winning at Change" to show how architects can deal with the change necessary for Enterprise Architecture or SOA initiatives. Mike's 8 steps applied to architecture projects are
1. Build strong business case
2. Secure executive sponsor and top level buy in
3. Create a Road Map
4. Communicate the Road Map
5. Empower Others to Act on the Road Map
6. Start small, deliver early and often (agile)
7. Expand, leverage reuse
8. Govern
Mike also gave some insight in building a strong business case by focusing on business processes.
We did not talk about SOA in technical terms. What we did tell them is that by leveraging a "new" technology, we could automate their entire workflow from contract to delivery without having to rewrite any of our backend systems. This new technology would allow us to connect their new web based systems to the existing systems through an "adapter". Of course, by adapter I mean services.
By going through the business need for BPM, Mike's organization was able to get the business to champion the SOA and BPM initiatives.
404 by JS Bournival Posted
Re: 404 by Steven Robbins Posted
  1. Back to top

    404

    by JS Bournival

    The «Mike also gave some insight» link isn't working.

  2. Back to top

    Re: 404

    by Steven Robbins

    Link is fixed. Thanks for the notice.


    Steve

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.