Guests are welcome to view our materials. To subscribe, edit, view raw markup, etc., you'll need to register for an account. Accounts are free (and will always be free) - your involvement helps us directly and indirectly (by demonstrating that our work matters to our funders...) StartingPoints has more info.
So what is the root of this project?
- Want to create a catalog of research methods in computing
- Want exemplar research that uses these research methods
- Want community to agree that these are the research methods we have in computing
Other goals
- Recruit community members
- Serve as the "home page" for new computing researchers
- Provide support for the research process including recommending communities, conferences, schools, internship opportunities etc (computing research 101 digital space)
- Provide support for the tenure track process
- Help to recruit students
- Make computing research more visible
- Make computing research more visible as a field
- Evaluate/Validate the personas
- Come up with detailed scenarios
- Have the community flesh out the scenarios
- Publish each aspect of the work
- Layered Evaluation : Evaluate each aspect of the work to promote reusability of "successful" parts
- TWiki is the first prototype
Personal needs:
- I need people to work through and vocalize how they are interacting with the personas (to ensure I'm not limiting people's experience/usage?)
- I'm really worried about the blacklist plugin...I think its very limiting.....cant we take a more open approach?
- A paper that discusses "Right and Rewards of Author contribution to non-institution (open-source) digital repos"
- Need to go back to the paper and understand what people's problems are with computing research
- Perhaps do a study of interviews with professors from different schools around the East Bay talking about what they'll want from a "Computing research 101 space"
Scenarios:
- Problem Scenarios are the current state of affairs. They also include wish lists of ideal interaction/functionality
- Activity Scenarios are sort of a 1-1 map from problem scenarios. They specify how to solve the problem scenarios (functionality). They also try to resolve current tradeoffs (especially of basic services)
- Information scenarios expand on the Activity scenarios. They make more detailed explanations of how the activity scenario will be/is?
- Interaction design scenario is the big one. It specifies input, system output, screen design, how long it takes to get something done etc
-- IfiOkoye - 05 Jun 2008
|
Copyright 1999-2009 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.