Minneapolis, Minnesota

April 29 to May 3, 2013

SATURN 2013 Software Architecture Conference: Courses

Two SEI courses on software architecture will be offered to SATURN 2013 attendees: Advanced Topics in Service-Oriented Architecture and Software Architecture Design and Analysis. These two-day courses are offered on April 29 and 30, 2013.

Advanced Topics in Service-Oriented Architecture

The goal of this course is to provide guidance in the following areas

  • architecting and designing service-oriented systems
  • implementing SOA governance
  • securing service-oriented systems
  • testing service-oriented systems

If implemented correctly, SOA adoption can provide business agility, reuse of business functionality, and leverage of legacy systems for an organization. The key word in the previous statement is "IF". There is still widespread belief that SOA can be implemented "out of the box", that SOA is all about technology, that securing service-oriented systems is accomplished via "out of the box" tools, and that testing service-oriented systems is no different than testing any other type of system. The reality is that

  • Service-oriented systems are composed of services, service consumers, and a SOA infrastructure that connects service consumers to services. The only component that can sometimes be implemented "out of the box" is the SOA infrastructure. However, SOA infrastructures are usually composed of a set of products as opposed to a single product in order to meet system quality requirements. The system as a whole needs to be architected in order to take advantage of the loosely-coupled, stateless, standards-based characteristics that have driven SOA adoption and at the same time meet system quality requirements.
  • SOA governance is the set of policies, rules, and enforcement mechanisms for developing, using and evolving service-oriented systems, and for analysis of their business value. A well-known problem in the SOA community is the need to establish effective SOA governance procedures to enable an organization-wide SOA initiative. A number of organizations and vendors address this problem through SOA governance frameworks that provide models, procedures, and tools for SOA governance. Many of these SOA frameworks are general purpose because they are intended to be useful for a diverse customer base. However, while designed for a wide customer base, vendor SOA frameworks tend to be are narrowly focused to work with the specific tools of the vendor. A critical problem for an organization when implementing SOA governance is to customize vendors' offerings to its specific technological and management context.
  • The security threats for service-oriented systems are not new or different; it is the level of exposure that is greater. Issues such as identity management, secure service composition and trust in third-party services become important requirements in this type of system. Security mechanisms have to be architected into service-oriented systems and security policies have to be defined and enforced via SOA governance.
  • In SOA environments, system components are distributed, deployed on heterogeneous platforms, and often not even available. There is often not a single owner of a service-oriented system. Because service-orientation projects have a primary goal of integration, the line between functional testing, integration testing and system testing is often blurred. The challenge for testers of service-oriented systems is that testing needs to take place at different levels and for each system component.

These are examples of challenges constantly faced by architects and developers tasked with the design and implementation of service-oriented systems.

Who should attend?

This course is valuable for:

  • System and Software Architects
  • Project Managers and IT personnel responsible for SOA implementations
  • Developers of service-oriented systems

Topics

The following topics are covered in this class:

  • Architecture and Design of Service-Oriented Systems
  • SOA Governance
  • Security Considerations for Service-Oriented Systems
  • Testing in SOA Environments

Objectives

This class provides a starting point for people tasked with the design and implementation of service-oriented architecture in the following areas:

  • architecting and designing service-oriented systems
  • implementing SOA governance
  • securing service-oriented systems
  • testing service-oriented systems

Completion of this course fulfills a training requirement for the SEI's SOA Architect Professional certificate program.

Prerequisites

Before registering for this course, participants must have successfully completed Service-Oriented Architecture: Best Practices for Successful Adoption or obtained an SEI waiver acknowledging equivalent service-oriented architecture knowledge. All requests for waivers must be submitted to course-info@sei.cmu.edu prior to the start of the course and should detail educational background and SOA professional experience.

Software Architecture Design and Analysis

A system's software architecture is widely regarded as one of the most important software artifacts. Software professionals routinely make decisions that impact that architecture, yet many times that impact is not fully considered or well understood.

  • Which design decisions will lead to a software architecture that successfully addresses the desired system qualities?
  • How do you know if a given software architecture is deficient or at risk relative to its target system qualities?

This two-day course provides in-depth coverage of the concepts needed to effectively design and analyze a software architecture. The essential considerations for defining any architecture are carefully examined and then illustrated through application of the SEI Attribute-Driven Design (ADD) software architecture design method. This course also explores architecture analysis in-depth and introduces the SEI Quality Attribute Workshop (QAW) and the SEI Architecture Tradeoff Analysis Method (ATAM). Through multiple exercises, participants study an application of these methods and get a chance to apply them to sample problems.

This course is based on the books Software Architecture in Practice, 2nd Edition and Evaluating Software Architectures: Methods and Case Studies.

The prerequisite for this course is the Software Architecture: Principles and Practices course, which is available as instructor-led classroom training and as eLearning.

Who should attend?

  • practicing software architects
  • designers and developers of software-reliant systems

Topics

  • life-cycle view of architecture design and analysis methods
  • the QAW, a method for eliciting critical quality attributes, such as availability, performance, security, interoperability, and modifiability
  • the ADD method, a method for designing a software architecture
  • the ATAM, a method for evaluating a software architecture based on a set of attribute-specific measures of the system such as performance, availability, modifiability, and security

Objectives

This course provides attendees with in-depth coverage of the concepts needed to effectively design and analyze a software architecture. After attending this course, participants will have a better understanding of

  • the essential considerations in any architectural design process
  • the QAW for eliciting critical quality attributes
  • the ADD method for designing an architecture
  • the role of architecture evaluation
  • using the methods within a software development life cycle

Prerequisites

Before registering for this course, participants must

Sponsors
Stay Connected

Get the latest SATURN news, important dates, and announcements on the SATURN Network blog, sign up for our email updates, follow us on Twitter (@SATURN_News, #SATURN2013), and join the SATURN LinkedIn Group.

SATURN Blog RSS SATURN on LinkedIn Twitter
SEI Customer Relations

Phone: +1 412-268-5800
Toll Free (within the USA):  +1 888-201-4479
FAX: +1 412-268-6257
E-mail:
info@sei.cmu.edu


Help us improve

Visitor feedback helps us continually improve our site.

Please tell us what you
think with this short
(< 5 minute) survey.