This preview shows page 1. Sign up to view the full content.
Unformatted text preview: er, may have lost as
much as US$50 million in second-quarter ticket revenues because of a
computer software problem in its passenger-reservation system.
The problem, which has been corrected, was discovered when a review of secondquarter performance revealed lower-than-expected load factors.
The airline said its Sabre reservation system indicated that aircraft had sold out of
discount fares when such seats were still available.
Certain classes of discount fares were prematurely closed and passengers requesting
those fares referred to other airlines. ''We gave that business away,'' an airline official
– Break It! Now, not later
In as many ways as possible Best testers: Users, Spets, Help Desk Best tests:
– Contextual: In user’s environment, by user
Broad: hardware, software, telecom
Abnormal, creative uses (by Help Desk folks) Testing--Process
1. Plan Test
4. Document Test Analysis 2. Code
3. Run Test Phase: Test Plan, Buy Hardware Design Phase: Detailed Test Plan Coding: Inspection, Syntax checking, Desk
Checking, Walkthrough, Unit/Integration/
System Tests Testing Phase: Acceptance Testing Testing--Types
Static Automated Code Inspection • Syntax Checking
Syntax • Walkthroughs
• Desk Checking
Desk • Unit Testing
• System Testing
• Stub testing
• User Acceptance
Tests (α , β )
Tests (no code execute) Dynamic
(code executes) System Installation Strategies
System Direct Parallel Single location Phased System Installation Strategies
System Direct—abrupt, cold turkey Parallel—safe: old and new co-exist Single location—pilot approach by branch Phased—gradual by module Installation St...
View Full Document
This note was uploaded on 11/17/2011 for the course ITM 311 taught by Professor Harrisonmcknight during the Fall '10 term at Michigan State University.
- Fall '10