Sunteți pe pagina 1din 47

A Report ON INDIAN RAILWAY (Online ticket reservation) Submitted in partial fulfillment for the degree of Bachelor of Technology IN Computer

Science & Engineering GVSET Guided By: Mr. Kamlesh lakhwani (Faculty of gyan vihar university) Submitted By: Ashish vyas 23 Ayush gupta 26 Computer Science A-1 iv sem Gyan vihar ,jaipur GYAN VIHAR SCHOOL OF ENGINEERING AND TECHNOLOGY MAHAL,JAGATPURA.JAIPUR (I) ABSTRACT

Dot net dealt as a framework signifies the foundation for software development. The dot net framework consists of the common language runtime, which provides many of the core services required for program execution. This project includes the contents of dot net base class library, which exposes a set of predeveloped classes to facilitate program development. The common language specifications (CLS) defines a minimum set of standards that all language using the dot net frame work must support, and the common type system (CTS) ensures type compatibility between components developed in different languages. A dot net executable is stored as a Microsoft intermediate language (MSIL) file. Here we have chosen the concept of disconnected architecture for our programming purpose, data set an in memory representation of the table and data tables objects independent of data adapters objects fill them programmatically. Data relation objects represent parent child relationship between columns of different tables .we used data relation objects to enforce constraints and retrieve related rows of data. Data binding and data viewing concept are also provided in the scene referring relationship between a data provider and data consumer receive data and display or otherwise process it, in the data binding process two sort of bindings are described: simple binding and complex binding .A simple bound controls bind a singe record at a time, where as complex bound

bind all available records at once. Data viewing an object that is associated with a data table and provides a filterable, sortable subset of the data contained by the underlying data. Table of Contents CHAPTER NO TITLE PAGE NO ABSTRACT (II) ACKNOWLEDGEMENT (IV) LIST OF FIGURE (VI) 11 1.1 .net 1 1.2 Principal 2 1.2.1 1.2.2 1.2.3 interoperablity common runtime engine language independent design feature technology Introduction

1.2.4 1.2.5 1.2.6 1.3

base class library security portability language infrastructure

common 3

1.4 6 1.5 Features 9 1.6 The 14 1.7 Common 14 1.8 1.9 Classes Service 15 1.10 .net 16 221 of

class

library

common

language

runtime

common

type

system

language

specification

layers

and

tiers

architecture

Software requirement specification

327 430 4.1 30 4.2 31 532 5.132 5.233 5.3635 736 838

Use case reports

Use case modeling

use case diagrams for reservation system

enquiry to issue of tickets

passenger reservation system

objective of prs

impact of prs implementation

Growth of Total Passenger Traffic on Indian project at a glance

appendix

refrences

(iv) ACKNOWLEDGEMENT I feel highly privileged to express my sincere thanks and deepest sense of gratitude to Mr. sunil sharma, Director, gyan vihar university. for giving us opportunity to complete the software engineering lab projectunder guidance fo mr.kamlesh , who has spared his precious time to complete this project. I express my deepest sense of gratitude towards Mr. Naveen hemrajani HOD Department of Computer Science,gyan vihar, Jaipur for clearing my doubts at any time of need and valuable inspiration during the project work. My thanks are extended to all staff members and persons who directly or indirectly helped me in achieving my goals. I could not have completed this work without the guidance of my parents. They deserve more credit than I can give for instilling in me a good work ethic and a desire to always learn more.

My thanks are extended to all friends who gave me nice company and kept my spirit high throughout this work. (v) Table of figure Figures name 1-Visual overview of the CLI 2-Class library 3-.net frame stack 4-Layer architecture 5-Two tier architecture 6-Three tier architecture 7-N tier architectures 8-use cases 9-issue of tickets 10-growth of passenger in india page no

INTRODUCTION:.NET Technology- Microsoft's .NET technology is a technology intended to connect. What to connect? Well the whole thing that can be linked through software - people, structures, computers, and extra things as well as devices. .NET can grasp servers that offer web services or the tools wanted to generate these services. What are Web Services and their profit? Well they can be called enhancements that assist businesses expand and connect by their clients and partners. Their profits are that they create the communication among business partners a lot easier and still increase the profits by creation a business known and accessible to much more people through the assist of the Internet. A main part of the .Net technology and structure is the ASP.net set of technologies. These web development technologies are used in the making of Websites and net services working on the .NET infrastructure. ASP.NET was build by Microsoft from one of their big technologies and web programmers can make use of any encoding language they want to write ASP.NET, from Perl to C Sharp (C#) and of course VB.NET and a few extra language unspoken with the .NET technology. The advantages of the ASP.NET technology are that it creates construction Websites, Web applications and Web services very simple and with fewer code those older languages. As well, the applications compiled in ASP.NET run quicker and with fewer errors. .NET Framework- The Microsoft .NET Framework is a software framework that can be installed on computers running Microsoft Windows operating systems. It includes a large library of coded solutions to prevent common programming problems and a virtual machine that manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform.

1 The framework's Base Class Library provides a large range of features including user interface, data and data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications. Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework.

Principal design features Interoperability : Because interaction between new and older applications is commonly required, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; access to other functionality is provided using the P/Invoke feature. Common Runtime Engine:

The Common Language Runtime (CLR) is the virtual machine component of the .NET framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling. 2 Language Independence : The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible datatypes and programming constructs supported by the CLR and how they may or may not interact with each other. Because of this feature, the .NET Framework supports the exchange of instances of types between programs written in any of the .NET languages. This is discussed in more detail in Microsoft .NET Languages. Base Class Library : The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction and XML document manipulation. Simplified Deployment: The .NET framework includes design features and tools that help manage the installation of computer software to ensure that it does not interfere with previously installed software, and that it conforms to security requirements. Security:

The design is meant to address some of the vulnerabilities, such as buffer overflows, that have been exploited by malicious software. Additionally, .NET provides a common security model for all applications. Portability:The design of the .NET Framework allows it to theoretically be platform agnostic, and thus cross-platform compatible. That is, a program written to use the framework should run without change on any type of system for which the framework is implemented. Microsoft's commercial implementations of the framework cover Windows, Windows CE, and the 3 Xbox 360. In addition, Microsoft submits the specifications for the Common Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language),[4][5][6] the C# language,[7] and the C+ +/CLI language[8] to both ECMA and the ISO. Common Language Infrastructure (CLI) The core aspects of the .NET Framework lie within the Common Language Infrastructure, or CLI. The purpose of the CLI is to provide a language-neutral platform for application development and execution, including functions for exception handling, garbage collection, security, and interoperability. Microsoft's implementation of the CLI is called the Common Language Runtime or CLR. Assemblies .NET assembly The intermediate CIL code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files. The assembly consists of one or more files, one of which must contain the manifest, which has the metadata for the assembly. The complete name of an assembly (not to be confused with the filename on disk) contains its simple text name, version number, culture, and public key token. The public key

token is a unique hash generated when the assembly is compiled, thus two assemblies with the same public key token are guaranteed to be identical from the point of view of the framework.

Architecture

Visual overview of the Common Language Infrastructure (CLI)

Class library

Namespaces BCL[9] System

in

the

System. CodeDom System. Collections System. Diagnostics System. Globalization System. IO System. Resources System. Text System. Text.RegularExpressions

The .NET Framework includes a set of standard class libraries. The class library is organized in a hierarchy of namespaces. Most of the built in APIs are part of either System.* or Microsoft.* namespaces. These class libraries implement a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. The .NET class libraries are available to all .NET languages. The .NET Framework class library is divided into two parts: the Base Class Library and the Framework Class Library.

The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime.[9] The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono.

The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework. It includes an expanded set of libraries, including WinForms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others. The FCL is much larger in scope than standard libraries for languages like C++, and comparable in scope to the standard libraries of Java

Versions

Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of .NET 1.0 were released.

The .NET Framework stack. Versi Version on Number Release Visual Date Studio 2002-02- Visual 13 Studio .NET

Default in Windows

1.0

1.0.3705.0

1.1

Visual 1.1.4322.57 2003-04Studio 3 24 2003 2.0.50727.4 2005-11- Visual 2 07 2005 3.0.4506.30 2006-11-

.NET Windows Server 2003

2.0

Studio

3.0

Windows

Vista,

06 2007-11- Visual 19 2008 8 .NET FRAMEWORK IN CONTEXT:-

Windows Server 2008 Studio Windows 7, Windows Server 2008 R2

3.5

3.5.21022.8

The following sections describe the main components and features of the .NET Framework in greater detail. Features of the Common Language Runtime The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system 9

services. These features are intrinsic to the managed code that runs on the common language runtime. With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registryaccess operations, or other sensitive functions, even if it is being used in the same active application. The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally feature rich. The runtime also enforces code robustness by implementing a strict type-and-codeverification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety

10 In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references. The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications. While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs. The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. 11 A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing.

Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance. Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft SQL Server and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.

Visual Studio Development Environment The .NET platform provides a comprehensive development environment known as the Visual Studio Team System. You can use the language of your choice within Visual Studio Team System to write applications that target the .NET Framework. As an integrated development environment (IDE), it provides all the tools you require to design, develop, debug, and deploy Windows, Web, Mobile, and Office-based solutions. Visual Studio is organized into several different versions, with some versions targeted at specific groups such as architects, testers, and others involved in the full life cycle of application development. You can install multiple versions side-by-side to obtain the required combination of features. 12 In addition to Visual Studio, Microsoft provides other development environments such as Expression Studio, and external libraries that are not included in the.NETFramework. The .NET Framework Class Library (FCL)

The FCL is a set of reusable object-oriented classes that provide basic platform functionality, from the data access classes of ADO.NET, to filesystem utility classes (including file, directory, and stream classes), to networking classes that allow easy implementation of DNS resolution, WHOIS lookups, and other network-related functionality. Developers can use the base classes directly or derive from these classes to provide customized functionality. The FCL also contains all classes that make up ASP.NET. These include classes that implement all of the functionality of the ASP intrinsic objects, as well as classes that provide additional functionality, from a rich engine for caching output and data to the ASP.NET Server Control model. This functionality brings to ASP.NET the simplicity of control-based development that has long been available to Visual Basic developers. In addition to classes that support Web application development , the FCL provides classes for developing console applications, Windows applications, and Windows NT or Windows 2000 Services. 13 The Common Type System (CTS) The CTS describes the set of types that are supported by the CLR. This includes both value types, which include primitive data types such as Byte, Int16, Double, and Boolean, and reference types, which include arrays, classes, and the Object and String types. The Common Language Infrastructure (CLI)

The CLI is a subset of the .NET Framework that has been submitted for standardization through the ECMA standards body. The CLI includes the functionality of the Common Language Runtime, as well as specifications for the Common Type System, type safety rules, Metadata, and Intermediate Language. It also includes a subset of the Framework Class Library that includes a Base Class Library (for built-in types and basic runtime functionality), a Network Library (for simple networking services and access to network ports), a Reflection Library (for examining types and retrieving information about types at runtime), an XML Library (for parsing XML), and Floating Point and Extended Array Libraries.

The Common Language Specication (CLS) The CLS is a subset of the types supported by the CLR, as well as a set of rules that language and compiler designers must follow. The purpose of the CLS is to provide robust interoperability between .NET languages, including the ability to inherit classes written in one .NET language in any other .NET language and crosslanguage debugging. 14 The rules defined by the CLS apply only to publicly exposed features of a class. For example, the internal implementation of a class can use non-CLScompliant types (such as the unsigned integer types), but as long as only CLS-compliant members are exposed publicly, the class can still take full advantage of the interoperability features enabled by the CLS. Classes While not a term specific to the .NET platform, the term class may be new to many ASP developers. A class is essentially the blueprint for an object. It contains the definition for how a particular object will be instantiated at runtime, such as the properties and methods that will be exposed publicly by the object and any internal storage structures. Layers and Tiers Layers

Layers are the logical groupings of the software components that make up the application or service. They help to differentiate between the different kinds of tasks performed by the components, making it easier to create a design that supports reusability of components. Each logical layer contains a number of discrete component types grouped into sublayers, with each sublayer performing a specific type of task. By identifying the generic types of components that exist in most solutions, you can construct a meaningful map of an application or service, and then use this map as a blueprint for your design.

15

Splitting an application into separate layers that have distinct roles and functionalities helps you to maximize maintainability of the code, optimize the way that the application works when deployed in different ways, and provide a clear delineation between locations where certain technology or design decisions must be made.

Presentation, Business, and Data Services At the highest and most abstract level, the logical architecture view of any system can be considered to be a set of cooperating services grouped into the following layers, as shown in Figure 1.

layer

architecture

16

Tiers Tiers represent the physical separation of the presentation, business, services, and data functionality of your design across separate computers and systems. Common tiered design patterns are two-tier, three-tier, and n-tier. The following sections explore each of these scenarios.

Two-Tier The two-tier pattern represents a basic structure with two main components, a client and a server. In this scenario, the client and server may exist on the same machine, or may be located on two different machines. Figure 6 illustrates a common Web application

scenario where the client interacts with a Web server located in the client tier. This tier contains the presentation layer logic and any required business layer logic. The Web application communicates with a separate machine that hosts the database tier, which contains the data layer logic.

The two-tier deployment pattern

17 Three-Tier

In a three-tier design, the client interacts with application software deployed on a separate server, and the application server interacts with a database that is also located on a separate server. This is a very common pattern for most Web applications and Web services. Figure 7 illustrates the three-tier deployment pattern.

The three-tier deployment pattern

N-Tier In this scenario, the Web server (which contains the presentation layer logic) is physically separated from the application server that implements the business logic. This usually occurs for security reasons, where the Web server is deployed within a perimeter network and accesses the application server located on a different subnet through a firewall. It is also common to implement a firewall between the client and the Web tier. Figure 8 illustrates the n-tier deployment pattern.

18

The n-tier deployment pattern ASP.NET architecture

19 Encrypting Configuration Configuration Information Using Protected

Part of securing an application involves ensuring that highly sensitive information is not stored in a readable or easily decodable format. Examples of sensitive information include user names, passwords, connection strings, and encryption keys. Storing sensitive information in a non-readable format improves

the security of your application by making it difficult for an attacker to gain access to the sensitive information, even if an attacker gains access to the file, database, or other storage location.

One of the primary places that sensitive information is stored in an ASP.NET application is the Web.config file. To help secure information in configuration files, ASP.NET provides a feature called protected configuration, which enables you to encrypt sensitive information in a configuration file. Overview of Protected Configuration You can use protected configuration to encrypt sensitive information, including user names and passwords, database connection strings, and encryption keys, in a Web application configuration file such as the Web.config file. Encrypting configuration information can improve the security of your application by making it difficult for an attacker to gain access to the sensitive information even if the attacker gains access to your configuration file. 20 SOFTWARE REQUIREMENT SPECIFICATION 1) Introduction: 1.1) Purpose: 1.2) Scope: 1.3)Abbreviations 1.4) References: 1.5) Technologies: 2)Overall Description: 2.01) Product Perspective: 2.02) Software

2.03) Hardware Interface: 2.04) Communication Interface 2.05) Product Function 2.06) User Characteristics 2.07) Constraints: 2.08) Use-Case Model Survey 2.09) Architecture diagram 2.10) Database design: 2.11) Assumptions and Dependencies: 3) Specific Requirements: 3.1) Use-Case Reports 3.2) Supplementary Requirements:

21 1) Introduction: 1.1) Purpose: The online railway reservation establishing and sustaining the goal of to provide the easiest and quickly way to get a much awaited online railway ticket. To provide the facility to get the ticket as well as cancellation and check the status of passenger. 1.2) Scope: ? Create different system users and assign different roles with related permissions. ? Manage all the account details such as passenger name, source, destination, address of the passenger, email addresses of all the passenger from one central location. ? Track all the passenger and their contact details. ? Maintain the services provided to the passenger through Service Level Agreements. ? Track all the payment details of the customer and their ticket ownership detail.

? Group the contacts together in a single account according to some criteria. ? Capture, View and edit all passenger transactions, including email, chats, and services calls in asingle system. ? Confirmation of end user identity and will verify which users are authorized to receive support. ? Maintain history of each customer and their related information about the ticket. ? View all the details of all the interactions made with the traveller. ? Activities like updations, creations done in the system by the system users will be maintained in the form of logs for auditing and maintaining the integrity of the system. 1.3) Abbreviations: ? Support transaction: Communication between support manager and customer /passenger regarding service provided, query & feedback for the product. 22 ? Payment transaction: Transaction between account manger and customer for all the payment of its purchase of ticket and services. ? Personal details: Details of customer such as username, e mail id, phone number, address etc. ? HTML: Hypertext Markup Language is a markup language used to design static web pages. ? Microsoft sql server: Microsoft sql server Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. ? HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. ? HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer). ? TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

1.4) References: ? IEEE SRS Format ? Problem Definition (Provided by guide) 1.5) Technologies: ? ASP.NET programming language ? Microsoft sql server: Database ? Rational: Design Tool 23 1.6) Overview: SRS will include two sections: ? Overall Description will describe major components of the system, interconnection and external interfaces. ? Specific Requirements will describe the functions of actors, their role in the system and constraints. 2) Overall Description: Describe the general factors that affect the product and its requirements. 2.01) Product Perspective: ? The web pages (XHTML/ASP) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols. ? The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. 2.02) Software Interface: Client on Internet: Web Browser, Operating System (any) Client on Intranet: Client Software, Web Browser, Operating System (any) Web Server: Operating System (any)

Data Base Server: Microsoft sql server, Operating System (any)

24 2.03) Hardware Interface: Client Side Processor RAM Internet Explorer 6.0 Pentium IV at 500MHz 64 MB Server Side Web sphere application serverV5.0 Pentium IV at 1GHz DiskSpace 1 GB

512 MB

2 GB

2.04) Communication Interface: ? Client on Internet will be using HTTP/HTTPS protocol. ? Client on Intranet will be using TCP/IP protocol. 2.05) Product Function: ? Track Account Level Data: In this module, receivables from customer are maintained. ? Service Level Agreements: It contains the agreements of providing the services related to product and customer. ? User Contact Information: It maintains all the details (Personal, Official, Contact, and Company) of the customer. ? Product Ownership Details: It maintains the information that does which customer own which product. ? Track Support Transactions: Maintenance of transactions related to the services providedto the customer in the form of support.

25 ? Maintaining Logs: Activities of the System Users can be tracked through the logs, which is maintained by the system. 2.06) User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too. 2.07) Constraints: ? GUI is only in English. ? Login and password is used for identification of customer and there is no facility for guest. ? This system is working for single server. ? There is no maintainability of back up so availability will get effected. ? Limited to HTTP/HTTPS.

26 Use case reports:

i) Administrator: Responsible for managing system users, viewing logs and managing standard groups of the system. # Manage System Users: The Administrator will create different roles. The system users will be created and will be assigned with the different roles. More than one task and permissions can be granted or revoked from the system users. # View Logs: Responsible for checking the logs of different system user for auditing and maintaining the integrity of the system. # Manage Standard Groups: Standard groups will be created and updated by the administrator, which will be visible to all the system users. #View All Details: View the customer details, payment details, purchase details, daily service transaction details.

Name of use case: View System Users Description: View the list of system users in a role and view the details of roles, tasks and permissions assigned to a system user. Preconditions: ? Administrator is already logged in. ? System users have already been created and assigned some roles, tasks and permissions. 27 Normal flow of events: The system user or a role will be selected. Query will be submitted. Relevant output will be displayed (If system user is selected then roles, tasks and permissions assigned to one will be displayed and if role is selected then list of system users assigned to that role will be displayed). Alternate flow of events: None.

Post Condition: None.

28 Name of use case: Create System Users Description: To create system users (Giving them a login name, password and assign roles, tasks and permissions to them). Preconditions: Administrator is already logged in.

Normal flow of events: New Login name, password, details, roles, tasks and permissions will be entered. Save the details. Alternate flow of events: A message appears for duplicate login name. The administrator has to fill the details again. Post condition: A login id is generated with its details.

29 Use case modeling-

30

Enquiry to issue of tickets-

31 Passnger reservation system(PRS) Exhibit 1. Objectives of PRS* Objectives of PRS 1. Service to Public a. Reduction in time and expense involved in ticketing b. Quicker service to passengers c. Quick and easy availability of information regarding trains and accommodation availability 2. Better working environment for staff 3. Reduction in scope for unethical practices in reserving ccommodation * from official documents Exhibit 2. Impact of PRS Implementation Before PRS Implementation 1. Reservation possible only at the train originating station. From other stations request sent through telegram. 2. Long queues and long waiting time for passengers. 3. Possibility of mistake very high as details written manually in register, leading to passenger inconvenience. 4. Possibility of booking clerk not giving correct availability position, since the waitlist information is not universally available. 5. Possibility of unethical practices while allotting reservation, since information access is restricted. After PRS implementation 1. Immediate reservation from any station to any station over IR, possible from any PRS counter. 2. Shorter queues because of availability of large number of universal PRS counters. 3. Possibility of mistakes reduced as the information printed on the ticket can be checked by the passenger. 4. Information regarding availability status is universally available over touch screens, Internet and phone. 5. Possibility of unethical practices largely eliminated

Exhibit 3. Growth of Total Passenger Traffic on Indian Year 1950-51 1960-61 1970-71 1980-81 1990-91 1997-98 1998-99 2000-2001 2001-2002 2002-2003 2003-2004 2004-2005 2005-2006 Number of Passenger (millions) 1284 1594 2431 3613 3858 4348 4411 4833 5093 4971 5112 5516 5886

33

34

PROJECT AT A GLANCE-This Indian railway the online reservation project describes the several items in detail. It includes many of the web pages which depicts the required information and ticket generating facility in less time as compare to the counter booking. Web pages are-home page, pnr status train schedule ,train fare, rules ,about us reservation ,maps and many more pages related with the information and facility which are provided by this project.

Pnr status-it has the facility to check the status of their reservation . It requires the 17 digit pnr no. to verify the reservation status. Train schedule-this web page gives the information about the schedule of the trains across all over india according to the their respective station for up and down both. Train fare-the train fare is according to the distance covered by the train .it generates the fare according to the category like handicapped persns,senior citizen, blind person, children etc. Maps-it has the maps of Indian railway with their zonal distribution.

35

APENDIX

Introduction to the C# Language and the .NET Framework:

C# is an elegant and type-safe object-oriented language that enables developers to build a variety of secure and robust applications that run on the .NET Framework. You can use C# to create traditional Windows client applications, XML Web services, distributed components, client-server applications, database applications, and much, much more. Visual C# 2008 provides an advanced code editor, convenient user interface designers, integrated debugger, and many other tools to make it easier to develop applications based on version 3.0 of the C# language and version 3.5 of the .NET Framework. C# Language C# syntax is highly expressive, yet it is also simple and easy to learn. The curly-brace syntax of C# will be instantly recognizable to anyone familiar with C, C++ or Java. Developers who know any of these languages are typically able to begin to work productively in C# within a very short time. C# syntax simplifies many of the complexities of C++ and provides powerful features such as nullable value types, enumerations, delegates, lambda expressions and direct memory access, which are not found in Java. C# supports generic methods and types, which provide increased type safety and performance, and iterators, which enable implementers of collection classes to define custom iteration behaviors that are simple to use by client code. In C# 3.0, Language-Integrated Query (LINQ) expressions make the strongly-typed query a first-class language construct. As an object-oriented language, C# supports the concepts of encapsulation, inheritance, and polymorphism. All variables and methods, including the Main method, the application's entry point, are encapsulated within class definitions. 36

A class may inherit directly from one parent class, but it may implement any number of interfaces. Methods that override virtual methods in a parent class require the override keyword as a way to avoid accidental redefinition. In C#, a struct is like a lightweight class; it is a stack-allocated type that can implement interfaces but does not support inheritance. In addition to these basic object-oriented principles, C# makes it easy to develop software components through several innovative language constructs, including the following:

Encapsulated method signatures called delegates, which enable type-safe event notifications. Properties, which serve as accessors for private member variables. Attributes, which provide declarative metadata about types at run time. Inline XML documentation comments. Language-Integrated Query (LINQ) which provides built-in query capabilities across a variety of data sources.

37

REFERENCES

1. Ariponnammal, S. and Natarajan, S. (1994) Transport Phonomena of Sm Sel X Asx, Pramana Journal of Physics Vol.42, No.1, pp.421-425. 2. Barnard, R.W. and Kellogg, C. (1980) Applications of Convolution Operators to Problems in Univalent Function Theory, Michigan Mach, J., Vol.27, pp.8194. 3 SOFTWARE ENGINEERING, A PRACTITIONERS

APPROACH By ROGER S. PRESSMAN Microsoft .NET FRAMEWORK 2.0 Web-Based Client Development By Glenn Johnson and Tony Northrup ASP.NET 2.0 By Bill Evjen Scott Hanselman www.microsoft.com www.learnvisualstudio.com

38

S-ar putea să vă placă și