WICSA2008 WS3 AnalysisAndDesign
From WICSA Conference Wiki
Contents |
WS3 - Analysis and Design
Session Chairs: Tom Lonski and Claudia Raibulet
Tuesday 19th February, 13:30 - 17:30 and Wednesday 20th February, 15:30 - 17:30.
Contributions
- A Framework for Estimating the Impact of a Distributed Software System's Architectural Style on its Energy Consumption. Chiyoung Seo, George Edwards, Sam Malek, Nenad Medvidović
- A Software Architecture for Cross-Layer Wireless Network Adaptations. Soon-Hyeok Choi, Dewayne E. Perry, Scott Nettles
- Extraction of Component-Based Architecture From Object-Oriented Systems. Sylvain Chardigny, Abdelhak Seriai, Mourad Oussalah, Dalila Tamzalit
- Simulating Software Architectures for Functional Analysis. Henry Muccini, Patrizio Pelliccione
- Towards Software Architecture Physiology: Identifying Vital Components. Ilham Alloui, Sorana Cimpan, Herve Verjus
Working Session Details
Welcome to the working session on Analysis and Design.
Attendees
Do you plan to join us? add your name to the following list!
- [[User:<wiki id>|<add your name here>]]
- Tom Lonski
- Claudia Raibulet
- Sam Malek
- Henry Muccini
- Soon-Hyeok Choi
- Michael Marzec
- Thorsten Keuler
- Sylvain Chardigny
- Snezana Mitrovic-Minic
- Seon ah Lee
- Phil Bianco
- Deokjin Kim
- Soonhyung Kim
- Viktor Iassinskii
- Richard Wu
- Ian Gorton
- Rob Nord
Session Overview
In order to have an effective working session, we propose to hold discussions in both small group and large group settings and to focus on finding common challenges, sharing current techniques and identifying future research needs. Key questions are:
- What are the key analysis and design elements in software architecture?
- How does software architecture promote estimation and simulation to lower risk in system development?
- How SA simulation differs from model simulation?
- How can we really integrate SA-based formal verification (e.g., model checking) with simulation, and which kind of advantages we can expect?
- In the context of evolving @ run-time systems:
- How simulation can help analyzing dynamic architectures?
- How dynamic architectures can be analyzed?
- How simulation can be integrated in the SA change management process?
- How does software architecture enable systems to adapt to change?
- How can software architecture be effective for legacy systems with implicit, undocumented, and organic architectures?
Additional questions identified during the working session are:
- Risk in software architecture analysis and design? (Need clarification from this discussion group.)
- Prototyping versus Simulations? (Need clarification from this discussion group.)
- What architecture properties can be "meaningfully" simulated? Latency? Reliability? Fault tolerance? Energy?
- Can real data be feed back into an architecture simulation?
- What, from a praticioner's view, will be available in the next 6 months / 1 year?
- How can I account for COTS products in a simulation?
- How can I build in power usage into my architecture based on the current rate of change of the implementation hardware?
Please join the discussion and add to this list.
Agenda
Tuesday, 19 Feb
| 13:30-13:45 | Welcome and goals |
| 13:45-15:15 | Paper presentations: Each presentation will be 15 minutes followed by a 10 - 15 minute question & answer period. The Q&A will be used to understand how the paper applies to the topics above. The goal of the Q&A is to guide and promote work in the later small group discussions. |
| 15:15-15:30 | Break |
| 15:30-16:30 | Complete paper presentations |
| 16:30-17:30 | Form small discussion groups and develop concrete answers to the above topics. Produce two examples of challenges, recommended techniques, and future research areas for each topic. |
Wednesday, 20 Feb
Working Session 6 (Adaptation) will be joining this working session. This will provide a larger forum for WS6 and provide us more information on how adaptation interacts with analysis and design.
| 15:30-16:00 | Two paper presentations. Presentations will be 10 minutes with 5 minutes of questions and answers. |
| 16:00-16:30 | Complete small group discussions |
| 16:30-16:45 | Break |
| 16:45-17:15 | Discussion group readout: Each discussion group will share their examples. Questions and discussion will be focused on explaining and understanding the examples. |
| 17:15-17:30 | Organize deliverables: Prepare summary slide and identify what material to include in the summary report. |
Deliverables
- Summary Presentation Slide - Photo of the Summary Presentation Slide
A single PowerPoint presentation slide that summarizes the results of the working groupʼs discussions. This will be used in the closing plenary session.
- Summary Report - PDF Version
The report will be produced by Claudia and Tom within a week of the conference ending and will be published here. The working session needs to summarize the findings and identify any other material to include in the report.
