KUFA UNIVERSITY Department of Computer Science 06/12/2015.

Slides:



Advertisements
Similar presentations
Verification and Validation
Advertisements

Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Stepan Potiyenko ISS Sr.SW Developer.
1 Software Testing and Quality Assurance Lecture 2 Software Verification & Validation.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Chapter 1 Principles of Programming and Software Engineering.
CSC 395 – Software Engineering Lecture 9: Testing -or- How I Stopped Worrying and Learned to Love the Bug.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
Verification and Validation CIS 376 Bruce R. Maxim UM-Dearborn.
Verification and Validation
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
Chapter 24 - Quality Management Lecture 1 1Chapter 24 Quality management.
COMP 354 Software Engineering I Section BB Summer 2009 Dr Greg Butler
Verification and Validation Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Testing. What is Testing? Definition: exercising a program under controlled conditions and verifying the results Purpose is to detect program defects.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Dr. Tom WayCSC Code Reviews & Inspections CSC 4700 Software Engineering.
Software Testing ©Dr. David A. Workman School of EE and Computer Science March 19, 2007.
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
University of Palestine software engineering department Testing of Software Systems Program Inspections, Walkthroughs, and Reviews instructor: Tasneem.
This chapter is extracted from Sommerville’s slides. Textbook chapter
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.
CS Data Structures I Chapter 2 Principles of Programming & Software Engineering.
1 Phase Implementation. Janice Regan, Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine subphases)
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Defects.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
KUFA UNIVERSITY Department of Computer Science 09/12/2015.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
KUFA UNIVERSITY Department of Computer Science. Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan.
CSI 1340 Introduction to Computer Science II Chapter 1 Software Engineering Principles.
Objects First With Java A Practical Introduction Using BlueJ Well-behaved objects 2.1.
How Are Computers Programmed? CPS120: Introduction to Computer Science Lecture 5.
Static Techniques for V&V. Hierarchy of V&V techniques Static Analysis V&V Dynamic Techniques Model Checking Simulation Symbolic Execution Testing Informal.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
VERIFICATION AND VALIDATION TECHNIQUES. The goals of verification and validation activities are to assess and improve the quality of the work products.
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
Static and Integration Testing. Static Testing vs Dynamic Testing  To find defects  This testing includes verification process  without executing.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
References & User group Reference: Software Testing and Analysis Mauro Pezze Software Engineering Ian Sommerville Eight Edition (2007) User group:
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
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.
Principles of Programming & Software Engineering
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
GUI Design and Coding PPT By :Dr. R. Mall.
Testing and Debugging PPT By :Dr. R. Mall.
Chapter - 8 Implementation.
CSC 480 Software Engineering
Verification and Validation
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Principles of Programming and Software Engineering
Basic Concepts in Software Design
Verification & Validation
Verification and Validation
Verification and Validation
Lecture 09:Software Testing
Software Engineering Lecture #45
GUI Design (cont.) and Coding (Lecture 8)
WALKTHROUGH and INSPECTION
Presentation transcript:

KUFA UNIVERSITY Department of Computer Science 06/12/2015

Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan 06/12/2015

Code review Code review -Code review is undertaken after the module successfully compiles and all the syntax error have been eliminated from the module -Code review are cost – effective strategies for eliminating coding error and for producing high quality code -Code review directly detect the error 06/12/2015

Coding standards and guidelines Coding guidelines Coding guidelines -Is provides general suggestions regarding the coding style -Leave the actual implementation of these guidelines to the discretion of the individual developers 06/12/2015

Type of code review 1- Code walkthrough -Is an informal code analysis technique -A few members of the development team are given the code for a couple days before the walkthrough meeting -Each member selects some test cases of code to hand run - the main objective of Code walkthrough is to discover the logical error in the code -Even though Code walkthrough is an informal analysis technique but have several guidelines over the years 06/12/2015

some Code walkthrough guidelines 1- the team that performing Code walkthrough should not be either too big or too small, it should consist between three to seven member 2- discussions should focus on discovery of errors and avoid how to fix the discovered error 3- mangers should not attend to foster cooperation among the engineers 06/12/2015

Cont.. 2- Code inspection - The aim of Code inspection is to check for the presence of some types of errors that usually creep in to code bcz the programmer oversight and to check whether coding standards Have been adhered to - Good s/w companies collect statistics regarding different type of error commonly committed by engineers and identify the types of error most frequently committed, such a list of commonly committed errors can be used as a check list during Code inspection to look out for possible errors 06/12/2015

some classical programming error checked during code inspection 06/12/ use uninitialized variable 2- non terminating loop 3- incompatible assignments 4- array indices out of bound 5- use incorrect logical operators or incorrect precedence among operators 6- mismatch between actual and formal parameter in procedure calls

Next lecture Testing phase Basic approach of testing Verification and validation

06/12/2015