Non-Functional Testing Standards Workshop EuroSTAR 2001 Stockholm – Sweden Graham Thomas Wall Street Systems.

Slides:



Advertisements
Similar presentations
Components of GIS.
Advertisements

Software Quality Seung Yang CS 525 Software Engineering II Dr. Sheldon X. Liang.
Network Design and Implementation
1/17 Non Functional Requirements by: Dr. Timothy Korson CPIS 443.
Pertemuan 16 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Eleventh Edition 1 Introduction to Information Systems Essentials for the Internetworked E-Business Enterprise Irwin/McGraw-Hill Copyright © 2002, The.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
SE 555 Software Requirements & Specification Requirements Quality Attributes.
SE 555 – Software Requirements & Specifications Introduction
1414 CHAPTER PROGRAMMING AND LANGUAGES. © 2005 The McGraw-Hill Companies, Inc. All Rights Reserved Competencies Describe the six steps of programming.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Introduction to Systems Analysis and Design
Software Testing Introduction. Agenda Software Testing Definition Software Testing Objectives Software Testing Strategies Software Test Classifications.
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
Pfleeger and Atlee, Software Engineering: Theory and Practice CS499 Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee 4 th Edition.
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
System Testing In a Hurry British Computer Society Specialist Interest Group In Software Testing 6th December 1999 Graham Thomas Wall Street Systems.
Samuvel Johnson nd MCA B. Contents  Introduction to Real-time systems  Two main types of system  Testing real-time software  Difficulties.
Categories of Testing.
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
RUP Implementation and Testing
- Component Inspection. -Usability Testing. -Unit Testing. -System Testing.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Configuration Management (CM)
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
An Introduction to Software Engineering. What is Software?
Module 7 Session 7.3 Visual 1 Module 7 Planning and Scheduling with the Critical Path Method Session 7.3 The computer and project management.
Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 9 Software Quality Assurance.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
Integration testing Integrate two or more module.i.e. communicate between the modules. Follow a white box testing (Testing the code)
G.Govi CERN/IT-DB 1 September 26, 2003 POOL Integration, Testing and Release Procedure Integration  Packages structure  External dependencies  Configuration.
Windows 95/98 Installation and Configuration Presented by Hua Wei.
TESTING (S,S,AND A,B) By KARTHIKEYAN KANDASAMY. TESTING Scenario testing – 1.System & 2. Usecase Defect bash System o Functional and non functional testing.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
Understanding Data Center Operations and Your Role Company Name Date - Time 1 | Introduction to the IBM Enterprise Environment 45 minutes 1 hour PowerPoint.
1.The following diagram illustrates the relationship among various hardware components. The arrows indicate the directions of data flow. Activity 1 Relationship.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Component 4: Introduction to Information and Computer Science Unit 9/Part e: Components and Development of Large Scale Systems.
System Testing 12/09. Hierarchy of Testing Testing Program Testing Top Down Bottom Up Integration TestingUnit Testing System Testing Big Bang Sandwich.
Microsoft dynamics crm online training.  Microsoft Dynamics CRM is a customer relationship management (CRM) solution that provides the tools and capabilities.
Java Programming, 3e Concepts and Techniques Chapter 1 Section 56 – An Introduction to Java.
Software Testing By Souvik Roy. What is Software Testing? Executing software in a simulated or real environment, using inputs selected somehow.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
Non Functional Testing. Contents Introduction – Security Testing Why Security Test ? Security Testing Basic Concepts Security requirements - Top 5 Non-Functional.
CPMGT 300 Week 4 Learning Team Collecting Requirements Check this A+ tutorial guideline at 300/CPMGT-300-Week-4-Learning-Team-Collecting-
Software Testing Strategies for building test group
Software Testing.
Designing the Physical Architecture
Testing the System.
(Professional Business Analyst Training organisation)
Software Engineering Development of procedures and systematic applications that are used on electronic machines. Software engineering incorporates various.
Quality Management Perfectqaservices.
Security Engineering.
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
PRODUCTION AND OPERATIONS MANAGEMENT
Software engineering Lecturer: Nareena.
IT INFRASTRUCTURES Business-Driven Technologies
Unit 2: Fundamentals of Computer Systems
Software Requirements Specification (SRS) Template.
Assignment 2: Activity 2 Produce a written report to explain how software utilities can improve the performance of Computer Systems. Select 3-4 utilities.
Chapter 11: Integration- and System Testing
Presentation transcript:

Non-Functional Testing Standards Workshop EuroSTAR 2001 Stockholm – Sweden Graham Thomas Wall Street Systems

2 Agenda l Introduction l History of the BCS SIGIST SWP l Work of the Group l Workshop m Procedure Testing m Performance Testing m Security Testing l Summary

3 Introduction l Who are we? l What do we do? l Why are we here today? l What can we do for you? l What can you do to help the group?

4 BCS SIGIST SWP history l Group established for 10+ years l Generated existing British Standards for Software Testing m BS7925-1Vocabulary of terms in software testing m BS7925-2Software component testing l Non-Functional Testing Techniques

5 Non-Functional testing techniques l Memory Management l Reliability l Usability l Maintainability l Configuration l Portability l Recovery l Disaster Recovery l Performance l Stress l Security l Procedure l Interoperability l Compatibility l Installability l Conversion

6 Work of the group l About a year ago... m Single threaded m 8 meetings per year m Low response rate m Possibility of another 8 years l A change of plan m Multi threaded m Team based approach m 12 meetings per year m Higher response rate

7 Work of group l To produce standards that are good enough l To ensure that they are workable l To produce them to a standard format l Structure of a technique l Normative m Analysis m Design m Measurement m Guidelines m Examples

8

9 Procedure Testing

10 Procedure Testing 1. Input 2. Output 3. Loop 4. Continuous 5. Workflow

11 Performance Testing

12 Performance Testing Computer System Application Security Layer InputsOutputs Test Tools Test Environment Performance Specialists Expected Load Required Level of Performance Test Cases Industry Standard Benchmarks Measured Performance

13 Security Testing

14 Summary l Introduced the BCS SIGIST SWP l Explained the work of the group l Three technique workshops l Help us to help you l Bookmark this site