Conversation (dialog) between the system and user to book flight (The user first select the flight he/ she want then fill contact information after that he/she will fill the information of each passenger here I chose 2 adults then will proceeds to the payment information) Dialogs and Storyboards After identifying all required dialogs, the designers must document the dialogs Many options exist; there are no de facto standards. One approach is to list the key steps followed for the dialog with a written description of what the user and computer do at each step. The format for writing these steps can follow the activity diagram described in Chapter 2 or the use case description format in Chapter 4 or it can be more free form. Designers can also document dialog designs by writing out how the user and system might interact if they were two people engaged in conversation. Sometimes, the designer can go right from the dialog to sketching a series of screens that make the design more visible. Consider the Check out shopping cart use case for the RMCSMS. A dialog between the system and user might follow this pattern: SYSTEM: USER: SYSTEM: USER: SYSTEME USER: What would you like to do? I'd like to check out. Okay. What is your e-mail address or account number? My e-mail address is nwells22@gmail.com. Fine. You are Nancy Wells at 1122 Silicon Avenue. Correct? es