1 / 29

Requirements vs. Design vs. Runtime

2. Papers. A Reconfiguration Mechanism for Statechart Based Components by Elkorobarrutia, Sagardui, et al (2007)Reconciling System Requirements and Runtime Behavior by Feather, Fickas, et al (1998). 3. The Questions. Can requirements and designs be leveraged to facilitate system adaption

belita
Télécharger la présentation

Requirements vs. Design vs. Runtime

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Requirements vs. Design vs. Runtime UC San Diego CSE 294 Fall Quarter 2007 Barry Demchak

    2. 2 Papers A Reconfiguration Mechanism for Statechart Based Components by Elkorobarrutia, Sagardui, et al (2007) Reconciling System Requirements and Runtime Behavior by Feather, Fickas, et al (1998)

    3. 3 The Questions Can requirements and designs be leveraged to facilitate system adaption … yet avoid emergent, inappropriate, or unpredictable behavior? What types of requirements and designs facilitate this? What types of runtime support facilitate this?

    4. 4 The Context – Autonomic Computing Autonomic Computing as defined by Kephart and Chess in IEEE Computer Society, January 2003 Systems and integration of systems is getting more complex (installation, tuning, configuration, maintainance) Design getting too complex ? push some design decisions to runtime self-* Self-configuration – based on high level policies Self-optimization Self-healing – detect, diagnose, repair Self-protection – malicious attacks, cascading failures

    5. 5 Two Approaches Statechart execution (Elkorobarrutia et al) Goal-oriented (Feather et al)

    6. 6 Statechart Execution Basic Approach Given a collection of substitutable components, have an application-independent way of choosing one No designer involvement needed Operates at higher level (i.e., component) than Class/Operation/Type (as in Java methodology per Faud) Develop statechart-based components Assist developer in creating executable components Make model available at runtime (i.e., reflection) Based on message dispatcher/receptor model (i.e., perhaps a leadin to SOA)

    7. 7 Sample Statechart

More Related