1 / 21

Process – Group C

Process – Group C. Participants. Luciano Nelly Bojan Alessandra Paola Oscar Sooyong Dennis Thomas Rogerio Jesper. Fact sheet. Name : Reconciling Software life-cycle activities

kobe
Download Presentation

Process – Group C

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. Process – Group C

  2. Participants • Luciano • Nelly • Bojan • Alessandra • Paola • Oscar • Sooyong • Dennis • Thomas • Rogerio • Jesper

  3. Fact sheet • Name: Reconciling Software life-cycle activities • Hypothesis: Life-cycle activities for self-adaptive software are different from activities known from life-cycle activities for traditional systems. • Observations: • The traditional separation of development time and runtime blurs – cmp. with Group A’s work. • Spirals • Long-term evolution • Short-term adaptation • Challenge: Understanding the relationships

  4. What we know Self-adaptation (evolution) requires that certain process elements are available at run-time • (Some) Understanding of • System • Goals • Environment • Dimensions • Evolution types • Foreseeable • Unforeseeable • Stakeholders Self-adaptive software system Adaptation logic monitor adapt monitor Domain logic Controllable software monitor effect Environment Non-controllable software, hardware, network, physical context

  5. What we(?) want to do!(long-term) • For a given Self-adaptive System; understand, define, and instantiate a tailored process, • Process Roles • Work Products • Activities • Process Element Librarywhere Dimensions define variants • [Life-time] Design time – Deployment time – Run-time • On-line – Off-line • Autonomous – Human Assisted – … Manual • Foreseeable - Unforeseeable Process Element Library Process

  6. Dimensions • [Life-time] Design time – Deployment time – Run-time • (@run-time) On-line – Off-line, • On-line, adaptation competes with a base-level system over resources. Alt. services provided by the system. • Off-line • Synchronous – Asynchronous • [Degree of automation] Autonomous – Human Assisted – … Manual • Foreseen – Unforeseen • Level of process support required, @run-time, required to perform adaptations • Monitored vs. unmonitored • Controlled vs. uncontrolled • Open vs. closed-loop • Other sources • Taxonomy unanticipated evolution • Modeling dimensions in SEfSAS 09

  7. Approach • Process Specification Framework (Reasoning) • Collect application specific scenarios • Development scenarios • Behavioral Scenarios • Perspectives • User, Developer, … • Case-study – Automatic workarounds

  8. Case study • Develop SPEM models for two processes • Traditional Evolution • Automatic Workarounds • SPEM models • Activity diagrams • Object model • Compare • Connect!

  9. Evolution (Trad) – Activity Diagram

  10. Evolution (Trad) – SPEM Static

  11. Automatic Workarounds - Activity

  12. Automatic Workarounds – SPEM Static • Library Elements • Development time instantiations • Run time instantiation Application Specializations

  13. Challenges • SPEM modeling • Process descriptions – Collaborations • Instances UML Class diagram • Mixin life-cycle phases • Stereotypes • UML profile • Understand sub-process integration • Models – Degree of reflection depends upon the the expressiveness of models • Observability/Controllability of the base-level application or adaptive-subsystems • Monitored, Controlled variables • Structural/Behavioral reflection • Reflective processes, modify process models@runtime • Instantiation process • COST function • Element Selection/Instantiation • Distribute responsibilities over the life-cycle • What should drive the developer into seeking self-adaptive behavior? • And… • Group A – Example of distribution challenge incl. tradeoff • Group B – Design Spaces input to process instantiation • Group D - Decentralization

  14. Remember…nota Waterfall!

  15. Sub-Process Integration e.g. Dependencies between elements in different life-cycle phases Capture and Understand the relationships!

  16. Reflective Processes

  17. Process Element Library System Model Evolution types Marking Perspectives Other dimensions Process Instantiation

  18. Process Instantiation Activities • Process Element Library • Develop Elements • Classify (Dimensions) • Instantiation • Selection using dimension attributes • Distribute responsibilities over the life-cycle and reflective sub-systems • Verification • Process Metrics @run-time

  19. Work ahead • Workarounds • Extend with more on development time • Interaction diagrams • Plastic • On-line/off-line • Development/Deployment (adaptation)/Run-time • Foreseen/Unforeseen

  20. Participants • Jesper Andersson • Luciano Baresi • Nelly Bencomo • Bojan Cukic • Alessandra Gorla • Paola Inverardi • Oscar Nierstrasz • SooyongPark • Dennis B. Smith • Thomas Vogel • Rogerio de Lemos

More Related