You are on page 1of 1

Solution Assessment and Validation

This course presents the building blocks of Topics


assessing solutions both for process Part 1
improvement and IT-enabled solutions. This I. Rationale in Measuring Solution Effectiveness
course is designed in two parts, i.e., assessing II. Techniques in Measuring Solutions
business value of a solution based on monetary III. Activity-Based Costing/Management (ABC/M)
returns and assessing the effectiveness of a IV.Cost of Poor Quality Techniques
software/system solution.
Part 2
The first part of the course covers quantifying I. Structured Testing
success of a solution into monetary terms. It shall a) The Test Processes
include the savings declaration of projects and b) Inputs t Acceptance Test Planning
the measuring techniques to quantify c) Roles in Software Acceptance Testing
improvement value. This is suitable for d) Levels of Testing
organizations who run kaizen, reengineering, e) Testing Types
software development, lean or six sigma projects. II. Test Design
a) Test Case
b) Fundamental Testing Strategies
The second part of the course discusses the
c) Deriving Test Cases from Use Cases
processes and deliverables of user testing. As
d) Deriving Test Cases for Performance Tests
business analyst, one of the primary e) Deriving Test Cases for Security/Access
responsibilities is to aid the customers in their Tests
acceptance testing prior to system/software f) Deriving Test Cases for Product Acceptance
acceptance or sign-off. Test
III.Test Case Design Approaches/Techniques
Training Objectives a) Validation Methods
At the end of the course, the participants will be b) Equivalence Partitioning
able to: c) Boundary Value (BV) Analysis
1. Describe Cost of Poor Quality Calculation IV.Test Reporting
Techniques and Activity-based
Costing/Management.
2. Identify tangible and intangible benefits of Duration 2 day(s)
solutions.
3. Draft acceptance test plan.
4. Draft test cases based on functional and non-
functional requirements.
5. Design test cases including test scenarios and
expected results.
6. Use IEEE Std 829 in writing acceptance test
plans.
7. Estimate testing costs and schedules using
proven techniques.

You might also like