Notes by Ian De Silva
Software Development Improvement Program: Enabling Software Excellence at a Hardware Company
Sascha Stoeter, ABB
ABB has historically been a hardware company, but it has been slowly increasing the amount of software development it does since the 80s. It is a distributed company (in 34+ countries) with software embedded into products such as controllers. Each team has its own set of tools to support development efforts.
Posted in Architecture-Centric Engineering, Architecture-Centric Practices, Quality Attribute Analysis, SATURN Conference
Tagged architecture evaluation, architecture review, Architecture Tradeoff Analysis Method, ATAM, EA, enterprise architecture, IT architecture, SATURN 2013, SATURN Conference, SEI, software architecture, software architecture evaluation, software architecture review, software design, software development, software engineering, Software Engineering Institute, system architecture, system of systems
Notes by Ian De Silva
Lean and Mean Architecting with Risk- and Cost- Driven Architecture
Eltjo Poort, CGI
Solution architecture includes more than just the software; it may include business processes, information systems, technologies, and the environment. Solution architecture approaches fill the gap between enterprise architecture approaches and technical architecture approaches. Enterprise approaches are weak on transformation and implementation, while technical architecture is weak on cross-technology stakeholder concerns.
In his tutorial on Tuesday, April 30 at SATURN 2013 titled Pragmatic Solution Architecting with Risk- and Cost-Driven Architecture (RCDA), Eltjo Poort, lead expert on solution architecture at CGI (formerly Logica), will present a solution-architecture approach tailored to today’s complex architecting environment. RCDA combines practices from enterprise and software architecture. Its risk-and-cost focus centers the approach on concrete drivers and helps teams to explain their architectural choices to managers and other business stakeholders in terms that they can understand.
RCDA practices were originally used within CGI to shape solutions for clients. The approach is based on well-vetted research work in Poort’s PhD thesis titled “Improving Solution Architecture Practices,” and has been successful within CGI, where 78% of lead architects trained in RCDA report that the training has made them more effective at their jobs.
Pragmatic Solution Architecting with Risk- and Cost-Driven Architecture (RCDA) has not been offered frequently in the U.S., so we encourage SATURN attendees to consider registering at the SATURN 2013 software architecture conference registration page. For more information, see Eltjo Poort’s blog.
Posted in Architecture-Centric Engineering, Architecture-Centric Practices, Conferences and Events, SATURN Conference
Tagged EA, enterprise architecture, SATURN 2013, SATURN Conference, SATURN Network, SEI, software architecture, software design, software development, software engineering, Software Engineering Institute
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).
Posted in Architecture and Agile, Architecture-Centric Engineering, Architecture-Centric Practices, Cloud Computing, SATURN Conference, Service-Oriented Architecture, Ultra-Large-Scale Systems
Tagged architecture evaluation, architecture review, Architecture Tradeoff Analysis Method, ATAM, cloud computing, documentation, EA, enterprise architecture, non-functional requirements, SATURN 2012, SATURN Conference, SEI, SOA, software architecture, software architecture evaluation, software architecture requirements, software architecture review, software design, software development, software engineering, Software Engineering Institute, technical debt, ULS systems, ultra-large-scale systems
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
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/.
Posted in Architecture-Centric Engineering, Architecture-Centric Practices, Conferences and Events
Tagged architecture evaluation, architecture review, Architecture Tradeoff Analysis Method, ATAM, EA, enterprise architecture, SEI, software architecture, software architecture evaluation, software architecture requirements, software architecture review, software design, software development, software engineering, Software Engineering Institute, system of systems
Notes by Bill Pollak, Peter Foldes, and Jack Chen
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?
Posted in Architecture and Agile, Architecture-Centric Engineering, Architecture-Centric Practices, SATURN Conference
Tagged EA, enterprise architecture, SATURN 2011, SATURN Conference, SEI, software architecture, software design, software development, software engineering, Software Engineering Institute
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. Continue reading
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…
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
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
