Testing and Evaluating Software Solutions Live Test Data.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Making the System Operational
Topics to be discussed Introduction Performance Factors Methodology Test Process Tools Conclusion Abu Bakr Siddiq.
Database System Concepts and Architecture
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
Water Rights Accounting. New Accounting Model New Technology: 1979 versus 2011 – Faster processors – Faster graphics – Larger, faster, memory – Larger,
ITAuditing Using GAS & CAATs
Elements of a Microprocessor system Central processing unit. This performs the arithmetic and logical operations, such as add/subtract, multiply/divide,
Final Year Project Progress January 2007 By Daire O’Neill 4EE.
Chapter 1 Section II Fundamentals of Information Systems
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Silberschatz, Galvin and Gagne  2002 Modified for CSCI 399, Royden, Operating System Concepts Operating Systems Lecture 19 Scheduling IV.
Abirami Poonkundran 2/22/10.  Goal  Introduction  Testing Methods  Testing Scope  My Focus  Current Progress  Explanation of Tools  Things to.
1/17 Non Functional Requirements by: Dr. Timothy Korson CPIS 443.
Transaction Processing IS698 Min Song. 2 What is a Transaction?  When an event in the real world changes the state of the enterprise, a transaction is.
1 Software Testing and Quality Assurance Lecture 40 – Software Quality Assurance.
GREEN CORP’S Blue Team Stock Trading System Fall 2000 Software Engineering I.
Systems Analysis and Design in a Changing World, 6th Edition
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
 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.
Introduction to Systems Analysis and Design
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
Load Test Planning Especially with HP LoadRunner >>>>>>>>>>>>>>>>>>>>>>
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
The Software Development Cycle Defining and understanding the problem.
Introduction to Systems Analysis and Design Trisha Cummings.
People in multimedia Systems. Multimedia Systems Multimedia systems are designed by a team of people who specialise in a particular field, For example:
Introduction to HP LoadRunner Getting Familiar with LoadRunner >>>>>>>>>>>>>>>>>>>>>>
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
15 1 Chapter 15 Database Administration Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
1 The Design of Multimedia Assessment Objects Gavin Sim, Stephanie Strong and Phil Holifield.
What is Sure Stats? Sure Stats is an add-on for SAP that provides Organizations with detailed Statistical Information about how their SAP system is being.
Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.
Quality of System requirements 1 Performance The performance of a Web service and therefore Solution 2 involves the speed that a request can be processed.
Navigating 3D Worlds via 2D Multi- Touch Interfaces Daniel Cope Supervised by Stuart Marshall 1.
Computer Systems Nat 4/5 Computing Science Operating Systems.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Highway Accident Avoidance & Identification System[HAAIS] Project ID :
Analysing Miss O’Grady. Analysing Analysing is the interpretation of the data. It involves examining the data and giving meaning to it. When data has.
Testing and Evaluating Software Solutions Reporting on the Testing Process.
Data Transfer The Kingsway School. Transfer Speed Data Transfer is measured in bits per second (bps) 1 Kilobit per second is 1000 bps 1 Megabit\per second.
1 Software. 2 What is software ► Software is the term that we use for all the programs and data on a computer system. ► Two types of software ► Program.
Information Systems Analysis and Design Reviews of IS and Software Process Spring Semester
PROG Developing Robust Modular Software.. Objectives What do we want? Programmatic Elements in a Business System. Logic Layer. Persistence (Data)
Welcome to OLK12 Portfolio Solutions! Your presenter today….Janet Syed.
Chapter 8 System Management Semester 2. Objectives  Evaluating an operating system  Cooperation among components  The role of memory, processor,
Unit 19 Computer Music Systems 1 Examine the hardware options available for the composition and production of music using computer technology assess the.
Testing and Evaluating Software Solutions Introduction.
CCNA1 v3 Module 1 v3 CCNA 1 Module 1 JEOPARDY K. Martin.
CS 325: Software Engineering February 16, 2016 Designing a Design Class Diagram Design Class Diagrams DCD: Restaurant Example DCD: ATM Example Software.
The information systems lifecycle Far more boring than you ever dreamed possible!
Intro to Web Server Load Testing © Thank you for attending Introduction to Web Server Load Testing.
Software Metrics and Reliability
Software Architecture in Practice
Gary Hughes, South Oakleigh College
COMPONENTS OF A COMPUTER
Introduction to Operating System (OS)
Maintaining software solutions
Basic Microsoft Word 2013.
Networking for Home and Small Businesses – Chapter 2
Automobile Suspension System
Nat 4/5 Computing Science Operating Systems
Chapter 3 Hardware and software 1.
Progression of Test Categories
Chapter 3 Hardware and software 1.
Networking for Home and Small Businesses – Chapter 2
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
A HW/SW Co-Simulator for System Validation
Presentation transcript:

Testing and Evaluating Software Solutions Live Test Data

Why Live Test Data? the use of live test data ensures that the testing environment accurately reflects the expected environment in which the new system will operate Are we still achieving our initial objectives?

Conditions to Test Large file sizes Mix of transaction types Response times Volume of data (load testing) Interfaces between modules and programs

Large File Sizes Highlight problems associated with data access Systems can perform at unacceptable speeds when accessing large files (particularly for network access) Large data files highlight aspects of code that are inefficient or are processor extensive – this is problematic if the processor is awaiting system resources to become available

Mix of Transaction Types Testing for modules and programs is strategic in that specific transactions are tested one at time System testing requires us to ensure that transactions occurring in a random order do not cause unforeseeable issues

Response Times The time taken for a process to complete, these may be higher when using live test data Should be tested on the minimum hardware requirements with any interfacing applications operating under normal or heavy loads Any processes that are likely to take longer than a second should provide user feedback, i.e. progress bar, update-mouse pointer to buffer wheel etc.

Volume of Data (Load Testing) Large amounts of data should be entered into the new system to test the performance of the application under extreme conditions CASE tools can be used to simulate the input of thousands of users simultaneously

Interfaces between modules and programs Tests and test data need to be created to analyse the interaction (interfacing) between different software components of the system Tests should examine the accuracy of data being passed as well as response times and the ability of the interface to cope with large files, different transaction types and large volumes of data

Things to consider: What effect does the new system have on the existing systems in the environment it is installed into? And vice-versa, does the existing system have an unexpected effect on the new system?

Readings and Activities Read pages of the textbook Complete Question 12 on page 246 of the textbook