October 2004J. B. Wordsworth J4ISDPAD1 Information Systems Development Processes and documents.

Slides:



Advertisements
Similar presentations
CLASS PROJECT How do you present yourself to a potential employer?
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Software Engineering-II Sir zubair sajid. What’s the difference? Verification – Are you building the product right? – Software must conform to its specification.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
1 Software Testing and Quality Assurance Lecture 2 Software Verification & Validation.
Software Testing and Quality Assurance
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Fall, 2006SW Eng Standalone Progs, Univ of Colorado Boulder 1 Wk 11 Glass Box Testing, Flow Graphs, Test Coverage SW Engineering of Standalone Programs.
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Understand.
SE 555 Software Requirements & Specification Requirements Validation.
Chapter 1 Software Engineering. Homework ► Read Section 2.2 (pages 79-98) ► Answer questions: ► 7, 8, 11, 12, & 13 on page 134. ► Answer on paper, hand.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Software Process and Product Metrics
Verification and Validation
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Chapter 24 - Quality Management Lecture 1 1Chapter 24 Quality management.
Chapter 7: The Object-Oriented Approach to Requirements
Software Inspections and Walkthroughs By. Adnan khan.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
Software Testing Life Cycle
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Lecture 16 Formal Technical Reviews (FTRs) (also know as inspections) FOR0383 Software Quality Assurance 9/19/20151Dr Andy Brooks Don´t review in your.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Phil Cronin Anne Hill Allen Schones CIS841 Summer on Campus 1998 IN-PROCESS INSPECTIONS FOR OBJECT ORIENTED DESIGNS.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Intro to Jackson Software Engineering Oct 6, 2005.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
CSC 395 – Software Engineering Lecture 14: Object-Oriented Analysis –or– Ripping the Band-Aid Off Quickly.
Software Quality Assurance Lecture # 6 By: Faraz Ahmed.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 OO Analysis & Design - Introduction to main ideas in OO Analysis & design - Practical experience in applying ideas -A large element is use of UML as.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
November 2003J. B. Wordsworth: J3ISDQR41 Information Systems Development Quality and Risk (4)
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Advances In Software Inspection
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
1 Software Testing and Quality Assurance Lecture 17 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Inspections - Page P3-L14-1 MEF-TRANSITION-P3-L14-1 Dr. M.E. Fayad Lesson 14: Inspections SoftwareEngineeringII.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
1 Software Testing and Quality Assurance Motivation and Review of Software Verification & Validation (2)
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Software Quality Engineering
CSC 480 Software Engineering
Software Quality Engineering
Software Life Cycle “What happens in the ‘life’ of software”
Verification and Validation
Software Quality Engineering
Rational Worldwide Software Symposium
Software Engineering Lecture #13.
Rational Worldwide Software Symposium
Software Engineering (Second Year) Dr
QA Reviews Lecture # 6.
CS 425 Software Engineering
CS 425/625 Software Engineering
Rational Worldwide Software Symposium
Software Reviews.
Andreas Altmannsberger Frank Bühler Mike Rowe
Presentation transcript:

October 2004J. B. Wordsworth J4ISDPAD1 Information Systems Development Processes and documents

October 2004J. B. Wordsworth J4ISDPAD2 Objectives Process models for information systems Quality assurance in the development process Standard techniques for analysis and design (O-O) Interpret and modify standard design diagrams (UML) Recent advances in IS technology (problem frames)

October 2004J. B. Wordsworth J4ISDPAD3 Supplementary information Jackson, M. A.: Problem Frames. Addison Wesley, 2001, X Maciaszek, L. A.: Requirements Analysis and System Design. Addison Wesley, 2001, Ould, M. A.: Managing Software Quality and Business Risk. Wiley, 1999, X Stiller, E. and Leblanc, C.: Project-based Software Engineering, an Object-Oriented Approach. Addison Wesley, 2002, X. Stevens, P. and Pooley, R: Using UML: Software Engineering with Objects and Components. Addison Wesley 2000,

October 2004J. B. Wordsworth J4ISDPAD4 Web page URL: Contains: Copies of slides used in lectures Exercises Sample examination questions References to related information

October 2004J. B. Wordsworth J4ISDPAD5 Process models Lines and boxes –Indicate activities, and their order Process definition –Describes what goes on in each box

October 2004J. B. Wordsworth J4ISDPAD6 Developing a model Choose the activities: –analysis –specification –design –implementation –testing –delivery Choose the framework: –sequence –iteration –alternation

October 2004J. B. Wordsworth J4ISDPAD7 Analysis Specification Design Implementation Test Planning Testing Begin End

October 2004J. B. Wordsworth J4ISDPAD8 Defining the activities Name of activity Inputs – what you need Method – how you should proceed Outputs –what you must produce Entry criteria – how you know it’s time to start Exit criteria – how you know you have finished

October 2004J. B. Wordsworth J4ISDPAD9 Requirements statement Analysis document Specification document Design document Analysis activity Design activity Specification activity

October 2004J. B. Wordsworth J4ISDPAD10 Design document Code Test plan Test log Implementation activity Testing activity Test planning

October 2004J. B. Wordsworth J4ISDPAD11 Inspections Discovering defects in work products Roles –Moderator –Reader –Inspector Preparation Meeting Correcting the defects Statistics

October 2004J. B. Wordsworth J4ISDPAD12 Specification document Draft design document Inspection report Design document Design activity Inspection activity Rework activity