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
Certification programs for software architects abound. How can you tell which programs best measure an architect’s capabilities? Or which ones are right for you? SATURN 2010 plans a track on architecture certification to pull together details on certification programs.
Waves of new categories of requirements reflect reactions of users, communities, and organizations alike to our changing environment. The past decade of software development enjoyed specializations around key concerns such as usability, security, and privacy and explorations on their architectural significance. Greenability has also been emerging as a key category of requirements to consider. Continue reading
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
Yesterday, I attended the tutorial on Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing by Doug Schmidt. While explaining a pattern sequence, he used an analogy of ordering hamburgers to explain two different ways of communicating in distributed systems. At McDonald’s, when a customer orders, the employee enters the request at the register, reaches back to the “cache” of precooked hamburgers kept warm under a heat lamp, and delivers it to the customer; the interaction is an example of “synchronous” communication. Continue reading
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.
