Trips-R-You Web-based Flight Booking Case Study

Featured
Sep 29, 2019
9619 Views
1 Comments
26 Likes

Case Study Purpose

The purpose of the Trips-R-You Flight Booking Case Study is to provide an integrated, end-to-end set of requirement examples. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. This case study, and associated artefacts, use the more traditional business terms Goals, High-level
Requirements (HLRs), and Detailed Requirements. Only functional requirements are addressed, and only within the context of a project chartered to deliver an IT-based solution.

The requirement examples included in this case study illustrate concepts presented in the
Requirements in Context series of articles, originally published in BATimes.com in 2016, and the Well-defined Data series, also published in BATimes.com, in 2018. The 2016 series has been updated by the author, and re-published in ModernAnalyst.com.

The following are links to the updated Requirements in Context series:

NOTE: The series would ideally be read in sequence, with subsequent articles building on concepts presented in prior articles. The last article includes a series summary and ‘take-away’ points.
NOTE: The series would ideally be read in sequence, with subsequent articles building on concepts presented in prior articles. The last article includes a series summary and ‘take-away’ points.

About the Author

The author of the above articles, and this case study, is Dan Tasker. He has recently retired after a career in IT that began in 1970. He spent his first 10 years working as a developer (called ‘programmer’ back then) in the United States and Canada. This was followed by two years teaching computer programming, database design, and data modelling. The remainder of his career was spent as a business analyst, in Canada, Australia, and New Zealand. Engaged sometimes as an employee and others on contract, he worked in a total of 11 industries and sectors, including utilities, transportation, clothing, shipping, government, financial services, and education. Some of the organizations he was involved with developed in-house software solutions, others were software solution vendors, and two were going through the process of acquiring a software solution from vendors.

About the Case Study

The case study involves a fictitious organisation — the Trips-R-You Travel Agency. The study deals with the requirements phase of an equally fictitious project, established to deliver a web-based customer self-service flight booking capability – often referred to as an Airline Reservation System.

The case study is divided into three sections, based on the three levels of requirements. The first section introduces the organization and a problem it faces. A goal is set that is intended to eliminate the problem, and a business case is commissioned to examine potential solutions.

The second section sees a project initiated to deliver the solution recommended by the business case. That project’s scope is shown, and how it leads to high-level requirements for the project.

The third section takes example HLRs to the detail level – one HLR involving each of the following functional capability types:

  • User Interface
  • Report
  • Data Import
  • Data Export
  • Automated Function

To support capturing the details involved in each of the above capability types, type-specific specification tools are utilized.

Section 3 begins by presenting one additional tool - a Data Dictionary. As the detail for a given HLR is discussed, the data-specific business needs involved are captured using this tool. The idea is to add entries about record types and fields (i.e. entities and attributes) the first time their need is discussed (e.g. an HLR for a specific screen or report). Once captured, those data-specific details are available for reference when those needs come up again, as they will, during discussions involving other HLRs. The detail in the data dictionary is shown to support a transition requirement for a new or updated database schema.

Like this article:
  26 members liked this article
Featured
Sep 29, 2019
9619 Views
1 Comments
26 Likes

COMMENTS

mail2rrmenon@gmail.com posted on Tuesday, February 25, 2020 3:39 PM
I have read few BA books and have worked as a BA. This work is serious serious study matter and should not be rushed through. I hope this material will be taught in BS (CS, MIS) courses in schools so as to equip software engineers reaching the market with deep technical skills and an appreciation of the criticality of Design and Development phase. Thanks to Dan Tasker for teaching us this complex topic in a manner that is fairly easy to consume and retain. Most grateful!
Only registered users may post comments.






Latest Articles

Requirements Life Cycle Management with Azure DevOps
Jul 05, 2020
0 Comments
Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stake...





Copyright 2006-2020 by Modern Analyst Media LLC