Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
I have a question regarding the Database. In a "real world" application, if I were to book flights, I would need a second database to hold information such as a passenger's name / address / etc. This information is obviously not in the db.db file. So, should I create a *NEW* database to hold customer information? Or is that going way beyond the scope of the assignment? In addition, the file db.db only has a field "available seats". Is that the number of seats left, or the total allowable? Don't we need to know the maximum number of seats available on each flight as well as the number of seats that have been booked?
I think holding Passenger information is over the requirements and not needed, and available seat means how many seats are left that can be booked, you don't need to know the capacity of the flight. Mark