The retreat was March 16 - 19.
Who went
- Turadg Aleahmad : full time
- Jim Slotta : full time
- Anthony Perritano : full time
- Jeff Holmes : full time
- Edward Burke : Wed morning - Fri morning
- Scott Cytacki : Wed morning - Fri morning
- Nate Titterton : Wed afternoon - Thu night
- Matt Fishbach : Wed afternoon - Thu night
- Chris Hoadley: snowed in
| Time | Activity |
|---|---|
| Tue night | arrival |
| Wed morning | Vision discussion |
| Wed afternoon | Level 1 discussion |
| Wed evening | Level 1 modeling |
| Thu morning | Level 2 discussion |
| Thu afternoon | Level 2 modeling |
| Thu night | decompress |
| Fri morning | bye-bye |
Activities in advance:
| Mon Mar 8 | plan for focus groups, recruiting (eg. classroom scenarios, authoring experience, assessment, activity structure) |
| Tue Mar 9 | conference with Concord, flesh |
| Tue Mar 9 | explain focus groups and recruit (to attend focus group or submit scenario by e-mail) |
| Wed Mar 10 | focus groups |
| Thu Mar 11 | focus groups |
| Mon Mar 15 | practice UML |
| Tue Mar 16 | run through focus group results |
| own time | flesh out Level 1 and 2 more, define critical points |
| developers write technical use cases | |
| familiarize with features and pitfalls of potential technologies (eg. EML, JXTA, JINI, RMI, J2EE, SOAP, REST, XPath, Groovy) |
Now
- investigate existing technologies and frameworks...things we don't have to write!
- User database / security
- Peer to peer communication
- Concurrency and synchronization of databases
- RMI. RPC, XML
- Web Services
- Determine interdependencies in technologies
- EJB requires a server, for example
- Survey existing Concord and Berkeley technologies
- Continue fleshing out the distributor thick-client model
- Client-side computation
- Concerns like bloating the client and need for high flexibility
- Generate use case scenarios of implementation
- Includes authoring, developing, teacher and learner context, research
- Re-use legacy code where applicable
- Client could be designed somewhat robust (e.g, download .jar files) allowing concurrent development of SAIL data model
- Possibility: code WISE 3 as a reference implementation
- Possibility: translate several modules, e.g., Drawing, Discussions, Concepting
- Questions:
- What important elements from Concord will move over?
- "Workspace" = structures that include all elements which need to be downloaded
Development Goals:
- Possible division of labor:
- Concord for authoring environment
- Berkeley for learning environment
- Client core concepts (medium for executing a run) must happen early in process (Fall 2004)
- Client must be fast, good cacher upstream and downstream, good and dependable listener, flexible grower, able to handle multiple user accounts
- Users need plug-able authentication
- JAAS
- initial system of users will be a reference
- need caching
Milestone Goals:
- SUMMER 2004:
- Prototype "Owlish" client. Using J2EE. Explore issues of caching
- Investigate technologies and commit to early platform
- Confirm minimum hardware requirements
>Matt needs a new dual processor Mac G5. Ha ha.
> Learner Machine: Approx. 0.5GHz processor with 128MB RAM?
> Classroom Server: Approx. 1GHz processor with 256MB RAM?
- FALL 2004:
- SPRING 2005:
- Learning environment Alpha
- SUMMER 2005:
- FALL 2005:
Things Needed on WIKI
- Rationale for initial technology platform options. Example: J2EE, What is it, Why is it good, What are its liabilities.
