09 - Transition Phase

Question 1

What are the objectives of the Transition Phase?

Answer 1

Ensure finished application is acceptable

• Must solve/meet business objectives
• Be usable by business community
• Must perform optimally
• Must be maintainable

Training of End Users

Question 2

What tests are conducted in Transition?

Answer 2

• Quick/Smoke Test
• Compliance Test
• Boundary & Exception Test
• Integration Test
• System Test
• Performance Test
• User Acceptance Testing

Question 3

Describe a Smoke Test

Answer 3

• A quick run-through of basic application functionality right after migration
• Briefly tests enough elements to show that the solution is essentially operable

Question 4

Describe a Compliance Test

Answer 4

• Ensures application quality
• Displays rules in variance of Guardrails and best practices

Question 5

Describe Boundary and Exception Test

Answer 5

Test extreme values to ensure all types of scenarios are covered

• Use cases should be used to create test scripts
• Should not be confused with checking for data entry errors

Exception test example: what happens when an interface is unavailable?

Question 6

Describe Integration Test

Answer 6

Tests all integration points in the application

Question 7

Describe System Test

Answer 7

A load test (business load) ensuring you actually testing against the actual business requirements

Question 8

Describe Performance Test

Answer 8

Ensure application is performing optimally at production loads

Question 9

What two tools are available to assist with Performance Testing?

Answer 9

Performance Analyzer (PAL)

• Readings from each test compared to baseline or typical expectations; analyzed for degradations after changes have been made
• Identifies possible bottlenecks; can be used at any time

Performance Profiler

• Provides more performance details than PAL
• Requires substantial overhead – should never be used in production

Question 10

Describe User Acceptance Testing

Answer 10

Test scripts are run that mimic real life test cases with both expected and extreme test scenarios

Question 11

What is the Autonomic Even Services Tool (AES)?

Answer 11

• In an additional Framework available for purchase
• Monitors the Web application
• Creates cases to be routed, assigned and worked on threshold violations

Question 12

What are the Roles in Transition?

Answer 12

• Business Sponsor
• Project Manager
• Business Architect
• SME’s
• DBA
• System Architect
• Testing Resources
• IT Resources

Question 13

What are the objectives of Go-Live?

Answer 13

• To address go-live tasks and application maintenance and support.
• Takes the final release candidate in Transition, supports its launch, and continues to maintain enhancements, fixes, and change requests by IT and business users

Question 14

What are the key activities in Go-Live?

Answer 14

• Data migration into production
• Application deployment into production
• Go-Live user support activities

Question 15

What are the key deliverables from Go-Live?

Answer 15

• Fully deployed Day-1 data Migration into production
• Fully deployed application into production
• Production support Plan/Documentation