Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.

Slides:



Advertisements
Similar presentations
Information Systems Systems Development Chapter 6.
Advertisements

Introduction to Software Testing Chapter 1 Model-Driven Test Design Paul Ammann & Jeff Offutt
System Development Life Cycle (SDLC)
Systems Development Environment
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Ch 3: Unified Process CSCI 4320: Software Engineering.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
UI Standards & Tools Khushroo Shaikh.
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Systems Development. Systems Development Life Cycle (SDLC) A “baseline” process for the development of application systems Contains a comprehensive set.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Copyright by Scott GrissomCh 1 Software Development Slide 1 Software Development The process of developing large software projects Different Approaches.
Maintenance = Software Evolution Any changes after the client has accepted the product is considered maintenance. n Any Changes? n What might these be?
Ch 3 Usability page 1CS 368 Usability Models the authors compare three usability models and introduce their own “the extent to which a product can be used.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
S/W Project Management
Instructional Design Eyad Hakami. Instructional Design Instructional design is a systematic process by which educational materials are created, developed,
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Higher Computing Software Development. Software Development Process There are 7 main stages involved in developing a new software program: Analysis Design.
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
User-Centered Development Methodology A user interface comprises “ those aspects of the system that the user comes in contact with.” ● Moran [1981]
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
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.
An Introduction to Software Engineering. Communication Systems.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
1 Week 7 - System analyst IT2005 System Analysis & Design.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS223: Software Engineering Lecture 16: The Agile Methodology.
Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Software Development Cycle and Roles in a Project Team
Introduction to Software Testing Model-Driven Test Design and Coverage testing Paul Ammann & Jeff Offutt Update.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
Software Design and Development Development Methodoligies Computing Science.
CEN3722 Human Computer Interaction Overview of HCI Dr. Ron Eaglin.
Information Systems Development
Project planning The systems life cycle.
The Software Development Cycle
The Systems Engineering Context
SNS College of Engineering Coimbatore
CS701 SOFTWARE ENGINEERING
Object oriented system development life cycle
Information Systems Development
CS 425/625 Software Engineering Software Evolution
Chapter 1 (pages 4-9); Overview of SDLC
“Would I have to do this all by myself …….?”
Usability Techniques Lecture 13.
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
The Software Development Process
Software Reviews.
The Software Development Cycle
Presentation transcript:

Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity is increasing multi-user real-time complexity no stopping criteria

Ch 4 The Process page 2CS 368 Usability Design a goal directed problem solving activity informed by intended use, target domain, materials, cost and feasibility a structured approach to interface development typical design life cycle requirements analysis (20%) design (15%) implementation (15%) testing (50%) maintenance user concerns direct the design rather than technical concerns iteration is a must

Ch 4 The Process page 3CS 368 Requirements Analysis obtain a thorough understanding of the problem to be solved must be complete must be correct identify user needs by performing a task analysis results in a specification document must be complete and precise for designers to develop an appropriate solution

Ch 4 The Process page 4CS 368 Software Design identify data structures select the platform design the look and feel design UI code results in a design document must be complete and precise for coders to simply implement the design resist coding at this stage

Ch 4 The Process page 5CS 368 Testing test functionality runtime errors usability results in a testing report must be thorough to convince a reader that the vast majority of errors have been removed and that the final product meets the original specs

Ch 4 The Process page 6CS 368 User Involvement traditionally, designers or systems analysts gather information from the users and serve as a liaison with developers participatory design strives to involve users to contribute early and often to the process some may even be a member of the design team (domain specialist) this leads to a better product with higher user satisfaction

Ch 4 The Process page 7CS 368 Development Team ideal design team skills human factors cognitive psychology (human perception) behavioral science graphic design empirical studies programming team members usability engineer user interface designer user interface developer graphic designer domain expert in one study 50% of a programmers time is spent communicating with team members 30% alone coding 20% on other activities such as travel

Ch 4 The Process page 8CS 368 Group Activity apply the traditional design process to the problem of baking desserts for a party of 500 people requirements analysis design implementation testing maintenance