Testing Strategies - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Testing Strategies

Description:

Testing Strategies Agenda Introductions Who is Paradigm? Types of Testing Post Implementation Patches Enhancements or Additions Upgrades Why? – PowerPoint PPT presentation

Number of Views:56
Avg rating:3.0/5.0
Slides: 17
Provided by: mgr137
Category:

less

Transcript and Presenter's Notes

Title: Testing Strategies


1
Testing Strategies
2
Agenda
  • Introductions
  • Who is Paradigm?
  • Types of Testing Post Implementation
  • Patches
  • Enhancements or Additions
  • Upgrades
  • Why?
  • What?
  • How?
  • When?
  • Where?
  • Who?

3
Introductions
  • Barb Bliznak
  • Managing Director
  • 281-744-9808 cell
  • 281-213-9612 home office
  • bbliznak_at_paradigm-erp.com
  • Lori Waters
  • Client Services Manager
  • 724-873-9001 office
  • lwaters_at_paradigm-erp.com

4
Mission Statement
  • To focus and commit to our customers success.
    Furthermore, to turn every engagement into a long
    term partnership with our customers.

5
History
  • Founded in 1999
  • Merger of HR and Financial/Supply chain
    integrators to provide end to end ERP integration
  • Staff approaching 80 consultants (full time and
    dedicated contractors)
  • Certified Lawson Partner
  • Full Implementations
  • Upgrades (9.0 certified)
  • Custom Support and Training

6
History (cont.)
  • Contracted by Lawson directly for
  • Management of complex integrations
  • Overflow
  • Turn around
  • Client Base
  • 25 million dollar School supply business to an
    international, multi-billion dollar retailer

7
Some of our clients
8
Why?
  • Patches
  • Individual/MSP/ESP
  • Enhancements or Additions
  • Processes
  • Technology
  • Upgrades
  • Cyclic
  • Full Upgrades

9
What?
  • Patches
  • Regression
  • Affected programs (per patch notes)
  • Critical Activities within those programs
  • Issue Resolution (why the patch was installed in
    the 1st place)

10
What?
  • Enhancements or Additions
  • Processes
  • Added or deleted functionality
  • Technology
  • Peripheral and/or integrated modules (such as the
    addition of AM would require GL, AP, AC etc.
    testing for the critical activities)

11
What?
  • Upgrades
  • UAT
  • Fully integrated testing on affected modules
    including RICE elements (Reports, Interfaces,
    Conversion, Enhancements)
  • Stress/Performance
  • Transaction and processes executed simultaneously
    to stress software, hardware and the network to
    validate peak performance configurations

12
How?
  • Testing
  • Plan
  • Schedule
  • Communicate
  • Execute
  • Migration
  • Plan
  • Schedule
  • Communicate
  • Deploy
  • Assess

13
When?
  • Depends?

14
Where?
  • Anywhere BUT Production

15
Who?
  • Functional Users
  • IT
  • Audit

16
Any Questions ???
Write a Comment
User Comments (0)
About PowerShow.com