Group Design Project 9
From VMT
- Return to Designing Social Interaction Software
Contents |
[edit] Instructions
- Revise your prototype and scenario based on the heuristic evaluation and the cognitive walkthrough.
- Discuss as a group your recommendations for further design and development of your prototype within the VMT context.
- More generally, discuss your conclusions about support for social networking in the VMT environment, based on the entire course experience.
[edit] Comments on Group Statements
- The comments this week reflect a significant growth in the depth of your thinking about the design. Despite major weaknesses of the heuristic evaluation and cognitive walkthrough to really test groupware, your use of these methods has clearly stimulated a better understanding and refinement of your designs.
- New and revised scenarios also show an important focusing and elaboration of your designs.
- With a little more design of layout details, your proposals are getting near to where some rapid prototyping of a simple version of running software should be developed for actual testing with small groups of users.
- Together, your proposals for new VMT extensions nicely address the problem of supporting social networking. I will share these ideas with the VMT project team and we will discuss these ideas over the summer. Thanks for your stimulating ideas and thoughtful reflections.
- Gerry 10:01, 9 June 2007 (EDT)
[edit] Team A Statement
- Members: Brian, Elizabeth, Olivia
- Date and Time of posting: Olivia 20:40, 4 June 2007 (EDT)
- Statement of improvments to project based on heuristic evaluation review and walk through::
General Description: VMT sync is an interactive forum designed to allow students the opportunity to do basic scheduling and blogging, all within the same application as the VMT TabbedChat. It has a basic 7-day scheduler that acts as a meeting planner and notifier. It includes profile viewing, blogging, and chat features.
We have decided to add the Help Tab back to the VMT. Somehow during week six we forgot to add it back and our walk-though and heuristic evaluation identified this error. It will assist user with learn functionality and solving problems. The detail in the help "Tab" is significant, so much so that, it the class lasted 10 more week, this would be a focus for a couple weeks. Searching help is important...
The system status is shown to users when a new meeting time is proposed. This is done by the system generating an auto e-mail as a result of changes being made to meeting schedules. Changes to blogs will show system status by changing color after the blog entries are read by the individual users. This is set up in the beginning when filling out the profile.
We modified the scheduler tab to make this more user friendly. First, the scheduler functionality was changed so that each date was represented by a clickable button, which is more intuitive for users. The actual date informaton was added to the button face, as well as the approximate meeting duration. Also, the color of the calendar buttons were changed to 'pop' and grab the users' attention. Whitespace was incorporated into the design for aesthetic purposes. The contrast of the bright orange with the whitespace directs the users to the primary functionality of this tab and accurately highlights the focal point of the page.
The remainder of the Sync window was divided amongst the rest of the functionality, which was not graphically shown in our initial prototype diagram. The first area was reserved for profiling and networking purposes. These allow users to track their contacts and math friends. An "Add Friend" button was incorporated to allow the dynamic changing of networking contacts.
The second area was reserved for blogging and messaging. These messages could be related to meeting change times and sorted by user, subject, and posting time. The buttons were clearly labeled so the users could identify their purpose immediately. Adding, changing, or removing a meeting time via these two buttons would update the calendar meeting times accordly. Users would be able to remove a meeting time via the "Update meeting" button by updating the meeting time to a "cancel meeting option". The blog functions is similar to the telephone, where sometime we leave each other message until we schedule to talk or meet about a particular topic or need. A convenient blue text box would allow the searching of blogging/message content.
The last Sync window area is reserved for information about a particular day. For example, if a day is clicked on (such as the Sunday 20-May button), the two buttons will become available, allowing the user to update the existing meeting time, or to add a new meeting time. Two arrows next to the year allows users to scroll between years, instead of scrolling by week to week.
To address Group D's critique on the potential for error prevention in our design, the default timezone of EDT streamlines all chatting and eliminates confusion as to, which timezone scheduling takes place in. There is no need to identify a specific timezone within the actual VMT SYNC tab, because this information is provide in our chat section of the VMT, which is availiable to all Tabs.
- Prototype of VMT Sync Interface::
[edit] Team C Statement
- Members: Ben, Kevin
- Date and Time of posting
Ben 10:31, 4 June 2007 (EDT)
Group statement on project.
Revised protoype and scenario: Our new prototype involves making the features of our revised searchable profiles more explicit. The actions performed are fairly simple and obvious, but we have made changes to streamline the interface (make the time zone component more obvious) and allow for the inclusion of predefined mathematical interests. The new scenario resembles the future scenario as described in a previous posting: a user logs in and needs to find group members for a particular math field. He or she does a search for both a predefined field of interest and their ideal meeting time; the user searches through their results, and uses the new feature which allows them to contact potential group members with one click; some amount of invited group members respond. The user can also search through their new member's profiles, and see who they are friends with; if they share similar interests and meeting times, they may also be invited to join. Recommendation for further design and development: One major suggested feature of our design is that users be able to quickly view the profiles of a user's friends. When a user chooses to edit their own profile, there is a box with the friends of that user listed. The user can type the name of a new friend into a line below the box and click add to add the other user to their friends list. There is also a remove button so a user can highlight the name of a friend and remove it from the list if they no longer want the other user on thier friends list. Being able to work with other individuals is one of the most important parts of the VMT; further development could be done to enable the formation of groups and to allow individuals to more completely identify themselves and more effectively search for potential group members. Conclusions about support for social networking in VMT environment: VMT already uses many tools which are uniquely situated to enable social networking, such as the chat feature, the whiteboard, and referencing tools. Social networking could be further supported by allowing the simple recognition and formation of groups with related interests and shared potential meeting times. This is especially important because the often global nature of networked online collaboration requires efficient and effective group formation in order to allow for the social networking tools to be put to use. One possible addition could be a feature which links novice to expert users. This could be used both in regards to technical questions about how to use VMT and in regards to mathematical questions. This could be institutued in a number of different ways, but the important suggestion (at least in this context) is that the differing levels of expertise which allow for interesting group interaction could also be harnessed to allow for individual skill building as well (which could later be used in a group setting).
[edit] Team D Statement
- Members: Bertha, Kate, Eric, Jeeves
- Date and Time of posting: Jeeves5454 12:44, 4 June 2007 (EDT)
As part of the discussions resulting from reviews and revelations on the initial design features and capabilities of the Mobile Communications Suite, the group felt that it would be necessary to develop new scenarios that would take into account the recommendations and results of our discussions.
The updated Scenario would also indicate more relevant data and fields for the user:
Assumption(s): 1) For users with non-traditional mobile Computing or messaging platforms including Cellphones with text message capabilities and /or email accounts only accessible from a certain location,have enabled usage of the Mobile Communications Extension, and designated the correct chat rooms as part of the user's profile.
2) All discussion boards will have a new tab added that will resemble traditional form views. All users registered in VMT will be able to create a new thread, reply to an existing thread and view all messages.
Scenario 1
The user wishes to enable the mobile communications extension so as to integrate VMT into his current digital lifestyle, and keep up to date with group announcements.
Participant: 1 User with access to traditional and non-traditional Computing platforms (Messaging systems included).
Event: The user will click on the link labelled "My Profile" in the VMT lobby page. Upon loading the page, the user will confirm personal information on names, VMT screen name, external email address, and the default project. To enable the Mobile Communications extension, the user must check a checkbox titled "Enable Mobile Communications". Beside this option will be a help link labeled "What is Mobile Communications?" Once enabled, the links will disappear, and a new sets of required fields will appear requesting a cell phone number or mobile email address, either is acceptable in the field, and the computer will differ between the two based on format. Furthermore, the user has to claim ownership of a discussion. This is easily done by selecting the relevant discussion from the dropdown of all discussions available under the default project. An Alias must be set to reduce complexity in receiving or sending messages. Atleast one discussion must be signed on for the extension to remain active.
Diagram 3 designates configuration of a profile after mobile communications extension has been enabled.
Scenario 2
It is currently the beginning of the week. A new problem has been presented but there has been no input yet. A member of the groups posts the first part of the solution and asks a question. Each group member has a profile which contains their identification as well as non-published cell phone number.
Participants: 1 User with access to traditional Computing platforms. 1 user with access to non-traditional mobile computing/messaging platform.
Event: The Web User updates the Forum Tab in the Chat room with the first part to the solution, and asks a question of the other members. Time is of the essence as there is a narrow window when all members of the team are active around the world. The Mobile Communications VMT extension monitoring the site for each user catches the updated message, and checks the other members affiliated with that chat room. All members associated with that room that are signed up for message updates are separated out, and checked for email or cell phone preferences, and the information is wrapped in an email with timestamp, member posted, user's alias of the forum and message to messaging server. The messaging server determines SMTP server for inbox receipt and contacts service provider. Service provider sends information to mobile User, the process having taken no more than 10 minutes. Mobile communications user, can check messaging platform for message at leisure.
Scenario 3
A problem is being discussed among members of a group. Each group member has a profile which contains their identification as well as non-published cell phone number.
Participants: 1 Mobile user currently on an hour commute, 1 traditional computing user currently spending the next hour researching the discussion problem and connected to the discussion forum.
Event: Mobile user sends a text message posting containing the user's alias of the discussion forum, and the message, as the user has an idea on how to solve the problem,prompting the group to respond. The message goes to a messaging server for VMT that identifies sender of the message with a member of the group by matching up the originating cell number or email header and user profiles. The message is added to the forum by the server. The traditional computing user sees the message when the forum is updated. The web user is able to focus his research using the information provided by the mobile user. How this enhanced the knowledge-building experience: The web user was able to benefit immediately from the mobile user's idea. Without the enhancement, the mobile user would not be able to post his message until after his 1 hour commute, at which time, the web user will no longer be researching the problem. The conversation's development will have been delayed, and so would knowledge-building.
Scenario 4
A problem is being discussed on the whiteboard. Each group member has registered with a username, cell phone number and email address. The users have met once and are in the middle of solving an equation. User one is at a lunch break at work and thinks of a possible variable to the problem at hand. He text messages the forum from his mobile communication device and in turn the forum sends out a text to all the group members via their cell phones or emails. User 4 is disabled and has a mild vision impairment but he has a modified phone to help him read the text. He would not be able to participate in this forum without this extension which allows him to customize his experience. The users meet at the next scheduled time and used the idea to solve the problem.
Diagram 1 and 2 describe the example interfaces present on the mobile communication device and traditional computing device respectively. As such, there are enhancements needed to the screens to designate a complete working model, including modification of titles, location, and information contained on Screen.
Future Plans and Ideas
The group has decided that further system integration is vital to the continued success of the Mobile Communication extension. By tying together disparate parts of the VMT ecosystem information can be distributed using the existing framework and user interface screens. Tying together the ability to send audio, video and pictures as the technology improves is also possible. Finally, development of system integration tools between Personal Information management software such as Google Calendar and equivalents, as well as some social networking sites will help to bridge the gap between work and learning. The development of a successful integrated collaboration tool that is open source and available to the world as a successful education module will improve the sustainability of useful and derivative works on the shoulders of giants. Social networking also requires that the system not supply the onus of continued interactivity on the user alone. Generation of content is dependent on users, but requires stimulus from external sources. In the case of the INFO 608 course, topics and projects were created to provide that stimulus. By enhancing a the immersion experience of collaboration on papers and designing new tools to build upon that concept, users gained an understanding for the alternative viewpoint. Users were able to gather relevant data and ideas and distill this down to information. Lengthy discussions with extensive documentation, often resulted in short one pagers with concrete information once wrung through the group discussion. In addition, collaboration software requires extensive skills and abilities in social networking, and articulation. Ideas incorrectly communicated result in non-implementation and confusion.
- Prototype of Cell Phone Interface, Diagram 1
- Prototype of Dicussion Forum Interface, Diagram 2
- Prototype for Profile Page, Diagram 3
[edit] Team E Statement
- Dave, Fernando, LisaG, Seth_E
- Fernando 23:51, 4 June 2007 (EDT)
[edit] General Description
The current implementation of the VMT Chat tool provides the ability to see users currently logged on to the chat room. Missing from this current implementation is a visual identification as to the group name or topic being discussed. The VMT tool does not support user presence status. Finally, a way to see where learning "buddies" are actively participating in the VMT environment is also missing. The proposed design would incorporate a title area for the chat room, the ability to set user status (i.e. active/away) with audio notification to other users, and keep a buddy list with indication of their current location.
[edit] Scenario
The following scenarios are based on real situations. Names have been changed to protect the innocent:
Dave logs in to VMT. In his infinite wisdom he mistakenly clicks on week 5 while hurriedly logging in and eating his pastrami sandwich at the same time. When the chat window comes up Dave sees the big Week 6 above the user names and realizes he's in the wrong week's chat room. He logs out and logins into the correct week, week 6.
The rest of his group proceeds to log in. They start a discussion into use cases. Midway through the discussion Dave has a stomach ache and has to literally run to the restroom. After 5 minutes of inactivity VMT auto sets his presence to away. Lisa is just about to ask Dave a question but sees that he is away; she continues to discuss the use cases with the other group members. Dave returns and clicks on the pull down and selects "Online" to set his presence in VMT. Lisa hears the system sound indicating a user has returned, which is the sound of a door opening. She then looks at her online status window, sees that Dave is back and proceeds to ask him if he posted yesterdays summary to the Wiki.
As they continue to work on their summaries with Fernando, a new user joins up. Hoj logs into the chat room and notices the big INFO 608 sign above the users. Now knowing that he was in the wrong place he apologies to the group and asks if they know where the Problem of the Week (PoW) chat room was. Since none of the users knew, Hoj proceeded to leave the room in order to email a VMT administrator. Then the new guy, Seth comes into the room and introduces himself. In order to accustom himself to this new strange environment, he adds the rest of the group as buddies. He can see their current status. He feels socially adapted now, and starts his collaborative adventure.
After their first meeting of the week, Fernando decides to change the title to update what meeting they were in. He clicks on update title and changes the chat room title to INFO 608 - Week 6 Meeting #2. On the second meeting, Fernando accidentally deleted everyone's fine work. Everyone in the group became upset. They no longer wanted to keep up with Fernando so they all pressed the delete button on the buddy status, removing Fernando as their buddy.
[edit] Prototype Screen Shots
[edit] Support for Social Networking in VMT environment
Understanding group cognition is the important first step. VMT has evolved as social networking has demanded, expanding to fit certain collaborative needs. To support this, the use of innovative tools and functions ameliorates the collaborative environment. Individuals support VMT functioning, using their "creative" tools to get around some features not supported by VMT. The extensive research and analysis of small group chat environments has contributed to the solutions to support demand for expanding functionality.
- Return to Designing Social Interaction Software
