Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.

Slides:



Advertisements
Similar presentations
Chapter 4 Design Approaches and Methods
Advertisements

Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 11.
The ADDIE Model By: Elva Juarez LEARNING THEORIES.
National Aeronautics and Space Administration Systems Engineering (SE) Tools National Aeronautics and Space Administration Example.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Instructional Design Amal Alelait ET500. Instructional Design  instructional design is the systematic process by which instructional materials are designed,
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Instructional Design Aeman Alabuod. Instructional Design instructional Design (also called Instructional Systems Design (ISD)) is the practice of creating.
1 Configuration Management 101 ITS Professional Capacity Building Program T3 Webinar February 21, 2008.
Project Management Fundamentals Project Organization and Integration
Effective Methods for Software and Systems Integration
7.1 The Software Engineering Discipline 7.2 The Software Life Cycle 報告者 : 林建任.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
CSI315 Web Applications and Technology Overview of Systems Development (342)
THE ROLE OF PROCESS IN SOFTWARE QUALITY By K.KARTHIKEYAN.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Paul Bourke DT211/3 & DT228/3 Team Project Paul Bourke Module Web Page:
Deployment General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation.
PROJECT MANAGEMENT Advanced Design, Multimedia & Web Technologies.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
End HomeWelcome! The Software Development Process.
Leaders in Asset Management Big Plans for your Property System? How to plan for a Property System Project Prepared by: Yudiann Carlo, CPPS
CHAPTER TWO THE MAKING OF MULTIMEDIA: AND MULTIMEDIA DEVELOPMENT TEAM
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
Chapter 14: Using the Scalable Decision Process on Large Projects The process outlined is meant to be scaleable. Individual steps can be removed, changed,
Introduction to Making Multimedia
Physics Project Management Chin-Sung Lin Eleanor Roosevelt High School.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
System Context and Domain Analysis Abbas Rasoolzadegan.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Evaluation Aims Process-focused: To monitor and improve the quality of the socio-cognitive engineering process Product-focused: To assess and improve the.
Chapter 3-Multimedia Skills
Lesson 3-Multimedia Skills. Overview Members of a multimedia team. Roles and responsibilities in a multimedia team.
© 2014 International Technology and Engineering Educators Association STEM  Center for Teaching and Learning™ Game Art and Design Unit 2 Lesson 1 Skills.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Development Project Dr Kris Welsh Dr Raheel Nawaz.
Information Systems Development
Individual Thinking Time
Fundamentals of Information Systems, Sixth Edition
Request for Proposal (RFP)
Informatics 121 Software Design I
Chapter 10 Development of Multimedia Project
Engineering Processes
Rational Unified Process
Informatics 121 Software Design I
Project Management Process Groups
Fundamentals of Human Computer Interaction (HCI)
Informatics 121 Software Design I
Engineering Processes
Informatics 121 Software Design I
Principles of HCI Design
From Use Cases to Implementation
Presentation transcript:

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation Business

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation Psychology

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation Design

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation Engineering

Project  The diagram shows the process of design, implementation and deployment for a single project Roles  The project is carried out by a design team, with well-defined roles, that may change during the project Phase :  Each box represents one phase of the project Methods  Each box can be carried out by one or more methods; need to choose the appropriate method for the project Tools  Each method has associated tools (formalisms, software, hardware) to carry out the method Outcomes  Each phase has outcomes, which must be documented; these are used to inform and validate the design Measures  Each design decision must be validated, by reference to outcomes from one of the phases Elements of Socio-cognitive Engineering

Phases General requirements  Scope, business case, user needs, constraints of project Theory of use  Theories of human cognition and interaction that inform the project Contextual studies  Observation and analysis of how people carry out activities and tasks, with their normal surroundings and tools Task model  Brings together theory of use and contextual studies into an integrated account of how people perform activities, think, work and interact with their current tools and resources

Phases (continued) Design concept  Concept of how people might perform tasks and interact with new technology, interface designs, system images Design space  Systematic exploration of the space of possible designs, selection of design choices System specification  Formal specification of the functions and constraints of the proposed system, to guide implementation

Phases (continued) Implementation  Coding, system integration Deployment  Documentation, packaging, marketing Evaluation  Not a single phase, but an activity that is carried out during each phase, to ensure that the system matches the requirements, and that the requirements are appropriate

Important Issues The process involves a dialogue between the phases  Refer back to previous outcomes  Consider of how the current outcomes can inform future phases Earlier decisions and outcomes may need to be revised to take account of later findings When the system is deployed it will lead to new ways of working and interacting,  Need for new requirements and task model

Verification and Validation Verification  Does the system design match the requirements and specification? Validation  Are the requirements and specification appropriate?

How to carry out a project 1.Form a team 2.Produce general requirements for the project 3.Decide which methods and tools will be used for each phase of the project 4.Decide how the process and outcomes will be documented 5.Decide how the project will be evaluated 6.Carry out each phase of the project, making sure that the requirements match the design 7.Carry out a continuous process of documentation and evaluation

Project team Need a mixture of skills Allocate roles  Roles are based on skills; one person may perform more than one role Some roles for a project team  Team leader  Market researcher: identify business opportunity  User researcher: research theory of use, gather information on stakeholders, plan and carry out contextual studies  Concept designer: produce design concept, example interfaces, storyboards  System designer: produce system specification  Programmer: implement system  Evaluator: evaluate all phases of the project

Activity (10 mins) Form into two project teams for your assignment Within your group, each person lists their skills Discuss possible roles in the project