1

ACKNOWLEDGMENT
The Satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose co-operation made it possible, whose constant guidance and encouragement crown all efforts with success. I am grateful to our Principal Mrs. TARANJEET KAUR SOOD and our head of department Prof. APARAJITA RANA. I am also thankful to our project guide Prof. TIMSY KAPOOR for guidance, inspiration and constructive suggestion that helped us in the preparation of this project and also thanks to Prof. NIDHI ARORA for their support and suggestion. I thank my parents and family who have always been co-operating and understanding. I also thank my colleagues who have helped in successful completion of the project.

TEENA DIXIT RAMANDEEP JUNEJA RUCHI KAMBLE

INDEX
TABLE OF CONTENTS

CHAPTER1 INTRODUCTION Overview of Internship . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Origin of the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Organization Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3

CHAPTER2 OBJECTIVE AND METHODOLOGY Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2

CHAPTER3 INTRODUCTION OF TECHNOLOGIES

CHAPTER4 REQUIREMENT SPECIFICATION Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Non-Functional Requirements. . . . . . . . . . . . . . . . . . . . . . . . 3.3 CHAPTER5

FEASIBILITY REPORT Technical Feasibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Economic Feasibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Operational Feasibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 CHAPTER6 PROCESS MODELING Context level DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 System diagram or Diagram o . . . . . . . . . . . . . . . .... ..5.2 CHAPTER7 FLOWCHART E-R DIAGRAM CHAPTER8 IMPLEMENTATION AND TESTING CHAPTER9 CONCLUSION References

CHAPTER 1 INTRODUCTION
This project of LIBRARY MANAGEMENT of gives us the complete information about the library. We can enter the record of new books and retrieve the details of books available in the library. We can issue the books to the students and maintain their records and can also check how many books are issued and stock available in the library. In this project we can maintain the late fine of students who returns the issued books after the due date.

1.1 Overview of Internship Internship refers to the employment of students nearing under-graduation in firms organizations, which operate on activities related to the respective students major subjects. The objective of enabling students to come into contact with real life applications regarding the knowledge and skills gained in both theoretical and practical courses of the university. The core courses of Computer Science are mainly theory-based and aid in providing a theoretical concept or base to the students so that they are equipped with sufficient knowledge for joining the work force after completion of under-graduation. Internship helps the students familiarize them with the experience of being employed in their field and effectively learning and applying the knowledge required carrying out their activities in the office. There are various reasons behind assigning students the course of Internship. The general objectives are outlined as follows: 1 Helping students break free from the theoretical world of textbooks and class courses and leap into the real world of applications of knowledge. 2 Enabling the students to effectively interact in a work environment within a hierarchy of employees. The efficiency in working in groups and under higher authorities is tested during this course. 3 Helping students to express dependability, initiative, resourcefulness and professionalism in the tasks they are assigned.

4 To evaluate the persons ability to communicate and operate under pressure, if required. 5 To help students enhance their creativity and efficiency in dealing with projects related to their field of study. 6 To enable students to pick up skills from the experience and projects of other employees to apply in their own tasks. It is extremely important for the person to be able to learn and apply the skill at the same time. Whether the interns have adequately fulfilled one or more of these objectives supervisors evaluate them after the viva voce. 1.2 Origin of the Report This report has been prepared as a requirement of the internship program. The report was based upon the LIBRARY MANAGEMENT. The topic, which was decided for doing the report, was duly approved by my institute supervisor. The report will definitely increase the knowledge of other students to know about LIBRARY MANAGEMENT SYSTEM.

CHAPTER 2 OBJECTIVE AND METHODOLOGY 2.1 Objective The main objective of the application is to automate the existing system of manually maintain the records of the Book Issue, Book Return from the student, Catalog and Book Search to be computerized. So the Book Issue, Return, Searching will be faster.

2.2 Methodology In general, Methodology is a systematic description of the sequence of activities required to solve a problem. In context to system development, methodology is a collection of procedures, techniques, tools and documentation aids, which help these system developers in their efforts to implement a new information system. The methodology that I have followed to develop the system was not specific one. It can be said that the methodology followed was a hybrid of the System approach and Prototyping approach. The circumstances that lead me to take a hybrid approach are given below. A-----The System approach: 1. Many important features of the system were readily identified before the development began 2. Data requirements were possible to be identified in advance. b-----The Prototyping approach: 1. The system had to be developed quickly and at the lowest possible cost. 2. Users had little experience with the type of system to be developed. 3. The risk associated with delivering wrong system was high.

There are two major activities in the system approach: Analysis and Design. As per the traditional (system) approach I have at first done the requirement analysis of the system. The purposes of the analysis are to: Understand the components & functions of the system. Identify the organizations information and processing needs. Determining the characteristics of the new system to meet these needs. After that I have developed a model of the system, which is partially automated and manual. A model is a representation of the real-world element, group of elements and the relationship among them. Models help us to frame our thinking and understanding about the real world. As Management Information System (MIS) is very complex, it helps us to use models to simplify and clarify the system. There are four types of models such as graphical model, mathematical model, narrative model, and physical model. I have represented the process model of the new system using Graphical models. Graphical models generally use such symbols as icons, boxes and lines tore present real-world elements and relationships. Data -Flow Diagrams (DFDs) are widely used by system nalysts to graphically represent information system. These graphical models show how data or information moves from one process to another in an organizational system. They are useful for showing how system work and are often used by system analysts both to design systems and to clarify to users to users, programmers and other system analysts about the way how components of the system fit together. Usually DFDs give logical description of the system. From the DFDs I have identified which processes of information system will be automated in order to meet the requirements.

Chapter 3 INTRODUCTION OF TECHNOLOGIES This project is oriented towards delivering the fundamental knowledge of all the resources, tools & concepts used for developing the project. It gives brief idea about LIBRARY MANAGEMENT System. LANGUAGE USED: MS SQL SERVER: Microsoft SQL Server is a relational database server, developed by Microsoft: it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for different workloads (ranging from small applications that store and retrieve data on the same computer, to millions of users and computers that access huge amounts of data from the Internet at the same time). True to its name, Microsoft SQL Server's primary query languages are T-SQL and ANSI SQL. Microsoft SQL Server 2000 is a full-featured relational database management system (RDBMS) that offers a variety of administrative tools to ease the burdens of database development, maintenance and administration. In this article, we'll cover six of the more frequently used tools: Enterprise Manager, Query Analyzer, SQL Profiler, Service Manager, Data Transformation Services and Books Online. Let's take a brief look at each: Enterprise Manager is the main administrative console for SQL Server installations. It provides you with a graphical "birds-eye" view of all of the SQL Server installations on your network. You can perform high-level administrative functions that affect one or more servers, schedule common maintenance tasks or create and modify the structure of individual databases. Query Analyzer offers a quick and dirty method for performing queries against any of your SQL Server databases. It's a great way to quickly pull information out of a database in response to a user request, test queries before implementing them in other applications,

create/modify stored procedures and execute administrative tasks. SQL Profiler provides a window into the inner workings of your database. You can monitor many different event types and observe database performance in real time. SQL Profiler allows you to capture and replay system "traces" that log various activities. It's a great tool for optimizing databases with performance issues or troubleshooting particular problems. Service Manager is used to control the MSSQL Server (the main SQL Server process), MSDTC (Microsoft Distributed Transaction Coordinator) and SQL Server Agent processes. An icon for this service normally resides in the system tray of machines running SQL Server. You can use Service Manager to start, stop or pause any one of these services. Data Transformation Services (DTS) provide an extremely flexible method for importing and exporting data between a Microsoft SQL Server installation and a large variety of other formats. The most commonly used DTS application is the "Import and Export Data" wizard found in the SQL Server program group. Books Online is an often overlooked resource provided with SQL Server that contains answers to a variety of administrative, development and installation issues. It's a great resource to consult before turning to the Internet or technical support. Hopefully, this article has provided you with a brief introduction to the various tools available to Microsoft SQL Server users. Now get out there and give them a whirl

VISUAL BASIC: VISUAL BASIC is a high level programming language which evolved from the earlier DOS version called BASIC. BASIC means Beginners' All-purpose Symbolic Instruction Code. It is a very easy programming language to learn. The code looks a lot like English Language. Different software companies produced different versions of BASIC, such as Microsoft QBASIC, QUICKBASIC, GWBASIC, and IBM BASICA and so on. However, people prefer to use Microsoft Visual Basic today, as it is a well developed programming language and supporting resources are available everywhere. Now, there are many versions of VB exist in the market, the most popular one and still widely used by many VB programmers is none other than Visual Basic 6. We also have VB.net, VB2005, VB2008

10

and the latest VB2010. Both Vb2008 and VB2010 are fully object oriented programming (OOP) language. VISUAL BASIC is a VISUAL and events driven Programming Language. These are the main divergence from the old BASIC. In BASIC, programming is done in a text-only environment and the program is executed sequentially. In VB, programming is done in a graphical environment. In the old BASIC, you have to write program code for each graphical object you wish to display it on screen, including its position and its color. However, In VB , you just need to drag and drop any graphical object anywhere on the form, and you can change its color any time using the properties windows. On the other hand, because the user may click on certain object randomly, so each object has to be programmed independently to be able to response to those actions (events). Therefore, a VB Program is made up of many subprograms, each has its own program code, and each can be executed independently and at the same time each can be linked together in one way or another. Like the BASIC programming language, Visual Basic was designed to be easily learned and used by beginner programmers. The language not only allows programmers to create simple GUI applications, but to also develop complex applications. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. Although VB programs can be compiled into native code executables from Version 5 onwards, they still require the presence of runtime libraries of approximately 1 MB in size. Runtime libraries are included by default in Windows 2000 and later, however for earlier versions of Windows, i.e. 95/98/NT, runtime libraries must be distributed together with the executable. Forms are created using drag and drop techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created,

11

but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a key press in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted. Visual Basic can create executables (EXE files), ActiveX controls, or DLL files, but is primarily used to develop Windows applications and to interface database systems. Dialog boxes with less functionality can be used to provide pop-up capabilities. Controls provide the basic functionality of the application, while programmers can insert additional logic within the appropriate event handlers. For example, a drop-down combination box will automatically display its list and allow the user to select any element. An event handler is called when an item is selected, which can then execute additional code created by the programmer to perform some action based on which element was selected, such as populating a related list. Alternatively, a Visual Basic component can have no user interface, and instead provide ActiveX objects to other programs via Component Object Model (COM). This allows for server-side processing or an add-in module. The runtime recovers unused memory using reference counting which depends on variables passing out of scope or being set to "Nothing", resulting in the very common problem of memory leaks. There is a large library of utility objects, and the language provides basic object oriented support. Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table. String comparisons are case sensitive by default.

12

Chapter 4 REQUIREMENT SPECIFICATION My requirement analysis founded a base on the new Information System that is to be implemented and provided me the guidelines to move further on developing my project. The answers that I get from the analysis are as described below. 3.1 Scope The main purpose of the Premier Bank Credit Card division and information service is to provide the customers financial flexibility, worldwide acceptance and round-the-clock convenience. Premier Bank issues only VISA Credit Cards, the renowned Credit Card brand. Cardholders can purchase goods/services up to the credit limit and can reuse the credit facility upon repayment. Credit Card is a safer substitute to cash and is the major mode of payment worldwide. Standard Chartered Bank is the first to introduce the TAKA CREDIT CARD. The card is issued basically to a persons name and the specific person can use the card in anywhere in India. The business activity of Premier Bank Credit Card section is to keep the records of all sales and customers requests, the information of cardholders and reports them to necessary documents. 3.2 Functional Requirements The functional requirements are organized in two sections; Requirements of the ATM and Requirements of the bank computer. Requirements of the ATM authorization process transaction (withdrawal process) Requirements of the bank computer authorization process (bank code and password) Transaction 3.2.1 HARDWARE REQUREMENTS Processor : Pentium III 630MHz

13

RAM Hard Disk Monitor Key board Printer

: : : : :

128 MB 20GB 15Color monitor 122 Keys Laser Printer

3.2.2 SOFTWARE REQUIREMENTS Operating system : Windows NT/XP/2007 Front End: Visual Basic 6.0 Back End: SQL SERVER 2000

3.3 Non-functional Requirements The non-functional requirement is bellowed. The ATM network has to be available 24 hours a day. Each bank may be processing transactions from several ATMs at the same time. The ATM must be able to use several data formats according to the data format that are provided by the database of different banks.

3.4 TECHNOLOGY SPECIFICATION Client-server Architecture: 2-Tier Architecture: - The two-tier application programming model was developed to enhance the file server application programming model. As compared with the file server application programming model, the two-tier application programming model provides you with improved usability, scalability, and flexibility of applications.

14

In Two-Tier model, you will have two separate layers namely Client & Server. The application developed using the two-tier application programming model have a user friendly interface. These application can support only a few users and allow data to be shared within a homogeneous environment.

3-Tier Architecture: - 3-Tier client-server architectures have 3 essential components: 1. A Client PC 2. An Application Server 3. A Database Server Tier Architecture Considerations: Client program contains presentation logic only Less resources needed for client workstation No client modification if database location changes Less code to distribute to client workstations One server handles many client requests More resources available for server program Reduces data traffic on the network

15

CHAPTER 4 FEASIBILITY REPORT After the requirement analysis the feasibility study determines whether a proposed system is feasible or achievable, given the organizations resources and constraints. That is why feasibility studies are must for any new and expanding project. This study takes a brief look at the major factor that will influence the ability of the system. It is independent of my initial research, analysis or overall review of any new venture. The three major area of this study is technical feasibility, economical feasibility, and operational feasibility. According to the requirements of the designing of ATM system, it is clear that a large amount of data is to be handled. To maintain all information for all the components a well-designed computerized system is needed. By implementation the system processing data consistency is improved. 4.1 Technical Feasibility In this part, it is ensured whether the existing technical resources hardware, software etc. will support the design of the proposed system. During the component analysis it was found that the Premier Bank uses computers. These computers work under a Local Area Network (LAN) based system. Therefore, it can be concluded that the proposed system is technically feasible. 4.2 Economic Feasibility After analyzing the technical feasibility, the economic feasibility has to be considered. It is very important to take under consideration the cost effect of the system.ATM system is designed and developed by government so Economic feasibility must be cost effective. The estimated cost of this project is two lakh rupees.

4.3 Operational Feasibility In this part, the existing managerial and organizational framework was studied. It was done in order to see whether the proposed system would change the working environment or not. The system, which was going to be implemented, obviously will

16

change the working environment but that must not be drastic and the users must feel comfortable handling and coping with the solution. CHAPTER 5 PROCESS MODELING 5.1 Context Level DFD The context diagram is the highest level in a data flow diagram and contains only one process, representing the entire system. All external entities are shown on the context diagram as well as major data flow to and from them. The diagram does not contain any data stores and is fairly simple to create

17

This diagram shows the Automatic Teller System software and the hardware that it interacts with. The arrows show the direction and type of data flowing between the software and each hardware element. The description of external entities is described below. Control System: This system enables and disables the customer interface and receives customer requests and system reports. A suitable Control System would be a personal computer linked to a central computer system with access to the Accounts Database. The customer interface (keypad, display, etc) is controlled by enabling and disabling the Card Reader, which is the customer's entry-point to the system. Requests for statements and chequebooks are posted to the Control System. It also receives status reports for low printer-paper and cash levels. Card Reader: The Card Reader receives the customer's card and retrieves the PIN and account number stored on it. This information is transmitted to the software system which enables the Customer Keypad and initiates the PIN verification procedure. When business is completed the Card Reader is instructed to return the card. If the customer enters an incorrect PIN, a fixed number of retries is permitted, after which the Card Reader is instructed to confiscate the card Customer Keypad: The Customer Keypad allows a customer to enter a PIN number, select options and enter cash values. The keypad is only enabled when a card is detected in the Card Reader. Customer Display: The Customer Display presents messages, options and reports to the customer. The display is active at all times. Printout Dispenser: This provides the customer with a printed balance or receipt. The Printout Dispenser reports to the system if the paper level is low.

18

Cash Dispenser: This assembles and delivers cash to the customer. The dispenser receives information about the values and quantities of notes to dispense (1 x TK.20, 2 x TK.5, etc). The Cash Dispenser reports to the system if the cash levels are low. 5.2 System Diagram or Diagram 0 System diagram is the explosion of the context diagram. Each process is numbered with an integer, generally starting from the upper left-hand corner of the diagram and working toward the lower right-hand corner. The major data stores of the system (representing master files) and all external entities are included on system diagram. Interact with Operator: This process deals with commands from the system operator. These are the commands which enable or disable the customer interface by controlling the Card Reader. The operator may issue these commands from another computer system or by using a switch on a control panel. Interact with Customer: This process handles all interactions with the customer and operates only when a card is detected in the Card Reader. Input is received initially from the Card Reader and then directly from the customer via the Customer Keypad. The customer receives output from the Customer Display, the Printout Dispenser and the Cash Dispenser .Customer interactions may also involve sending reports to the Control System. The initial step of all customer interactions is to verify the customer's PIN number. After this a menu of options is presented on the display which the customer selects by pressing appropriate keys on the keypad. These options lead to other displays and requests for further input. Some options require account details which are retrieved from the Accounts Database and may also involve updating the database. During the final stage of all customer interactions the Card Reader is instructed to either return or confiscate the card Prepare Command: This process handles communication with the Card Reader hardware. The system requires that the Card Reader is able to receive the following commands:

19

ENABLE Makes the Card Reader ready to receive a card DISABLE Prevents the Card Reader from accepting a card RETURN Ejects a card from the Card Reader RETAIN Confiscates an unauthorized card The Card Reader is enabled and disabled by commands from the system operator. A card is returned or retained in response to interactions with the customer.

Update Display: This process deals with the Customer Display screen. When no card is in the Card Reader, the Customer Display shows general information (such as 'Insert Card').When a card is detected the display is updated in response to customer interactions. If the system is disabled by the system operator, the display is updated to indicate the system status. The following is a list of screens which are shown on the Customer Display. General Information - Insert Card and other messages PIN Verification - Enter PIN message Main Options - Some or all of the following; Display Balance, Print Balance, Cash with Receipt, Cash without Receipt ,Order Statement, Order Cheque book, Return Card Current Balance - Customer's account balance and cleared funds Balance Printed - Take Your Balance message Withdrawal Options - Pre-defined cash amounts and Other Amount option Cash Amount - Enter Amount for cash withdrawal Cash Dispensed - Take Your Cash message Receipt Printed - Take Your Receipt message Statement Ordered - Statement Ordered message

20

Cheque book Ordered - Cheque book Ordered message Card Returned - Take Your Card message Card Retained - Card Retained message (for failed PIN verification) Prepare Message: This process prepares and transmits messages to the Control System. These message scan be requests from customers for statements and cheque books or reports concerning the levels of printer-paper and cash.

Prepare Printout: This process prepares and controls the use of the Printout Dispenser to produce balance reports and receipts. The customer's balance is retrieved from the Accounts Database (if required). If the printer-paper level becomes low options which involve printouts are disabled and a warning message is sent to the Control System. Manage Withdrawal: This process receives requests for withdrawals of specific amounts from a certain account and operates the Cash Dispenser. Before proceeding, the customer's details in the Accounts Database are checked. If the request exceeds the customer's balance (or agreed overdraft) the withdrawal is denied. The system uses a denomination selection algorithm based on the notes available and the amount required. The Accounts Database is updated after each withdrawal. If the cash level becomes low, options providing cash withdrawals are disabled and a warning message is sent to the Control System CHAPTER 6 FLOW CHART AND E-R DIAGRAM Flow-chart: A flow chart is defined as a pictorial representation describing a process being studied or even used to plan stages of a project. Flow charts tend to provide people with a common language or reference point when dealing with a project or process .Four particular types

21

of flow charts have proven useful when dealing with a process analysis: top-down flowchart, detailed flow chart, work flow diagrams, and a deployment chart. Each of the different types of flowcharts tends to provide a different aspect to a process or a task. Flow charts provide an excellent form of documentation for a process, and quite often are useful when examining how various steps in a process work together .When dealing with a process flow chart, two separate stages of the process should be considered: the finished product and the making of the product. In order to analyze the finished product or how to operate the process, flow charts tend to use simple and easily recognizable symbols. The basic flow chart symbols below are used when analyzing how to operate a process. Dig 4-In order to analyze the second condition for a flow process chart, one should use the ANSI standard symbols.

22

Flow chart for Pin validation:-

23

24

ER-DIAGRAM: It is clear that the physical objects from the previous section are interdependent to each other. They are related to each other. However, a good design will minimize redundancy and attempts to store all the required information as small as space as possible E-R Diagram for ATM System:-

25

CHAPTER 7 IMPLEMENTION AND TESTING Implementation Approaches Incremental model: Incremental Modal mainly required to distribute the inventory Management process into parts where each part or step reach a separate objective, as and when one step fulfil, there would be starting of another one to fulfil the further process, thus all incremental steps are correlated amongst them. And each incremental inventory management steps has its own importance for reaching the appropriate, cost control and maintenance of proper and timely inventory. The result of an incremental step will lead to input of next incremental step.

26

Process Model: Incremental Prototype model: In order to make this project we have used prototype model as a software model. The prototype model demands a systematic sequential approach to software development that begins at the basic prototype and Progress through analysis, design, coding, testing & maintenance. This model encompasses the following activities:

27

Black Box Testing This specification describes testing methods which can be used to ensure that the system fulfils the requirements indicated in the project brief. The following procedures are described: 1. 1 Card Authorization 2. Cash Withdrawal (with or without receipt) 3. Display Balance (on screen or printout) 4. Order statement or Cheque book 1. Card Authorization: Before any transactions take place the customer must insert their card into the system and enter their Personal Identification Number (PIN). If the number entered matches the number on the card the customer is allowed to continue with their transaction. If the customer fails to enter the correct PIN their card will be confiscated and a message is sent to the bank's main computer. The customer is allowed three attempts to enter their PIN

OBJECTIVE: To test the PIN verification procedure TEST 1: Enter the correct PIN EXPECTED OUTCOME: Successful PIN validation TEST 2: Enter 1 incorrect PIN and then the correct PIN EXPECTED OUTCOME: Successful PIN validation TEST 3: Enter 2 incorrect PINs and then the correct PIN EXPECTED OUTCOME: Successful PIN validation TEST 4: Enter 3 incorrect PINs EXPECTED OUTCOME: Unsuccessful PIN validation - retain card, notify bank

28

2. Cash Withdrawal: The system should allow customers to withdraw money from their current accounts. Before allowing the withdrawal, the system should check the customer's balance to ensure that funds are available to cover it. If not, the system should offer any funds that are available (if any) or otherwise refuse the withdrawal. Each transaction should be recorded by the bank's main computer and the customer's accounts updated. A receipt for the transaction may be requested.

OBJECTIVE: To test the cash withdrawal procedure TEST 1: Request available funds without receipt EXPECTEDOUTCOME: Requested cash dispensed, accounts updated TEST 2: Request available funds with receipt EXPECTED OUTCOME: Requested cash & receipt dispensed, accounts updated TEST 3: Request more than available funds, accept available EXPECTEDOUTCOME: Available cash dispensed, accounts updated TEST 4: Request more than available funds, refuse available EXPECTED OUTCOME: No cash dispensed TEST 5: Request funds with none available EXPECTED OUTCOME: No cash dispensed 3. Display Balance: The customer should be able to check the balance in their account. This must be retrieved from the bank's main computer. A printout of the balance and available funds may be requested. OBJECTIVE: To test the balance checking procedure TEST 1: Request balance on screen

29

EXPECTED OUTCOME: The balance is retrieved and displayed on the screen TEST 2: Request printout of balance EXPECTED OUTCOME: The balance is retrieved and a printout is dispensed

4. Order Statement or Cheque book: The customer should be able to order a statement or a cheque book. The request is sent to the bank's main computer. OBJECTIVE: To test the statement/cheque book ordering procedure TEST 1: Request a statement EXPECTED OUTCOME: The request is sent to bank's main computer TEST 2: Request a cheque book EXPECTED OUTCOME: The request is sent to bank's main computer.

30

FINAL PROJECT SHOTS

Splash form: - For loading the project.

31

Welcome form:-It is welcome form of the project

32

Login-form:-This is the main form of the project from where administrator and user can be easilyidentified

33

Administration Log-in form:-It is log in form from where administrator can log in.

34

MDI form: - It Is MDI form for administrator

35

Create form: - This is Input form from where administrator can add, and update the records.

36

User-login form:-It is log-in screen for user.

37

ATM option form:-It is the form from where user can perform their specific option.

38

Withdrawal form:-It is a form from where user can withdrawal money from its account.

Passward change form:-This is the input form from where user can change its passward.

39

Balance inquiry form:-From this form user can know its actual account balance.

40

DATABASE DESIGN:Table name: - ADMIN TABLE Primary key: - Password Description: - This table stores information of particular Administrator.

41

Table name: - USER TABLE Primary key: - User_id Description: - This table stores information of particular User.

42

Table name: - TRASACTION TABLE Primary key: - ACC_no. Description: - This table stores information of Transaction of particular User.

CHAPTER 8 CONCLUSION Back in 1969, Chemical Bank announced that a new form of banking was being launched. With that, customers were provided with plastic cards designed with a magnetic strip that could be used with a machine built into a wall. Gone were the days of having to stand in line for a teller or not having money on hand after normal banking hours. Almost everyone has heard of and used an ATM machine. Interestingly, some of people feel that ATM machines are the best thing to happen in the banking world while other people consider them a curse. The main complain thread about ATM machines is that while they

43

are convenient, they are expensive to use. However, if we look at it from a banking perspective, business is business .Regardless of what we think of ATM machines; there is no doubt that they have changed the world and the way in which we do things. For example, think how many times we have been out somewhere only to discover we have no cash and we are out of checks, ah, but in the corner, there is an ATM machine. In the blink of an eye, was wiping the card and now have cash on hand. In addition to pulling money out, the ATM machine also makes it convenient to deposit money, transfer money, and check balances. Best of all, to use an ATM machine, we do not have to go to the bank. We will find ATM machines at other banks, grocery stores, shopping malls, along the road side, Buckingham Palace, airports, in casinos, and even on the South Rim of the Grand Canyon. For this reason, ATM machines are extremely helpful! Lastly, the outcome of internship project is not just a product or report, there are more than that. Here I learned how to work in professional environment with challenges in the real development world, how to improve analysis and design techniques and how to cope with different working situations. Not only that, through report writing I got to know how to compose professional and formal reports for any project or research works. These will help me a lot in future not only while working in industries but also in higher studies. Lastly, again I am grateful to IUB for giving me this opportunity to conduct my internship.

44

REFERENCES

1. OBrien, James A. 2000 Introduction to Information Systems: Essentials for the Internetworked E-Business Enterprise. , McGraw-Hill.2.

2. Kendall, Kenneth E., Kendall, Julie E. 2003 Systems Analysis and Design, Prentice-Hall India.3.

3. Pressman, R.S. 2001 Software Engineering: A Practionars Approach, McGraw-Hill.4.

4. Whitten, Jeffrey L., Bentley, Lonnie D., Dittman, Kevin C. 2001 Systems Analysis and Design Methods , McGraw-Hill 5. VB 6.0,Sanjeev Sharma, Nandan Tripathi 6. Microsoft SQL Server 7.0,John Franckowiak , Edward Whalen