09 - Transition Phase Flashcards
What are the objectives of the Transition Phase?
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
What tests are conducted in Transition?
- Quick/Smoke Test
- Compliance Test
- Boundary & Exception Test
- Integration Test
- System Test
- Performance Test
- User Acceptance Testing
Describe a Smoke Test
- A quick run-through of basic application functionality right after migration
- Briefly tests enough elements to show that the solution is essentially operable
Describe a Compliance Test
- Ensures application quality
- Displays rules in variance of Guardrails and best practices
Describe Boundary and Exception Test
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?
Describe Integration Test
Tests all integration points in the application
Describe System Test
A load test (business load) ensuring you actually testing against the actual business requirements
Describe Performance Test
Ensure application is performing optimally at production loads
What two tools are available to assist with Performance Testing?
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
Describe User Acceptance Testing
Test scripts are run that mimic real life test cases with both expected and extreme test scenarios
What is the Autonomic Even Services Tool (AES)?
- In an additional Framework available for purchase
- Monitors the Web application
- Creates cases to be routed, assigned and worked on threshold violations
What are the Roles in Transition?
- Business Sponsor
- Project Manager
- Business Architect
- SME’s
- DBA
- System Architect
- Testing Resources
- IT Resources
What are the objectives of Go-Live?
- 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
What are the key activities in Go-Live?
- Data migration into production
- Application deployment into production
- Go-Live user support activities
What are the key deliverables from Go-Live?
- Fully deployed Day-1 data Migration into production
- Fully deployed application into production
- Production support Plan/Documentation
