CS 451 Software Engineering Winter 2009
|
|
- Aubrie Lindsey
- 8 years ago
- Views:
Transcription
1 CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104, University Crossings
2 Testing Process
3 Testing Testing only reveals the presence of defects Does not identify nature and location of defects Identifying & removing the defect => role of debugging and rework Preparing test cases, performing testing, defects identification & removal all consume effort Overall testing becomes very expensive : 30-50% development cost
4 Levels of Testing The code contains requirement defects, design defects, and coding defects Nature of defects is different for different injection stages One type of testing will be unable to detect the different types of defects Different levels of testing are used to uncover these defects
5 Levels of Testing User needs Acceptance testing Requirement specification System testing Design Integration testing code Unit testing
6 Unit Testing Different modules tested separately Focus: defects injected during coding Essentially a code verification technique, covered in previous chapter UT is closely associated with coding Frequently the programmer does UT; coding phase sometimes called coding and unit testing
7 Integration Testing Focuses on interaction of modules in a subsystem Unit tested modules combined to form subsystems Test cases to exercise the interaction of modules in different ways May be skipped if the system is not too large
8 System Testing Entire software system is tested Focus: does the software implement the requirements? Validation exercise for the system with respect to the requirements Generally the final testing stage before the software is delivered May be done by independent people Defects removed by developers Most time consuming test phase
9 Acceptance Testing Focus: Does the software satisfy user needs? Generally done by end users/customer in customer environment, with real data Only after successful AT software is deployed Any defects found,are removed by developers Acceptance test plan is based on the acceptance test criteria in the SRS
10 Other forms of testing Performance testing tools needed to measure performance Stress testing load the system to peak, load generation tools needed Regression testing test that previous functionality works alright important when changes are made Previous test records are needed for comparisons Prioritization of testcases needed when complete test suite cannot be executed for a change Smoke testing Nightly build
11 Defect logging and tracking A large software may have thousands of defects, found by many different people Often person who fixes (usually the coder) is different from who finds Due to large scope, reporting and fixing of defects cannot be done informally Defects found are usually logged in a defect tracking system and then tracked to closure Defect logging and tracking is one of the best practices in industry
12 Defect logging A defect in a software project has a life cycle of its own, like Found by someone, sometime and logged along with info about it (submitted) Job of fixing is assigned; person debugs and then fixes (fixed) The manager or the submitter verifies that the defect is indeed fixed (closed) More elaborate life cycles possible
13 Validation and Verification Validation: a different set of activities that ensures that the software that has been built is traceable to customer requirements. Are we building the right product? Verification: the set of activities the ensures that software correctly implements a specific function. Are we building the product right?
14 Organizing Testing Software testing may be viewed as a spiral process: 15
15 Organizing Testing Software Testing Steps 16
16 Software Testing Strategies How do you know when you are done testing? There is no definitive answer to this question. Many possible answers: You are never done testing. You are done testing when you run out of money or time. Depends upon the certainty of failure you desire. 17
17 Strategic Issues Specify product requirements in a quantifiable manner long before testing commences State testing objectives explicitly. test coverage, mean time to failure, cost to find and fix defects, remaining defect density or frequency of occurrence Understand the users of the software and develop a profile for each user category. Build robust software that is designed to test itself. 18
18 Unit Testing
19 Testing Strategies Unit Testing focuses verification effort on the smallest unit of software design. (The component or module) Considerations: The module interface is tested to ensure that information properly flows into and out of the program unit under test. All independent paths through the control structure are exercised to ensure that all statements in a module have been executed at least once. Boundary conditions are tested to ensure that the module operates properly. Error handling paths are tested. 20
20 Testing Strategies Unit Testing Procedure Unit testing is normally considered as an adjunct to the coding step. Design of tests can be done before coding begins (Agile programming) 21
21 Testing Strategies Unit Testing Procedure Since each component is not a stand alone program, a bit of work must be done to perform the test. Create a driver, usually a main program, that accepts test case data and passes it to the component to be tested. It also may print relevant results. Stubs replace modules that may not be coded and are subordinate to the component to be tested. A stub may do minimum data manipulation, provides verification of entry, and returns control to the module undergoing testing. Unit testing is simpler when modules are highly cohesive. 22
22 Junit Example Java Code to Test public class Math { static public int add(int a, int b) { return a + b; } }
23 Junit example JUNIT test case import junit.framework.*; public class TestMath extends TestCase { public void testadd() { int num1 = 3; int num2 = 2; int total = 5; int sum = 0; sum = Math.add(num1, num2); assertequals(sum, total); } }
24 Integration Testing
25 Integration Testing Why is unit testing not enough? Data can be lost across an interface. One module can have an inadvertent effect on another. Global data structures can present problems Individually acceptable imprecision may become magnified. Integration testing is a systematic technique for constructing the software architecture while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure that has been dictated by design.
26 Integration Testing There is a tendency to attempt non-incremental integration construct the whole program via a bigbang approach. Thus to combine all components at once and test it as an entire program. Top Down Integration is an incremental approach to construction of the software architecture. Modules are integrated by moving downward through the control hierarchy, beginning with the main control module.
27 Integration Testing -- Top Down Modules subordinate to the main control module are incorporated into the structure in either a depth first or breath first manner.
28 Integration Testing -- Top Down The integration process is preformed in five steps: 1. The main control module is used as a test driver, and stubs are substituted for all components directly subordinate to the main control module. 2. Depending on the integration approach selected (i.e. depth or breath first), subordinate stubs are replaced one at a time with actual components. 3. Tests are conducted as each component is integrated. 4. On completion of each set of tests, another stub is replaced with the real component. 5. Regression testing may be conducted to ensure that new errors have not been introduced.
29 Bottom Up Integration Begins construction and testing with atomic modules. Since all subordinates are always available, there is no need for stubs. Bottom up integration follows the following steps: 1. Low-level components are combined into clusters that perform a specific software subfunction. 2. A driver (control program for testing) is written to coordinate test cases input and output. 3. The cluster is tested. 4. Drivers are removed and clusters are combined moving upward in the program structure. One major disadvantage of bottom up integration is that the program as an entity does not exist until the last module is added.
30 Bottom Up Integration
31 Regression Testing
32 Regression Testing Each time a new module is added, the software changes. These changes may cause problems with functions that previously worked. Therefore, we must re-execute some subset of tests that were already conducted to ensure that changes have not propagated unintended side effects. Any time you test, if successful you will find errors. When those errors are corrected, software changes. Therefore, regression testing must be performed in order to ensure that those changes did not propagate unintended side effects. Regression tests may be conducted manually I do not recommend this.
33 Testing in the OO Context
34 Unit Testing in the OO Context With OO the concept of the unit changes. Because of the dependence of sub classes, unit testing is a bit more complicated. In the OO context, unit testing is basically Class testing. Cannot simply test methods in a super class and assume they are still valid in each subclass Subclasses may re-define important attributes or subordinate methods Must fully test all methods of all classes
35 Integration Testing in the OO Context Unlike non OO programming, OO programming does not have an hierarchical control structure. Integrating one object at a time is also difficult because of the direct and indirect interactions of the components that make up the class. There are two basic strategies: Thread-based Use-based
36 Test Strategies for OO Software Thread-based testing integrates the set of classes required to respond to one input or event for the system. Each thread is integrated and tested individually. Regression testing is applied to ensure no side effects occur. Good for GUIs, other event-driven multithreaded software
37 Test Strategies for OO Software Use-based testing begins the construction of system by testing those classes that use very few server classes. After independent classes are tested, the next layer of classes, called dependent classes are tested. This continues until the entire system is constructed. AKA: Bottom-up testing with objects
38 Test Strategies for OO Software Drivers can be used to test operations at the lowest level and for testing groups of classes. A driver may be used to replace the user interface. Stubs may be used where collaboration between classes is required but one or more of the collaborating classes is not fully implemented.
39 Test Strategies for OO Software Cluster testing is one step in integration testing of OO software. Here, a cluster of collaborating classes is exercised by designing test cases that attempt to uncover errors in the collaborations.
40 Validation Testing Validation Testing Validation testing begins at the culmination of integrations testing. Testing focuses on the user-visible actions and user-recognizable output from the system. Validation can be defined as: Validation succeeds when software functions in a manner that can be reasonably expected by the customer. Software validation is achieved through a series of tests that demonstrate conformity with software requirements.
41 Test Strategies for Publicly-used Software What to do if your product does not have one or a few customers? Most software product builders use a process called alpha and beta testing to uncover errors that only the end-user seems able to find. The alpha test is conducted at the developer s site by end-users. The beta test is conducted at the end-user sites. Beta tests usually do not have the developer present.
42 Recovery Testing Recovery Testing most computer-based systems must recover from faults and resume processing within a prespecified time. Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that recovery is properly preformed.
43 Security Testing Any computer system that manages sensitive information or causes actions that can improperly harm or benefit individuals is a target for improper or illegal penetration. Lot s of security issues. In your code In libraries and frameworks In database access In OS layers Security testing finds faults with the protection mechanisms built into the system that may allow improper access.
44 Security Testing During security testing, the tester plays the role(s) of individual who desires to penetrate the system. Penetration testing requires high skill and the ability to think outside the box Best to get an independent testing group that specializes in penetration testing Usually it s not the software, but people issues. People often give out secure information. No system can truly protect against this 100%.
45 Stress Testing So far all testing assumed normal program functions and performance. Stress tests are designed to confront programs with abnormal quantity, frequency, or volume. Multiple interrupts per second Increased data rate Test max memory Excessive disk hunting
46 Performance Testing Designed to test the run-time performance of software within the context of an integrated system. Should be performed at all steps of the testing process. Not until system elements are fully integrated that performance of a system can really be ascertained. Often requires hardware and software instrumentation to measure resource utilization.
47 Summary Validation and Verification Different Types of Testing Context purposes
Chapter 17 Software Testing Strategies Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For
More informationModule 10. Coding and Testing. Version 2 CSE IIT, Kharagpur
Module 10 Coding and Testing Lesson 26 Debugging, Integration and System Testing Specific Instructional Objectives At the end of this lesson the student would be able to: Explain why debugging is needed.
More informationIntroduction to Automated Testing
Introduction to Automated Testing What is Software testing? Examination of a software unit, several integrated software units or an entire software package by running it. execution based on test cases
More informationSoftware Testing Strategies and Techniques
Software Testing Strategies and Techniques Sheetal Thakare 1, Savita Chavan 2, Prof. P. M. Chawan 3 1,2 MTech, Computer Engineering VJTI, Mumbai 3 Associate Professor, Computer Technology Department, VJTI,
More informationSoftware Development: The Waterfall Model
Steven Zeil June 7, 2013 Contents 1 Software Development Process Models 2 1.1 Components of the Waterfall Model................................. 2 1.1.1 What is a requirement?. 2 1.1.2 Testing..........
More informationBasic Unix/Linux 1. Software Testing Interview Prep
Basic Unix/Linux 1 Programming Fundamentals and Concepts 2 1. What is the difference between web application and client server application? Client server application is designed typically to work in a
More informationComparing the Testing Approaches of Traditional, Object-Oriented and Agent- Oriented Software System
Comparing the Testing Approaches of Traditional, Object-Oriented and Agent- Oriented Software System N.Sivakumar 1 and K.Vivekanandan 2 Department of computer Science and Engineering Pondicherry Engineering
More informationSoftware testing. Objectives
Software testing cmsc435-1 Objectives To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testing To describe strategies for generating
More informationMetrics in Software Test Planning and Test Design Processes
Master Thesis Software Engineering Thesis no: MSE-2007:02 January 2007 Metrics in Software Test Planning and Test Design Processes Wasif Afzal School of Engineering Blekinge Institute of Technology Box
More informationSoftware Testing Interview Questions
Software Testing Interview Questions 1. What s the Software Testing? A set of activities conducted with the intent of finding errors in software. 2.What is Acceptance Testing? Testing conducted to enable
More informationSoftware Engineering Question Bank
Software Engineering Question Bank 1) What is Software Development Life Cycle? (SDLC) System Development Life Cycle (SDLC) is the overall process of developing information systems through a multi-step
More informationChapter 11: Integration- and System Testing
Chapter 11: Integration- and System Testing Chapter 14: Testing (2/2) Object-Oriented Software Construction Armin B. Cremers, Sascha Alda & Tobias Rho (based on Bruegge & Dutoit) Software Lifecycle Activities...and
More informationChapter 11: Integrationand System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11: Integrationand System Testing Integration Testing Strategy The entire system is viewed as a collection of subsystems (sets
More informationSoftware Engineering. How does software fail? Terminology CS / COE 1530
Software Engineering CS / COE 1530 Testing How does software fail? Wrong requirement: not what the customer wants Missing requirement Requirement impossible to implement Faulty design Faulty code Improperly
More informationSoftware Testing. Definition: Testing is a process of executing a program with data, with the sole intention of finding errors in the program.
Software Testing Definition: Testing is a process of executing a program with data, with the sole intention of finding errors in the program. Testing can only reveal the presence of errors and not the
More informationLevels of Software Testing. Functional Testing
Levels of Software Testing There are different levels during the process of Testing. In this chapter a brief description is provided about these levels. Levels of testing include the different methodologies
More informationSoftware Testing. Knowledge Base. Rajat Kumar Bal. Introduction
Software Testing Rajat Kumar Bal Introduction In India itself, Software industry growth has been phenomenal. IT field has enormously grown in the past 50 years. IT industry in India is expected to touch
More informationBasic Testing Concepts and Terminology
T-76.5613 Software Testing and Quality Assurance Lecture 2, 13.9.2006 Basic Testing Concepts and Terminology Juha Itkonen SoberIT Contents Realities and principles of Testing terminology and basic concepts
More informationKarunya University Dept. of Information Technology
PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main
More informationPresentation: 1.1 Introduction to Software Testing
Software Testing M1: Introduction to Software Testing 1.1 What is Software Testing? 1.2 Need for Software Testing 1.3 Testing Fundamentals M2: Introduction to Testing Techniques 2.1 Static Testing 2.2
More informationSoftware Testing Lifecycle
STLC-Software Testing Life Cycle SDLC Software Testing Lifecycle Software Testing Life Cycle (STLC) defines the steps/ stages/ phases in testing of software. However, there is no fixed standard STLC in
More informationTesting and Inspecting to Ensure High Quality
Testing and Inspecting to Ensure High Quality Basic definitions A failure is an unacceptable behaviour exhibited by a system The frequency of failures measures the reliability An important design objective
More informationCSTE Mock Test - Part III Questions Along with Answers
Note: This material is for Evaluators reference only. Caters to answers of CSTE Mock Test - Part III paper. 1. Independence is important in testing is mostly due to the fact that (Ans: C) a. Developers
More informationCSTE Mock Test - Part I - Questions Along with Answers
Note: This material is for Evaluators reference only. Caters to answers of CSTE Mock Test - Part I paper. 1. A branch is (Ans: d) a. An unconditional transfer of control from any statement to any other
More informationABSTRACT. would end the use of the hefty 1.5-kg ticket racks carried by KSRTC conductors. It would also end the
E-Ticketing 1 ABSTRACT Electronic Ticket Machine Kerala State Road Transport Corporation is introducing ticket machines on buses. The ticket machines would end the use of the hefty 1.5-kg ticket racks
More informationSoftware Engineering I: Software Technology WS 2008/09. Integration Testing and System Testing
Software Engineering I: Software Technology WS 2008/09 Integration Testing and System Testing Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Overview Integration testing
More informationMANUAL TESTING. (Complete Package) We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info
MANUAL TESTING (Complete Package) WEB APP TESTING DB TESTING MOBILE APP TESTING We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info START DATE : TIMINGS : DURATION :
More informationAPPROACHES TO SOFTWARE TESTING PROGRAM VERIFICATION AND VALIDATION
1 APPROACHES TO SOFTWARE TESTING PROGRAM VERIFICATION AND VALIDATION Validation: Are we building the right product? Does program meet expectations of user? Verification: Are we building the product right?
More informationFSW QA Testing Levels Definitions
FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis
More informationSoftware Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement
Software Quality Engineering Slide (Ch.12) 1 Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement Jeff Tian, tian@engr.smu.edu www.engr.smu.edu/ tian/sqebook Chapter 12.
More informationChapter 8 Software Testing
Chapter 8 Software Testing Summary 1 Topics covered Development testing Test-driven development Release testing User testing 2 Program testing Testing is intended to show that a program does what it is
More informationTesting Tools Content (Manual with Selenium) Levels of Testing
Course Objectives: This course is designed to train the fresher's, intermediate and professionals on testing with the concepts of manual testing and Automation with Selenium. The main focus is, once the
More informationChapter 11, Testing, Part 2: Integration and System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11, Testing, Part 2: Integration and System Testing Overview Integration testing Big bang Bottom up Top down Sandwich System testing
More informationDefinitions. Software Metrics. Why Measure Software? Example Metrics. Software Engineering. Determine quality of the current product or process
Definitions Software Metrics Software Engineering Measure - quantitative indication of extent, amount, dimension, capacity, or size of some attribute of a product or process. Number of errors Metric -
More informationBusiness Application Services Testing
Business Application Services Testing Curriculum Structure Course name Duration(days) Express 2 Testing Concept and methodologies 3 Introduction to Performance Testing 3 Web Testing 2 QTP 5 SQL 5 Load
More informationSoftware quality engineering. Quality assurance. Testing
4 Software Quality Engineering c Jeff Tian, to be published by John Wiley, 2005 Software quality engineering Quality assurance Testing Figure 1.1. engineering Scope and content hierarchy: Testing, quality
More informationOutline. 1 Denitions. 2 Principles. 4 Implementation and Evaluation. 5 Debugging. 6 References
Outline Computer Science 331 Introduction to Testing of Programs Mike Jacobson Department of Computer Science University of Calgary Lecture #3-4 1 Denitions 2 3 4 Implementation and Evaluation 5 Debugging
More informationThe Theory of Software Testing
The Theory of Software Testing Adtha Lawanna Department of Information Technology, Faculty of Science and Technology Assumption University, Bangkok, Thailand E-mail: Abstract Software
More informationSoftware Engineering Introduction & Background. Complaints. General Problems. Department of Computer Science Kent State University
Software Engineering Introduction & Background Department of Computer Science Kent State University Complaints Software production is often done by amateurs Software development is done by tinkering or
More informationManaging and Maintaining Windows Server 2008 Servers
Managing and Maintaining Windows Server 2008 Servers Course Number: 6430A Length: 5 Day(s) Certification Exam There are no exams associated with this course. Course Overview This five day instructor led
More informationTesting, Debugging, and Verification
Testing, Debugging, and Verification Testing, Part II Moa Johansson 10 November 2014 TDV: Testing /GU 141110 1 / 42 Admin Make sure you are registered for the course. Otherwise your marks cannot be recorded.
More informationTesting Introduction. IEEE Definitions
Testing Introduction IEEE Definitions Software testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the
More informationTest Specification. Introduction
Test Specification Introduction Goals and Objectives GameForge is a graphical tool used to aid in the design and creation of video games. A user with little or no experience with Microsoft DirectX and/or
More informationhttp://www.test-institute.org International Software Test Institute
THE ONLY BOOK CAN SIMPLY LEARN SOFTWARE TESTING! Page 1 Contents ABOUT THE AUTHOR... 3 1. Introduction To Software Testing... 4 2. What is Software Quality Assurance?... 7 3. What Is Software Testing?...
More informationAutomation and Virtualization Increase Utilization and Efficiency of J2EE Applications
TECHNICAL WHITEPAPER Automation and Virtualization Increase Utilization and Efficiency of J2EE Applications Introduction Progressive IT departments have broadly adopted application servers and the Java
More informationLast Class: OS and Computer Architecture. Last Class: OS and Computer Architecture
Last Class: OS and Computer Architecture System bus Network card CPU, memory, I/O devices, network card, system bus Lecture 3, page 1 Last Class: OS and Computer Architecture OS Service Protection Interrupts
More informationFormal Software Testing. Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com
Formal Software Testing Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com Scope of Testing Find defects early Remove defects prior to production Identify Risks Unbiased opinion When Should Testing
More informationKnow or Go Practical Quest for Reliable Software
Know or Go Practical Quest for Reliable Software Dr.-Ing. Jörg Barrho Dr.-Ing. Ulrich Wünsche AVACS Project meeting 25.09.2014 2014 Rolls-Royce Power Systems AG The information in this document is the
More informationOracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008
Oracle Insurance Policy Administration System Quality Assurance Testing Methodology An Oracle White Paper August 2008 Oracle Insurance Policy Administration System Quality Assurance Testing Methodology
More informationQuestions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
More information8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across
More informationBenefits of Test Automation for Agile Testing
Benefits of Test Automation for Agile Testing Manu GV 1, Namratha M 2, Pradeep 3 1 Technical Lead-Testing Calsoft Labs, Bangalore, India 2 Assistant Professor, BMSCE, Bangalore, India 3 Software Engineer,
More informationJUnit. Introduction to Unit Testing in Java
JUnit Introduction to Unit Testing in Java Testing, 1 2 3 4, Testing What Does a Unit Test Test? The term unit predates the O-O era. Unit natural abstraction unit of an O-O system: class or its instantiated
More informationTools for Integration Testing
Tools for Integration Testing What is integration ing? Unit ing is ing modules individually A software module is a self-contained element of a system Then modules need to be put together to construct the
More informationDecomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces
Software Engineering, Lecture 4 Decomposition into suitable parts Cross cutting concerns Design patterns I will also give an example scenario that you are supposed to analyse and make synthesis from The
More information4.13 System Testing. Section 4 Bidder's Products, Methodology, and Approach to the Project. 4.14 System Training
Section 4 Bidder's Products, Methodology, and Approach to the Project 4.1 FACTS II Requirements Summary 4.11 Interfaces 4.2 Functional Requirements 4.12 System Development 4.3 Technical Requirements 4.13
More informationDesign principles in Test Suite Architecture
Design principles in Test Suite Architecture InSTA 2015 (International workshop on Software Test Architecture) Graz, Austria 2015/4/13(Mon) Nishi, Yasuharu The University of Electro-Communications, Japan
More informationVerification and Validation of Software Components and Component Based Software Systems
Chapter 5 29 Verification and Validation of Software Components and Component Based Christina Wallin Industrial Information Technology Software Engineering Processes ABB Corporate Research christina.wallin@mdh.se
More informationApplication Centric Infrastructure Object-Oriented Data Model: Gain Advanced Network Control and Programmability
White Paper Application Centric Infrastructure Object-Oriented Data Model: Gain Advanced Network Control and Programmability What You Will Learn This document discusses application centric infrastructure
More informationApproach of Unit testing with the help of JUnit
Approach of Unit testing with the help of JUnit Satish Mishra mishra@informatik.hu-berlin.de About me! Satish Mishra! Master of Electronics Science from India! Worked as Software Engineer,Project Manager,Quality
More informationExample Software Development Process.
Example Software Development Process. The example software development process is shown in Figure A. The boxes represent the software development process kernels. The Software Unit Testing, Software Component
More informationSOFTWARE TESTING: TECHNIQUES & TYPES
SOFTWARE TESTING: TECHNIQUES & TYPES Ravinder Yadav, Aakash Goyal, Surender Kumar Rawal Dronacharya College Of Engineering Abstract Software testing is the process of testing the software product.software
More information應 用 測 試 於 軟 體 發 展 生 命 週 期. Testing In The Software Development Life Cycle
The Second Management Innovation and Practices Conference, Tamsui, Taiwan, April 2001,Volume 2, pp59-68 應 用 測 試 於 軟 體 發 展 生 命 週 期 Testing In The Software Development Life Cycle 蔡 博 元 莊 立 文 真 理 大 學 資 訊
More informationSoftware Quality Testing Course Material
Prepared by Vipul Jain Software Quality Testing Course Material Course content is designed and will be taught in such a manner in order to make a person job ready in around 10-12 weeks. Classroom sessions
More informationCSC 2405: Computer Systems II
CSC 2405: Computer Systems II Spring 2013 (TR 8:30-9:45 in G86) Mirela Damian http://www.csc.villanova.edu/~mdamian/csc2405/ Introductions Mirela Damian Room 167A in the Mendel Science Building mirela.damian@villanova.edu
More informationCloud Computing. Up until now
Cloud Computing Lecture 11 Virtualization 2011-2012 Up until now Introduction. Definition of Cloud Computing Grid Computing Content Distribution Networks Map Reduce Cycle-Sharing 1 Process Virtual Machines
More informationSoftware Testing Tutorial
Software Testing Tutorial SOFTWARE TESTING TUTORIAL Simply Easy Learning by tutorialspoint.com tutorialspoint.com i C O P Y R I G H T & D I S C L A I M E R N O T I C E All the content and graphics on this
More informationICAPRG529A Apply testing techniques for software development
ICAPRG529A Apply testing techniques for software development Release: 1 ICAPRG529A Apply testing techniques for software development Modification History Release Release 1 Comments This Unit first released
More informationDesign and Implementation of Life Insurance Assets Management methods using Create Insurance System
www..com 22 Design and Implementation of Life Insurance Assets Management methods using Create Insurance System Sai Divya Kalagatla 1, Chandra Babu. K 2 and Mohana Roopa. Y 3 1 Department of Computer Science,
More informationGroup18-CUCE2012. Mr. Mobile Project. Software Testing Plan (STP) Version: 4.0. CM Identifier: G18_SE004
Group18-CUCE2012 Mr. Mobile Project Software Testing Plan (STP) Version: 4.0 CM Identifier: G18_SE004 26 April 2010 Revision History Prepared/ Modified by Ahmed Adel Ahmed Abdullah, Ahmed Hafez and Sheriff
More informationEngineering Process Software Qualities Software Architectural Design
Engineering Process We need to understand the steps that take us from an idea to a product. What do we do? In what order do we do it? How do we know when we re finished each step? Production process Typical
More informationContinuous Integration, Delivery and Deployment. Eero Laukkanen T-76.5613 - Software Testing and Quality Assurance P 20.11.2015
Continuous Integration, Delivery and Deployment Eero Laukkanen T-76.5613 - Software Testing and Quality Assurance P 20.11.2015 System Integration In engineering, system integration is defined as the process
More informationAdvancements in the V-Model
Advancements in the V-Model Sonali Mathur Asst. Professor, CSE Dept. ABES Institute of Technology Ghaziabad, U.P-201009 Shaily Malik Lecturer, CSE Dept. Maharaja Surajmal Institute of Tech. Janakpuri,
More informationRelay2 Enterprise Cloud Controller Datasheet
Relay2 Enterprise Cloud WLAN Network Controller Provides the power of enterprise network services without the complexities and cost of traditional hardware- based Wi- Fi controllers The Relay2 Enterprise
More informationSoftware Testing. System, Acceptance and Regression Testing
Software Testing System, Acceptance and Regression Testing Objectives Distinguish system and acceptance testing o How and why they differ from each other and from unit and integration testing Understand
More informationSoftware in safety critical systems
Software in safety critical systems Software safety requirements Software safety integrity Budapest University of Technology and Economics Department of Measurement and Information Systems Definitions
More informationTest Data Management Best Practice
Test Data Management Best Practice, Inc. 5210 Belfort Parkway, Suite 400 Author: Stephanie Chace Quality Practice Lead srchace@meridiantechnologies.net, Inc. 2011 www.meridiantechnologies.net Table of
More informationCPSC 330 Software Engineering
CPSC 330 Software Engineering Lecture 4: Unit ing, JUnit, and Software Development Processes Today Unit ing and JUnit Software Development Processes (as time allows) Reading Assignment Lifecycle handout
More informationDistribution One Server Requirements
Distribution One Server Requirements Introduction Welcome to the Hardware Configuration Guide. The goal of this guide is to provide a practical approach to sizing your Distribution One application and
More informationTESTING FRAMEWORKS. Gayatri Ghanakota
TESTING FRAMEWORKS Gayatri Ghanakota OUTLINE Introduction to Software Test Automation. What is Test Automation. Where does Test Automation fit in the software life cycle. Why do we need test automation.
More informationAC 20-148 REUSABLE SOFTWARE COMPONENTS
AC 20-148 REUSABLE SOFTWARE COMPONENTS December 7, 2004 12/7/04 AC 20-148 CONTENTS Paragraph Title Page 1. Purpose....1 2. Motivation for this Guidance....1 3. Document Overview...1 4. General Guidelines
More informationIntroduction to Embedded Systems. Software Update Problem
Introduction to Embedded Systems CS/ECE 6780/5780 Al Davis logistics minor Today s topics: more software development issues 1 CS 5780 Software Update Problem Lab machines work let us know if they don t
More informationAn Analysis on Objectives, Importance and Types of Software Testing
Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology IJCSMC, Vol. 2, Issue. 9, September 2013,
More informationHow To Test A Web Based System
Testing Web-Based Systems-Checklists Testing Web-Based Systems -Checklist Overview-: Web-based testing should be RISK ORIENTED. This article describes the risks, presents the types of testing that can
More informationProduct Build. ProPath. Office of Information and Technology
Product Build ProPath Office of Information and Technology Table of Contents Product Build Process Maps... 1 Process: Product Build... 3 Product Build and Goals... 4... 4 Goals... 4 Product Build RACI
More informationSAFE SOFTWARE FOR SPACE APPLICATIONS: BUILDING ON THE DO-178 EXPERIENCE. Cheryl A. Dorsey Digital Flight / Solutions cadorsey@df-solutions.
SAFE SOFTWARE FOR SPACE APPLICATIONS: BUILDING ON THE DO-178 EXPERIENCE Cheryl A. Dorsey Digital Flight / Solutions cadorsey@df-solutions.com DIGITAL FLIGHT / SOLUTIONS Presentation Outline DO-178 Overview
More informationScience and Practice of Software Testing
Dr. S.S.Riaz Ahamed / Internatinal Journal of Engineering Science and Technology STUDYING THE FEASIBILITY AND IMPORTANCE OF SOFTWARE TESTING: AN ANALYSIS Dr.S.S.Riaz Ahamed Principal, Sathak Institute
More informationTo introduce software process models To describe three generic process models and when they may be used
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSOFTWARE DEVELOPMENT SD
CONTENTS 1.SOFTWARE-DEFINITION 2.TYPES OF SOFTWARE 3.SOFTWARE DEVELOPMENT 4.SOFTWARE LIFECYCLE 5.WATERFALL MODEL 6.ITERATION MODEL 7.V SHAPED MODEL 8.SPIRAL MODEL SOFTWARE DEVELOPMENT SD MODULE 1 1.SOFTWARE:
More informationTesting Automation for Distributed Applications By Isabel Drost-Fromm, Software Engineer, Elastic
Testing Automation for Distributed Applications By Isabel Drost-Fromm, Software Engineer, Elastic The challenge When building distributed, large-scale applications, quality assurance (QA) gets increasingly
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationContents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
More informationHow era Develops Software
How era Develops Software Executive Summary: In an organized, iterative, carefully documented manner, era has built a dense infrastructure of methodology, standards, and procedures to underpin the development
More informationChapter 6, The Operating System Machine Level
Chapter 6, The Operating System Machine Level 6.1 Virtual Memory 6.2 Virtual I/O Instructions 6.3 Virtual Instructions For Parallel Processing 6.4 Example Operating Systems 6.5 Summary Virtual Memory General
More informationSoftware Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering Software Processes Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software process models To describe three generic process models and when
More informationStandard Glossary of Terms Used in Software Testing. Version 3.01
Standard Glossary of Terms Used in Software Testing Version 3.01 Terms Used in the Foundation Level Syllabus International Software Testing Qualifications Board Copyright International Software Testing
More informationTEST PLAN Issue Date: <dd/mm/yyyy> Revision Date: <dd/mm/yyyy>
DEPARTMENT OF HEALTH AND HUMAN SERVICES ENTERPRISE PERFORMANCE LIFE CYCLE FRAMEWORK CHECKLIIST TEST PLAN Issue Date: Revision Date: Document Purpose The purpose of
More informationCUSTOMER GUIDE. Support Services
CUSTOMER GUIDE Support Services Table of Contents Nexenta Support Overview... 4 Support Contract Levels... 4 Support terminology... 5 Support Services Provided... 6 Technical Account Manager (TAM)... 6
More informationIntegrated Error-Detection Techniques: Find More Bugs in Java Applications
Integrated Error-Detection Techniques: Find More Bugs in Java Applications Software verification techniques such as pattern-based static code analysis, runtime error detection, unit testing, and flow analysis
More informationIEEE ComputerSociety 1 Software and Systems Engineering Vocabulary
IEEE ComputerSociety 1 Software and Systems test item. (1) system or software item that is an object of testing (IEEE 829-2008 IEEE Standard for Software and System Test Documentation, 3.1.48) (2) work
More information