Chapter 1 Quality terminology Error: human mistake Fault: result of mistake, evidenced in some development or maintenance product Failure: departure from.

Slides:



Advertisements
Similar presentations
Copyright 2006 Pearson/Prentice Hall. All rights reserved.
Advertisements

Chapter 1 What is Software Engineering Shari L. Pfleeger
Testing and Quality Assurance
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
1 Chapter 4 - Part 1 Software Processes. 2 Software Processes is: Coherent (logically connected) sets of activities for specifying, designing, implementing,
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
Chapter 2 – Software Processes
ISNE101 Dr. Ken Cosh. Recap  We’ve been talking about Software…  Application vs System Software  Programming Languages  Vs Natural Languages  Syntax,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Chapter 1 4th Edition What is Software Engineering Shari L. Pfleeger
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
What is software engineering?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
The analysis steps. Problem Analysis Sub-problem 3 Sub-problem 2 Sub-problem nSub-problem 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
CSC230 Software Design (Engineering)
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Chapter 3 Software Processes.
ECNG3023: Introduction to Software Engineering Kevon Andrews Rm. 329 Ph: x3156 Open Hours:
SE: CHAPTER 1 Why Software Engineering ?
Software Quality SEII-Lecture 15
Chapter 2 What is software quality ?. Outline What is software? Software errors, faults and failures Classification of the causes of software errors Software.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
What is software? Software is a set of items or objects that form a configuration that includes: –Programs –Documents –Data.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
Instructor: Peter Clarke
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Lecture 3 Software Engineering Models (Cont.)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
1 Software Engineering Ian Sommerville th edition Instructor: Mrs. Eman ElAjrami University Of Palestine.
An Introduction to Software Engineering
What is Software Engineering? The discipline of designing, creating, and maintaining software by applying technologies and practices from computer science,
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
CS251 – Software Engineering Lecture 9: Software Design Slides by Mohammad El-Ramly, PhD
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
CSE 303 – Software Design and Architecture
Software Engineering for Capstone Courses Richard Anderson CSE 481b Winter 2007.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
CSCI 3428: Software Engineering Tami Meredith Chapter 1 Why Software Engineering.
Lecture#1 Introduction….Cont Software Quality Engineering Subject : 19(A/B) – {Assignment /Query}
Chapter 1 SOFTWARE ENGINEERING What is Software Engineering.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini II. Software Life Cycle.
Software engineering Software Processes.
Chapter3:Software Processes
Requirements Analysis Scenes
Software Processes (a)
Software Processes.
What is software quality?
An Overview of Software Processes
The Object-Oriented Thought Process Chapter 02
PPT1: Basics of software engineering
Software Processes.
What is software quality?
Exam 1 review CS 360 Lecture 20.
UML Design for an Automated Registration System
Presentation transcript:

Chapter 1 Quality terminology Error: human mistake Fault: result of mistake, evidenced in some development or maintenance product Failure: departure from the system’s required behavior

Chapter 1 Garvin’s perspectives on quality Transcendental view: something we recognize but can’t define User view: fitness for purpose Manufacturing view: conformance to specification Product view: tied to inherent product characteristics Value-based view: depends on customer’s willingness to pay

Chapter 1 Systems approach Identify activities and objects. Define the system boundary. Consider nested systems, system interrelationships.

Chapter 1 Building a house vs. software Determining and analyzing requirements Producing and documenting the design Detailed specifications Identifying and designing components Building components Testing components Integrating components Making final modifications Continuing maintenance Requirements analysis and definition System design Program design Writing programs Unit testing Integration testing System testing System delivery Maintenance

Chapter 1 Key factors altering software engineering practice (Wasserman) criticality of time-to-market for commercial products shifts in economics of computing (lower HW, higher development/maintenance costs) availability of powerful desktop computing extensive local- and wide-area networking availability and adoption of OO technology graphical user interfaces unpredictability of waterfall model of development

Chapter 1 Wasserman’s basis for good software engineering Abstraction Analysis and design methods and notations User interface prototyping Software architecture Software process Reuse Measurement Tools and integrated environments

Chapter 1 Information systems example Piccadilly Television: regional British TV franchise Advertising scheme has many constraints: –alcohol adverts only after 9pm –if actor in show, no same actor in advert within 45 minutes –if advert in class of product, no other advert in same class during same break –rates dependent on amount of time bought Software to determine, track advertising time

Chapter 1 Real-time example Ariane-5 rocket, from European Space Agency June 4, 1996: functioned well for 40 seconds, then veered off course and was destroyed Contained four satellites: cost was $500 million Reused code from Ariane-4 rocket

Chapter 1 Ariane-5 definition of quality From Lions report: –“… demonstrated the high quality of the Ariane-5 programme as regards engineering work in general and completeness and traceability of documents.” –“… the supplier of the SRI … was only following the specification given to it. … The exception which occurred was not due to random failure but a design error.”