DIALOGUE CONTROL

In any commattication there arc Iwo types of user ehalogu es. These ale long session•osi• en led transactions and shun transaction. Going through a monolithic document page b) page can be considered as a sessio•noriented transaction. Going 10 a particular page directly through art indes can be considered as a short transaction. Selection of the trans action mode will depend on the type of device we use. A session may be helpful in case senices offered through computen with large screens and MOWS, for desires watt limited inputioutput like ..SNIS for instance, short transactions may be desired. Let us consider an example of bank balance enquiry over the Internet. In ease of Interne, banking through desktop computer, the user has to go through the following minimum dialogues: I. Falter the UM. or the bank site. 2. Enter the account m u mberipx5 sword and Login into the application. 3. Select the balance enquiry dialogue and see the balance. 4. Logout from the internee banking. The dialogue above is an example of session-oriented trantarben. Using short a:attrac-tion, the same Objective' can be met through one single dialogue. In short transaction user sends a SIAS message, say 'alb:al% to the system and receives the information on balance. The appRICation se-mkt* 4/ the 5 dialogue steps as one dialogue. In this C134 many steps like authentication, selection of transactions need to be performed in smarter ways. For example, the user authentication will be done through the mobile number of the user. It can be assumed that mobile devices are personaL therefore, authenticating the mobile phone irnplies authenticating the user account.