Sam Malek

1
Sam Malek

• Self-Architecting Software Systems
• Jan, 29, 2009

2
Role of Architecture in Adaptive Software Systems

• Adaptive Software
• Software that changes its functionality
  (capabilities) at runtime
• In the absence of explicit architecture the
  engineer is left to reason about adaptation
• From Memory
• From source code
• Architecture can serve as the primary focus of
  reasoning

3
Self-Adaptive Software Systems

• Many software systems are highly distributed,
  embedded, and long lived ? need self-adaptive
  software
• Important questions
• Under what conditions does the system undergo
  adaptation?
• Should the system be open-adaptive or
  closed-adaptive?
• What type of autonomy must be supported?
• What kind of information must be collected?
• How often is adaptation considered?
• What is the performance impact?

4
SASSY Self-Architecting Software System

• Pushing the envelop
• From self-adaptive software ? self-architecting
  software
• User specifies requirements in an activity
  modeling language
• Autonomously construct an optimal software system
  that satisfied the users requirements

5
Similar to Lego
6
SASSY Targets Web Services

• Service software component (module) that is made
  available publicly
• Broker a directory for finding services
• Consumer uses the functionality provided by the
  services

7
Targets Pervasive Scenariose.g., Emergency
Response Domain
8
Overall Process
9
Modeling the Requirements (1)
10
Modeling the Requirements (2)
11
Modeling the QoS Requirements
12
Self-ArchitectBase Architecture
13
Self-ArchitectEnhanced Architecture
14
Self-ArchitectCoordinators Behavior
15
Methodology
16
Summary
17
Projects Ideas

• Projects related to SASSY
• Research and develop SASSY infrastructure
  services
• Monitoring services
• Adaptation services
• Develop a small emergency response software
  system based on existing standards in this domain
• Take a look at www.USGovXML.com
• Research and compile a library of architectural
  patterns applicable in the SOA domain for
  improving the QoS properties
• Research and develop alternative approaches to
  modeling requirements, architecture, and
  coordination
• Investigate extensions to BPEL or alternatives
  for distributed coordination of SOA software
  systems

18
Project Ideas Continued

• Projects related to other aspects of the course
• Software architecture
• Autonomic computing
• QoS analysis
• Coordination
• A detailed survey
• You will need to develop an interesting taxonomy
  or analysis of a research area
• Empirical studies
• Need to find several competing approaches/techniqu
  es and experimentally compare