Nick Rozanski and Eoin Woods have continued their journey of building a comprehensive handbook on Systems Software architecture with the publication of the second edition of Software Systems Architecture. InfoQ spoke to the authors on a couple of new topics, the System Context viewpoint and Agile, that are covered in the latest edition.
Sparx Systems, an Austrian based vendor of UML tools, has recently published version 9.2 of Enterprise Architect. The new version adds features like enhanced simulation capability and support for describing ontologies.
Evolve is a lightweight tool for creating, wiring up and executing Java components. Developers can use Evolve to graphically describe JavaBeans and also optionally generate Java code for setters and getters. InfoQ spoke with Andrew McVeigh about the tool.
Architexa is a new Eclipse-based UML modeling tool that allows developers to quickly gain insight into code relationships through UML diagrams, and share what they find with others.
James Kovacs explains how to use TDD and BDD to focus the architectural efforts on the high-value areas of the code in order to obtain just-in-time software architecture.
David Starr presents some of the tools in Visual Studio Ultimate 2010 helpful for building an application’s architecture: Architecture Explorer, Dependency Graphs, UML Modeling, and Layer Diagrams.
Eoin Woods explains how Barclays Global Investors (BGI) designed Apex, a new porfolio management system, to meet the challenges it faces and why BGI chose to combine mainstream, boutique and open source Java technologies, including Oracle, WebLogic, Spring, Swing, JIDE, Flux, CPLEX, MVEL and XStream, to create an architecture with some interesting variations on the standard J2EE form.
Mike Williams, co-creator of Erlang discusses the history of and influences on Erlang as well as languages and paradigms used at Ericsson for large scale development and embedded programming.
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
