GTA GroupWare Task Analysis n Task analysis concepts n GTA -Task analysis in design of complex systems n Methods of task knowledge collection n GTA conceptual.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
Advertisements

Using the Semantic Web to Construct an Ontology- Based Repository for Software Patterns Scott Henninger Computer Science and Engineering University of.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
6. Envisioning the future system: Task model 2 Envisioning the future task world, not available for observation but modeling will allow: comparison to.
Concepts in design Functionality and beyond. work organization/ practice Client users’ knowledge/ behavior/needs Technology Task Model 1 Task Model 2.
Knowledge Acquisition. Knowledge Aquisition Definition – The process of acquiring, organising, & studying knowledge. Identified by many researchers and.
Analysis Concepts and Principles
Introduction to Software Engineering Dr. Basem Alkazemi
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Day 2 Prior to today Participated in the one day class on Cognitive Ergonomics, read all material of that class studied the reader for today read the paper.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
ADL Slide 1 December 15, 2009 Evidence-Centered Design and Cisco’s Packet Tracer Simulation-Based Assessment Robert J. Mislevy Professor, Measurement &
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
USE Case Model.
Software Engineering 8. System Models.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Groupware DESIGN Lecture 10.
An Approach to Task Modelling for User Interface Design Costin Pribeanu National Institute for Research and Development in Informatics, Bucureşti, Romania.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Methodology Conceptual Databases Design
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Framework for designing learning objects Jorma Enkenberg & Henriikka Vartiainen This project has been funded with support from the European Commission.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
1 CMPT 275 Software Engineering Requirements Gathering Activity Janice Regan,
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introduction to Software Engineering Lecture 1.
Methodology - Conceptual Database Design
Overview of MOT Knowledge representation system : Basic Modeling Editor LexiconGrammarSemantics Pragmatics MOT Editor.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Part4 Methodology of Database Design Chapter 07- Overview of Conceptual Database Design Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Information Systems Architecture (ISA) Conceptual blueprint for organization’s desired information systems structure Consists of:  Data (e.g. Enterprise.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Methodology Conceptual Databases Design
An Overview of Requirements Engineering Tools and Methodologies*
Methodology Conceptual Database Design
Modelling rich interaction
Object-Oriented Analysis
SYS466 Domain Classes – Part 1.
Methodology Conceptual Databases Design
Presentation transcript:

GTA GroupWare Task Analysis n Task analysis concepts n GTA -Task analysis in design of complex systems n Methods of task knowledge collection n GTA conceptual framework n Representations and tools n Sources

Task analysis concepts n Complex tasks and goals (n to 1) hierarchies, flow, multiple processes n users’ unit tasks (Card, Moran & Newell) & n systems’ basic tasks (Tauber) n primary tasks & n secondary tasks n actions, communication acts

GTA -Task analysis in design of complex systems n Complex systems: multiple users who interact / collaboratemultiple users who interact / collaborate with / through technologywith / through technology n “Phases” in iterative design analysisanalysis specificationspecification evaluationevaluation

GTA -Task analysis in design of complex systems n iterative design analysis specification implementation evaluation

GTA -Task analysis in design of complex systems n analysis Task model 1: current task world Task model 2: envisioning the future

Methods of task knowledge collection Knowledge sources: domain experts / (future) usersdomain experts / (future) users observation of expert behaviorobservation of expert behavior documentsdocuments interaction in situationinteraction in situation Task model 1: current task world

Methods of task knowledge collection n domain experts / (future) users knowledge elicitation: knowledge elicitation: e.g. Sebillotte / Graesser question method e.g. Sebillotte / Graesser question method Question: explain as detailed and complete as possible how you … Answer: “… X and therefor Y” “…X because of Y” “…X because of Y” Additional questions: Why X? / How X?

Methods of task knowledge collection n Interaction in situation (people, artifacts, history) Ethnographic methods, e.g. Ethnographic methods, e.g. interaction analysis (Jordan, Henderson) interaction analysis (Jordan, Henderson) Identify “hot spots” video - content log - review with actors - generate hypothesis - compare with alternative records - identity patterns video - content log - review with actors - generate hypothesis - compare with alternative records - identity patterns

Methods of task knowledge collection Task model 2: envisioning the future Knowledge sources: task model 1 (needs, inconsistencies, conflicting goals) client (requirements, standards, law) technology (constraints, possibilities and expectations, challenges)

GTA conceptual framework Complementary viewpoints, redundant descriptions and cross references: n Agents n Work n Situation

GTA conceptual framework n Agents actors (individual humans, institutes and groups, machines, systems) with attributesactors (individual humans, institutes and groups, machines, systems) with attributes roles, defined with tasks and object relationsroles, defined with tasks and object relations organization (structure of actors, allocation of roles, delegation and mandates)organization (structure of actors, allocation of roles, delegation and mandates)

GTA conceptual framework n Work task / goal structure / actions (related to roles)task / goal structure / actions (related to roles) task descriptions (objects and situation)task descriptions (objects and situation) hierarchical decompositionhierarchical decomposition temporal structure and triggeringtemporal structure and triggering protocols and (expert) strategies - situatedprotocols and (expert) strategies - situated

GTA conceptual framework n Situation objects in object structure (type relations, semantic relations)objects in object structure (type relations, semantic relations) environmentenvironment history of situationhistory of situation

Representations and tools n GTA representations conceptual entitiesconceptual entities structuresstructures media registrationsmedia registrations

Representations and tools n Conceptual entities relation to other entitiesrelation to other entities template format for different conceptstemplate format for different concepts –Task, Object, Role, Agent, Event

Task Template

Object Template

Role Template

Agent Template

Event Template

Representations and tools n Structures, relation between entities of a type: type hierarchies (“is a”)type hierarchies (“is a”) decomposition treesdecomposition trees semantic relations (“contains”)semantic relations (“contains”) flow (of data, of control, triggering relations)flow (of data, of control, triggering relations)

Representations and tools n Media registrations video clipsvideo clips sound tracksound track picturepicture

Representations and tools n Tools: a design environment for collaborative design EUTERPE editors for representation typeseditors for representation types a repository of task model elementsa repository of task model elements representations as a view on the databaserepresentations as a view on the database tools for analysis and reasoningtools for analysis and reasoning translation to HTMLtranslation to HTML

Task World Ontology Task Agent Role Event Object name(string) goal(string) start_condition(string) stop_condition(string) initial_state(string) final_state(string) duration(integer) frequency(string) type(enum) user_actions(string) system_operations(string) name(string) skills(string) attitude(string) miscellaneous(string) name(string) goal(string) name(string) attribute(Name,Value)* action(Name)* name(string) description(string) Contains Responsible Performed_by PlaysTriggers Subtask Uses Triggers Used_by Subrole Is Performed_by

Sources n literature on GTAliterature on GTA EUTERPE toolEUTERPE tool examplesexamples