Professional Documents
Culture Documents
SKYTECH SYSTEMS
Contents
SOFTWARE TESTING 2 / 50
SKYTECH SYSTEMS
Contents
• Requirement Management
• Configuration Management
• Software Testing Fundamentals
• Testing Policy Vs Quality Policy
• Testing Economics and Testing Cost
• Testing Levels
• Testing Techniques
SOFTWARE TESTING 3 / 50
SKYTECH SYSTEMS
Contents
SOFTWARE TESTING 4 / 50
SKYTECH SYSTEMS
Software Testing
STATIC DYNAMIC
Logical Errors
SOFTWARE TESTING 5 / 50
SKYTECH SYSTEMS
• Testing
A Process of evaluating a particular
product to determine whether the product contain
any defects
• Software Testing
SOFTWARE TESTING 6 / 50
SKYTECH SYSTEMS
Error Free
Efficient
Secured
Flexible
SOFTWARE TESTING 7 / 50
SKYTECH SYSTEMS
QUALITY PRINCIPLES
Quality is defined as meeting the Customer’s
requirements in the First time and Every time.
SOFTWARE TESTING 8 / 50
SKYTECH SYSTEMS
Software Quality
• Critical Quality • Other Attributes
– Completeness
Attributes – Compatibility
– Portability
– Maintainability – Internationalization
– – Understandability
Dependability
– Scalability
– Efficiency
– Robustness
– Usability – Testability
– Reusability
– Customizability
SOFTWARE TESTING 9 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 10 / 50
SKYTECH SYSTEMS
Why Quality?
SOFTWARE TESTING 11 / 50
SKYTECH SYSTEMS
Cost of Quality
• The three categories of costs associated with
producing quality products are
Quality Assurance
Vs
Quality Control
• Quality Assurance
- process oriented
(Software development)
- Defect prevention
(Identify & Rectify)
• Quality Control
- Product Oriented (quality of the entire
product is checked or tested)
SOFTWARE TESTING - Defect detection 13 / 50
SKYTECH SYSTEMS
Software Process
A particular method of doing some
thing, generally involving a number of
steps or operations is a process.
SOFTWARE TESTING 14 / 50
SKYTECH SYSTEMS
Software Process
• Process – Projects – Products
A software process specifies a method of
developing software.
A software project, on the other hand, is a
development project in which a software
process is used.
A Software product is the outcome of a
software project.
SOFTWARE TESTING 15 / 50
SKYTECH SYSTEMS
ACT DO
CHECK
Testing & Evaluating
SOFTWARE TESTING 16 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 17 / 50
SKYTECH SYSTEMS
SDLC
(SOFTWARE DEVELOPMENT
LIFE CYCLE)
SOFTWARE TESTING 18 / 50
SKYTECH SYSTEMS
Agenda
• Team Organization Deliverable Turn-in
– Project Assignments to be posted on the web-
site
• Introduction to Software Development
Activities
• Survey of Lifecycle Models
SOFTWARE TESTING 19 / 50
SKYTECH SYSTEMS
Software Engineering
• Layered Technology
– Key Process Areas
Tools
Methods
Process
Quality
SOFTWARE TESTING 20 / 50
SKYTECH SYSTEMS
Process Principles
• Prescribes all major activities
• Uses resources, within a set of constraints, to
produce intermediate and final products
• May be composed of sub-processes
• Each activity has entry and exit criteria
• Activities are organized in a sequence
• Has a set of guiding principles to explain goals
• Constraints may apply to activity, resource or
product
SOFTWARE TESTING 22 / 50
SKYTECH SYSTEMS
Requirement Analysis
Design
Development
Testing
Implementation
Maintenance
SOFTWARE TESTING 23 / 50
SKYTECH SYSTEMS
Requirement Analysis
• Study done by organization against customer’s
requirement is documented as SRAS( software
requirement analysis specification)
Design Process
• Decompose entire project into units / modules and
prepare dataflow diagram and communication.
• CDD(Comprehensive Design Document)
= HCL + LLD
Design Process
Low Level Design
High Level Design
LLD
HCD
SOFTWARE TESTING 25 / 50
SKYTECH SYSTEMS
HLD
• High-Level Design (system Design)
SOFTWARE TESTING 26 / 50
SKYTECH SYSTEMS
LLD
• Low Level Design (Detailed Design)
SOFTWARE TESTING 27 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 28 / 50
SKYTECH SYSTEMS
Testing
• Unit testing
• STATIC(Reviewing)
• Integration testing • DYNAMIC (Execution)
• System testing
SOFTWARE TESTING 29 / 50
SKYTECH SYSTEMS
Integration testing
SOFTWARE TESTING 30 / 50
SKYTECH SYSTEMS
System Testing
SOFTWARE TESTING 31 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 32 / 50
SKYTECH SYSTEMS
Project Management
• Project Management is nothing but
organising, Planning,ans scheduling
software projects.
– Project staffing
– Project planning
– Project scheduling
– Project monitoring
SOFTWARE TESTING 33 / 50
SKYTECH SYSTEMS
Risk Management
Software Risks
SOFTWARE TESTING 34 / 50
SKYTECH SYSTEMS
Requirements Management
• Requirements management is managing changes
in the evolving software in a cost effective
manner. Changes may come externally or
internally.
• External changes may be due to
problem,customer, environment.
• Internal changes may be due to requirements,
design, implementation, testing, maintenance
SOFTWARE TESTING 35 / 50
SKYTECH SYSTEMS
Configuration Management
• Standards and procedures for managing changes in
an evolving software product is configuration
management.
• New versions of software systems are created as
they change for different machines/OS, offering
different functionality.
• Software systems are sometimes called baselines
as they are a starting point for further
development.
SOFTWARE TESTING 36 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 37 / 50
SKYTECH SYSTEMS
version/variants/releases
• Version : An instance of a system, which is
functionally distinct in some way from
other system instances.
• Variant: An instance of a system, which is
functionally identical but non-functionally
distinct from other instances of a system.
• Release : An instance of a system, which is
distributed to users outside of the
development team.
SOFTWARE TESTING 38 / 50
SKYTECH SYSTEMS
V 1.1b V 1.1.1
V 1.1a
SOFTWARE TESTING 39 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 40 / 50
SKYTECH SYSTEMS
STF
• What is Defects ?
– The purpose of testing is to find defects. A
defect is a variance from a desired product
attribute. Two categories of defects are
2. Variance from product specifications.
SOFTWARE TESTING 41 / 50
SKYTECH SYSTEMS
Defects
• 1. Wrong : The specifications have been implemented
incorrectly. This defect is a variance from customer / user
specification. (correctly mentioned in specification but
wrongly implemented)
• 2. Missing : A specified or wanted requirement is not in the
built product. This can be a variance from specification, an
indication that the specification was not implemented.
( given in specification but missed out in application)
• 3. Extra : A requirement incorporated into the product that
was not specified. This is always a variance from
specifications, but may the user of the product desire an
attribute. (any thing that dissatisfies)
SOFTWARE TESTING 42 / 50
SKYTECH SYSTEMS
Test case
• Set of procedures written by a tester which
execute in our system to find defect.
SOFTWARE TESTING 43 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 44 / 50
SKYTECH SYSTEMS
TESTING LEVELS
• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing
SOFTWARE TESTING 45 / 50
SKYTECH SYSTEMS
Unit Testing
• Unit testing is a testing in which the
individual unit of the software are tested in
isolation from other parts of a program.
Advantage :
• To catch the defects that occurs at the early
stage of software development.
• To minimize the ration of defects before
moving to next level
SOFTWARE TESTING 46 / 50
SKYTECH SYSTEMS
Integration Testing
• Integration testing refers to the testing in
which software units of an application
combined and tested for a communication
interfaces between them.
SOFTWARE TESTING 47 / 50
SKYTECH SYSTEMS
Module - 6 Module - 2
System
Module - 5 Module - 3
Module - 4
SOFTWARE TESTING 48 / 50
SKYTECH SYSTEMS
SOFTWARE TESTING 49 / 50
SKYTECH SYSTEMS
Integration
• Bottom-up Integration testing :
In bottom up integration, all modules are added
or combined from lower level hierarchy to
higher level hierarchy I.e., the lower level
model is tested in isolation first, then the next
set of higher level modules are tested with the
previously tested lower modules.
• Worker modules are grouped into builds and
integrated.
SOFTWARE TESTING 50 / 50