DIA: Emotional Baggage by Matt Reynolds

Introduction In 1992, Denver sought to build a world-class connector airport. Doing this required bags to move faster than any other airport. And a baggage system like no other.

Stakeholders Passengers: Bags in the right place at the right time. Airlines: The most bags in the right place at the right time. And, cost. Airport: Schedule, cost, scope.

Functional Requirements Move bags between landside and aircraft or between two aircraft. Easy right?

Functional Requirements Consider constraints: 1. Integrate with other processes (fueling, catering, passengers)

Functional Requirements Consider constraints: 1. Input from multiple airline ticketing systems.

Non-Functional Requirements Efficiency: Airlines and passengers want bags to move fast. Capacity: Airlines and the Airport want the system to move as many bags as possible.

Non-Functional Requirements Reliability: Passengers want bags to make it to the right place at the right time. Quality: Passengers don’t want bags to be abused.

Schedule & Budget Schedule: Two years. Budget: Design, implement and build for $190 MM. Put another way: $250,000/day in cost flow.

Results The project is literally a case study in failure. 2 years over schedule $100 million over budget

Themes for Analysis 1.Indicators for trouble. 1.Failures in requirements elicitation and elaboration. 2.Models that capture failure.