91
ATHPATNA.COM (“Centralized Transaction Information System”) SUMMER TRAINING PROJECT REPORT RAYAT INSTITUTE OF ENGINEERING AND INFORMATION TECHNOLOGY Bachelor of Technology In Computer Science and Engg.

centralised transaction information system

Embed Size (px)

Citation preview

Page 1: centralised transaction information system

ATHPATNA.COM (“Centralized Transaction Information System”)

SUMMER TRAINING PROJECT REPORT

RAYAT INSTITUTE OF ENGINEERING AND INFORMATION

TECHNOLOGY

Bachelor of Technology

In

Computer Science and Engg.

By:-

Amit Kumar (90570306925)

Page 2: centralised transaction information system

DECLARATION:

I hereby declare that the project work entitled “ashok tyre house” is an authentic record of my own

work carried out at CDAC PATNA as requirements of Industry Internship project for the summer

training of B-TECH, R.I.E.I.T, Railmajra, under the guidance of Mr.Rajeev kumar singh during June

to july, 2011.

Amit KumarDate: (Signature)

Certified that the above statement made by the student is correct to the best of our knowledge and belief.

Mr.Rajeev kumar singh

Page 3: centralised transaction information system

TRAINING CERTIFICATE

Page 4: centralised transaction information system
Page 5: centralised transaction information system

ACKNOWLEDGEMENT

I would like to take this opportunity to thank everyone who put forth their time and effort to help me

to develop this project. This project takes a long time from the collection of information to the

completion.

The satisfaction that accompanies the successful completion of the task would be incomplete without

the mention of the people whose ceaseless cooperation made it possible, whose constant guidance and

encouragement crown all efforts with success. We are grateful to our Project Guide Mr. Rajeev kumar

singh for the inspiration and the constructive suggestions that helped us in preparation of the project

Athpatna.com. His valuable guidance has leaded us towards the definite approach.

Amit kumar

Member Athpatna Team.

Page 6: centralised transaction information system

TABLE OF CONTENTS .

1.Organization Overview……………………………………………………………………….

2. Profile of the Problem………………….…………………………………………………..…

3. Existing System……………………………………………………………………………….a) Introductionb) Existing Softwarec) DFD for the system

4. Problem Analysis………………………………………………………………………………a) Product Definitionb) Feasibility Studyc) Project Plan

5. Software Requirements……………………………………………………..............................a) Introductionb) General Descriptionc) Specific Requirements

6. Design………………………………………………………………………………………….. a) System Designb) Design Notationsc) Detailed Designd) Flowchartse) Pseudo Code

7. Testing……………………………………………………………….………………………...a) Functional Testingb) Structural Testingc) Levels of testingd) Testing of the Project

8. Implementation………………………………………………….…………………………..…a) Implementation of the project b) Conversion Planc) Post – implementation and Software Maintenance

9. Project Legacy……………………………………………………………………………….…

Page 7: centralised transaction information system

a) Current Status of the project b) Remaining areas of concernc) Technical and Managerial lessons learnt

10. Snapshots….………………..……………………………………………….……….………...

11. Bibliography……………………………………………………………………….………….

12. Attendance Reports…….………………………………………………………….………....

13. Appraisal Forms……………………..……………………………………………………....

Page 8: centralised transaction information system
Page 9: centralised transaction information system

COMPANY PROFILE

Fig 1.1 CDAC ACTS PATNA

Center for Development of advanced Computing (C-DAC) is the premier R&D organization of the

department of information technology (DIT), Ministry of Communications & Information Technology

(MCIT) for carrying out R&D in IT Electronics and associated areas. The setting of C-DAC in 1988

itself was to built Supercomputers (PARAM) in context of denial of import of Supercomputer by

USA. Because of creative echo system in CDAC, more areas such as health, informatics, etc. got

created.

C-DAC’s Advanced Computing Training School (ACTS) was set up in the 1992 to import quality

training in high-end technologies to existing and prospective users of advanced computing. Over the

last 15 years, the activities of ACTS have extended nationally through a network of four centers in

Pane, Delhi, Bangalore, and Hyderabad and almost forty six Authorized Training Centers (ACTS).

Page 10: centralised transaction information system

Career Foresight (a unit of sai Education & Health Awareness Trust ) is a fast growing illustrious

Authorized training Center (ATC) of CDAC were formed in the year 2009 with the objectives to

established a strong network of technology professionals and scientists to address regional issues and

bring technology to people.

Our Achievements:

Successfully completed post graduated diploma in advanced computing (DAC) batches

(two batches), past graduated students placed in reputed companies. Provided free job oriented

(careers in it, business process outsourcing and other it enabled services) training to the students

belonging to the minority communities under the scheme of ministry affairs, government of India.

listed in government of India’ SUIDAI empanelled training agency.

Key differentiating factors:

1. Career Foresight (a unit of Sai Education & Health Awareness Trust) is the only CDAC

center in North and North East India.

2. Recognized as the best IT training brand in India.

3. Administered by Department of Information Technology, Government of India.

4. Centrally controlled by CDAC headquarter ,Pune .

5. The course curriculum designed in collaboration with industry to meet the contemporary

requirement of ICT which focus on holistic professionals development of students.

6. Well equipped lab and lecture theater with a capacity to train 80 students per batch.

7. Guest lecturers from the the C-DAC centers also visit and train advanced modules.

8. Apart from the resident faculties, experts from different distant places train the students

with the help of Video Conferencing.

9. Classes on business communications and personality development are conducted by IT

experts.

Page 11: centralised transaction information system

10.Organizes weekly technical meeting to discuss on new innovative technologies.

11.The center is supported by IT Practitioners of various domain experiences working in many

parts of country and abroad.

12. The director of the center has track record of doing business successfully in Bihar more than

three Decades with a single objectives of bringing technical and economical growth in the

home state.

Our Aim:

1. To set up a world class IT institute and research center.

2. To identify local problem that can be solved by technology, either existing or needs some

research.

3. To help state government in making Bihar e-governance, IT-enabled and e-literate state in

the country so that it may be regarded as proffered destination for IT business.

4. To build skilled manpower pool to make regional human resources more marketable in IT.

5. To initiate projects to bring efficiency in the healthcare system using IT and other technology

tool.

6. To run academic quality improvement programs.

7. To foster entrepreneurial activities in the region by providing an accessibility of technology

and professional services.

8. To established a software and project management institute, which would help companies

bring quality in product development and delivery process.

9. To organize Science Conferences and seminars to improve general awareness and facilitate

technology networking.

10.We are in the process of establishing a world class BCA and MCA College for providing IT

education in our state.

Page 12: centralised transaction information system

Some of the courses offered by us:

Post graduate programs

1. Diploma in Advanced computing (DAC)

This course is globally recognized as a premier course for those aspiring to establish a career in the

software industry.

2. Diploma in VLSI Design (DVLSI)

This is a specialized course that trains students in various aspects o VLSI design and is recognized

leading organizations in the VLSI industry.

3. Diploma in Advanced Computer Arts (DACA)

This course enables students and users to employ multimedia technology in their profession, like

architecture, fine arts, film production or television programming.

4. Diploma in Language Computing (DLC)

This course aims to provide a self-contained introduction to the central issues of Natural Languages

processing (NLP), to introduce various practical skills associated with the design and implementation

of NLP systems, and to prepare students (software engineers and linguists) for computer modeling for

the implement language technology tools and applications.

Page 13: centralised transaction information system

5. Diploma in Healthcare Informatics (DHI)

The objectives of this course is enables the student to understand the art and applicable science of

introducing, managing , and organizing information and technology related to human healthcare.

6. Diploma in information System and Cyber security (DISCS)`

This course is targeted towards grooming students in the arena of human-computer interaction and

Cyber and Network Security.

7. Diploma in System Software Design( DSSD)

This course provide training to develop system software development professional to assures security

software design & implementation practices as per the industry needs.

8. Diploma in Embedded System Design( DESD)

The embedded Systems Design course is designed with equal emphasis on hardware and software and

prepares Electronics design engineers to meet the needs of Electronics and IT industry for the design

and development of state of the arts embedded systems.

Under graduate programs:

1. Diploma in Information technology( DIT)

2. Advanced diploma in Information Technology (ADIT)

3. Diploma in Multimedia Creations (DMC)

4. Preparatory Course For Diploma In Advanced Computing(PreDAC)

5. Diploma in Digital Art(DDA)

Page 14: centralised transaction information system

The Leadership Team

1. Ramraj Pandey, MS Electrical and Comp Eng, Michigan, USA

Over 10 years in IT and Aerospace industry, currently engagement manager, Volks Wagon,

Michigan USA

2. Arun Kumar Singh A very successful entrepreneur , having two KIDZEE school at Muzaffarpur, Carpet

manufacturing and Export business for last 20 years, Sale Distributor of ZEE-TV in Bihar.

3. Manoj Kumar PhD in (Digital Signal Processing of Seismo-Electromagnetic signals ) Over 7 years of

experiences in the analysis , design and development of small to large corporate strategic and

critical business application and projects.

4. Samir Kumar MishraAuthor of a book on java , a leading member of open source and web 2.0 community.

The Advisory Team

1. DR.S. K. ChakrabortyProfessor Emeritus, Chairman, Dept of Applied Physics, NIT, KURUSHETRA.

2. Dr. Ashok GhoshHOD, Environmental Science Dept. A.N. College, Patna

3. Dr. M.J. WarsiProfessor, Gorge Washington, St. Lucia, USA

4. Dr. M Orrair

Professor , University of Michigan, USA

Page 15: centralised transaction information system

5. Dr. B. K. Sharra Professor and HOD, Electronics Eng, NIT Patna.

6. Mr. G.S. Singh A senior IT professional with 30+yrs of experiences, working in a TATA Company Pune.

7. Mr. Kedar A Kayal A senior design engineer using high end IT Systems for last10+yrs, currently working with a well

known R&D Center in Bangalore.

8. Ms Tulika Kayal A senior IT professional working with a well known MNC in Bangalore.

9. Ms. Lipika singhA senior IT professional working with a well known Financial Product Company in Bangalore.

Page 16: centralised transaction information system

LITREATURE REVIEW

2.1 INTRODUCTION TO .NET FRAMEWORK:

The Microsoft .NET Framework is a software framework available with several 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.

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.

Version 3.0 of the .NET Framework is included with Windows Server 2008 and Windows Vista. The current version of the framework can also be installed on Windows XP and the Windows Server 2003 family of operating systems. A reduced "Compact" version of the .NET Framework is also available on Windows Mobile platforms, including smart phones.

Overview:

.NET Framework 3.5 builds incrementally on the new features added in .NET Framework 3.0. For example, feature sets in Windows Workflow Foundation (WF), Windows Communication Foundation

Page 17: centralised transaction information system

(WCF), Windows Presentation Foundation (WPF) and Windows Card Space. In addition, .NET Framework 3.5 contains a number of new features in several technology areas which have been added as new assemblies to avoid breaking changes. They include the following:

Deep integration of Language Integrated Query (LINQ) and data awareness. This new feature will let you write code written in LINQ-enabled languages to filter, enumerate, and create projections of several types of SQL data, collections, XML, and Datasets by using the same syntax.

ASP.NET AJAX lets you create more efficient, more interactive, and highly-personalized Web experiences that work across all the most popular browsers.

New Web protocol support for building WCF services including AJAX, JSON, REST, POX, RSS, ATOM, and several new WS-* standards.

Full tooling support in Visual Studio 2008 for WF, WCF, and WPF, including the new workflow-enabled services technology.

New classes in .NET Framework 3.5 base class library (BCL) that address many common customer requests

2.2 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 Interrupt Services and System Enterprise Services 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.

Page 18: centralised transaction information system

Language Independence:

The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible data types 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 Xbox 360. In addition, Microsoft submits the specifications for the Common Language Infrastructure (which

Page 19: centralised transaction information system

includes the core class libraries, Common Type System, and the Common Intermediate Language), the C# language, and the C++/CLI language to both ECMA and the ISO, making them available as open standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.

2.3 ARCHITECTURE:

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: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

Page 20: centralised transaction information system

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. A private key can also be specified known only to the creator of the assembly and can be used for strong naming and to guarantee that the assembly is from the same author when a new version of the assembly is compiled (required to add an assembly to the Global Assembly Cache).

Metadata:

All CLI is self-describing through .NET metadata. The CLR checks the metadata to ensure that the correct method is called. Metadata is usually generated by language compilers but developers can create their own metadata through custom attributes. Metadata contains information about the assembly, and is also used to implement the reflective programming capabilities of .NET Framework.

Page 21: centralised transaction information system

Security:

.NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a call stack walk: every assembly of each method in the call stack is checked for the required permission; if any assembly is not granted the permission a security exception is thrown.

When an assembly is loaded the CLR performs various tests. Two such tests are validation and verification. During validation the CLR checks that the assembly contains valid metadata and CIL, and whether the internal tables are correct. Verification is not so exact. The verification mechanism checks to see if the code does anything that is 'unsafe'. The algorithm used is quite conservative; hence occasionally code that is 'safe' does not pass. Unsafe code will only be executed if the assembly has the 'skip verification' permission, which generally means code that is installed on the local machine.

.NET Framework uses application domains as a mechanism for isolating code running in a process. Application domains can be created and code loaded into or unloaded from them independent of other application domains. This helps increase the fault tolerance of the application, as faults or crashes in one application domain do not affect rest of the application. Application domains can also be configured independently with different security privileges. This can help increase the security of the application by isolating potentially unsafe code. The developer, however, has to split the application into sub domains; it is not done by the CLR.

Class library:

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,

Page 22: centralised transaction information system

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. 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 Silver light 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 Win Forms, 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.

Memory management:

The .NET Framework CLR frees the developer from the burden of managing memory (allocating and freeing up when done); instead it does the memory management itself. To this end, the memory allocated to instantiations of .NET types (objects) is done contiguously from the managed heap, a pool of memory managed by the CLR. As long as there exists a reference to an object, which might be either a direct reference to an object or via a graph of objects, the object is considered to be in use by the CLR. When there is no reference to an object, and it cannot be reached or used, it becomes garbage. However, it still holds on to the memory allocated to it. .NET Framework includes a garbage collector which runs periodically, on a separate thread from the application's thread, that enumerates all the unusable objects and reclaims the memory allocated to them.

The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage collector. The GC runs only when a certain amount of memory has been used or there is enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim memory are reached, the GC runs are non-deterministic. Each .NET application has a set of roots, which are pointers to objects on the managed heap (managed objects). These include references to static objects and objects defined as local variables or method parameters.

Currently in scope, as well as objects referred to by CPU registers. When the GC runs, it pauses the application, and for each object referred to in the root, it recursively enumerates all the objects

Page 23: centralised transaction information system

reachable from the root objects and marks them as reachable. It uses .NET metadata and reflection to discover the objects encapsulated by an object, and then recursively walk them. It then enumerates all the objects on the heap (which were initially allocated contiguously) using reflection. All objects not marked as reachable are garbage. This is the mark phase.

2.4 ASP.NET:

ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services.

2.4.1 New Features in ASP.NET 3.5:

 ASP.NET AJAX:

In ASP.NET 2.0, ASP.NET AJAX was used as an extension to it. You had to download the extensions and install it. However in ASP.NET 3.5, ASP.NET AJAX is integrated into the .NET Framework, thereby making the process of building cool user interfaces easier and intuitive.

The integration between web parts and the update panel is much smoother. Another noticeable feature is that you can now add ASP.NET AJAX Control Extenders to the toolbox in VS2008. Even though this is an IDE specific feature, however I feel it deserves a mention over here for developers, who had to add extenders using source view earlier. It is also worth noting that Windows Communication Foundation (WCF) now supports JSON along with other standard protocols like SOAP, RSS and POX.

New Controls:

The List View and Data Pager are new controls added along with a new data source control called the Line Data Source.

Page 24: centralised transaction information system

List View:

The List View control is quiet flexible and contains features of the Grid view, Data grid, Repeater and similar list controls available in ASP.NET 2.0. It provides the ability to insert, delete, page (using Data Pager), sort and edit data. However one feature of the List View control that stands apart, is that it gives you a great amount of flexibility over the markup generated. So you have a complete control on how the data is to be displayed. You can now render your data without using the <table> tag. You also get a rich set of templates with the List View control.

Grid View:

Data Pager provides paging support to the List View control. The best advantage is that you need not have to keep it ‘tied’ with the control on which the paging is being done. You can keep it anywhere on the page.

Data Pager gives you a consistent way of paging with the controls that support it. Currently only List View supports it as it implements the Page able Item Container. However support is likely to be added to other List controls as well.

2.4.2 ASP.NET Merge Tool:

ASP.NET 3.5 includes a new merge tool (aspnet_merge.exe). This tool lets you combine and manage assemblies created by aspnet_compiler.exe. This tool was available earlier as an add-on.

New Assemblies:

The new assemblies that would be of use to ASP.NET 3.5 developers are as follows:

         System.Core.dll - Includes the implementation for LINQ to Objects         System.Data.Linq.dll - Includes the implementation for LINQ to SQL         System.Xml.Linq.dll - Includes the implementation for LINQ to XML         System.Data.DataSetExtensions.dll - Includes the implementation for LINQ to Data Set        System.Web.Extensions.dll: Includes the implementation for ASP.NET AJAX (new

enhancements added) and new web controls as explained earlier.

Some Other Important Points:

1.    ASP.NET 3.5 provides better support to IIS7. IIS7 and ASP.NET 3.5 modules and handlers support unified configuration.

2.    You can have multiple versions of ASP.NET on the same machine.

Page 25: centralised transaction information system

3.    For those who are wondering what happened to ASP.NET 3.0, well there isn’t anything called ASP.NET 3.0.

4.    VS 2002 worked with ASP.NET 1.0, VS 2003 worked with ASP.NET 1.1, and VS 2005 worked with ASP.NET 2.0. However VS 2008 supports multi-targeting, i.e. it works with ASP.NET 2.0, and ASP.NET 3.5. 

2.5 C# .net:

C# (pronounced C Sharp) is a multi-paradigm programming language that encompasses functional, imperative, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft as part of the .NET initiative and later approved as a standard by ECMA (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure.

C# is intended to be a simple, modern, general-purpose, object-oriented programming language. Its development team is led by Anders Hejlsberg, the designer of Borland's Object Pascal language. It has an object-oriented syntax based on C++ and is heavily influenced by Java. It was initially named Cool, which stood for "C-like Object Oriented Language." However, in July 2000, when Microsoft made the project public, the name of the programming language was given as C#. The most recent version of the language is 3.0 which was released in conjunction with the .NET Framework 3.5 in 2007. The next proposed version, 4.0, is in development.

Features of C#:

By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or FORTRAN. In practice, all existing compiler implementations target CIL.

Page 26: centralised transaction information system

Some notable C# distinguishing features are:

There are no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.

C# supports a strict Boolean data type, Boolean. Statements that take conditions, such as while and if, require an expression of a Boolean type. While C++ also has a Boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to Boolean, allowing a to be an integer, or a pointer. C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly Boolean can prevent certain types of programming mistakes such as if (a = b) (use of = instead of ==).

In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one which has been garbage collected), or to random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the System IntPtr type, but it cannot dereference them.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses memory leaks by freeing the programmer of responsibility for releasing memory which is no longer needed. C# also provides direct support for deterministic finalization with the using statement (supporting the Resource Acquisition Is Initialization idiom).

Multiple inheritances are not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication, avoid dependency hell and simplify architectural requirements throughout CLI.

C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers and conversion from a derived type to a base type.

Page 27: centralised transaction information system

This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between Booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default.

Enumeration members are placed in their own scope. C# provides properties as syntactic sugar for a common pattern in which a pair of methods,

access or (getter) and mutator (setter) encapsulate operations on a single attribute of a class. Full type reflection and discovery is available. C# currently (as of 3 June 2008) has 77 reserved words.

2.6 SQL EXPRESS 2005:

Microsoft SQL Server Express is the freely-downloadable and distributable version of Microsoft's SQL Server relational database management system. It offers a database solution specifically targeted for embedded and smaller-scale applications. Unlike its predecessor, MSDE, there is no concurrent workload governor which “limits[s] performance if the database engine receives more work than is typical of a small number of users." It does, however, have a number of technical restrictions which make it undesirable for large-scale deployments, including:

Maximum database size of 4 GB per database (compared to 2 GB in the former MSDE). The 4 GB limit is per database (log files excluded) and can be extended in some scenarios through the use of multiple interconnected databases.

Hardware utilization limits: o Single physical CPU, multiple coreso 1 GB of RAM (runs on any size RAM system, but uses only 1 GB)

Absence of SQL Server Agent Service

Although its predecessor, MSDE, was virtually devoid of basic GUI management tools, SQL Server Express includes several GUI tools for database management. Among these tools are:

SQL Server Management Studio Express SQL Server Configuration Manager SQL Server Surface Area Configuration tool

Page 28: centralised transaction information system

SQL Server Business Intelligence Development Studio.

A relatively late addition to the SQL Server Express product line is a reduced functionality version of SQL Server Reporting Services, but features such as Analysis Services, Integration Services, and Notification Services are only available in the "Standard" edition and higher editions.

Features of SQL Server 2005:

1) Reporting Services:-In SQL Server Reporting Services increase there benefit to customers. These include centralized report storage and management, control over how reports are processed or administered, and also have ability to fastest changing reports formats (HTML, Excel, PDF, etc.). This entire capabilities make reporting Services is valuable. So Web-based reporting has ability to make up-to-date information available to a distributed group of users. Reporting Services provides a impressive way to find and view reports, the Reporting Services interface may not be the most appropriate one for all report users.

2) Partitioned Tables and Indexes:-SQL Server 2005 has ability to partition tables and indexes have always been a design to improve performance and manageability in larger databases. Microsoft SQL Server 2005 has many new features that simplify the design of using this feature.

3) Xml Web services:-SQL Server 2005 provides a standard method for getting the database engine by using SOAP via HTTP. With the help of this methods, we can send SOAP/HTTP requests to SQL Server to execute stored procedures, extended stored procedures, T-SQL batch statements and scalar-valued user-defined functions which can have with or without parameters .When we use SQL Server as a Web Service that can for HTTP SOAP requests requires must create an HTTP endpoint and defining the methods that the endpoint exposes. When we create HTTP endpoint, that endpoint must be created with a unique URL that we uses to listen for incoming HTTP requests.

4) Database Mirroring:-Database mirroring provides solution to provide high availability at the database level where all things depends upon the database. In SQL Server we can maintained synchronized copies of a database on two separate servers allows switching between them. And its plays its role on failure of primary server.

5) CLR Integration:- Microsoft SQL Server 2005 has adopt the database programming model hosting by the Microsoft .NET Framework 2.0 Common Language Runtime (CLR). .Net CLR hosted inside

Page 29: centralised transaction information system

SQL Server to improve performance, security and reliability. This helps developers to write procedures, triggers, and functions in any of the CLR languages.

2.7 DATA NORMALIZATIONS:

Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored.

First Normal Form (1NF):First normal form (1NF) sets the very basic rules for an organized database:

Eliminate duplicative columns from the same table. Create separate tables for each group of related data and identify each row with a unique

column or set of columns (the primary key).

Second Normal Form (2NF):Second normal form (2NF) further addresses the concept of removing duplicative data:

Meet all the requirements of the first normal form. Remove subsets of data that apply to multiple rows of a table and place them in separate tables. Create relationships between these new tables and their predecessors through the use of foreign

keys.

Third Normal Form (3NF):Third normal form (3NF) goes one large step further:

Meet all the requirements of the second normal form. Remove columns that are not dependent upon the primary key.

Fourth Normal Form (4NF):Finally, fourth normal form (4NF) has one additional requirement:

Page 30: centralised transaction information system

Meet all the requirements of the third normal form. A relation is in 4NF if it has no multi-valued dependencies.

Page 31: centralised transaction information system

3.1 INTRODUCTION ON CENTRALIZED TRANSACTION INFORMATION

SYSTEM:

Page 32: centralised transaction information system

The payment transaction centralized control system — is a system for forwarding all payment documents to an enterprise's Head Office from its branches via Raiffeisen Bank Aval's branch network. The aim is expediency and timeliness, as well as compliance of out-going payment documents with the enterprise's corporate standards. Payment is then made (or rejected) by the Bank's relevant division.

The centralized system users:

Raiffeisen Bank Aval offers users of its system of centralized control of payment transactions:

The issue of a consolidated statement of the accounts of the enterprise's structural divisions to its Head Office, which guarantees the analysis of out-going payment documents and earnings in all of the enterprise's structural divisions;

Specified purpose of payment, which allows the analysis of various entries in all structural divisions.

The payment transaction centralized control system operates via the Client-Bank channels; the Bank installs relevant software free of charge.

Centralized transaction provide facility to admin is type of online Shoppe where we purchase new trends and new age clothes jewelries, Men item Women item every type of Male & female materials can be available here. Shopping cart for fashion special online store for whose people whose want new fashion and like new fashion items. This web site has two phases first is Admin and Second is user.

Centralized transaction basically provides the way administrator control transaction and view different activity on different center.

ADMINISTRATOR FEATURES:

Control and confirm all out-going payment documents (or a random selection thereof) from their locations;

Page 33: centralised transaction information system

Optimize their cash flows;

Reduce expenditures.

Additional services:

Page 34: centralised transaction information system

3.Existing System

Introduction

This product is going to be developed because the client required a system which should be simple and easy to

understand. The existing system which is present is the one that handles different hotel bookings manually by the user

on the site. But this system is very difficult to understand and use. So client provide us the details about the system,

which he wants to make.

Existing Software

Limitations of Existing System

Timing and retrieving problem: Retrieval of information is very time consuming, because of large volume of

data. Thus if it is required to trace a particular record, a large number of records need to be scanned. The

processing speed was slow. It takes long time to get End-results whereas in Hotel Booking we get the results in

few seconds.

Redundancy: In existing system data is maintained on registers/sheets. This often leads to considerable

redundancy in the stored data, thus leading to wastage of storage space. Generating Reports for the particular

instance is difficult. Reporter has to collect information from many formats and files and hence it will take long

time to design the reports where as in Hotel Booking Web application a different Module is specified for each

and every action and user can book hotels at any time without any chaos and difficulty.

Problem of updating : In existing system since everything is stored on paper so it’s quite difficult and time

consuming to update the data about any particular record.

Maintenance of data : Maintenance of data is very difficult. As daily many hotel vacancies are to be examined,

so it is very difficult to search and trace the vacancies according to one’s requirements when required.

Page 35: centralised transaction information system

Security problem : There is no security in the existing system because any one read the booking details where

the all information is written.

Difficulties in debugging the errors : There are more chances for debugging the errors in existing system as

compared to computerized system.

Page 36: centralised transaction information system

4.Problem analysis

Product Definition:

Product will be used by web based companies. Here product means a new project. The interaction will be taken place

between client and developers. Client will search new hotels from the hotel booking software. Product will be assigned

to product related team. There will be a team leader who will lead the members. Whole product will be divided into

small tasks and those tasks will be assigned to team members. After completion of task team member will update the

task status. By using all these convention it’s very easy to manage a product.

Feasibility Study:

Feasibility study involves analysis of the proposed system as a candidate solution to the problem domain so as to

identify, describe, evaluate and assess system and thus enabling to select the best system the solution domain. Our

Feasibility study must answer three key questions: -

Is there a new and better way to do the job that will benefit the user?

What are the costs and savings of the alternatives?

What is recommended?

The two considerations are involved in the feasibility analysis: technical and behavioral feasibility.

Types of Feasibility:

There is various measure of feasibility that helps to decide whether a particular project is feasible or

not. These measure include-

Operational Feasibility

Page 37: centralised transaction information system

Technical Feasibility

Economical and Financial feasibility

Operational Feasibility

A proposed system is beneficial only if it can be turned into an information system that will meet the

operational requirements of an organization. A system often fails if it does not fit within existing

operations and if user resists the changes.

Important issues a system developer must look are:

Will the new system be used if implemented in an organization?

Whether the system provides right information to the right place

Whether the new system affects the current users in the system

Online Hotel Booking is developed keeping in mind about all these requirements.

The application developed will be fully implemented in the organization and it will not fail to user

specific Results and it is adaptable to change as per the current needs when we make changes.

Technical Feasibility

Based on outline design of system requirements in terms of inputs, outputs, files and procedures, the

technical issues raised during technical feasibility include:

Page 38: centralised transaction information system

Does the necessary technology exist to do what is proposed?

Does the proposed equipment have the technical capacity to hold the data required to use a new

system?

Adequate responses provided by the proposed system?

Is the system flexible enough to facilitate expansion?

Is there any technical guarantee of accuracy, reliability, ease of access and data security?

The Solution developed to conduct the booking of hotels is technically feasible as

per all the requirements are fulfilled corresponding to the software as well as the hardware

requirements. The System is flexible to be executed on the Systems when they fulfill the minimum

requirements as mentioned before and work will when system is expanded too

Economical Feasibility

In making recommendation a study of the economics of the proposed system must be justifiable in

terms of cost and benefit, to ensure that the investment in a new/changed system provide a reasonable

return.

In our proposed system various costs are evaluated, even though finding out the cost of the proposed

project is difficult we assume and estimate the costs and benefits as follows:

Cost associated with the development of the system

Page 39: centralised transaction information system

Costs associated with operating the system

Project Plan

Page 40: centralised transaction information system

Development Schedule

The following steps were followed in developing the application:

Study, Analysis and Requirement Specifications: The study of the existing system and its drawback gave an idea

about what kind of interface was required. The study was conducted through information gathering and studying

the existing system.

Design of the proposed system: The next step was to design the screen, windows and reports for the inputs and

outputs. The concerned authorities consulted during the design phase to ensure client acceptances and not to miss

out on any vital information. In the same phase, the project was broken down into various modules.

Coding of the design system: A modular approach was followed, where, in each module, a well-defined procedure

was developed independently. These modules were developed to use the same database file structure to ensure

integrity.

Page 41: centralised transaction information system

System documentations: This stage consists of documenting the layout of entire system. It indicated the purpose

of interlinking of different modules along with the integration of the entire system.

Testing and Debugging: Preliminary test were done with the self-generating dummy data. After identifying and

removing errors, it was tested for all activities together.

Page 42: centralised transaction information system

Module Wise partitioning of Project:

The whole Project was divided into following modules:

Home Page handling Module.

Search Module.

Book Now Module.

Hotel Partners.

Portal Admin

Miscellaneous.

Page 43: centralised transaction information system

5.Software Requirement Analysis

Introduction

In the software requirements specification we states the goals and objectives of the software. The main objective of this “Centralized Transaction Information System ” is to meet the client’s requirement. The function and performance allocated to software part of system engineering are refined by establishing a complete information description, a detailed functional description, a representation of system behavior, an indication of performance requirement and design constraints appropriate validation criteria, and other information pertinent to requirement. The software requirement specification is produced at the culmination of the analysis task.

A description of each function required to solve the problem is presented in the Functional Description. So with the

help of this we are able to solve all the problems of the Centralized Transaction Portal. Validation Criteria is probably

the most important and ironically the most often neglected section of the software requirement specification. In this we

use all the validation that is required by the software so that no one should be able to enter the wrong data into the

software.

General Description

Centralized Transaction Information Portal refers to a group of software development methodologies based on iterative

development, where requirements and solutions evolve through collaboration between self-organizing cross-functional

teams. Each team works through a full software development cycle including planning, requirements analysis, design,

coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders. Multiple iterations

may be required to release a product or new features.

Now according to client requirement this site contain following different sections :

1) Dealing with the Home Page 2) Search facility3) Book now facility4) Hotel Admin Section5) Miscellaneous section

Page 44: centralised transaction information system

Hotels Admin does following tasks:

Handle a hotel profile and hotel information

Update and modify the hotel details

Manage various policies and facilities

User and user roles:

Manage users like normal users or hotel users

Manage user roles

The software development technologies used in the project are as follows:

ASP.NET HTML CSS SQL SERVER Windows XP Operating System with IIS Web Server.

Hardware Requirement:

Micro Processor : Pentium Processors 2.1 GHz (above)

RAM : 512 MB (recommended)/ above

Storage : 12GB in Hard Disk Drive

Software Requirement:

Environment : Windows XP Professional Service Pack 2/ above

Page 45: centralised transaction information system

Technology : ASP.NET3.5 (Visual Studio 2008), .Net Framework

Database services : SQL Server 2005/above

Page 46: centralised transaction information system

6.Design

System Design

System design refers to the designing of the system it begins when feasibility study is completed. Basically it is divided

into two parts, such as:

Logical design: It specifies the design of input and output files design databases.

Physical design: It specifies the coding part when logical design is complete this begins. It done to see that whether the

current of proposed system will work according to the needs of the user or not.

Design Notations

Data flow diagram is graphical tool used to describe and analyze the movement of data through system –

manual or automated- including the process, stores of data and delays in the system. Data flow diagrams are

the central tool and the basis from which other components are developed. The transformation of data from

input to output through process may be described logically and independently of the physical components

associated with the system. They are termed logical data flow diagrams.

Components of DFD’s

Data Flow: Data move in a specific direction from an origin to a destination in a form of a document

Page 47: centralised transaction information system

letter, telephone call or virtually any medium.

Process: People, procedures or devices that are used to produce data. The physical component is not

identified

Source or Destination of Data: External sources or destinations of data which may be people,

programs, organizations or other entities, interact with the system but are outside its boundary. The

term source and sink are interchangeable with origin and destination.

Data Store: Here data are stored or referenced by a process in the system. The data store may

represent computerized or non-computerized devices.

Cardinality and Modality

Cardinality:

The data model must be capable of representing the number of occureences of objects in a given relationship. The

cardinality of the object relationship pair is:

One to One(1:1): An occurrence of object ‘A’ can relate to one and only one occurrence

of object ‘B’ and vice-versa.

One to Many(1:N): An occurance of object ‘A’ can relate to one or many occurrences of

object ‘B’ and vice-versa but an occurrence of object ‘B’ can relate to only one

occurrence of object ‘A’.

Many to Many(M:N): An occurrence of ‘B’ can relate to one or many occurrences of

‘A’ and vice versa

Modality

The modality of a relationship is zero if there is no explicit need for the relationship to occur or the relationship is

optional. The modality is 1 if the relationship is mandatory.

Page 48: centralised transaction information system

The object relationship pair can be represented graphically using the Entity Relationship Diagrams.

A set of primary components are identified for the Entity Relationship Diagram

1. Attribute

2. Relationships

3. Various type of indicators

DFD SYMBOLS:

= Source or Destination of data

= Data flow

= Process that transform data flow

=DATABASE

After I finished the database design, the next step was the architectural design. The method we chose was to draw the

DFD (Data Flow Diagram).

Detailed Design

Database Design

Page 49: centralised transaction information system

The core of this project is the database design. Basically for management software, users only communicate with

database through interface. Whether your database is designed reasonable and sufficient will have a direct effect on the

quality of the product. Conceptual modeling is an important phase in designing a successful database application.

Design just followed the traditional approach of concentrating on the database structures and constraints. All together

there are three entities: employee, project and task, represented by rectangles. Each entity has its own attributes,

represented by eclipses; the key attribute is represented by a bolded eclipse. Those entity attributes are indispensable

information that is necessary to manage project.

Page 50: centralised transaction information system

7.Testing

Software testing is an investigation conducted to provide information about the quality of the product or service under test. Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results Software Testing is the process of executing a program or system with the intent of finding errors.

Objectives of Testing

Testing is a process of executing a program with the intention of finding errors.

To perform testing, test cases are designed. A test case is in particular made up of

artificial situation upon which a program is exposed so as to find errors. So a good test

case is one that finds undiscovered errors.

Techniques of Software Testing

Unit Testing

In this phase of testing, separate units of software system are tested. This is also known as component

testing in which each module is tested alone to find any error in its source code. Programmer performs

this testing as part of the development life cycle.

Integration Testing

This testing is done to test the communication between different components of the software; all the

modules that a program comprises are being brought together to test whether they are functioning in

correct order with their counterpart.

System Testing

Page 51: centralised transaction information system

This level of testing is done to test the functionality of software as a complete system. System testing

is entirely different then integration testing. In integration testing interaction of component are tested

while in system testing interaction of complete software with the system is tested. Besides system

functionality and behavior, system testing may include testing configuration, throughput, security,

resource utilization, and performance.

Black-box test design

It treats the system as a "black-box", so it doesn't explicitly use knowledge of the internal structure.

Black-box test design is usually described as focusing on testing functional requirements. The

research in black-box testing mainly focuses on how to maximize the effectiveness of testing with

minimum cost

White-box test design

It allows one to peek inside the "box”, and it focuses specifically on using internal knowledge of the software to guide the selection of test data. Testing plans are made according to the details of the software implementation, such as programming language, logic, and styles. Test cases are derived from the program structure. White-box testing is also called glass-box testing, logic-driven testing

Performance testing

Performance has always been a great concern and a driving force of computer evolution. Performance evaluation of a software system usually includes: resource usage, throughput, and stimulus-response time and queue lengths detailing the average or maximum number of tasks waiting to be serviced by selected resources. Typical resources that need to be considered include network bandwidth requirements, CPU cycles, disk space, disk access operations, and memory usage

Reliability testing

Software reliability refers to the probability of failure-free operation of a system. It is related to many aspects of software, including the testing process. Directly estimating software reliability by quantifying its related factors can be difficult. Testing is an effective sampling method to measure software reliability.

Page 52: centralised transaction information system

Security testing

Flaws in software can be exploited by intruders to open security holes. With the development of the Internet, software security problems are becoming even more severe.The purpose of security testing of these systems include identifying and removing software flaws that may potentially lead to security violations, and validating the effectiveness of security measures.

Testing Strategies

Not all the testing works are done at last minute. Some of them are parallel with your coding process. I tested each function separately. Each function in the software is like a module, which is the smallest unit of the software. Basically, all the functions that user can use are linked to the interface. Once the link has been clicked, the corresponding function will be called. The interface is acting as the driver for the unit testing, and there is no stub needed in this case. Because the units in this project are not based on each other, so no integration testing was applied. After I finished my own testing for each module tested the software as a user. He used alpha test, which means I was recording the usage problems and errors 2 1 when he did the testing. Then I corrected the errors and solved the usage problems. Then we did the same process again until the final version.

a) Functional Testingb) Structural Testingc) Levels of testingd) Testing of the Project

Page 53: centralised transaction information system

8.Implementation

Implementation is the process of having professional checkpoints and put new equipments into user,

trained user, install, the new application and constructs any files or data needed to use it.

This phase is less creative then system design. It’s mainly concerned with user training site

preparation and file conversions. Depending on the size of the organization that will involve in using

the application, the risks involved in its use. System developers may choose to test the operation in

only one area of the firm with only one or two persons. Sometimes they may run an old or new system

in parallel way to compare the results. In other situation system developers stop using the old system

one-way and start using the old system the other way.

During the final step user acceptations is tested followed by user training depending upon the

nature of the system extensive user training may be required. Conversion usually takes place at about

the same time the user is being trained or later. System testing checks the readiness and accuracy of

the system to access update and retrieve data from new files. Once the program becomes available,

test data are used for testing. If successful the program are run with actual live data.

The Online Centralized Transaction Information System is under development right now. So it’s running

on company’s server. The server link is http://www.athpatna.com. So this software is not on client’s

server.

Post Implementation

After installation phase is complete and user staff is adjusted to the changes traded by the new system,

evaluation and maintenance starts.

Like any other system, this is an aging process that requires periodic maintenance of hardware and

software. If the new information is inconsistent with the design specification maintenance to keep it

tuned with the design specification. The importance of the maintenance is to continue, to bring the

Page 54: centralised transaction information system

new system to the standards. User priority changes in the organizational programs or the

environmental factors also caught for the system analysis.

Maintenance is necessary to eliminate errors in the working system. During its working live and to

tune the system to any variations in it’s working environment. Often small system is brought to the

operation and changes are made to remove them.

System planners must always plan them for resources availability to carry out their maintenance function. The importance of maintenance is to continue to bring new system to standard.

a) Implementation of the project b) Conversion Planc) Post – implementation and Software Maintenance

Page 55: centralised transaction information system

9.Project Legacy

Current Status of the Project

The project is under development with number of database tables as well as transaction tables

and a number of screens and reports. Enhancements can be done if required but the project is yet

to be implemented. Rough Documentation has being prepared. Following acceptance criteria has

fulfilled.

User friendly: It means the user does not need to over work hard to understand more

about it to do a particular task. The user can easily interface with the software to complete their

work.

Modularity: The modules are interconnected with each others. It makes the task easier.

The main page consists of entering into the profile of any individual or any institutions. This

page consists of sign in (username and password) into the software. If the user has a profile

he/she has to enter its username and password, then the user can access his/her account and its

work done. If the user does not have his/her account, its privilege to admin to create user.

Transparency: No one can view others account. One can view all the content of his/her

own account. Only admin is able to see everyone status. Other user’s have different permissions

according to their work. User’s will complete their tasks and update the tasks status. In this project

management system there are different level of user which will use this software according to their

need and requirement.

Security: Because no one can view the content of others account without privilege, so this system is more secured. All the update related your blog in your own hand. Hosting PHP applications on a server requires a careful and constant attention to deal with these security risks. There are advanced protection patches for web hosting environments.

Page 56: centralised transaction information system

Technical Lessons Learnt

Extensive knowledge .Net

Knowledge of SQL Server 2005.

Knowledge of HTML.

Knowledge of C#.

SNAPSHOTS:

Page 57: centralised transaction information system

Snap shot for home page:

Snap shot for sign in page:

Page 58: centralised transaction information system

Snap shot of admin Kolkatta:

Page 59: centralised transaction information system

Snap shot of different section:

Page 60: centralised transaction information system

Snap shot for account:

Page 61: centralised transaction information system

Snap shot for alignment:

Page 62: centralised transaction information system

Snap shot for carriage:

Page 63: centralised transaction information system

Snap shot for cash flow:

Page 64: centralised transaction information system

Snap shot for party outstanding:

Page 65: centralised transaction information system

Snap shot for taxation:

Page 66: centralised transaction information system

Snap shot for Transaction:

Page 67: centralised transaction information system

Snap shot for Vechile no:

Page 68: centralised transaction information system

Snap shot for voucher:

Page 69: centralised transaction information system
Page 70: centralised transaction information system

11. Bibliography

[1] www.asp.netspider.com

[2] www.c#codeproject.com

[3] www.quickstart.asp.net

[4] www.msgn.microsoft.com

[5] www.google.com

[6] www.w3school.com