Iterative design and prototyping
|
|
- Nancy Hampton
- 6 years ago
- Views:
Transcription
1 Iterative design and prototyping
2 Iterative design and prototyping Requirements of the iterative segments cannot be specified from the beginning. Only way is to built them and test them on real users. It is software engineering problem,together with technical and managerial issues.
3 PROTOTYPES Iterative design is described by the use of the prototypes. simulate or animate some features of intended system different types of prototypes throw-away incremental evolutionary
4 THROW AWAY The prototype is built and tested. The experience gained is taken to built original system. Actual prototype is discarded. INCREMENTAL Final product is built as a separate component. Final system is partitioned into independent components. Final component is released as a series of product.
5 EVOLUTIONARY Prototype is not discarded it serves as basic for the next iteration of design. Actual system evolves from the limited initial version to its final release.
6 Cont An animation of requirement can involve no real functionality. Full functionality can be provided at the expense of other performance characteristics. Prototype of an interactive system is used to test requirements by evaluating with user. Providing realism is costly.
7 CONT.. On the management side there are several problems Management issues time planning non-functional features contracts
8 TIME Building prototype takes time. Value of prototyping is appreciated only if it was Fast. At the same time it should not produce erroneous results. Planning Most project managers do not have the experience necessary for adequately planning and costing a design process which involves prototyping.
9 NON-FUNCTIONAL FEATURES Most important features of the system will be non-functional one. This problem is similar to the technical issue of prototype realism CONTRACTS The design process is often governed by contractual agreements b/w customer and designer. There must be an effective way of translating the result from prototype into document.
10 Techniques for prototyping Storyboards Probably the simplest of a prototype is the storyboard. Storyboard do not require must in term of company system power to construct. For Interactive system design storyboard provides snapshot of interface at particular points of interaction. Storyboard usually includes annotations and scripts Indicating how the interaction will occur.
11 Limited functionality simulations More functionality must be bulit into the prototype to demonstrate the work that the application will do. Some portion of the functionality must be simulated by the design team. Once the stimulation is built,it can be evaluated and changed rapidly based on users experiences.
12 Cont.. Well-known and successful prototyping tool is hypercard. The graphical images are placed on cards,and links between cards can be created for animation effects. One technique for simulation which does not require very much computer supported functionality,is the wizard of Oz techniques.
13 High-level programming support HyperTalk was an special purpose high-level Programming language It makes easy for the designer to program certain features of an interactive system. Attach functional behaviour to the specific interactions that the user will be able to do. It is Implementation dependent.
14 Cont.. User interface management system Can be considered to provide high level programming support. It is separate the application functionality from its presentation. The job of UIMS,is to allow the programmar to connect the behaviour at the interface with the underlying functionality.
15 WARNING ABOUT ITERATIVE DESIGN There are 2 problems First,it is often the case that design decisions taken at the very beginning stage of prototyping is wrong. Second,if in the process of evaluation,a potential usability problem is diagonised,it is important to understand the reason for the problem
16 DESIGN RATIONALE Design rationale is information that explains why a computer system is the way it is. Design rationale relates to an activity of both reflection and documentation that occur throughout the entire life cycle.
17 REASONS FOR DESIGN RATIONALE Explicitly,design rationale provide a communication mechanism among the member of the design team. Accumulated knowledge in the form of design rationale for a set of products can be reused for another situation. The effort required to produce a design rationale forces designer to be more delibrate.
18 CONT. Usually there is no single best alternative.often designer is faced with a set of Trade-off s between different alternatives. In project management, accountability is good. Usability is very much dependent on the context of its use.
19 PROCESS-ORIENTED DESIGN RATIONALE Process-oriented preserves order of deliberation and decision-making Two examples: Issue-based information system (IBIS) Design space analysis
20 Issue-based information system (IBIS) Basis for much of design rationale research process-oriented Main elements: issues hierarchical structure with one root issue positions potential resolutions of an issue arguments modify the relationship between positions and issues gibis is a graphical version
21 . structure of gibis Position supports Argument specializes Issue responds to responds to Position objects to Argument Sub-issue questions generalizes Sub-issue Sub-issue
22 Design space analysis structure-oriented QOC hierarchical structure: questions (and sub-questions) represent major issues of a design options provide alternative solutions to the question criteria the means to assess the options in order to make a choice DRL similar to QOC with a larger language and more formal semantics
23 The QOC notation option Criterion Question Option option Criterion option Criterion Consequent
24 Psychological design rationale To support task-artefact cycle in which user tasks are affected by the systems they use aims to make explicit consequences of design for users designers identify tasks system will support scenarios are suggested to test task users are observed on system psychological claims of system made explicit negative aspects of design can be used to improve next iteration of design
25 THANK YOU!!!!!
Human Computer Interaction Lecture 14. HCI in Software Process. HCI in the software process
Human Computer Interaction Lecture 14 HCI in Software Process HCI in the software process Software engineering and the design process for interactive systems Usability engineering Iterative design and
More informationHCI in the software process
chapter 6 HCI in the software process HCI in the software process Software engineering and the process for interactive systems Usability engineering Iterative and prototyping Design rationale the software
More informationHCI in the software. chapter 6. HCI in the software process. The waterfall model. the software lifecycle
HCI in the software process chapter 6 HCI in the software process Software engineering and the process for interactive systems Usability engineering Iterative and prototyping Design rationale the software
More informationHuman Computer Interaction Lecture 06 [ HCI in Software Process ] HCI in the software process
Human Computer Interaction Lecture 06 [ HCI in Software Process ] Imran Ihsan Assistant Professor www.imranihsan.com aucs.imranihsan.com HCI06 - HCI in Software Process 1 HCI in the software process Software
More informationSoftware Engineering
Software Engineering 0 Software design process or life cycle called Software Engineering 0 that addresses the management and technical issues of the development of software systems. 0 The software life
More information6.5 DESIGN RATIONALE. 248 Chapter 6 n HCI in the software process
248 Chapter 6 n HCI in the software process First, it is often the case that design decisions made at the very beginning of the prototyping process are wrong and, in practice, design inertia can be so
More informationInterface Implementation
Interface Implementation HCI Lecture 11 David Aspinall Informatics, University of Edinburgh 26th October 2007 Outline Overview Software Engineering Usability Engineering Explaining Design Implementation
More informationDesign, prototyping and construction
Overview Design, prototyping and construction Prototyping and construction Conceptual design Physical design Generating prototypes Tool support What is a prototype? Why prototype? A prototype is a small-scale
More informationHuman-Computer Interaction. CA357 Lecture 7 More on Prototyping
Human-Computer Interaction CA357 Lecture 7 More on Prototyping Overview By the end of the session, you should be aware of: Design Importance of prototyping Low fidelity vs High fidelity prototyping Why
More informationSoftware Prototyping Animating and demonstrating system requirements. Uses of System Prototypes. Prototyping Benefits
Software Prototyping Animating and demonstrating requirements Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 8 Slide 1 Uses of System Prototypes
More informationDesign Rationale Modeling Representations
Agenda Design Rationale Modeling Representations EE382V Software Architecture and Design Intent Pankaj Adhikari, Bill Reinhart 7 MAR 2006 Why Rationale? Design Rationale s Roots Modeling Rationale IBIS
More informationWhat is a prototype?
analysis of stakeholders, field studies ANALYZE Problem scenarios claims about current practice metaphors, information technology, HCI theory, guidelines DESIGN Activity scenarios Information scenarios
More informationPrototyping for usability engineering
analysis of stakeholders, field studies ANALYZE Problem scenarios claims about current practice Prototyping for usability engineering metaphors, information technology, HCI theory, guidelines DESIGN Activity
More informationDesign, prototyping and construction
Chapter 11 Design, prototyping and construction 1 Overview Prototyping and construction Conceptual design Physical design Generating prototypes Support for design 2 Prototyping and construction What is
More informationRequirements Validation and Negotiation (cont d)
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Joerg Doerr Requirements Validation and Negotiation (cont d) REQUIREMENTS VALIDATION AND NEGOTIATION Requirements Validation Techniques 2 Techniques Overview
More informationIPM 15/16 T2.1 Prototyping
IPM 15/16 T2.1 Prototyping Miguel Tavares Coimbra Acknowledgements: Most of this course is based on the excellent course offered by Prof. Kellogg Booth at the British Columbia University, Vancouver, Canada.
More informationBusiness Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3)
Business Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3) COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module
More informationPrototyping. SWE 432, Fall Web Application Development
Prototyping SWE 432, Fall 2018 Web Application Development Conceptual design Goal: match users mental model Tool: Metaphor - analogies from existing system Offers expectations about what system does &
More informationThe process of interaction design and Prototyping
Chapter 6 edited The process of interaction design and Prototyping 1 Overview What is involved in Interaction Design? Importance of involving users Degrees of user involvement What is a user-centered approach?
More informationSri Vidya College of Engineering & Technology Question bank (unit 2) UNIT 2 TWO MARKS
UNIT 2 TWO MARKS 1. What is design? Achieving goals within constraints. The design helps to focus on certain things like goals, constraints and tradeoffs Goals purpose (who is it for, why do they want
More informationPrototyping. Oct 3, 2016
Prototyping Oct 3, 2016 Announcements A1 marks available A2 due Wednesday Questions? What is a prototype? In interaction design a prototype can be (among other things): a series of screen sketches a storyboard,
More informationConcepts of user-centered design
Lecture 1 Concepts of user-centered design What is UCD? Primary goad: making products usable Is there any difference? Usable Usefulness Usability Why important? Increased productivity Reduced errors Reduced
More informationSpecifying and Prototyping
Contents Specifying and Prototyping M. EVREN KIYMAÇ 2008639030 What is Specifying? Gathering Specifications Specifying Approach & Waterfall Model What is Prototyping? Uses of Prototypes Prototyping Process
More informationSOFTWARE REQUIREMENTS ENGINEERING LECTURE # 7 TEAM SKILL 2: UNDERSTANDING USER AND STAKEHOLDER NEEDS REQUIREMENT ELICITATION TECHNIQUES-IV
1 SOFTWARE REQUIREMENTS ENGINEERING LECTURE # 7 TEAM SKILL 2: UNDERSTANDING USER AND STAKEHOLDER NEEDS REQUIREMENT ELICITATION TECHNIQUES-IV 12 th June, 2013 Instructor Information 2 Course Instructor:
More informationFinal Project Report
16.04.02 Final Project Report Document information Project Title HP Tool Repository of SESAR standard HP methods and tools Project Number 16.04.02 Project Manager DFS Deliverable Name 16.04.02 Final Project
More informationUser Centered Design And Prototyping
User Centered Design And Prototyping Why User Centered Design is important Approaches to User Centered Design Rapid prototype techniques The Design Of Well Crafted Tools The All Too Common Approach In
More informationA Design Rationale Representation for Model-Based Designs in Software Engineering
A Design Rationale Representation for Model-Based Designs in Software Engineering Adriana Pereira de Medeiros, Daniel Schwabe, and Bruno Feijó Dept. of Informatics, PUC-Rio, Rua Marquês de São Vicente
More informationCS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS 1. Explain iterative waterfall and spiral model for software life cycle and various activities
More informationSOFTWARE ENGINEERING DECEMBER. Q2a. What are the key challenges being faced by software engineering?
Q2a. What are the key challenges being faced by software engineering? Ans 2a. The key challenges facing software engineering are: 1. Coping with legacy systems, coping with increasing diversity and coping
More informationFor presentation at the Fourth Software Engineering Institute (SEI) Software Architecture Technology User Network (SATURN) Workshop.
For presentation at the Fourth Software Engineering Institute (SEI) Software Architecture Technology User Network (SATURN) Workshop. The authors can be reached at cb@mitre.org or ioannis @Mitre.org. In
More information3 Prototyping and Iterative Evaluations
3 Prototyping and Iterative Evaluations Viktoria Pammer-Schindler March 15, 2016 Prototyping and Iterative Evaluations 1 Days and Topics March 1 March 8 March 15 April 12 April 19/21 April 26 (10-13) April
More informationModeling Issues Modeling Enterprises. Modeling
Modeling Issues Modeling Enterprises SE502: Software Requirements Engineering Modeling Modeling can guide elicitation: It can help you figure out what questions to ask It can help to surface hidden requirements
More informationRequirements. Requirements. Types of Requirement. What Is a Requirement?
Beatrice Åkerblom beatrice@dsv.su.se Everything else in software development depends on the requirements. If you cannot get stable requirements you cannot get a predictable plan... What Is a Requirement?!
More informationModule B1 An Introduction to TOGAF 9.1 for those familiar with TOGAF 8
Informs the capability Ensures Realization of Business Vision Business needs feed into method Refines Understanding Informs the Business of the current state Sets targets, KPIs, budgets for architecture
More informationCS/ISE 5714 Spring 2013
CS/ISE 5714 Spring 2013 Chapter 11. Prototyping Chapter 10. UX Goals, Metrics, Targets Introduction A way to evaluate design before it s too late and too expensive Copyright MKP. All rights reserved. 2
More informationSoftware Engineering Lifecycles. Controlling Complexity
Software Engineering Lifecycles Class url:http://laser.cs.umass.edu/courses/cs320.spring11/ Controlling Complexity Separation of Concerns Planning Ahead Do a little work now to make later work easier The
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2015/2016 Eddy Groen Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More information3 Evaluating Interactive Systems
3 Evaluating Interactive Systems Viktoria Pammer-Schindler March 23, 2015 Evaluate 1 Android Sensing Tutorial Day on April 23 Save the Date!!! Evaluate 2 Days and Topics March 11 March 16 Intro Designing
More informationIntro to Modelling and UML
CSCD01 Engineering Large Software Systems Intro to Modelling and UML Joe Bettridge Winter 2018 With thanks to Anya Tafliovich and Steve Easterbrook Getting Started So, you ve just started working on a
More informationPrototyping. Unit 5. Zeno Menestrina, MSc Prof. Antonella De Angeli, PhD
Prototyping Unit 5 Zeno Menestrina, MSc zeno.menestrina@unitn.it Prof. Antonella De Angeli, PhD antonella.deangeli@unitn.it Assessment Pervasive game to support social life in/from the campus 2 Assessment
More informationCS -213 Human Computer Interaction Spring Prototyping. Imran Ihsan. Assistant Professor (CS) Air University, Islamabad
CS -213 Human Computer Interaction Spring 2015 07 Prototyping Imran Ihsan Assistant Professor (CS) Air University, Islamabad www.imranihsan.com www.opuseven.com opuseven iimranihsan imranihsan iimranihsan
More informationLECTURE 11 USABILITY -PROTOTYPING
October 13th 2014 LECTURE 11 USABILITY -PROTOTYPING 1 Recapitulation Lecture #10 Tool box for HCI Task Analysis Cognitive techniques GOMS/CCT ERMIA CWA Dialogue Analysis-Design Color/Text Analysis-Design
More informationRecapitulation Lecture #10 LECTURE 11 USABILITY - PROTOTYPING. Waterfall with iteration. Example: Cognitive Task Analysis
Recapitulation Lecture #10 October 13th 2014 LECTURE 11 USABILITY - PROTOTYPING Tool box for HCI Task Analysis Cognitive techniques GOMS/CCT ERMIA CWA Dialogue Analysis-Design Color/Text Analysis-Design
More informationSelf-Managed Systems: an Architectural Challenge
Self-Managed Systems: an Architectural Challenge Kramer, Jeff and Magee, Jeff FOSE 07: 2007 Future of Software Engineering Summarized by Jason Porter Introduction A self-managed system is a system which
More informationWhat is a prototype?
Prototyping Unit 4 Learning outcomes Understand the uses of different types of prototypes for different kinds/stages of design and be able to choose appropriately Know the basic techniques for low-fidelity
More information13/9/10 PROTOTYPING. Cris3an Bogdan
PROTOTYPING Cris3an Bogdan cris3@kth.se 1 What is a prototype? Concrete representation of an interactive system/service, or relevant part of it Tangible artifact Relevance depends on what is being explored
More informationGoals PROTOTYPING) Cris%an(Bogdan( (
PROTOTYPING) Cris%an(Bogdan( cris%@kth.se( ( Goals illustrate(how(we(can((help(designers)( generate(and(share(new(ideas,(get(feedback( from(users(or(customers( choose(among(design(alterna%ves,(and( ar%culate(reasons(for(design(choices.(
More informationChapter 8: Class and Method Design
Chapter 8: Class and Method Design Objectives Become familiar with coupling, cohesion, and connascence. Be able to specify, restructure, and optimize object designs. Be able to identify the reuse of predefined
More informationWhat is a prototype?
Prototyping Unit 4 Learning outcomes Understand the uses of different types of prototypes for different kinds/stages of design and be able to choose appropriately Know the basic techniques for low-fidelity
More informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationDesign Sketching. Misused Metaphors. Interface Hall of Shame! Outline. Design Sketching
1 Design Sketching * slides marked Buxton are courtesy of, from his talk Why I Love the ipod, iphone, Wii and Google, remix uk, 18-19 Sept. 2008, Brighton Prof. James A. Landay University of Washington
More informationVANCOUVER Chapter Study Group. BABOK Chapter 9 Techniques
VANCOUVER Chapter Study Group BABOK Chapter 9 Techniques May 27, 2015 David Ghotbi, CBAP Agenda Chapter 8 Review Pop Quiz Break Chapter 9 Review Pop Quiz Q & A 2 Chapter 9 Techniques Techniques: Alter
More informationCMSC 435: Software Engineering Section 0201
CMSC 435: Software Engineering Section 0201 Atif M. Memon (atif@cs.umd.edu) 4115 A.V.Williams building Phone: 301-405-3071 Office hours Tu.Th. (11:00am-1:00pm) Don t wait, don t hesitate, do communicate!!
More informationOverview of the course. User-Centred Design. Group. Practical issue. Writting the report. Project work. Fang Chen
Overview of the course User-Centred Design Fang Chen 6 lectures, 3 hr each. L 1: April 6, 9-12, user-centered design concept L2: April 14, 9-12, usability concept L3. user-centered requirement study L4.
More informationAgile Accessibility. Presenters: Ensuring accessibility throughout the Agile development process
Agile Accessibility Ensuring accessibility throughout the Agile development process Presenters: Andrew Nielson, CSM, PMP, MPA Ann Marie Davis, CSM, PMP, M. Ed. Cammie Truesdell, M. Ed. Overview What is
More informationProcess of Interaction Design and Design Languages
Process of Interaction Design and Design Languages Process of Interaction Design This week, we will explore how we can design and build interactive products What is different in interaction design compared
More informationIntroduction to Software Specifications and Data Flow Diagrams. Neelam Gupta The University of Arizona
Introduction to Software Specifications and Data Flow Diagrams Neelam Gupta The University of Arizona Specification A broad term that means definition Used at different stages of software development for
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT PRINCIPLES OF USER INTERFACE DESIGN
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT PRINCIPLES OF USER INTERFACE DESIGN Monday 19 th March 2018 - Afternoon Answer any FOUR questions out of
More informationLECTURE 11 USABILITY - PROTOTYPING
1 October 11 th 2018 LECTURE 11 USABILITY - PROTOTYPING 2 HCI & InfoVis 2018, Lecture 11 1 Recapitulation Lecture #10 Toolbox for HCI & IV Dialogue Analysis Dialogue Notations STN Petri Nets Flow Charts
More informationh(p://ihm.tumblr.com/post/ /word- cloud- for- hci- human- computer- interacbon CS5340 Human-Computer Interaction ! January 31, 2013!
h(p://ihm.tumblr.com/post/105778492/word- cloud- for- hci- human- computer- interacbon CS5340 Human-Computer Interaction January 31, 2013 Today s Class Administrivia User-centered Design Establishing Requirements
More informationA Collaborative User-centered Approach to Fine-tune Geospatial
A Collaborative User-centered Approach to Fine-tune Geospatial Database Design Grira Joel Bédard Yvan Sboui Tarek 16 octobre 2012 6th International Workshop on Semantic and Conceptual Issues in GIS - SeCoGIS
More informationDREAM & TEAM: A Tool and a Notation Supporting Exploration of Options and Traceability of Choices for Safety Critical Interactive Systems
DREAM & TEAM: A Tool and a Notation Supporting Exploration of Options and Traceability of Choices for Safety Critical Interactive Systems Xavier Lacaze and Philippe Palanque LIIHS IRIT, Université Paul
More informationWhat is a prototype?
Prototyping Unit 4 Learning outcomes Understand the uses of different types of prototypes for different kinds/stages of design and be able to choose appropriately Know the basic techniques for low-fidelity
More informationSeng310 Lecture 8. Prototyping
Seng310 Lecture 8. Prototyping Course announcements Deadlines Individual assignment (extended) deadline: today (June 7) 8:00 am by email User testing summary for paper prototype testing- Thursday June
More informationSupporting Design Communication with Explicit Representation of Evaluation Feedback
Scandinavian Journal of Information Systems Volume 6 Issue 2 Article 5 1994 Supporting Design Communication with Explicit Representation of Evaluation Feedback Torbjörn Näslund Linköping University, Sweden,
More informationSoftware Architecture
Software Architecture Does software architecture global design?, architect designer? Overview What is it, why bother? Architecture Design Viewpoints and view models Architectural styles Architecture asssessment
More informationAdministrivia. Added 20 more so far. Software Process. Only one TA so far. CS169 Lecture 2. Start thinking about project proposal
Administrivia Software Process CS169 Lecture 2 Added 20 more so far Will limit enrollment to ~65 students Only one TA so far Start thinking about project proposal Bonus points for proposals that will be
More informationFundamentals of Programming Session 13
Fundamentals of Programming Session 13 Instructor: Reza Entezari-Maleki Email: entezari@ce.sharif.edu 1 Fall 2014 These slides have been created using Deitel s slides Sharif University of Technology Outlines
More informationExamination Questions Time allowed: 1 hour 15 minutes
Swedish Software Testing Board (SSTB) International Software Testing Qualifications Board (ISTQB) Foundation Certificate in Software Testing Practice Exam Examination Questions 2011-10-10 Time allowed:
More information142
Scope Rules Thus, storage duration does not affect the scope of an identifier. The only identifiers with function-prototype scope are those used in the parameter list of a function prototype. As mentioned
More informationImplementation Architecture
Implementation Architecture Software Architecture VO/KU (707023/707024) Roman Kern KTI, TU Graz 2014-11-19 Roman Kern (KTI, TU Graz) Implementation Architecture 2014-11-19 1 / 53 Outline 1 Definition 2
More informationKlocwork Architecture Excavation Methodology. Nikolai Mansurov Chief Scientist & Architect
Klocwork Architecture Excavation Methodology Nikolai Mansurov Chief Scientist & Architect Overview! Introduction Production of software is evolutionary and involves multiple releases Evolution of existing
More informationSoftware Development Process Models
Software Development Process Models From classical notions to more agile approaches th@cs.toronto.edu, BA8134 Code & Fix or Cowboy Coding 1) Write program 2) Test and fix program Problems: program users
More informationAdobe LiveCycle ES and the data-capture experience
Technical Guide Adobe LiveCycle ES and the data-capture experience Choosing the right solution depends on the needs of your users Table of contents 2 Rich application experience 3 Guided experience 5 Dynamic
More informationInteractive (High-fi) Prototype (Group)
Interactive (High-fi) Prototype (Group) Midway Milestone due at the start of your studio (Thursday/Friday Dec 1-2) Final Prototype due at the start of your studio (Thursday/Friday Dec 8-9) Writeup due
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1 Verification vs validation Verification: "Are we building the product right?. The software should
More informationSafety Case Composition Using Contracts - Refinements based on Feedback from an Industrial Case Study
Safety Case Composition Using Contracts - Refinements based on Feedback from an Industrial Case Study Jane Fenn and Richard Hawkins BAE SYSTEMS, Brough, UK Phil Williams General Dynamics (United Kingdom)
More informationProgramming in C. main. Level 2. Level 2 Level 2. Level 3 Level 3
Programming in C main Level 2 Level 2 Level 2 Level 3 Level 3 1 Programmer-Defined Functions Modularize with building blocks of programs Divide and Conquer Construct a program from smaller pieces or components
More informationIn this Lecture you will Learn: Testing in Software Development Process. What is Software Testing. Static Testing vs.
In this Lecture you will Learn: Testing in Software Development Process Examine the verification and validation activities in software development process stage by stage Introduce some basic concepts of
More informationProjects. Quiz #2. Projects. Projects. Reading Assignment #3. Projects. What is the purpose of Marissa s Gravity Project?
Quiz #2 What is the purpose of Marissa s Gravity Project? Write one tradeoff in usability engineering. Projects Project Phase 1 reports due on Oct. 25 Phase 1: team formation & topic choice, understanding
More informationImplementation Architecture
Implementation Architecture Software Architecture VO/KU (707023/707024) Roman Kern ISDS, TU Graz 2017-11-15 Roman Kern (ISDS, TU Graz) Implementation Architecture 2017-11-15 1 / 54 Outline 1 Definition
More informationAdministrative Stuff. Examples of project processbooks and link to a project prototype on the website Next Week: Evaluation methods, cultural probes
Administrative Stuff Examples of project processbooks and link to a project prototype on the website Next Week: Evaluation methods, cultural probes Prototyping Irene Rae Computer Sciences CS-570 Introduction
More informationSample Exam Syllabus
ISTQB Foundation Level 2011 Syllabus Version 2.9 Release Date: December 16th, 2017. Version.2.9 Page 1 of 46 Dec 16th, 2017 Copyright 2017 (hereinafter called ISTQB ). All rights reserved. The authors
More informationCPSC 444 Project Milestone III: Prototyping & Experiment Design Feb 6, 2018
CPSC 444 Project Milestone III: Prototyping & Experiment Design Feb 6, 2018 OVERVIEW... 2 SUMMARY OF MILESTONE III DELIVERABLES... 2 1. Blog Update #3 - Low-fidelity Prototyping & Cognitive Walkthrough,
More informationA Business Aware Transaction Framework for Service Oriented Environments
A Business Aware Transaction Framework for Service Oriented Environments Benedikt Kratz M.Sc. (B.Kratz@uvt.nl) Tilburg University Infolab Ph.D. Supervisor: Prof. Dr. M.P. Papazoglou ICSOC 2005 Ph.D. Symposium
More informationdt+ux Design Thinking for User Experience Design, Prototyping & Evaluation Autumn 2016 Prof. James A. Landay Stanford University
DESIGN THINKING FOR USER EXPERIENCE DESIGN + PROTOTYPING + EVALUATION Hall of Fame or Shame? Early Stage Prototyping Computer Science Department October 20, 2016 Paper ipad App By 53 2 Hall of Fame or
More informationDesign Patterns. An introduction
Design Patterns An introduction Introduction Designing object-oriented software is hard, and designing reusable object-oriented software is even harder. Your design should be specific to the problem at
More informationInformation Security Policy
April 2016 Table of Contents PURPOSE AND SCOPE 5 I. CONFIDENTIAL INFORMATION 5 II. SCOPE 6 ORGANIZATION OF INFORMATION SECURITY 6 I. RESPONSIBILITY FOR INFORMATION SECURITY 6 II. COMMUNICATIONS REGARDING
More informationUsability Evaluation as a Component of the OPEN Development Framework
Usability Evaluation as a Component of the OPEN Development Framework John Eklund Access Testing Centre and The University of Sydney 112 Alexander Street, Crows Nest NSW 2065 Australia johne@testingcentre.com
More informationAgenda. Bibliography
Humor 2 1 Agenda 3 Trusted Digital Repositories (TDR) definition Open Archival Information System (OAIS) its relevance to TDRs Requirements for a TDR Trustworthy Repositories Audit & Certification: Criteria
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms
Standard Glossary of Terms used in Software Testing Version 3.2 Foundation Extension - Usability Terms International Software Testing Qualifications Board Copyright Notice This document may be copied in
More informationCS Human Computer Interaction
Part A 1. Define HCI CS6008 - Human Computer Interaction UNIT-I Question Bank FOUNDATIONS OF HCI 2. What are the basic requirements of an Successful Interactive System? 3. What is STM & LTM? 4. List out
More informationObject-Oriented Software Engineering Practical Software Development using UML and Java
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 5: Modelling with Classes Lecture 5 5.1 What is UML? The Unified Modelling Language is a standard graphical
More informationCOSC 341 Human Computer Interaction. Dr. Bowen Hui University of British Columbia Okanagan
COSC 341 Human Computer Interaction Dr. Bowen Hui University of British Columbia Okanagan 1 Recall: Learning About Your User Common ways to elicit user feedback: Interviews Focus groups Expert reviews
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation 1 Objectives To introduce software verification and validation and to discuss the distinction between them To describe the program inspection process and its role in V & V To
More informationDESIGN AND ANALYSIS OF ALGORITHMS. Unit 1 Chapter 4 ITERATIVE ALGORITHM DESIGN ISSUES
DESIGN AND ANALYSIS OF ALGORITHMS Unit 1 Chapter 4 ITERATIVE ALGORITHM DESIGN ISSUES http://milanvachhani.blogspot.in USE OF LOOPS As we break down algorithm into sub-algorithms, sooner or later we shall
More informationTowards Semantic Interoperability between C2 Systems Following the Principles of Distributed Simulation
Towards Semantic Interoperability between C2 Systems Following the Principles of Distributed Simulation Authors: Vahid Mojtahed (FOI), vahid.mojtahed@foi.se Martin Eklöf (FOI), martin.eklof@foi.se Jelena
More informationChapter 2: Functions and Control Structures
Chapter 2: Functions and Control Structures TRUE/FALSE 1. A function definition contains the lines of code that make up a function. T PTS: 1 REF: 75 2. Functions are placed within parentheses that follow
More informationCS:2820 (22C:22) Object-Oriented Software Development
The University of Iowa CS:2820 (22C:22) Object-Oriented Software Development! Spring 2015 Software Complexity by Cesare Tinelli Complexity Software systems are complex artifacts Failure to master this
More informationThe software lifecycle and its documents
The software lifecycle and its documents Supplementary material for Software Architecture course B. Meyer, May 2006 Lifecycle models Origin: Royce, 1970, Waterfall model Scope: describe the set of processes
More information