Exercise two

Jiangbo Cheng 20043051 Jing Sun 20034243

Entity-Relationship diagrams
* Refund related user refund type * *

to 1

Account related user refund type

from 1

Payment related user payment type

1
* Airport company

1
* Seat canceling Time date

to 1 where canceled

from 1 where booked

*

1
* Seat booking time date trip number

1 0..1 1

Flight info. searching arrive time departure time available seats airplane type

1..*
Route

1 1
Seat *

1
date of validity class price airplane type return or single

Dictionary Seat: entity, the seat on an indicated flight, where only one passenger could sit in once a time. Arrive time: state, when flight lands on ground. Departure time: state, the time flight closes the doors. Refund: entity, when the user canceled a booking, the booking system pays the money back to the users registered bank account. Payment: entity, the user clicks the Yes button to confirm paying for the booking. Account: entity, the users personal information including full name, birthday, email address, postal address Seat canceling: event, the user cancels one or more seat through OATS before one week when the flight departure Seat booking: event, the user books one or more seat through OATS before two hours when the flight departure

Validation 1. Consistency We used informal analysis and inspection of the ERD to ensure it is consistent. 2. Checking validity by elementary Sentences To check whether the ERD represents our subject domain, we translated the diagram into simple sentences and ask domain specialists whether these sentences are true. The subject domain model of our system can be translated into the following sentences: A flight searching can result any number of seat booking A seat booking requires one payment. A payment needs to be accomplished by one account An account is able to do any number of payment A payment may be applicable to any number of seat booking A seat booking can be done by any number of flight searching A seat canceling results one refund A refund needs one account An account may be applicable to any number of refund A refund is only available to one seat canceling A seat booking can book any number of seats A seat needs only one booking A seat is applicable to one seat canceling

A seat canceling can cancel one seat We can see this model correctly represents the subject domain. 3. Checking validity by Snapshots Seat (s, Sep 10) Route Return Copenhagen-Paris (s, Sep 10) Return Copenhagen-Paris The table shows a return seat from Copenhagen to Paris with its data of validity, containing book date and cancel date. 4. Identification The ERD diagram clarifies what a seat, a seat booking, a seat canceling, a payment, a refund are, but does not mention passengers. These entities are not part of the subject domain because there is no way, at least in our case study, that OATS can know their identity. In our case study, the OATS does not authenticate them and so passengers are not part of the subject domain of the OATS. The OATS communicates with passengers, but not about them. According to these four method on validation, we can actually evaluate the ERD is a very good correspondence between subject domain, and it is complete. Aug 20 Aug 30 Book Aug 20 cancel None