• Sally will combine team slides and post on wiki

2. Standardization

• Team 1 will use single page to present list of technology where appropriate
• Teams will use Gliffy as Task Analysis Graphic; use default font
• Symbology of Task Analysis Graphic is based on Jonassen depending on what task analysis the individual groups use
• We will use the following terminology when discussing/ writing reports for LATIST: Tool – used to describe entire LATIST, component – used when describing one of the three parts of LATIST (Explore, Select, Demonstrate), sub-component – used when talking about sub portions/functions within each individual component, we will use term “select” vice choose, system response will be “display” not provide, we will use “Exit” for all cases vice close.

3. Sub-Component Connectivity

• All teams agree sub-components need connectivity through some time of navigation tool whether based on tagging or other means. We need to validate “user requirement” wording.

4. Sub-team content assignments:

• Teams are not ready to ask the other teams for what they need
• We’ll pick Learning Objectives from Bloom’s Taxonomy Level 1, 4, 6

5. Individual Research Components/Misc.

• Keep working on research papers
• Portfolios due 25th of this month