1. Introduction2. The Current System2.1. Description:2.2. Problems:2.3. Problem Scope and Solution:3. Software Architecture3.1. Alternatives:3.1.1. Repository Based Architecture:3.1.2. Client Server Architecture:a) Remote Procedure Call (RPC)b) Remote Data Access (RDA)c) Queued Message Processing3.1.2.1. Two-Tier Client Server Architecture:3.1.2.2. Three-Tier Client Server Architecture:3.2.1. Comparison between Two-Tier and Three-Tier Architectures:3.2.1.1. Criteria:b) Component Upgradeability: How easy will it be to upgrade a component in the system? (Easy, Difficult)3.2.1.2. Results: a) Development Time: Developing the application using a three-tier model will take slightly longer than using a two-tier model. The three-tier model requires that more care be placed on specifying communication protocols between th3.2.1.2. Results: a) Development Time: Developing the application using a three-tier model will take slightly longer than using a two-tier model. The three-tier model requires that more care be placed on specifying communication protocols between th3.2. Recommendation:4. Global Architecture Design4.1. Global Architecture Overview:4.2. Distribution Issues:4.3. Process Cycles:4.4. Data Distribution:4.5. Process Distribution:5. Selections5.1. Hardware Classes:5.2. Hardware Selection:5.2.1. Database Server Selection Criteria:5.2.2. Database Server Recommendation:5.2.3. Client/Workstation Node Recommendation:5.3. Software:5.3.1. Database Server Operating System:5.3.2. Client/Workstation Systems:5.3.3. Database:5.3.3.1. Overview:5.3.3.1.1. IBM DB2:5.3.3.1.2. Oracle:5.3.3.1.3. Microsoft SQL Server:5.3.3.1.4. Microsoft Access:5.3.3.2. Recommendation:5.3.4. Programming Language:5.3.4.1. Overview:5.3.4.1.1. Microsoft Visual Basic:5.3.4.1.2. Microsoft Visual J++:5.3.4.1.3. Microsoft Visual C++:5.3.4.1.4. Microsoft Visual Basic & Visual C++:5.3.4.2. Recommendation:5.4. Network5.4.1. Type:5.4.2. Network Interface Cards:5.4.3. Connectivity:5.4.3.1. Overview:5.4.3.1.1. Workgroup Hub:5.4.3.1.2. Workgroup Switch:5.4.3.1.3. Router:5.4.3.2. Recommendation:5.4.4. Network Wiring:6. Input/Output Procedures:6.1. System Modules:6.1.1. Administration Module:6.1.1.1. Add Employee:6.1.1.2. Add Supplier:6.1.1.3. Add Flight:6.1.2. Financial/Reports Module:6.1.2.1. Pay Supplier:6.1.2.2. View Financial Reports:6.1.3. Booking Module:6.1.3.1. Create New Booking:6.1.3.2. Cancel Booking:6.1.3.3. Add Flight to Booking:6.1.3.4. Add Hotel Reservation to Booking:6.1.3.5. Add Car Rental to Booking:6.1.3.6. Add Customer Account:6.1.3.7. Look Up Customer Account:6.2. Security7. Database Design:7.1. E-R Diagram:7.1.1. E-R Diagram Optimization Overview:a) Analysis of Redundanciesb) Removing Generalizations7.1.2. Database Schema:7.1.2.1. Entities:7.1.2.2. Relationships:8. Interface Design8.1. Designing the Interface:9. ConclusionAppendix A1: Repository Based Software ArchitectureAppendix A2: Two-Tier Client Server ArchitectureAppendix A3: Three-Tier Client Server ArchitectureAppendix B1: Server ComparisonAppendix B2: Client System ConfigurationAppendix C: Database ComparisonAppendix D1: ACID Compliant DatabaseAppendix D2: Relational Schema using Normal Formsa) First Normal Form (1NF): A relational schema is in this form if it does not include any multiple valued attributes or composite attributes.b) Second Normal Form (2NF): A relational schema is in this form if it is in 1NF and all non-key attributes depend on all elements of its key, rather than a subset.c) Third Normal Form (3NF): A relational schema is in this form if it is in 2NF and none of its non-key attributes depends on any other non-key attribute.Appendix E1: Database Cost ModelAccesses:Appendix E2: Cases of RedundancyCost Comparison:Results:Appendix F1: Initial E-R DiagramAppendix F2: Optimized E-R Diagram (Tables in Database)Appendix F3: E-R Data DictionaryAppendix G1: Revised Use Case DiagramAppendix G2: Use Case Diagram Data DictionaryAppendix H1: Revised Class DiagramAppendix H2: Class Diagram Data DictionaryAppendix I1: State Diagram - Add Hotel Reservation To BookingAppendix I2: State Diagram – Add Flight to DatabaseAppendix J: Sequence Diagram – Generate Supplier ReportAppendix K: Collaboration Diagram – Creating a New BookingAppendix L: Characteristics of a Good Interfacea) Affordances:b) Mapping:c) Feedback:d) Mental Model:e) Forcing Functions:f) Automatic Learning:Appendix M1: User Interface – Main ProgramAutomatic Learning: When the program is started for the first time, no windows are shown, however any windows that are still on screen when closing the program, will appear in the exact same location on the next loading of the program, providing a type oAffordances: The main interface has very little clutter which makes it easy to find functions, also the application uses icons and menus standard to many Windows based programs.Mapping: The menus are appropriately labelled to help the user find the action they want to perform quickly. If the user wants to perform a fast search, they use the Query menu. If they want to manage the flights table, they go to Activities>Flights.Appendix M2: User Interface – Flights WindowAffordances: The form uses standard windows components, which most users are very comfortable with using.Mapping: All the buttons have clear and simple icons which explain exactly what they do. The navigation buttons have arrows, the insert button has a picture of a record, the delete has an X. Most people, through their experiences with other programs aForcing Functions: Depending on which record the user is currently looking at, the navigation buttons in the top left hand corner are active or inactive. For example, when the user is on the first record the first two buttons (which go to previous recorMental Model: This form provides two views of the data. Some users prefer to view the data in tables, while others prefer to only see one record at a time. The form layout provides excellent mental models of what the system is doing for different typesAppendix M3: User Interface – Querying Database/Sorting/FilteringForcing Functions: The sorting fields in the Sort dialog are greyed out until the user chooses the number of fields they want to sort by on the right hand side. Only one of these buttons
View Full Document
Unlocking...