ArchStudio Meeting: July 25, 2008
Meeting to discuss and decide on ArchStudio 5 xADL design issues.
Logistics
- Location:
- ICS2-136 on the UCI Campus
- Time:
- 11AM-5PM (scheduled)
- Notes:
- BYO Lunch
- Attendees:
- TBD
Outcomes
- TBD
Agenda
Old Business
- Open ticket status
- TPS/SVN integration problems
- TPS Performance problems
- Ensuring archstudio-dev can be on the CC list for Trac tickets without requiring moderation.
- Revisit metamodel issues briefly
New Business
Following is a list of questions we would like to attempt to answer at this meeting. Feel free to refine/expand the list, and send answers to Kari Nies.
- Main question: What should we change in the design of xADL for ArchStudio 5 and how should we change it?
- What should be the future of xArch?
- Basic concepts? (e.g., identifiers, links, descriptions)
- Changes to structural modeling?
- Handling of subarchitectures?
- Changes to xADL's type system?
- Alternative type systems?
- Future of variants, options, and versions?
- Future of changesets?
- Future of hints?
- Other features?
- Traceability
- Implementation mapping
- Eclipse integrations?
- UML-like diagrams?
- etc.
- Integration of third-party schemas / metamodel elements?
- What should our schema versioning policy be and how should it be implemented?
- How should we help instance documents track the evolution of xADL?
- To what extent should xADL be separated (in our marketing) from ArchStudio?
