- •About the Authors
- •Contents at a Glance
- •Contents
- •Introduction
- •Goal of the Book
- •How to Use this Book
- •Introduction to the .NET Framework
- •Common Language Runtime (CLR)
- •Class Library
- •Assembly
- •Versioning
- •Exceptions
- •Threads
- •Delegates
- •Summary
- •Introduction to C#
- •Variables
- •Initializing Variables
- •Variable Modifiers
- •Variable Data Types
- •Types of Variables
- •Variable Scope
- •Types of Data Type Casting
- •Arrays
- •Strings
- •Initializing Strings
- •Working with Strings
- •Statements and Expressions
- •Types of Statements
- •Expressions
- •Summary
- •Classes
- •Declaring Classes
- •Inheritance
- •Constructors
- •Destructors
- •Methods
- •Declaring a Method
- •Calling a Method
- •Passing Parameters to Methods
- •Method Modifiers
- •Overloading a Method
- •Namespaces
- •Declaring Namespaces
- •Aliases
- •Structs
- •Enumerations
- •Interfaces
- •Writing, Compiling, and Executing
- •Writing a C# Program
- •Compiling a C# Program
- •Executing a C# Program
- •Summary
- •Arrays
- •Single-Dimensional Arrays
- •Multidimensional Arrays
- •Methods in Arrays
- •Collections
- •Creating Collections
- •Working with Collections
- •Indexers
- •Boxing and Unboxing
- •Preprocessor Directives
- •Summary
- •Attributes
- •Declaring Attributes
- •Attribute Class
- •Attribute Parameters
- •Default Attributes
- •Properties
- •Declaring Properties
- •Accessors
- •Types of Properties
- •Summary
- •Introduction to Threads
- •Creating Threads
- •Aborting Threads
- •Joining Threads
- •Suspending Threads
- •Making Threads Sleep
- •Thread States
- •Thread Priorities
- •Synchronization
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Primary and Foreign Keys
- •Referential Integrity
- •Normalization
- •Designing a Database
- •Low-Level Design
- •Construction
- •Integration and Testing
- •User Acceptance Testing
- •Implementation
- •Operations and Maintenance
- •Summary
- •Creating a New Project
- •Console Application
- •Windows Applications
- •Creating a Windows Application for the Customer Maintenance Project
- •Creating an Interface for Form1
- •Creating an Interface for WorkerForm
- •Creating an Interface for CustomerForm
- •Creating an Interface for ReportsForm
- •Creating an Interface for JobDetailsForm
- •Summary
- •Performing Validations
- •Identifying the Validation Mechanism
- •Using the ErrorProvider Control
- •Handling Exceptions
- •Using the try and catch Statements
- •Using the Debug and Trace Classes
- •Using the Debugging Features of Visual Studio .NET
- •Using the Task List
- •Summary
- •Creating Form1
- •Connecting WorkerForm to the Workers Table
- •Connecting CustomerForm to the tblCustomer Table
- •Connecting the JobDetails Form
- •to the tblJobDetails Table
- •Summary
- •Introduction to the Crystal Reports Designer Tool
- •Creating the Reports Form
- •Creating Crystal Reports
- •Creating the Windows Forms Viewer Control
- •Creating the Monthly Worker Report
- •Summary
- •Introduction to Deploying a Windows Application
- •Deployment Projects Available in Visual Studio .NET
- •Deployment Project Editors
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Populating the TreeView Control
- •Displaying Employee Codes in the TreeView Control
- •Event Handling
- •Displaying Employee Details in the ListView Control
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Adding the Programming Logic to the Application
- •Adding Code to the Form Load() Method
- •Adding Code to the OK Button
- •Adding Code to the Exit Button
- •Summary
- •The Created Event
- •Adding Code to the Created Event
- •Overview of XML
- •The XmlReader Class
- •The XmlWriter Class
- •Displaying Data in an XML Document
- •Displaying an Error Message in the Event Log
- •Displaying Event Entries from Event Viewer
- •Displaying Data from the Summary.xml Document in a Message Box
- •Summary
- •Airline Profile
- •Role of a Business Manager
- •Role of a Network Administrator
- •Role of a Line-of-Business Executive
- •Project Requirements
- •Creation and Deletion of User Accounts
- •Addition of Flight Details
- •Reservations
- •Cancellations
- •Query of Status
- •Confirmation of Tickets
- •Creation of Reports
- •Launch of Frequent Flier Programs
- •Summarizing the Tasks
- •Project Design
- •Database Design
- •Web Forms Design
- •Enabling Security with the Directory Structure
- •Summary
- •Getting Started with ASP.NET
- •Prerequisites for ASP.NET Applications
- •New Features in ASP.NET
- •Types of ASP.NET Applications
- •Exploring ASP.NET Web Applications
- •Introducing Web Forms
- •Web Form Server Controls
- •Configuring ASP.NET Applications
- •Configuring Security for ASP.NET Applications
- •Deploying ASP.NET Applications
- •Creating a Sample ASP.NET Application
- •Creating a New Project
- •Adding Controls to the Project
- •Coding the Application
- •Summary
- •Creating the Database Schema
- •Creating Database Tables
- •Managing Primary Keys and Relationships
- •Viewing the Database Schema
- •Designing Application Forms
- •Standardizing the Interface of the Application
- •Common Forms in the Application
- •Forms for Network Administrators
- •Forms for Business Managers
- •Forms for Line-of-Business Executives
- •Summary
- •The Default.aspx Form
- •The Logoff.aspx Form
- •The ManageUsers.aspx Form
- •The ManageDatabases.aspx Form
- •The ChangePassword.aspx Form
- •Restricting Access to Web Forms
- •The AddFl.aspx Form
- •The RequestID.aspx Form
- •The Reports.aspx Form
- •The FreqFl.aspx Form
- •Coding the Forms for LOB Executives
- •The CreateRes.aspx Form
- •The CancelRes.aspx Form
- •The QueryStat.aspx Form
- •The ConfirmRes.aspx Form
- •Summary
- •Designing the Form
- •The View New Flights Option
- •The View Ticket Status Option
- •The View Flight Status Option
- •The Confirm Reservation Option
- •Testing the Application
- •Summary
- •Locating Errors in Programs
- •Watch Window
- •Locals Window
- •Call Stack Window
- •Autos Window
- •Command Window
- •Testing the Application
- •Summary
- •Managing the Databases
- •Backing Up the SkyShark Airlines Databases
- •Exporting Data from Databases
- •Examining Database Logs
- •Scheduling Database Maintenance Tasks
- •Managing Internet Information Server
- •Configuring IIS Error Pages
- •Managing Web Server Log Files
- •Summary
- •Authentication Mechanisms
- •Securing a Web Site with IIS and ASP.NET
- •Configuring IIS Authentication
- •Configuring Authentication in ASP.NET
- •Securing SQL Server
- •Summary
- •Deployment Scenarios
- •Deployment Editors
- •Creating a Deployment Project
- •Adding the Output of SkySharkDeploy to the Deployment Project
- •Deploying the Project to a Web Server on Another Computer
- •Summary
- •Organization Profile
- •Project Requirements
- •Querying for Information about All Books
- •Querying for Information about Books Based on Criteria
- •Ordering a Book on the Web Site
- •Project Design
- •Database Design
- •Database Schema
- •Web Forms Design
- •Flowcharts for the Web Forms Modules
- •Summary
- •Introduction to ASP.NET Web Services
- •Web Service Architecture
- •Working of a Web Service
- •Technologies Used in Web Services
- •XML in a Web Service
- •WSDL in a Web Service
- •SOAP in a Web Service
- •UDDI in a Web Service
- •Web Services in the .NET Framework
- •The Default Code Generated for a Web Service
- •Testing the SampleWebService Web Service
- •Summary
- •Creating the SearchAll() Web Method
- •Creating the SrchISBN() Web Method
- •Creating the AcceptDetails() Web Method
- •Creating the GenerateOrder() Web Method
- •Testing the Web Service
- •Securing a Web Service
- •Summary
- •Creating the Web Forms for the Bookers Paradise Web Site
- •Adding Code to the Web Forms
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Overview of Mobile Applications
- •The Microsoft Mobile Internet Toolkit
- •Overview of WAP
- •The WAP Architecture
- •Overview of WML
- •The Mobile Web Form
- •The Design of the MobileTimeRetriever Application
- •Creating the Interface for the Mobile Web Forms
- •Adding Code to the MobileTimeRetriever Application
- •Summary
- •Creating the Forms Required for the MobileCallStatus Application
- •Creating the frmLogon Form
- •Creating the frmSelectOption Form
- •Creating the frmPending Form
- •Creating the frmUnattended Form
- •Adding Code to the Submit Button in the frmLogon Form
- •Adding Code to the Query Button in the frmSelectOption Form
- •Adding Code to the Mark checked as complete Button in the frmPending Form
- •Adding Code to the Back Button in the frmPending Form
- •Adding Code to the Accept checked call(s) Button in the frmUnattended Form
- •Adding Code to the Back Button in the frmUnattended Form
- •Summary
- •What Is COM?
- •Windows DNA
- •Microsoft Transaction Server (MTS)
- •.NET Interoperability
- •COM Interoperability
- •Messaging
- •Benefits of Message Queues
- •Limitations
- •Key Messaging Terms
- •Summary
- •Pointers
- •Declaring Pointers
- •Types of Code
- •Implementing Pointers
- •Using Pointers with Managed Code
- •Working with Pointers
- •Compiling Unsafe Code
- •Summary
- •Introduction to the Languages of Visual Studio .NET
- •Visual C# .NET
- •Visual Basic .NET
- •Visual C++ .NET
- •Overview of Visual Basic .NET
- •Abstraction
- •Encapsulation
- •Inheritance
- •Polymorphism
- •Components of Visual Basic .NET
- •Variables
- •Constants
- •Operators
- •Arrays
- •Collections
- •Procedures
- •Arguments
- •Functions
- •Adding Code to the Submit Button
- •Adding Code to the Exit Button
- •Summary
- •Introduction to Visual Studio .NET IDE
- •Menu Bar
- •Toolbars
- •Visual Studio .NET IDE Windows
- •Toolbox
- •The Task List Window
- •Managing Windows
- •Customizing Visual Studio .NET IDE
- •The Options Dialog Box
- •The Customize Dialog Box
- •Summary
- •Index
PROJECT CASE STUDY AND DESIGN |
Chapter 18 |
403 |
|
|
|
|
|
Reporting flight status. On demand, line-of-business executives also report the seat availability in the business and executive classes to passengers.
Confirmation of reservation. Line-of-business executives can confirm the ticket of a passenger 72 to 24 hours before the departure of the flight. The confirmation can be carried out over telephone as well as across the reservation counters at regional offices.
Having examined the role of business executives in SkyShark Airlines, you can understand the requirements of the airline portal easily. These requirements are explained in the next section.
Project Requirements
The airline portal required by the airline should be an integrated solution that allows all business executives and customers to access data that is pertinent to their roles. Notice the inclusion of customers that I made in the preceding sentence. By enabling customers to manage their information, such as their ticket status and the confirmation status of their reservation, the airline wants to reduce the workload of its line-of-business executives and enhance customer experience.
Based on the roles of executives discussed in the previous section, you can infer that the responsibilities of the airline executives are well defined. The airline portal uses the role of these executives as a framework for imparting its functionality. Thus, the portal enables different sets of tasks for business managers, network administrators, and line-of-business executives. In this section, I list all tasks that need to be accomplished in the airline portal and also examine how these tasks will be accomplished.
Creation and Deletion of User Accounts
The procedure of creating a new user account is given in the following list:
1.A business manager decides when a new user account needs to be created and uses the online portal to send an e-mail message to the network administrator. The username and the role of the user are specified in the e-mail message.
404 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
NOTE
As a convention, the username selected by the network administrator for a new user account is the same as the Windows 2000 domain account user ID for the user.
2.Network administrators use the online portal to create a new user account. When the new account is created, an e-mail message is triggered to the user. The e-mail message specifies the username, password, and the privacy policy of the airline (as an attachment).
3.When the user logs on for the first time, it is mandatory for the user to change his or her password.
When a user is no longer required to use the airline portal, the network administrator deletes the user account from the airline portal.
Addition of Flight Details
After you add new user accounts, users can access the airline portal.The next step, after adding user accounts, is to add the details of new flights so that registered users can access the airline portal and perform reservations and cancellations.
To add new flight details, a business manager uses the following information:
Flight number
Origin and destination
Number of seats in the business and executive class
Fares for the two classes
Type of aircraft
The business manager adds the information to the airline portal, and the flight is ready to accept reservations and cancellations.
Reservations
Line-of-business executives perform reservations on flights after flight details are added by business managers. Reservation of passengers on flights is a three-step procedure, as specified following:
PROJECT CASE STUDY AND DESIGN |
Chapter 18 |
|
405 |
|
|
||||
|
|
|
|
|
1.The passenger supplies the flight number, the class, and the date of journey. The line-of-business executive uses this information to retrieve the flight status. The flight status is intimated to the passenger.
2.If the passenger wishes to continue with the reservation, the line-of- business executive accepts the name and e-mail address of the user to perform the reservation.
3.The e-mail address of the user is optional and is used to check if the customer qualifies for a frequent flier discount. If the customer qualifies for a discount, the discount is deducted from the ticket fare and the ticket is generated.
Cancellations
If a passenger wishes to cancel a ticket, the passenger approaches the line-of-busi- ness with the ticket number. The line-of-business executive cancels the ticket and refunds the fare to the passenger. The refund applicable to a customer is calculated depending upon the departure time of the flight, by using the following scheme:
If the user has not boarded the flight, as checked by the status in the confirmation of reservations, and the flight has departed, 80 percent of the fare is refunded.
If the flight has not departed, 10 dollars are subtracted from the fare and the remaining amount is refunded.
Query of Status
Passengers can query the status of their tickets as well as the status of flights. To query the status, passengers can either contact the line-of-business executives or query the information from the online portal of SkyShark Airlines. The online portal for the airline presents information about flight schedules, flight status, and ticket status. The online portal can also be used to confirm reservations. I will describe the online portal in detail later in this project.
Confirmation of Tickets
Passengers need to confirm their tickets before the departure of the flight. This practice is established to ensure that seats of passengers who decide not to travel
406 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
on the scheduled date are offered to the passengers in the waiting list. To confirm their ticket, passengers can use the options given in the following list:
Use the ticket number to confirm the ticket with the line-of-business executive, either by telephone or in person.
Use the ticket number and e-mail ID to confirm the reservation on the online portal.
Creation of Reports
Business managers can generate reports to view the performance of flights. The types of reports supported by the airline portal are specified in the following list:
Monthly flight revenue. The monthly flight revenue report retrieves the total revenue generated from all the flights in a given month. The business manager needs to select the month and year to run the report.
Flight revenue report. The flight revenue report reports the total revenue generated from a flight. To run this report, the business manager needs to specify the flight number.
Customer affinity report. The customer affinity report retrieves the customers who have flown the flight maximum number of times or who have paid the maximum fare. To run this report, the business manager needs to specify how many customer records the application should retrieve. This report is used to launch the frequent fliers program.
Total revenue report. The total revenue report is used to retrieve the total revenue that has been generated by the airline since a given month and year.
Launch of Frequent Flier Programs
Business managers are responsible for launching frequent flier programs that are used for giving discounts to customers who frequently fly with the airline. Customers are given discounts if they specify either of the parameters specified in the following list:
Frequency of flight. Customers who frequently fly the airline are given a discount of a certain percent on their ticket fare. The business managers determine the frequency of flight and the discount percentage.