Unit 241 Integration Phase  The objective of this section is to introduce how the software product is realized from a set of programs, program units or.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Software Life Cycle and Models
Presentation by Prabhjot Singh
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
Ch 3: Unified Process CSCI 4320: Software Engineering.
Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials Implementation and Testing.
Implementation and Integration1 Concepts and practices.
Integration testing Satish Mishra
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
Integration and System Testing CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 29, 2007.
© 2005 by Prentice Hall Chapter 4 System Testing & Implementation Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Unit 191 Introduction to Software Engineering The objective of this section is to introduce the subject of software engineering. When you have read this.
Introduction to z/OS Basics © 2006 IBM Corporation Chapter 8: Designing and developing applications for z/OS.
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Illinois Institute of Technology
1 Testing. 2 About Testing  The reason the program is in testing is that it probably doesn’t work!  We test to find bugs before our users and hope that.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Software Testing Name: Madam Currie Course: Swen5431 Semester: Summer 2K.
Design, Implementation and Maintenance
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
SOFTWARE QUALITY ASSURANCE Maltepe University Faculty of Engineering SE 410.
Software System Integration
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
BY: GARIMA GUPTA MCA FINAL YEAR WHAT IS SOFTWARE TESTING ? SOFTWARE TESTING IS THE PROCESS OF EXECUTING PROGRAMS OR SYSTEM WITH THE INTENT.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
CSI315 Web Technology and Applications
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
ECE 355: Software Engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Integration testing l Tests complete systems or subsystems composed of integrated.
Implementation & Integration Phase Implementation, then integration: Implementation, then integration:  Each module is implemented by member of programmer.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 Chapter 9 Database Design. 2 2 In this chapter, you will learn: That successful database design must reflect the information system of which the database.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
Ranga Rodrigo. The purpose of software engineering is to find ways of building quality software.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Testing -- Part II. Testing The role of testing is to: w Locate errors that can then be fixed to produce a more reliable product w Design tests that systematically.
1 Chapter 22 Developer Testing. 2 introduction Testing is the most popular quality-improvement activity Testing is the most popular quality-improvement.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Program Development Cycle Modern software developers base many of their techniques on traditional approaches to mathematical problem solving. One such.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Distributed Information Systems. Motivation ● To understand the problems that Web services try to solve it is helpful to understand how distributed information.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
Module 4: Systems Development Chapter 14: Design And Implementation.
Software Design Process
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
Dr. DEVENDRA TAYAL– THE SCOPE OF SOFTWARE ENGINEERING.
Software Engineering Lecture # 1.
CSC 480 Software Engineering Test Planning. Test Cases and Test Plans A test case is an explicit set of instructions designed to detect a particular class.
Integration testing Integrate two or more module.i.e. communicate between the modules. Follow a white box testing (Testing the code)
Software Development Life Cycle (SDLC)
CS451 Software Implementation and Integration Yugi Lee STB #555 (816) Note: This lecture was designed.
Software Requirements Specification Document (SRS)
Software Project Management
Student Name USN NO Guide Name H.O.D Name Name Of The College & Dept.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Software Engineering Zhang Shuang
Testing throughout Lifecycle Ljudmilla Karu. Verification and validation (V&V) Verification is defined as the process of evaluating a system or component.
Software Testing. Purpose: Find errors! not prove that the program does not have them Types of tests: Unit Test Integration Test Function Test Load Test.
Automated Software Testing
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Engineering Lecture #14.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

Unit 241 Integration Phase  The objective of this section is to introduce how the software product is realized from a set of programs, program units or modules. When you have read this section you will: ounderstand the importance of the object oriented design that leads to the modular programming and integration; oknow the difference between the unit testing and the integration testing.

Unit 242  During the integration phase, the various component modules are combined to build the software product. The modules may be integrated using top-down approach or bottom-up approach. Suppose the product is integrated bottom-up. If there is a major design fault, then it will show up late, necessitating an expensive rewrite. Conversely, if the modules are integrated top-down, then the lower level modules usually will not receive as thorough a testing as would be the case if the product were integrated bottom-up.  Integration testing, system testing and acceptance testing are integral part of Implementation Phase. What is Integration?

Unit 243  The purpose of integration testing is to check that the modules combine correctly to achieve a product that satisfies its requirements. During the integration testing, particular care must be paid to testing the module interfaces.  When integration testing is completed, system testing is performed. The functionality of the product as a whole (including the performance, security, robustness, safety, maintainability, scalability etc.) is checked against the specifications.  The final aspect of this phase is acceptance testing. The software is delivered to the client, who tests the software on the actual hardware using actual data, as opposed to test data (sample data used by the developers). A software product cannot be considered to satisfy its specifications until the product has passed its acceptance tests. What is Integration? (cont ’ d)

Unit 244 The Integrated Software  Here we see the integrated software of the project.  The name of the project is Bank.  The software is integrated with the Account.class, Customer.class and Bank.html.

Unit 245 Exercises 1.What is a bottom-up approach of integration? 2.What is a top-down approach of integration? 3.What are the advantages and disadvantages of the two approaches?