This event has ended. Visit the official site or create your own event on Sched.
  • Registration is open every day from 7:30 a.m. until the close of the day’s sessions. 
  • 30-minute refreshment breaks are at 10:00 a.m. and 2:30 p.m. daily (Wednesday afternoon break is at 2:00 p.m.). 
  • Lunch is 12:00-1:00 p.m. daily in the Catalina Ballroom (Monday lunch is in the Shutters Hospitality Suite)

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Learning [clear filter]
Monday, May 2


Designing Modern SOA Systems

In 15 years, service-oriented architecture (SOA) has gone from a buzzword to an established technology. But new patterns, frameworks, and standards continue to emerge in the SOA space. In this recently developed course, we will focus on design decisions and tradeoffs that SOA architects face today. Topics that will be covered include REST constraints and good practices; SOA solutions that include event-driven messaging, API gateways, and orchestration platforms; and microservices vs. monoliths, security, alternatives for integration to external systems, and other design considerations for SOA solutions.

avatar for Paulo Merson

Paulo Merson

Brazilian Federal Court of Accounts (TCU)
Paulo Merson has been programming in the small and programming in the large for over 30 years. Paulo is a software developer at the Brazilian Federal Court of Accounts. He is a Visiting Scientist with the Software Engineering Institute (SEI), a certified instructor for Arcitura, and... Read More →

Monday May 2, 2016 8:30am - 4:30pm
Fairbanks B


DevOps and Continuous Delivery: Practices, Architecture, and Security

This course is targeted at architects designing software-intensive systems with a goal of adopting DevOps practices to enable continuous delivery of high quality and secure software. If you know nothing about DevOps, don’t fear. The course begins with a brief overview of DevOps and key concepts. If you attended last year, consider coming again since roughly half of the material is new. In addition to examples of designing for deployability from real projects, we have added deep dives and case studies that focus on variability options and the pros and cons of popular DevOps architectural patterns such as microservices, feature toggling, canary testing, and image baking. We also explore more deeply how to integrate static analysis tools into the deployment pipeline to minimize architectural drift and provide tips for how to get the best value from them. Practical takeaways include a template for specifying measurable deployability requirements and a handout with more than 20 architectural tactics successfully used on DevOps projects. To keep things interesting, we also include a facilitated discussion session on the role of the architect and Infrastructure as Code.

avatar for Stephany Bellomo

Stephany Bellomo

Carnegie Mellon Software Engineering Institute
Stephany Bellomo is a Senior Member of the Technical Staff at the Carnegie Mellon Software Engineering Institute (SEI). She teaches SEI courses in Service-Oriented Architecture Migration of Legacy Components and Software Architecture Principles and Practices. Bellomo is a member... Read More →
avatar for Rick Kazman

Rick Kazman

University of Hawaii and Carnegie Mellon Software Engineering Institute
Rick Kazman is a Professor at the University of Hawaii and a Research Scientist at the Software Engineering Institute. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He is the author... Read More →

Monday May 2, 2016 8:30am - 4:30pm
Fairbanks C


Managing Technical Debt for Software

Technical debt occurs when a design or construction approach is taken that’s expedient in the short term but that increases complexity and cost in the long term. Whether it results from ignorance, accident, or strategy, all software-reliant systems carry some technical debt. If managed well, some technical debt can accelerate design exploration. Left unrecognized and unmanaged, accumulated technical debt results in increased development and sustainment costs. This course is designed for professionals who develop and maintain software-reliant systems to gain a better understanding of

  • how technical debt manifests in software
  • what developers, architects, and managers need to know about technical debt
  • how to manage technical debt effectively

This one-day course emphasizes the importance of intentional and strategic management of technical debt that is supported by architecture-focused practices.

avatar for Rod Nord

Rod Nord

Carnegie Mellon Software Engineering Institute
Dr. Robert Nord is a Senior Member of the Technical Staff at the SEI, where he develops effective methods and practices for software architecture. He also leads research on strategies for scaling agile development by incorporating architecture practices. Before joining the SEI... Read More →
avatar for Ipek Ozkaya

Ipek Ozkaya

Carnegie Mellon Software Engineering Institute
Ipek Ozkaya is a Senior Member of the Technical Staff at the SEI and deputy lead of the Architecture Practices Initiative. She develops effective methods for improving software development and system evolution by emphasizing software architecture practices, software economics... Read More →

Monday May 2, 2016 8:30am - 4:30pm
Fairbanks D