3 Index Introduction CSCW Origin and State of the ArtMotivationObjectivesCSCW Origin and State of the ArtBasic Concepts regarding CSCW EnvironmentsConceptual Model for CSCW EnvironmentsTOUCHECase StudyTOUCHE CASE ToolConclusions, Contributions and Future Works

4 IntroductionMotivationAt the beginning, technology solved problems that people had in an individual way. Soon afterwards, groups of people work together through computer networks.Technology has evolved to cover people’s needs: communication and collaboration among them to achieve a common objective.Computer Science systems have evolved in such a manner that now we usually talk about software communities instead of Personal Computers.

5 Q Introduction SE: Software EngineeringMotivationSE: Software EngineeringCSCW: Computer-Supported Cooperative WorkGroupware: Applications based on CSCWCSCW allows extending ideas from different fields to computation.SE has guided the development of software applicationsprocess models and methodologies.SE could guide the development of groupware applications.But… groupware has special characteristics:collaboration, cooperation, communication, coordination, time, space, etc.if considered, they can contribute to achieve a quality developmentQ

6 Requirements gathering Prototype and User evaluationIntroductionMain ObjectiveThe definition of a process model and a methodologydevelopment of CSCW interfacesattending explicitly to the specific featuresto cover the lack of specific methods in this senseClient1Requirements gathering2Prototype and User evaluationAnalysis3Design4Implementation

7 Introduction ObjectivesKnowing time-space, collaboration, cooperation, coordination, communication concepts. Analysing the way in which task modelling, awareness and the Model-Based User Interface Development approach can be adapted and extended to be applied for Collaborative Environments.Conceptual modelcommon and well defined vocabularyProcess modelto develop quality CSCW systems which considers the user as part of a group and taken into account special features on the user interface.Methodologyto be used in every stage in the defined process modelTraceabilityIntra & inter-stageCase studyto validate its utility and to show an example of use.Tool CASE prototypeto support and automate the proposed process model.

9 CSCW Origin and State of the ArtThe very beginning of CSCW and groupwareMid ’70s  Office AutomationExtension of some applications to group ideas1981  GroupwarePeter y Trudy Johnson-LenzPeter y Trudy Johnson-Lenz, 1978: “intentional group processes plus software to support them”Mid ’80s  CSCWFrom a multidisciplinary conferenceS. Greenberg,1991: ”The study and theory of how people work together, and how the computer and related technologies affect group behavior.”CSCW starts as an effort from very different fields with an only objective: people interested in using technology to support them in their work

10 CSCW Origin and State of the ArtThe basis of CSCWCoordinationCooperation & ColaborationCommunicationGroupware is application & CSCW is the philosophy behind groupware

11 CSCW Origin and State of the ArtClassificationsClassifications are a way to order groupware applications to know their featuresFirst classification: Johansen’s Time-Space MatrixBut applications are getting more and more complicatedSometimes it is very difficult to classify an application into one only cellThere are some other newer solutions: Grudin, Ellis, Andriessen, DeSanctis, etc.Same TimeDifferent TimeSame placeFace to face interactionAsynchronous interactionDifferent placeSynchronous distributed interactionAsynchronous distributed interaction

14 CSCW Origin and State of the ArtSome examplesMedical applicationsSocial awareness and availabilityarchitectureslarge displaysKnowledge sharingEvaluation methodsSystemsDistilling knowledgeCommunitiesInteractions with shared displaysTabletop designOrganizational issuesGamesCases from the fieldDistributed teamsSynchronous collaborationGesturing, moving and talking togetherBridging the physical and the digitalInformation sharing and accessUnderstanding CSCW: looking from aboveOperational transformationInterruptions

15 Index Introduction CSCW Origin and State of the ArtBasic Concepts regarding CSCW EnvironmentsConceptsCSCW MethodologiesThe need of a common languageConceptual Model for CSCW EnvironmentsTOUCHECase StudyTOUCHE CASE ToolConclusions, Contributions and Future Works

16 Basic Concepts regarding CSCW EnvironmentsSince every researcher,in every CSCW research,considers some concepts……when talking about CSCW it is necessary to know about…

20 Basic Concepts regarding CSCW EnvironmentsTasks and group tasksOperatorsNotationOperatorDescriptionT1 ||| T2interleavingthe actions of the two tasks can be performed in any orderT1 [] T2choiceselection between tasksT1 |[]| T2synchronizationthe two tasks have to synchronize on some actions in order to exchange informationT1 |=| T2order independenceThe two tasks must be performed. The first one must finish its performance before the second one startsT1 [> T2deactivationwhen one action from the second task occurs the first task is deactivatedT1 >> T2enablingwhen the first task is terminated then the second task is activatedT1 []>> T2enabling with information passingIn this case we want to highlight that when T1 task terminates it provides some value for task T2 besides activating itT1 |> T2suspend-resumeSuspension / resumpsion of the taskT1*iterationthe task is iterativeT1(n)finite iterationhow many times the task will be performed is specified[T1]optional taskits performance is not mandatoryTrecursionthe possibility to include in the task specification the task itself.Type of tasksAbstraction. are tasks which require complex actions.Interaction: are performed by user interactions with the system.Application: are completely executed by the system.User: are performed by the user, without interacting with the systemCooperation: composite tasks where several users participate

22 Basic Concepts regarding CSCW EnvironmentsAwareness and shared workspaceAwareness: “knowing what is going on” [Endsley, 1995]Gutwin and Greenberg [Gutwin, 2004] summarize four important points about awarenessAwareness is knowledge about the state of a particular environment.Environments change over time, so awareness must be kept up to date.People maintain their awareness by interacting with the environment.Awareness is usually a secondary goal —that is, the overall goal is not simply to maintain awareness but to complete some task in the environment.It is very related to shared context: A shared context is a set of objects where the objects and the actions performed on the objects are visible to a set of users. [Ellis, 1991]

23 Basic Concepts regarding CSCW EnvironmentsAwareness and shared workspaceWorkspace awareness elementsWorkspace awareness elements (past)[Gutwin, 1997]CategoryElementSpecific questionsWhoPresenceIdentityAuthorshipIs anyone in the workspace?Who is participating? Who is that?Who is doing that?WhatActionIntentionArtifactWhat are they doing?What goal is that action part of?What object are they working on?WhereLocationGazeViewReachWhere are they working?Where are they looking?How much can they see?How far can they reach?CategoryElementSpecific questionsHowAction historyArtifact historyHow did that operation happen?How did this Artifact come to be in this state?WhenEvent historyWhen did that event happen?Who (past)Presence historyWho was here, and when?Where (past)Location historyWhere has a person been?What (past)What has a person been doing?techniques to support workspace awareness [Gutwin, 2004]embodimentscan provide people with a representation in the workspaceexpressive artifactsworkspace objects that maximize the amount of feedthrough information that is provided for the group’s benefit.visibility techniquesaddress the visibility problem

26 Basic Concepts regarding CSCW EnvironmentsMethodologies for CSCW systemsThere is a lack in this senseMany methodologies and process models, but no specific ones regarding CSCW systemsMany approaches[Dumont, 2001] describes a method to specify interfaces by using scenarios[Zhao, 2001] briefly shows the process model of a cooperative design[Kirsh, 2004; Morris, 2004] talk about methodologies to evaluateEtc.AMENITIES (A MEthodology for aNalysis and desIgn of cooperaTIve systEmS) [Garrido, 2003]It does not take into account UICIAM (Collaborative Interactive Applications Methodology)It is not a process model, but a methodology which could be integrated into a process modelIt has been parallel developed to TOUCHE

28 Conceptual Model for CSCW EnvironmentsThe need of a common languagePsychologyPhilosophyCSCW… and many other areas…Computer ScienceAnthropologyResearch fields inside Computer Science

29 Conceptual Model for CSCW EnvironmentsThe need of a common languageGetting a common well-defined vocabulary…… is very important when people from different fields work togetherThere are several approaches to classify and/or specify concepts related to a specific domain:Taxonomiestoo simple and too fixedFolksonomies (Vander Wal 2004)“Tagging allows for the kind of multiple, overlapping associations that the brain itself uses, rather than rigid categories”, O’Reilly 2005“Taxonomies limit the dimensions along which one can make distinctions, and local choices at the leaves are constrained by global categorizations in the branches. It is therefore inherently difficult to put things in their hierarchical places, and the categories are often forced”, Gruber 2005Microformats (Tanket 2005)“a set of simple, open data formats built upon existing and widely adopted standards”Not to especifyOntologiesA data model that represents a set of concepts within a domain and the relationships between those concepts“An ontology is an explicit specification of a conceptualization”, Gruber 1993

30 Conceptual Model for CSCW EnvironmentsAn ontology as a solution to vocabulary varietyThe definition of an ontology could be very complete……as complicated as you needW3C -- provides  OWL Web Ontology LanguageIn this PhD Thesis a solution to the lack of a common vocabulary is proposed by means of the formalization of a list of terms which are well defined and relateda list of concepts around the collaborative environments knowledge domainObjective: having a foundation to specify…the organizational structure of the users in a CSCW systemrelationships among themIt is a conceptual model to speak a common language and to avoid ambiguities in the use of such terms.The method we use to represent, define and put into relation the concepts we consider fundamental when modelling the organizational structure of the users of a CSCW system is an ontology.It is not essential to develop a complex ontology with such concepts

33 Conceptual Model for CSCW EnvironmentsThe proposed conceptual modela little example: co-interactionDefinitionA co-interaction is a group organizational relationship among two actors which express an interaction among them to achieve a common objective, which could not be reachable without such an interaction.Contextual DefinitionSee TaskSee ObjectiveGroup Task, ObjectiveTwo system actors colud be related by means of a co-interaction to collaborate performancing a group task and reaching a common objectiveTaskA co-intereaction shows a collaboration among two system actors. In order to do this interaction, each actor have to perform a composite or atomic task. Such a composition would be a group task. Different co-interactions carry out more complex group tasksSynonymsNoEnglish termCo-interaction

36 Requirements gatheringTOUCHEGeneral descriptionTOUCHETask-Oriented and User-Centred Process Model for Developing Interfaces for Human-Computer-Human EnvironmentsProcess model & methodologyWe have arrived up to this point afterthe study of the state of the artthe study of fundamental conceptsthe implementation of some tools which has provided us with the necessary expertise: CE4Web, etc.establishing the bases by means of a specific vocabulary described in the ontology and the conceptual model3421Requirements gatheringAnalysisDesignImplementationClientNormal steps in the process modelPossible iterationsTraceability among stagesPrototypeandUser evaluation

37 Requirements GatheringTOUCHEStage 1.- Requirements gatheringAnalysisRequirements GatheringStep 3System objectives definitionStep 4Requirements definitionStep 2Organizational structure and system actors identificationStep 5Requirements and objectives ordinationStep 1Problem domain knowledge acquisition“We need to model what we learn from our users, to confirm with them and with our clients our understanding of the work to be supported and to incorporate that understanding into the software we build” [Constantine, 1999]Based on the work of Amador Durán [Durán, 2000]Modified to consider CSCW issuesSystem Requirement Document or DRS

44 Requirements gathering Behaviour and StructureTOUCHEStage 2.- AnalysisRequirements gatheringAnalysisBehaviour and StructureRoles and TasksRole identification and descriptionTask identification and descriptionActorsRequirementsDesignStructureBehaviourCDTDClassesOSDAbout the problem domain studyLooks for whatRoles and tasks are identified and describedTraceability

54 TOUCHE Traceability Intra-stage Inter-stageStage 3.- DesignTraceabilityIntra-stageUsing the same elements in each model (navigation & presentation)Inter-stageDomain objectsManipulated by AIOs in the AUIDActors and rolesIn the ACIDTasksTo go from one UI to another in the AUIDSome of them are necessary in some AICs in the ACID

57 Index Introduction CSCW Origin and State of the ArtBasic Concepts regarding CSCW EnvironmentsConceptual Model for CSCW EnvironmentsTOUCHECase StudyProblem DescriptionHow to develop it within TOUCHETOUCHE CASE ToolConclusions, Contributions and Future Works

58 Case StudyProblem description: COREA (Collaboration & Cooperation, Reviewers and Authors)The groupware application should allow some users to elaborate the same document through the InternetCollaboration, communication, cooperationThe document will be a draft copy up to the moment one of them decides to make public a final version.There is a little review process beforeThe final version is sent to some reviewers as a candidate document.Reviewers analyze the document and set up their opinion.Then, one responsible person analyzes all the opinions and decides if it is really published or not.Final published documents can be read by other users, who can make some comments about the already published documents.

74 Index Introduction CSCW Origin and State of the ArtBasic Concepts regarding CSCW EnvironmentsConceptual Model for CSCW EnvironmentsTOUCHECase StudyTOUCHE CASE ToolImplementation and Working of TOUCHE CASE ToolConclusions, Contributions and Future Works

75 TOUCHE CASE ToolIntroductionProcess models and methodologies traditionally proposed in Software Engineering show its real utility when there is a CASE tool that supports them to carry out the projects from the beginning as much automatically as possible.It mechanizes some tasks and makes the specification of the system easier.A CASE tool maintains the coherence of the systemThe mechanization of actionsdecreases the work that analysts and developers should accomplishsource code is produced from the very first stage of requirements gathering.

78 Conclusions, Contributions and Future WorksSoftware has changed  user as a member of a group | Through the InternetImportant to considercommunication, colaboration, cooperation and coordination in software developmentthe user in the shared workspaceNew development method, techniques, methodologies are necessaryIn this work we have contributed with:Conceptual modelClassification techniqueProcess model and methodology: from HCI to CSCWCASE Tool to support the methodologyThere are several contributions and publicationsIt is a wide workThere are a lot of possible extensions to this work: future works

79 Conclusions, Contributions and Future WorksThe precise definition of a process model, and the methodology to be performed in every stage, for the task-oriented and user-centred development of user interfaces for CSCW systems: TOUCHEA classification method for groupware tools based on the most relevant researchers’ works in the areaA conceptual model for CSCW environments to work with a common vocabularyAn adaptation of the requirements gathering stage of mono-user information systems to a requirements gathering stage centred on CSCW systems.Proposal of an analysis methodology for CSCW systems considering both the structure and the behaviour by defining new specific models and associated diagrams.An adaptation from the HCI (human-computer interaction) interface design to the CSCW onedefinition of new facets based on awareness criteriaextension of the notation (definition of new AIOs)definition of new diagrams for representing navigation and presentationAn adaptation from the HCI interface implementation to the CSCW systems interface implementation: new CIOs, composed CIOs.Establishment of the traceability inter- and intra stages within the process model.A CASE tool prototype to assist the whole process model.

83 Conclusions, Contributions and Future WorksPublications6 international journals (5 LNCS)9 international conferences6 national conferences1 international book chapterVictor M. R. Penichet, María D. Lozano, J.A. Gallud: An Ontology to Model Collaborative Organizational Structures in CSCW Systems. International book chapter for publishing. Springer. Selected from Interacción 2006 to be extended

84 Conclusions, Contributions and Future WorksConceptual model extension: dynamism, role changing, session modelRequirement analysis and validation stages in the first stage: Requirement gatheringDevelopment of a groupware toolkit with a complete and common set of groupware toolsCSCW patterns to improve development times and qualityIntroduction of evaluation and quality criteriaConsideration of accesibility and usability criteria: a new project has started from this pointDesign extension to consider all the dimensions: Data structure design, Architectural design, Procedural design introduceTaking into account planification and risk analysis, and specific stages to situate prototyping and evaluationImproving the CASE Tool: design and usability of the tool; automation and traceability; implementation stageUsiXML extension with the presented proposal for CSCW systemsExtension of the process model to ease communication protocols, access control and notifications in groupware applications [Ellis, 1991]