CSCW Notes Common probs in design Grudin - 16 years old but same mistakes still being made Make apps and push problems aside. Music - FX. 1998. 10years after Grudin. Successful app Awareness - 1992. Similarities to web and hypermedia but predating slightly Awareness problem. Evaluation a bit dodgy to make it work. Grudin Important to pay attention to who is getting the benefits and who is doing the work. Multi-user different from single user. If people doing the work not getting the benefits then they won't do it Fault in problem anaylsis Hard to design for multiuser people Don't always look at things from other peoples POV Hard to evaluate Have to run it live Differentiated between CSCW systems and apps Systems much bigger scale. Willing to put in more effort/support More important Enforced Apps Smaller Less important Less support People willing to change/be changed for system but not for app. E-prints People not adding papers to e-prints Direct benefits? Possibly to staff but not for postgrad Indirect benefits - looking or other peoples papers but not your own Could add benfits for people who had to upload papers Do annoying tasks for use - more automated Is e-prints a CSCW workspace? Collaberative task Can't edit paper with your name on it unless you were the one that added Is automation a requirement? computer support cooperative Attempt to give a framework for a collaberative process Might become but might not be now. Access grid Grid operator not want to get up at 7am can't use access grid Why was the "grid operator" needed? Cooperative concept mapping - works fine as long as physical layer was up to it (ie connection speed) Both users get benefit and don't have to do much extra work ie clear benefits for the people doing the work Wiki - great for person keeping track. Burden on people who have to add to it. success or failier based very much social group using it. social issues adapting behavior based on situation. Erikson & Keller - Transluscence as opposed to transparancy vs privacy Is it still relevent? In general - yes? In specifics - bit out of date Hard to think for groups. Requirement analysis Collaberation makes design process harder MusicFX Evaluation of CSCW - one hour session with 10/20 users. Not great evaluation. Not long enough to check This evaluation Small improvement Is that due to more control for the users Just different Or because it was actually an improvement Big advantage - not put conceptualy more work on people Staff less work Users small amount of work during sign up (when having to do work anyway) Anything after that voluntary Users feel more in control Task performance possibly not the best measure Network effect Need many users for it to be useful Have to think about communication between people rather than just human-computer