Tag Archives: SATURN 2014

Anthony Tsakiris on Facilitating the Mini Quality Attributes Workshop, Will Chaparro and Michael Keeling, SATURN 2014 Presentation

by Anthony Tsakiris
Ford Motor Company

Architecture development activities as presented in books, articles, and classes are sometimes “heavy” – that is, they require a lot of time and people resources relative to what is available. That’s my view from an automotive embedded-control-systems environment. An argument can be made that that’s what it takes, but there’s another reality that time and resources are truly in short supply. It’s difficult to get stakeholders who are busy with multiple projects and production concerns to commit big chunks of their time to an activity like a Quality Attribute Workshop for a new project.

Continue reading

Russ Miller on Engineering Velocity: Continuous Delivery at Netflix, Dianne Marsh, SATURN 2014 Keynote

by Russell Miller
Vice President of Technology Services at Impulse.com
Co-host of Architectural Concepts podcast

At SATURN 2014 there were a number of excellent sessions on DevOps and Continuous Delivery; one of those was Dianne Marsh’s keynote entitled, “Engineering Velocity: Continuous Delivery at Netflix.” Dianne is the director of engineering tools at Netflix, a company that has led the way in terms of continuous delivery. Dianne’s main objective for the talk was to share details and philosophy from Netflix that the audience could consider for application in their organizations as a means to improve their velocity. She did a great job achieving that objective.

Continue reading

Podcast: Amazing Architectures Don’t Happen by Accident

At the Architectural Concepts Podcast, SATURN 2014 Technical Chair Michael Keeling discusses techniques for exploring and uncovering the shortest path to amazing architectures, mapping the idea of design modes to software architecture.

In the podcast, Michael also discusses the rapid software architecture workshop, based on these ideas, that he delivered at SATURN 2014.

Listen now.

Impressions of SATURN 2014

“SATURN has become my favorite annual professional event,” says Eltjo Poort at Eltjo’s Solution Architect Blog. Read Eltjo’s review of SATURN 2014.

Wide-Ranging SATURN 2014 Conference Draws Near-Record Attendance

Summary of the SATURN 2014 conference published on the SEI website.

Scott Hanselman Interviews Len Bass at SATURN 2014

Portland, Oregon native and well-known writer and blogger Scott Hanselman spoke at SATURN 2014 this year (“JaveScript, the Cloud, and the New Virtual Machine”) and, while there, he interviewed Len Bass for The Hanselminutes Podcast: Fresh Air for Developers. Len is a senior principal researcher at NICTA in Australia. During his long and distinguished career at the SEI, Len was co-author many seminal publications in the field of software architecture including Software Architecture in Practice.

In the podcast, Stories of Computer Science Past and Present with Len Bass, Len shares stories from his 40+ year career in software.

SATURN 2014 Team Collaboration Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Transparency: An Architecture Principle for Socio-Technical Ecosystems
Felix Bachmann and Linda Northrop, Software Engineering Institute

Felix and Linda shared their experience as a team in the XSEDE project. They presented compelling evidence of the need to have transparent architecture and architectural practices in socio-technical ecosystems like XSEDE. XSEDE is a virtual, high-performance computer system that allows interactivity for scientists (e.g., biologists, mechanical engineers, environmentalists) all over the world to run their experiments. Experiments are usually of the types that need super-powerful computing capabilities. The system is distributed over a wide distance, and engineers or developers have different global and local priorities. Due to the size of the project and the high complexity, architectural guidance was necessary to ensure the success of the project. Felix’s and Linda’s team responsibilities are to help the team make the right architectural decisions, coach the team on how to incorporate architectural practices, and research missions.

Continue reading

SATURN 2014 Promoting Quality Attributes: Lessons Learned from the Trenches Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Can You Hear Me Now? The Art of Applying Communication Protocols When Architecting Real-Time Control Systems
Todd Farley, BAE Systems, Inc.

BAE Systems deals with architecting real-time control systems. These systems are usually complicated and distributed. Also, the lifetimes of projects are usually very long. So BAE must always answer this question: Which process should they adapt? The problems they face tend to fall into three categories:

  • motion control systems (~robots)
  • computation-intensive algorithms
  • user interfaces

Continue reading

SATURN 2014 Art and Science of Scalability Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

BI/Big Data Reference Architectures and Case Studies
Serhiy Haziyev and Olha Hrytsay, SoftServe, Inc.

Serhiy and Olha shared their experience with the tradeoff between modern and traditional (non-relational and relational) reference architectures. They looked into the challenges associated with each approach and gave tips from real-life case studies on how to deal with big data reference architecture. As a reminder, they visited some of the known big data challenges:

  • Data is generated from many and different sources.
  • As data grows, it becomes complicated and heterogeneous (velocity and volume) until it’s no longer manageable.

Continue reading

SATURN 2014 The Business of Software Architecture Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Under N: Acceptance to Delivery in N Hours
Umashankar Velusamy, Verizon Communications, Inc.

Umashankar started the presentation with a simple question: Are all deliveries the same? Humans take about 9 months to “deliver” babies. Cats and dogs take about 2 months to do so. So not all deliveries are the same. In the software industry, the same thing applies—different deliveries take different amounts of time. However, we tend to apply a one-size-fits-all solution to everything. Umashankar asked another question: Does it make since to wait 2 weeks or even 2 months for something to deliver, when it takes only 12 hours to deliver? It’s definitely doesn’t make sense, Umashankar answers.

Continue reading