Differences between revisions 8 and 9
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
|
[http://seams.self-adapt.org/wiki/Exemplars Exemplar] page... |
|
| Line 5: | Line 8: |
| * Populate [http://seams.self-adapt.org/wiki/ModelProblem:Utility Utility] page | |
| Line 6: | Line 10: |
|
* Populate Znn exemplar content from benchmark page: description of Znn system, quality concerns, implementation subsections * Add paragraph snippet for Rainbow solution, port more texts from thesis |
* Populate [http://seams.self-adapt.org/wiki/ModelProblem:ZnnExemplar Znn exemplar] content from benchmark page: description of Znn system, quality concerns, implementation subsections * Add paragraph snippet for [http://seams.self-adapt.org/wiki/ModelSolution:RainbowZnn Rainbow solution page], port more texts from thesis |
Action items to make progress
Exemplar page...
- Bradley:
- [done] Initial page skeletons.
- Help port more text??
Populate Utility page
- Owen:
Populate Znn exemplar content from benchmark page: description of Znn system, quality concerns, implementation subsections
Add paragraph snippet for Rainbow solution page, port more texts from thesis
Challenge Problems for self-adaptive systems
Inspiration: http://www.cs.cmu.edu/~ModProb/KWIC.html
Problems with ModProb is that it is static.
- Really want modern, community-involved, wiki-ish solution
- Allow people to post problems and solutions
Structure of Content
- Description of the exemplar/problem
- Relevance - why is this example a good example
- Quality concerns - what properties does the exemplar expose / elucidate / manipulate? e.g., performance, secuirity, cost, correctness, reliability, availability (exemplars could exhibit one or multiple concerns?)
- Criteria for comparison?
Mechanisms & deployment of exemplar - deployment/installation, effectors, probes, testing environment, ...
- Solution descriptions - what should go in this? Code, outline, repair strategies?
Content Organization
Site is to be organized by the challenge problems.
- To the extent that a technology solves multiple problems, should there also be organization by technology (Give me all Rainbow solutions)?
- What about concern (i.e., give me all performance related examples)?
- What about comparison criteria (i.e., give me all the solutions ordered by engineering cost [for those that address this])?
Being able to do this requires more heavyweight content management system.
Governance
- What is the quality of a solution?
- Should the wiki be moderated?
- Who by?
- What is the problem space? Centralized only? Decentralized, self-organizing, software only or all self-* applications (like adaptive hard drives). Who blesses the problems?