1. Presented by the GMU Win-Win Team March 17, 2004 Status Report

2. Performance Analysis ACTION PLAN:  Create role models  Create use cases  Create content models  Create wire frames  Plan usability testing  Design and develop prototype  Continue to research and to write white papers

3. From Needs Analysis to Design Action Plan Employing a usage-centered design will allow the WIN-WIN team to focus on what the stakeholders are trying to accomplish and on what the software, via the user interface, will need to accomplish those tasks. This process incorporates five key elements:  Pragmatic design guidelines  Model-drive design process  Organized development activities  Iterative improvement  Measures of quality (p. 23) The interrelationship of role models, task models, and content models provides a multi-perspective approach to viewing the work, the user, and the interface to support them. This model-driven approach helps the designers to frame issues and focus on what is essential (Constantine et al., 1999, p. 29).

4. DESIGN Create role models The relationship between the users and solution system is known as the role models. These are abstractions; that is, they are an aggregation of people’s needs, interests, expectations, behaviors and responsibilities characterizing their relationship with the system. In constructing these models, the designer is aggregating information to evolve an understanding of (1) How are they going to interact with the system; and (2) What do they expect from the system. Through telephone and face-to-face interviews, we asked stakeholder representatives:  What do you do in your job?  What would help you to do your job more effectively?

5. Design Benchmarking CoPs  Math Forum Math Forum  Tapped In Tapped In  Johns Hopkins ELC Johns Hopkins ELC  Indiana's Inquiry Learning Forum Indiana's Inquiry Learning Forum

6. DESIGN Create use cases Based on the role models, the use case is an abstract, simplified, and technology-free narrative description of one meaningful task or interaction with a system by an external user. Use cases describe the actual interaction between a user and a system in terms of user actions and system responses taking place through a particular user interface. Essential Use Case is:  One kind of use to which a system can be put  A narrative description of interaction between the user in some user role and some system  Describes, in narrative form, an interaction that is complete, meaningful and well-defined to a particular user  Based on purposes or intentions of users rather than concrete steps or mechanisms

7. DESIGN Create content models The interface content model is an abstract representation of the contents of a user interface, (i.e., the various interaction spaces for a system) and their interconnections. Each use case will be supported in the content model design (Constantine et al., 1999)  Each interaction space becomes a collection of parts of the user interface (i.e. Window, screen, dialogue box) populated by specific user interface components (toolbars, command buttons, selection lists, etc.)  Within each interaction context, the tools and materials to be supplied to the user are represented by post-it notes in various colors  Enables designers to work out structure and overall organization of the user interface without having to draw pictures and commit to a particular choice of graphical user design  Retains a focus on the problem, on usage and user needs over a longer period of time - tuning in to what is truly necessary.

8. White Papers –High Tech High Schools Overview of technology in schools Theoretical Framework Implementation The model –After-school Programs (AS) & Community Technology Centers (CTC) Overview of AS & CTC Theoretical framework Identify key common attributes Identify Challenges & make Recommendations –Community of Practice Overview of Communities of learning and CoPs Theoretical framework Challenges of building, maintaining and sustaining CoPs