search menu icon-carat-right cmu-wordmark

SATURN 2015 Presentations

April 2015 Presentation

Presentations from the program of SATURN 2015 (April 27-30, 2015, in Baltimore, Maryland)


Software Engineering Institute



In 2015, the Software Engineering Institute (SEI) Architecture Technology User Network (SATURN) Conference celebrated its 11th year. Each year, SATURN attracts an international audience of practicing software architects, industry thought leaders, developers, technical managers, and researchers to share ideas, insights, and experience about effective architecture-centric practices for developing and maintaining software-intensive systems.

Sessions and presentations included:

  • ADD 3.0: Rethinking Drivers and Decisions in the Design Process, Humberto Cervantes and Rick Kazman
  • Agilizing the Architecture Department, Eltjo Poort
  • A Partner Is Good to Have, but Difficult to Be, David Kane and Dave Dikel
  • Architecting Hybrid Cloud Solutions with Watson Developer Cloud, Will Chaparro
  • Architecting Public-Facing Website Software for High Concurrent User Load, Derrick Lau
  • Cost-Benefit Analysis in Technical Debt Reduction, Andriy Shapochka
  • Design Thinking Is for You, Ariadna Font Llitjós, Jeff Patton, and Jonathan Berger
  • DevOps Essentials for Software Architects, Len Bass
  • Does Your Cloud Solution Look Like a Mushroom?, Kim Carter
  • Enterprise Applications Health Improvement Program, Eswaran Thandi
  • Exploiting Fast and Slow Thinking, Rebecca Wirfs-Brock
  • From Monolith to Microservices: A Leadership Perspective on Legacy Application Modernization, Einar Landre, Jørn Ølmheim, and Harald Wesenberg
  • Improving Architectural Refactoring Using Kanban and the Mikado Method, Paul Boos
  • Injection, Modularity, and Testing: An Architecturally Interesting Intersection, George Fairbanks
  • Introduction to Architecture-Centric Design Thinking, Michael Keeling
  • Keeping the Beat: Rhythm and Trust in Architecture, David Kane
  • (Keynote) Progress Toward an Engineering Discipline of Software, Mary Shaw
  • Leading Change: Engaging Critical Stakeholders for Project Success (Presentation and spreadsheet), Marisa Sanchez
  • Living a Nightmare, Dreaming a Dream: A Drupal Deployment Dilemma, Gail E. Harris
  • Locating the Architectural Roots of Technical Debt, Rick Kazman, Yuanfang Cai, Serhiy Haziyev, and Volodymyr Fedak
  • Making Better Architectural Choices with the Architecture Valuation Framework, Voytek Janisz
  • Maturing Agile Teams and Driving Quality Through Architecture Principles, Amine Chigani and Yun Freund
  • Maximize Your Business Impact as an Architect, Eltjo Poort
  • My Silver Toolbox, Michael Keeling
  • Never Again Offline?! Experiences in the Outstanding Role of Data in a Large-Scale Mobile App Ecosystem, Matthias Naab, Ralf Carbon, and Susanne Braun
  • Open Medical Record System Plus (OpenMRS+): OpenMRS for Non-Communicable Diseases, Gloria Ingabire
  • Open Systems Architecture: Progress and Challenges, Douglas Schmidt
  • Programming in the 1960s: A Personal History, Len Bass
  • QA to AQ: Shifting from Quality Assurance to Agile Quality, Joseph Yoder and Rebecca Wirfs-Brock
  • Quality Requirements on a Shoestring, Thijmen de Gooijer
  • Smart Decisions: An Architecture Design Game, Serhiy Haziyev, Olha Hrytsay, Rick Kazman, and Humberto Cervantes
  • Software Architecture as Code, Simon Brown
  • Sustainably Supporting Data Variability, Atzmon Hen-Tov, Jordan Menzin, and Joseph Yoder
  • Systems Characterization: An Approach to Modernizing Disparate Legacy Systems, Jane Orsulak and Julie Kent
  • Systems of Action: A Stack Model for Capability Classification, Einar Landre and Jørn Ølmheim
  • Taming Big Balls of Mud with Agile, Diligence, and Hard Work, Joseph Yoder
  • The Architectural Analysis for Security (AAFS) Method, Jungwoo Ryoo and Rick Kazman
  • The Business Side of a Software Architect, Tomer Peretz
  • The Value of Architecture and Architects, Shrikant Palkar
  • Using Hazard Analysis to Make Early Architecture Decisions for an Autonomous Automotive Application, Joakim Fröberg
  • Understanding Quality Goals, David Gelperin
  • What Coderetreats Have Taught Us About Design, Jim Hurne and Joseph Kramer
  • When and Where to Apply the Family of Architecture-Centric Methods, Timothy Morrow, Michael J. Gagliardi, and William G. Wood
  • Why They Just Don't Get It: Communicating Architecture to Business Stakeholders, Jochem Schulenklopper and Eelco Rommes