Navigation


Home

Final Presentation

Final Prototype

Individual Assns

Work Distribution

 

Assignment #1
Project Proposal

Assignment #2
Personas, Goals, and Task Analysis

Assignment #3 (REVISED)
Scenarios, Comparative Analysis, and Initial Design

Assignment #4
Low-fi Prototyping and Usability Testing

Assignment #5
First Interactive Prototype and Presentation

Assignment #6
Heuristic Evaluation

Assignment #7
Second Interactive Prototype and Heuristic Evaluation Integration

Assignment #8
Pilot Usability Study and Formal Usability Test Design

Assignment #9
Third Interactive Prototype and Final Write-up

Assignment #3 REVISED
Scenarios, Comparative Analysis, and Initial Design
March 11, 2004

Table of Contents
  1. Summary
  2. Task Scenarios
  3. Revised Initial Designs
  4. Revised Personas and Task Analysis
  5. Other Issues
  6. Comparative Analysis (not changed)
  7. Assignment #3 Original Version

  8. Work Distribution Table

 

Collaboration Repository: A Brief Summary

The Collaboration Repository project is a repository of research documents, field project information, and authors in the area of 'IT and Development' that will feature user annotations. The project has been designed to service a growing community of individuals from academia, research, non-profits and government who are working in some form in IT and Development. This is an area that is still in its infancy and lacks a reliable central information repository. The repository will have an open structure, encouraging users to add and edit information on projects and research. Initially, it will be monitored by moderators from within the Berkeley community. However, the long-term goal of the repository is to allow users to select their own moderators.

In short, the Collaborative Repository plans to be for the research area of 'IT and Development' what the ACM Digital Library is for Computer Science, except that the Collaborative Repository is meant to be a lot more decentralized. In the first stage, we plan to create the structure for the database and a user interface for annotations. The annotation feature, very important to this system, is meant to allow users to comment on the data items and documents stored in the repository. The overall goal at this stage is to create an open-enough structure so that later improvements are easy to implement.

 

 

Task Scenario #1: Viewing and Adding Annotations

Jeff is working on his latest economic cooperation plan, involving two well-known organizations. He finds a project in the Collaboration Repository about building a small business in the town of Mbale, Uganda. After reading through the project summary, he clicks on the "View/Hide Annotations" button to view all the annotations. The page refreshes, showing a small icon following any annotated text. Jeff randomly clicks on an icon and a small pop-up window appears, showing a list of all the annotations for that icon in the top half, and the first listed annotation in the lower half of the window. He reads a few of the annotations and finds them useful for expressing short comments and ideas to specific parts of the text. Jeff closes the pop-up window and continues on to the user reviews.

After reading a few user reviews, Jeff decides to add his own annotation to one of them. He selects the text, "NGO strategic planning and organizational development," and clicks on the "Annotate" button. A new window pops up with the text that Jeff has selected as well as some form fields for him to fill in and add his annotation. He fills in all of the fields and types in a short blurb about the program he is currently developing, then clicks "Save." The pop-up window closes and the project page refreshes, showing a small icon following the text that he just annotated. He clicks on the icon and reads through his own annotation. Jeff feels satisfied that he has contributed his knowledge, and found some valuable information for his economic cooperation program as well.

 

Task Scenario #2: Creating a Project

Tamara Sen has been working on a project with her crew of graduate students on creating a GSI map to submersible borewells in rural Bangladesh. Opinions on the use of borewells are highly contentious, especially in the flat plains of Bangladesh, which are areas highly prone to drought. Tamara has a disadvantage in being several thousand miles away from her test bed. Thus, she is very keen on receiving information from the field on what development professionals and planners think about this project.

She goes to the Collaborative Repository and adds the basic information on her project, inserts a short summary, and clicks on a "Request Review" button for her category. By doing this, she ensures that everyone who subscribes to the mailing list for categories such as "/resources/water," "/asia/bangladesh," and "/information_systems/GIS," will know that a new project has been added, and that the project creator is looking for reviews. With the knowledge that she has just opened a Pandora's Box, Tamara waits for the flurry of reviews to be posted to her project. She wonders if she should opt to receive  all the reviews of her project through email reminders.

 

Task Scenario #3: Searching for a Project/Document

After endless hours of searching the web for information about healthcare technologies in Colombia, Stephanie has found little credible and relevant information. Realizing she needs a much more trustworthy source, she turns to the Collaboration Repository after hearing a colleague mention that it helped their organization. Stephanie goes to the website of the repository and clicks on "Search." Presented with a set of categories options, along with a specialized keyword search prompt, Stephanie can't contain her smile. She selects the most relevant choices encompassing healthcare and Columbia, types in 'technology' in the keyword prompt, and hits the search button. The search results contain a series of documents and projects from which she can peruse at will. With so many hours saved, Stephanie now has more time to write her PhD thesis.

 

Revised Initial Designs

Shane's Initial Design

Laheem's Initial Design

Joyojeet's Initial Design

 

Problem Statement Revision #3

"IT and Development" is an emerging area in the field of Development Studies that incorporates academic and field work from a number of disciplines such as Economics, Computer Science, Sociology, Information Management, and Regional Planning. Since it has yet to become an organized subset of any academic discipline, research in this area is scattered and obtained through multiple sources. Consequently, academic researchers must go through a tedious, iterative process of running the same sets of search terms across several generic databases and web sources. Furthermore, IT and Development field workers, or people who are working on location in a developing country, are usually dispersed throughout the world. They do not have easy access to forums, physical or online, to interact and share information with each other or with academia. Since IT and Development is an area of study still in its infancy, case studies are a critical learning tool for field workers. Their field experiences and input are vital in academic research.

The lack of a central repository (akin to ERIC for researchers in Education or the ACM digital library for Computer Scientists), plus the absence of an information exchange forum, creates the need for an open online meeting place where academics and field workers can exchange information and comment on each other's work. This central repository would include both field projects and research documents. It would allow users to easily store information on field projects, document their progress, and make comments on projects and documents. Such an application would be especially useful if layered with a function to allow annotations.

If these annotations can be indexed, they can be more of an asset to users. Users can add or view comments and references which are specific to certain blocks of text. They can define new terms within the text on the website. They will also be able to start new threads of discussion that link into documents. Some key elements to the success of such a system include creating the right mix of openness, to encourage use of the system, devising mechanisms to monitor content, and designing a system that is scalable, which is essential in an area of research that is constantly evolving.

 

Persona of an Academic Researcher
 
Name: Stephanie Kam

Title: PhD candidate in Economics
Organization: UC Berkeley
Age: 29
Education: BA Social Welfare, minor in Economics, University of New Hampshire
Specialties: Microfinance networks, IT for Development
Responsibilities:

- Remain abreast of research and news in South East Asia
- Write papers on relevant topics
- Attend conferences and presentations

Summary:

Stephanie is a 29-year-old graduate student at the University of California, Berkeley, pursuing a PhD in Economics. She has a BA in Social Welfare from University of New Hampshire and a minor in Economics. Her current research is on Microfinance Networks, and she plans to work in South East Asia once her degree is completed. Before coming to Berkeley, Stephanie lived in Oahu, Hawaii, where she was the director of a non-profit organization that helped fund technology projects in throughout South East Asia. When not working, she can be found perusing the Economist, painting for hours on end, and attending social mixers.

Stephanie's academic or personal work has always involved research in development-related projects. Often described as focused and resourceful, she starts her day early to accomplish her many tasks, ranging from research topics to Bay-Area Economic Forum meetings. Being pressed for time, yet focused on the task at hand, she sometimes finds herself spending hours of fruitless searches on the web.

When she does find a relevant document on the web, Stephanie is often skeptical. Her rigorous and detailed approach to analyzing leads her to believe that many times, sources online are exaggerated, biased, vague, or short on empirical evidence. She is especially interested in getting more direct commentary from development professionals working in the field in developing countries. In addition, Stephanie is willing to contribute her knowledge and expertise to an organization or online site if it had significant interest and exchange of ideas.

Goals:

  • Find credible sources. Having a way to get feedback and commentary from sources helps build trust on the documents and reports she finds online.
  • Efficient searching. Given her demanding schedule, having a central source to begin searching for information can save countless hours.
  • Up to date resources. Stephanie wants to know the latest news on current projects and work. This will help her stay abreast on research and news in South East Asia.

 

Persona of an NGO Program Coordinator
 
Name: Jeff Calder

Title: Program Coordinator, Sub-Saharan Africa
Company: Foundation for African American Economic Cooperation
Age: 33
Education: BA Business Administration, Georgetown University; MA International Affairs, Columbia University
Work Experience: Peace Corps Volunteer, Uganda; US Department of Commerce African Trade Policy Analyst

Summary:

Jeff is a program coordinator for the Foundation for African American Economic Development, a non-profit organization based in Seattle, Washington. His organization's mission is to foster economic cooperation between Africa and the United States by promoting commercial and educational activities. The Foundation serves as a hub through which U.S. private sector companies are connected with non-governmental organizations (NGO) and grassroots organizations operating in Africa. Jeff's job is to develop partnership programs where the American company will guide the NGO to increase private sector investment, build business relationships, and improve the overall environment for business in Africa. His programs must address issues of decreasing unemployment, increasing family income, and educating young people.

To develop these programs, Jeff must first research many different organizations to successfully match up the goals of the American company with an appropriate organization in Africa. He draws upon his network of contacts in Africa and the US, making many phone calls to setup meetings and discuss program objectives. These phone calls often last over an hour, making his phone bill a nightmare. After matching up the organizations, Jeff must fly to Africa, where he meets with senior directors to flesh out the program in detail. These business trips take up to four months and can involve multiple organizations and programs. To get a better sense of the educational and economic difficulties, he also spends a fair amount of time talking to local residents. Many of his notes are written on pieces of paper, which quickly fall out of order in the shuffle of travel.

While designing these programs, Jeff would like to communicate with other program coordinators working in the field to get their ideas and advice. However, this poses a major challenge since it is difficult to contribute ideas and track their progress without a central and comprehensive repository of the information.

Given his disorganized field notes and the lack of input from other program coordinators, Jeff wishes that there were a single source to go to learn about projects. This site would have interlinked data about related projects, contact information, and the ability to offer and seek advice from other program coordinators and individuals.

Jeff drives a silver BMW X3 and is a fan of jazz and folk music. In his free time, he volunteers at a youth outreach organization, where he works with street kids to keep them in school and off drugs. While in Africa, he enjoys going on safaris and documenting the indigenous rituals and ceremonies.

Goals:

  • Develop cooperative economic programs between a US private-sector company and an NGO operating in Africa.
  • Eliminate impediments to economic growth in Africa.
  • Help individuals build a better life for themselves, their families, and their communities by increasing an NGO's organizational capacity and sustainability.

 

Persona of an Associate Professor
 
Name: Tamara Sen

Title: Associate Professor
Company: University of California, Berkeley (Energy and Resources Group)
Age: 41
Education: PhD in Economics
Specialties: Development Studies, Water Resources, Biomass Energy, GIS/IT use in Energy Project Mapping

Summary:

Tamara is a young and energetic activist-academic who is considered one of the rising stars in her field - irrigation projects in developing areas. She began her career as an economist at Brown University, but gradually shifted her area of interest towards energy-related topics. She recently received tenure at the Energy and Resources Group (ERG) at UC Berkeley, but considers herself a teacher rather than a researcher.

Not surprisingly, her class in Energy Economics is almost always oversubscribed, and her office hours are always overbooked. In her classes, she sometimes encourages reading groups, where students write papers and share them with each other. Students are then handed back copies of their work with written comments and annotations from their peers. However, Tamara grades the students' papers electronically, and sends them back as .doc files with her comments embedded. As a fairly skilled Internet user, she sets up Yahoo! groups for all her classes.

Recently, Tamara has been involved in an NSF grant with other Berkeley professors to do research on IT for Developing Countries. Her main role in the grant is identifying suitable testbeds in developing nations for deploying technology developed at Berkeley. For both this NSF project and for her class, she needs to do many database searches. Most of her research comes from library sources; though she receives valuable academic research through informal links and references from colleagues.

Tamara subscribes to a number of development studies related mailing lists, and saves messages that are of interest to her. She often contacts field researchers through her networks of contacts, and solicits personal opinions from them on existing projects and on her own writings. She wishes there were some way that the mailing list messages and her own conversations with the field researchers could be better documented. Incidentally, one of her colleagues in Computer Science suggested the idea of annotating documents online. Ever since, she has been a strong proponent for creating a database for development studies which can handle annotations.

Tamara is married to a researcher at Berkeley, and lives in El Cerrito. In her spare time, she takes belly-dancing lessons at Ashkenaz, a bar she occasionally visited during her graduate school days.

Goals:

  • Get information on field projects for her NSF grant.
  • Create networks with field researchers for her and her students and use their knowledge in assessing academic work
  • Conceptualize a database for development studies.

 

Task Analysis
Key: high frequency
(hi)
medium frequency
(med)
low frequency
(lo)

* = optional task

Task Stephanie Kam Jeff Calder Tamara Sen
Locate Relevant Research
Search for documents med hi hi
Search for projects hi hi hi
Search for individuals/organizations
hi hi hi
Increase Exposure/Awareness of Organization
Post papers low low hi
Post projects med hi med
Post information about individual/organization hi med low
Writing grants, papers, research results hi med hi
Find New Contacts & Funding Sources
Find existing programs
low hi hi
Find funding organizations low med low
Locate individuals with field work knowledge hi hi hi
Collaborating on Papers/Research
Subscribe and post to mailing lists
med med hi
Seek advice and opinions through email hi med hi
 

 

Justification for Changes in Personas and Task Analysis Table

Justification for Changes in Personas
For all of the personas, we emphasized the fact that they need to search through many different sources of information. The value proposition of our system is that all of the information about a project is located at a single source. The user would only have to visit one website to find all their information needs. Thus, the personas would want to use our system because it offers significant time saving advantages over their old methods of finding information.

To address the lack of annotating, we modified Stephanie's persona to include getting direct commentary from field researchers. We also changed Jeff into more of a field researcher, who travels to Africa and collects data in order to develop his programs. The ability to annotate projects and documents would allow him to share ideas with other program coordinators and better develop his programs. Annotating is something the personas would be doing in order to help other people out, as well as a task they would do to obtain information (sort of like a contextual discussion list about a specific topic).

We replaced Betsy's persona with that of Tamara, an associate professor. Betsy's persona did not add anything new to the task analysis, whereas Tamara's includes more tasks revolving around annotating and collaborating with field researchers.

Justification for Changes in Task Analysis Table
We made some changes to the task analysis table to better reflect the tasks of our personas. While it seems that some of the tasks would be done outside of our system, like searching for information on individuals and organizations, we plan to incorporate everything into our system. This way, users will not need to go to different sources to find their information.

 

Privacy and Credibility Issues

Our long-term goal is to get UC Berkeley to host the site; the affiliation with UC lends a lot of credibility to the service. More importantly, we need to build a critical mass of users as a way to build on the credibility further. For purposes of privacy, we will never display email addresses, and tell users at the point of registration and at the point of adding new content, that any information they add with their names attached to it, can be accessed publicly. Users will also have the option of interacting with the system anonymously.

We also need to mention to users that all information they put on the site must be original and not be restricted by copyright. This initially excludes a large number of journals that do not allow their articles on public forums. We allow users to delete any information they put on the repository by making a request to delete from their profile pages.

 

Comparative Analysis

IMDB

ThinkCycle.org

Digital Dividend

AiDA Development Gateway

   

 

Top of Page Top

 

© Copyright 2004 CollaboRepo Team. All Rights Reserved.