Lifecycle models For more info on these models – see text

Slides:



Advertisements
Similar presentations
kareRCIserIsviFIsaRsþGnuvtþKMerag
Advertisements

SDLC – Beyond the Waterfall
Software Development Life-Cycle Models
Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
CS305: HCI in SW Development
HCI in the software process Chapter 6
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas The primarily goal of a system is to create value for the organization. Many failed systems were abandoned.
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
The Process of Interaction Design. Overview What is Interaction Design? —Four basic activities —Three key characteristics Some practical issues —Who are.
The Process of Interaction Design
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
What is Interaction Design?
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo.
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
1 The Design Process Lecture 9 Date: 2 nd March. 2 Overview Life-Cycle Models in HCI 4 basic activities in HCI Requirements Design Develop/Build Evaluation.
Introduction to Software Engineering Dr. Basem Alkazemi
ICS 463: Intro to Human Computer Interaction Design 2. User-Centered Design Dan Suthers.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
03/12/2001 © Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Software Engineering Incorporating Interface Design Into Software Engineering.
Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design process –Explain the importance of iterative.
Imran Hussain University of Management and Technology (UMT)
CS3205: HCI in SW Development
The process of interaction design. Overview What is involved in Interaction Design? –Importance of involving users –Degrees of user involvement –What.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
Software Engineering Environment  A quality focus: constant incremental improvement  Process: framework to organize development activities  Methods:
CS3205: HCI in SW Development Software process and user-centered design Readings: (1) ID-Book, Chapter 9 (2) Ch. 1 from Task-Centered User Interface Design.
27. august 2007 Lektion 1c 1 Interaktionsdesign- processen Sharp Kapitel 9 Anker Helms Jørgensen Interaktionsdesign Efteråret 2007 Lektion 1c.
Chapter 9 The process of interaction design. Fundamental activities Understanding the requirements Producing a design solution that satisfies those requirements.
 What is involved in Interaction Design? › What is a user-centered approach? › Four basic activities  Some practical issues › Who are the users? › What.
1 The Design Process Lecture 6 DeSiaMorewww.desiamore.com/ifm.
Week 8 - The process of interaction design
Computer Science Department California Polytechnic State University San Luis Obispo, CA, U.S.A. Franz J. Kurfess CPE/CSC 484: User-Centered Design and.
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 4 User Centred Design Gary Marsden ( ) July 2002.
The Spiral Model Sultana & Mahmood. Systems development life-cycle The process of creating or altering computer systems The models that define the processes.
Intro. to Software Engineering 1CSCI 3333 Data Structures.
GCE ICT (Double Award) Unit 5: Web Development. Unit 5 Strand (a)Your project plan Strand (b) Investigation of client’s requirements Strand (c) Developing.
© Bennett, McRobb and Farmer 2005
Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
MIS40850 Comparative Software Engineering Process Frameworks - Part 4 -
LECTURE 3 Outline What is interaction design about?
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
Plan-Driven Processes Emerson Murphy-Hill. The Planning Spectrum 2 Source: Barry Boehm “Get Ready For Agile Methods, With Care,” IEEE Computer, Jan 2002.
CS305: HCI in SW Development Software process and user-centered design Readings: ID-Book, Chapter 9.
Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.
The Process of Interaction Design
Unit 6 Application Design KLB Assignment.
User-Centered Design and Development
Digital media & interaction design
The Design Process Lecture 9 Date: 2nd March.
User-Centered Design and Development
Software Engineering Lecture 09 & 10.
Computer Science Life Cycle Models.
Lecture 2 Revision of Models of a Software Process
Basic SDLC Models SDLC  System Development Life Cycle.
SOFTWARE ENGINEERING LECTURE 2
Project Lifecycle and IT Product Life Cycle
Human Computer Interaction Lecture 14 HCI in Software Process
PRESENTED BY P.SANDEEP MSc,MTech
Presentation transcript:

Lifecycle models For more info on these models – see text Specific References are in notes view Present the model you think is most appropriate for IXD and Web 2.0 processes

Lifecycle models Show how activities are related to each other Lifecycle models are: management tools simplified versions of reality Many lifecycle models exist, for example: From software engineering: waterfall, spiral, JAD/RAD, Microsoft from HCI: Star, usability engineering

A simple interaction design model Identify needs/ establish requirements (Re)Design Evaluate The Preece, Rogers and Sharpe model See text: first edition p. 186; second edition p. 448 Build an interactive version Final product Exemplifies a user-centered design approach

Traditional ‘waterfall’ lifecycle From software engineering Traditional ‘waterfall’ lifecycle Requirements analysis Design Code A traditional approach See text: first edition p. 187; second edition p. 449 Test Maintenance

Spiral model (Barry Boehm) From software engineering Spiral model (Barry Boehm) Important features: Risk analysis Prototyping Iterative framework so ideas can be checked and evaluated Explicitly encourages considering alternatives Good for large and complex projects but not simple ones See text: first edition p. 189; second edition p. 449

Spiral model (Barry Boehm) From software engineering Spiral model (Barry Boehm) Important features: Risk analysis Prototyping Iterative framework allowing ideas to be checked and evaluated Explicitly encourages alternatives to be considered Good for large and complex projects but not simple ones From cctr.umkc.edu/~kennethjuwng/spiral.htm

A Lifecycle for RAD (Rapid Applications Development) From software engineering A Lifecycle for RAD (Rapid Applications Development) Project set-up JAD workshops Iterative design and build See text: first edition p. 188; second edition p. 450 Engineer and test final prototype Implementation review

DSDM lifecycle model From software engineering Dynamic Systems Development Model is typical of Rapid Application Development (RAD )processes developed in the 90’s to become overcome some of the limitations of the more lock step manufacturing models. RAD models attempt to take user centred view and to minimise risk caused by changing requirements during a project. See TEXT 2nd edition p. 450 - 454

The Star lifecycle model From Human Computer Interaction The Star lifecycle model Implementation task/functional analysis Requirements specification Prototyping Evaluation The Star Model (Hartson and Hix, 1989) Important features: Evaluation at the center of activities No particular ordering of activities. Development may start in any one Derived from empirical studies of interface designers UCD is a very general philosophy that instantiates itself in the context of a design project. Within HCI there have been many attempts to come up with actual life cycles where users are central. Examples include Rubinstein and Hersch successive iteration of 5 stages, info collecion, design, implementation, evaluation and deployment. The one here is taken from Hartson and Hix model came about by analysing how design takes place in practice evaluation is central: results of each activity are evaluated before going onto next one both bottom-up and top -down required in waves software designers are familiar with this in their work and call it ‘yo-yoing’ it is important to do both structure and detail at the same time in practice this is what is done - but the end result suggests otherwise corporate requirements dictate a top=down approach which is what gets recorded Conceptual/ formal design

Usability engineering lifecycle model From Human Computer Interaction Usability engineering lifecycle model Reported by Deborah Mayhew Important features: Holistic view of usability engineering Provides links to software engineering approaches, e.g. OOSE Stages of identifying requirements, designing, evaluating, prototyping Can be scaled down for small projects Uses a style guide to capture a set of usability goals

Your Model for AGILE

Your Model for AGILE & IXD