King Saud University College of Computer and Information Sciences Department of Information Technology CAP312 – Software Engineering II Second Semester 1432/1433 H Tutorial #2 Architectural Design Q1. Suggest and draw the architecture diagram of the following systems: An automated ticket-issuing system used by passengers at a railway station The most appropriate architectural structural model would be a centralized model with a shared repository for route and pricing information. Storing all the information in a central location allows for changes to be immediately available to all ticket machines. It's reasonable to assume that there are other subsystems used for administrative functions (such as updating the data in the repository). The centralized system also allows global information (e.g., ticket sales) and route use to be collected and processed. Given the distributed nature of this application, one might be led to consider a client/server architecture. If there is only one server (the repository), the actual structure would be the same (as the repository structure), regardless of what you call it. A computer-controlled video conferencing system which allows video, audio and computer data to be visible to several participants at the same time The most appropriate structure here is a client-server model. The client application would be required to do considerable processing to handle the complex multimedia data fed to it from the server(s). Q2. Using the basic model of an information system, as presented below, suggest the components that might be part of an information system that allows users to view information about flights arriving and departing from a particular airport. Students should consider the levels in the information system and should identify components that might be included at each level. Examples of these components might be: Level 1 (Database level): Flight database; Flight status database; Airport information; Level 2: (Information retrieval level): Status management; Flight management; Search; Level 3: (User interaction level): Authentication and validation; session management; forms management Level 4 (User interface): browser