You are on page 1of 70

A Project Report On

VIDEO LIBRARY SYSTEM


U P DESCO
AEc
(CMS COMPUTER INSTITUTE) & {ABHINAV COMPUTERS education }
Submitted as a part of Project Training requirement for the degree of UPDESCO educations

Submitted By:
Rajesh Kumar Sunil kumar Renu Singh Ravinder kumar Sanjay Wati Joni kumar Priti Gautam Harandar kumar Sanjay kumar Gautam

Ramnivas

CERTIFICATE

I hereby certify that the work which is being presented in project report entitled Video OF Library System performed & at CMS,INSTITUTE COMPUTERS ABHINAV

COMPUTER INSTITUTE in partial fulfillment of the UPDESCO EDUCATION computer degree, is an authentic record of my work carried out under the supervision of RANU CHAUDHRY ( Sr. Faculty at CMS Institutes).

This is to certify that the above statement made by the candidate is correct to the best of my knowledge. This is to certify that project on VIDEO LIBRARY MANAGEMEN SYSTEM has been successfully completed by following members
Rajesh Kumar Sunil kumar Ranu Singh Ravinder kumar Sanjay Wati Joni kumar Priti Gautam

Harandar kumar Sanjay kumar Gautam Ramnivas Dated : _24_11_2004

PLACE: 2nd floor , shivam plaza , opp. UCO Bank , P.L. Sharma Road ,Meerut(U.P)
PH: (0121) 2662460, 2654930

Mr. RANU CHAUDHRY Project Guide

(Rajesh Kumar)

INDEX
S.NO.
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14.
15.

Name
Preface Acknowledgement Objective and Scope Theoretical Background Problem Analysis System Analysis Feasibility Study Software Engineering Paradigm Applied System Design SDLC System Study Requirement Specification Fact Finding Software Requirement Hardware Requirement DFD ER Diagram 18. Database Design 19. Structure of Table 20. Screens 21. Coding 22. Conclusion 23. Bibliography

16. 17.

PREFACE

Video Library system is computerization of the library that is maintained manually. Library system involved various task to maintain the library like maintaining a list of Video, list of members, and detailed report of issued and returned video with fine. In this project we use one database that is Library (containing five tables) these are. Video Entry (contain details of Video), Fine table (contain Fine details), Member Entry (contain details of members), issue table and last but not the least return table. The Visual Basic provides a screen for the Library Management System that was primarily manual in libraries. It works on MS- Access. The references for the MS-Access and Visual Basic are provided with the introduction with the System Development Life Cycle. The coding part has been attached with the output generated. The project is the result of complete hardworking with the System Software and Hardware limitations that has flowcharts to tell us about the working of the project.

ACKNOWLEDGEMENT
I would like to express our gratitude and thanks to Mr. RANU CHOADRE, who guided me throughout and offered valuable suggestions for the improvement of this project. I am also indepted to Mr SACHIN CHOADER (Director, CMS) who guided me and gave valuable information that contributed to the completion of this project. No efforts have been spared in making this project, but however some error may have inadvertently crept in, please forgive me for that. I will consider rewarded if this project is appreciated.

(Rajesh Kumar)

OBJECTIVE AND SCOPE OF THE PROJECT

In the present era of the Information technology, the value of time has been increase incredibility. Computer has revolutionized our way of life style by providing us an aster and accurate method getting information in less time. My project Name is A Video Library is a small step towards this approach. My project name is meant for maintaining an Video Library. This project can add new Audio/Video items, member and customer. Modify an existing record as needed and deleting the record, which is no longer needed. The prime aspects of this project are searching. We can search and display a record according to ID Number of an Video item customer and member. This project has a potential to be helpful in the working of any library of this type. Finally in hope is that my project would be appreciated.

THEORETICAL BACKGROUND

A Video Library as a library situated in a city in which a number of varieties of new and old Video CDs and cassettes are available. IT Provides a facility for taking membership; we can tack a membership by paying particular fee. Each member can issue any item for one day and return it within the time, otherwise a fine will be charged. We can also purchase items from the library as a customer. Library creates a bill to customer for his purchase, and also creates a receipt to the customer after accepting amount of purchase. There is requirement to generating the day wise report for Bill, Receipt, Issue items, returns Items and Stock Report for CDs and cassettes available in Library.

PROBLEM ANALYSIS
The first step in the problem definition phase is to develop clear and unambiguous goals about our project. Usually, the goals for a software project being with general statement such as Maintaining and managing the overall Operation of Library such as maintains the stock, preparing the bill to a customer, managing the issuing and returning the item by a member and preparing the reports. That problem definition gives us a direction in which to move but there much more to be considered and analyzed before we sit down at the keyboard. To develop software the first thing, which comes in mind, is that why we need to develop software. What are the problems faced by the user or staff to maintain manually their records so that they decided to computerized their working.

In library there are so many tasks, which are tedious and time Consuming. The person who maintain library manually face so many problems like searching details of particular record, security problem is the main problem which is faced by the person that they maintain registers and any one can change details easily. To solve these types of problems we design a computerized Library management system, which is easy to operate, and only authorized person can edit the information. Record entry and searching is not time consuming and fine is calculated automatically.

SYSTEM ANALYSIS
Identification of the need Since the world is growing for globalization, every organization wants to beat its competitors and wants to grow. Enterprises Resourceful Planning (ERP) is the need of todays organization. Survival on manual system is difficult so, thats why organization of the corporate world wants to computerize their departments. The web site should be complete database driven and interactive that should provide the registration form, re-registration form, fee submission, fee details etc. and data catalogs. The success of a system depends largely on how accurately a problem is defined thoroughly investigated, and properly carried out to the choice of solution. Analysis is a phase in which the requirements for a system are identified. System analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. The question is: what must be done to solve the problem? One aspect of analysis is defining the boundaries of the system and determining whether or not a candidate system should consider other related system. During analysis data are collected on the available files, decision points and transaction handle by the parent system. Data flow diagram, interviews, on-site observation, questionnaires are used as logical system model and tools to perform the analysis.

Tasks, which are performed as an analyst. Gathered all facts about the present system from the employees. Studied strengths and weakness of the current system. Determined what must be done to solve the problem. Prepared a functional specification document.

In order to reduce the time, there is a need for computerized system that can retrieve data, insert data, update existing data, or delete existing data. These web sites are developed with the aim of reducing time, reducing manpower, and reducing cost so that the records can be easily maintained. The volume of work and complexity are increasing year by year. This system reduces complexity and workload. PRELIMINARY INVESTIGATION A request to take assistance system from information system can be made many reasons, but in each case someone in the organization initiate the request. When the request has three parts:
Request clarification Feasibility study Request approval

Request clarification Many request from employees and users in the organization are not clearly defined. Therefore, it becomes necessary that project request must be examined and clarified properly before considering systems investigation.

Feasibility Study The feasibility study is carried out by a small group of people who are familiar with information systems techniques, understands the parts of the business or organization that will be involved or affected by the project, and are skilled in the system analysis and design process. Request approval: It is not necessary that all requested projects are desirable or feasible. Some organization receives so many project requests from employees that only a few of them can be pursued. However, those projects that are feasible and desirable should be put into a schedule. In some cases, development can start immediately, although usually systems staff members are busy on other ongoing projects. When such situation arises, management decides which projects are most urgent and schedules them accordingly. After a project request is approved, its cost, priority, completion time, and personnel requirements are estimated and used to determine where to add it to any existing project list. Later on, when the other projects have been completed, the proposed application development can be initiated. Analysis is a process of studying a problem and to fine the best solution to that problem. System analysis gives for the design and the implementation. Analysis is one phase of the very important phases of

the system development life cycle. System development is a problem solving technique. Analysis involves interviewing the client and the user.

FEASIBILITY STUDY
The result of feasibility study is a formal proposal. This is simple Reports - A format document detailing the nature and scope of the proposed solution. The proposal summarizes what is going to be done. Three key considerations are involved in the feasibility analysis: Economic, Technical and Behavioral. Economical Feasibility: Economic analysis is the frequently used method for evaluating the effective of a candidate system. More commonly known as cost/benefit analysis. The procedure is to be determining the benefits and savings that are expected from a candidate system and compare them costs. If benefits outweigh costs, then the decision is made to design and implement the system. Otherwise, further chance of being approved. This is an ongoing effort that improves in accuracy is judged not feasible.

Technical Feasibility : Technical feasibility centers, around the existing computer system hardware, software etc. and to what extent it can support the proposed addition. For example: if the current computer is operating at 80% capacity an arbitrary calling then running another application could overload the system or require additional hardware. This involves financial considerations to accommodate technical enhancements. If the budget is a serious constraint then the project is judged not feasible. Operational Feasibility:
[

It is common knowledge that computer installations have something to do with turnover, transfers, retraining and changes in employees job requires special efforts to educate, sell, and train the staff on new ways of conducting business.

SOFTWARE ENGINEERING PARADIGM APPLIED Computer aided software engineering can be as simple as a single tool that supports a specific software engineering activity or as complex as a complete environment that standards and myriad other components. Each building block forms a foundation for the next, with tools sitting as the top of the heap. It is interesting to note that the foundation for effective CASE environment has relatively little to do with software engineering tools themselves. Rather, successful environment architecture must consider the human work patterns that are applied during the software engineering process. The environment architecture, composed of the hardware platform and system support (including networking software, software management, and object management services), lays the groundwork for CASE. But the CASE environment itself demands other building blocks. A set of portability services provides a bridge between CASE tools and their integration framework and the environment architecture. The integration framework is the collection of specialized programs that enables individual CASE tools to communicate with one another, to create a project database, and to exhibit the same look and feel to the end-user (the software engineer). Probability services allow CASE tools and their integration framework to migrate across

different hardware platforms and operating systems without significant adaptive maintenance. The building blocks represent a comprehensive foundation for the integration of CASE tools. However, most CASE tools in use today have not been : constructed using all these building blocks. In fact, some CASE tools remain point Solution That is, a tool is used to assist in a particular software engineering activity (e.g. analysis modeling) but does not directly communicate with other tools, is not tied into a project database, is not the part of an integrated CASE environment (I-CASE). Although this situation is not idea, a CASE tool can be used quite effectively, even if it is a point solution. At the low end of the integration spectrum is the individual (point solution) tool. When individual tools can provide facilities for data exchange, the integration level is improved slightly.

SYSTEM DESIGN
The most creative and challenging phase of the system life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specification that will be applied in implementing the candidate system. The FIRST step is to determine how the output is to be produced and in what format samples for the output (and input) are also presented. The SECOND step is input data and master files (database) have to be designed to meet the requirements of the proposed output. The operational (processing) phase are handled through program construction and testing including a list of the programs needed to meet the systems objective and complete documentation. Finally, details related to justification of the system on the user and the organization are documented and evaluated by management as a step toward organization are documented and evaluated by management as a step towards implementation. To design the system we must note the following points:

To identify the software components which satisfy the system design. To design and document the software components and their linkage.

In this component the software components and relevant interfaces such as, interactions with existing internal and external systems, network connections, standard input and output formats are to be identified. The operational (processing) phases are handled through program construction and testing including a list of the programs needed to meet the systems objective and complete documentation. Finally, details related to justification of the system on the user and the organization are documented and evaluated by management as a step toward implementation. Identify relevant interface Interaction with the existing system Interaction with existing external system. Network connections Standard input formats Standard output formats Program specifications

SOFTWARE DEVELOPMENT LIFE CYCLE


The Software Development Life Cycle is a set of practices, which we use to produce a software product. Following phases are included in life cycle along with the objectives. 2.1 Project Initiation To consider and identify the procedures and activities that needs to be done for this particular project. To document the procedures and activities required. To provide sufficient information for the project to commence. 2.2 Requirement Definition To further develop the selected solution, by analyzing requirement and designing the system. To document the findings to provide the service user with the clear understanding of the proposed system. 2.3 System Design

To identify the major components to be contained in the system. To design and document the system, designing scope of what it will achieve. To provide sufficient information for the next phase to proceed. 2.4 Program Design To identify the Software Components which satisfy the System Design. To design and document the Software Components and their linkage. 2.5 Code Planning To code programs, so as to meet the detailed design specification. The coding for screen and report design is done taking project guidelines into considerations. The coding should consist of comments for ease of maintenance and future references. 2.6 Testing To test programs to meet the detailed design specifications. 2.7 Installation To deploy and configure the System.

SYSTEM STUDY
System Study is specifically for the phases that we have followed for the completion of our product Garments Stock Management System during the specified time. The phases covered in the project are: 1. Project Initiation Here, we have decided the project to be chosen & why we have opted for this particular project and how it will benefit us. 2. Requirement Definition Here, we personally the visited at workshop to read the current Stock Management System and then we analyzed the requirements of the project. 3. Proposed System Based on the requirements of the current system, the discussion with our Project Leader and limitations imposed by the technologies available to us, a system is being proposed out here.

4.

System Design This phase was being divided into two sub-phases: High Level Design Low Level Design

5.

Screen Designing Here, all the Screens were being designed using Visual Basic.

6.

Coding In this phase, Visual Basic is used as a fronthand tool and Access as backhand tool.

7.

Testing Here, first individual modules were being tested. Once, satisfied with working of all the individual modules, all of them were integrated, and they were tested as whole product.

REQUIREMENT SPECIFICATIONS
We choose our project to automate the Automated Library system for Excel Net computer Education Agra because till now institute library is managed manually for the classification of books and book issue and return. Library management includes various tasks. Visual basic is graphical user interface based language, and using the user knows the appearance of the output.

For managing databases we used MS-Access, visual basic support MS-Access for connecting databases using ODBC and Microsoft jet engine. In MS-Access we can easily create tables, queries and many more useful operations.

FACT FINDINGS
After obtaining this background knowledge, the analyst begins to collect data on the existing systems outputs, inputs and costs. The tools used in data collection are : Review of written documents On-site observations Interviews Questionnaires. We use On-site Observation technique for data collection. In On-site Observation we find that the person who maintain library. In that system he faces so many problems. Like He maintain book details register and maintain registers for member details, book issue and return records. And he calculates fine for late returned book manually. This may results error in calculations. This system is time consuming too. Beside librarian student also faces some problems. The main problem faced by students is that the manual process is very time consuming.

SOFTWARE REQUIREMENT

OPERATING SYSTEM

Windows 98, XP

FRONT END

Visual Basic 6.0

BACK END

Ms-Access 97

Windows And Visual Basic


Graphical user interfaces, or GUIs, have, revolutionized the microcomputer industry. They demonstrate the proverb, A picture is worth a thousand words, hasnt lost its truth to most computer users. Windows applications generally have a consistent user interface. This means that users can spend more time mastering the application and less time worrying about which keystrokes do what within menus and dialog boxes. For a long time there were few such tools for developing Windows applications. Before Visual Basic was introduced in 1991, developing Windows applications was much harder than developing DOS applications. Visual Basic language is having a several faces. One is Visual, which comprises of objects and tools that easily assembles themselves into a modern Windows interface. Whereas developing a Windows application required expert C programmers and hundreds of lines of code for the simplest task. Even the experts had trouble.

VISUAL BASIC FEATURES


Event Driven Programming
Visual Basic Language is an event driven programming language. We can perform actions on any events of controls to make an easy programming and to use system to perform best operations. With the controlling of events we can open a new form, control keyboard and mouse.

Distributed Programming
Visual Basic gives a facility to make system as distributed application. System made in visual basic can run on Internet application. The main advantage of distributed application is that it can run on any platform with out doing any changes.

GUI Programming Language


GUI gives a graphical environment to work on graphics. This feature makes easy operation to use system for user. It provides many graphical tools to use system.

Third Generation Language Visual Basic is a third generation language. It as also called a High Level language and procedural language. Visual basic gives the ability to user to write commands and integrated applications together.

Overview of How We Develop a Visual Basic Application


The first step in developing a Visual Basic application is to plan what the users will see, in other words, to design the interface. What menus do we want? How large window should the application use? How many windows should there be? Should the user be able to resize the windows? Where will we place the command buttons that the user will click on to activate the applications? Will the applications have places (text boxes) in which to enter text? What sort of controls do we need to accomplish what we want?

DATABASE CONCEPTS
A database is simply a systematic organization of data. Traditionally, databases are organized using fields and records. A record is all the information about one item. Common office database applications often need a more complex structure than this. A database often requires several related collection of fields and records. For this reason, Access uses the term table to refer to this matrix of records and fields.

MS - ACCESS 97
Access provides an extremely powerful, easy-to-use database that serves you when you require the power of a fully relational database. Using Access we can create a variety of database, as well as enter, edit, and find data in existing databases.

HARDWARE REQUIREMENT
This software requires following configuration of an CMS or compatible P.C. Microprocessor 486 or higher. RAM 16 M.B. or higher. Windows 98 /XP Operating System. Hard Disk Drive with 2.1 G.B. free disk space. Floppy Disk Drive Compact Disk Drive A Mouse Dot Matrix or Laser Printer for report generation. A Keyboard. A Monitor.

DATA FLOW DIAGRAM


For Membership

MEMBER INFORMATION FILE

Member
LIBRARY CARD

Members hip

For New Video

VEDIO INFORMATION

Books

Purchas e

For Video Issue

VIDEO INFORMATION FILE MEMBER INFORMATION FILE


VIDEO ISSUE

Member

Issue

VIDEO ISSUE FILE

For Video Return

Member

Return
VIDEO RETURN

VIDEO RETURN FILE

For Late Video Return

LATE RETURN

Memb er
FINE CHARGED

FINE FILE

Fine

Data Flow Diagram for Ordering System

Audio/Video Information

Customer

Process Order

Customer Information File

Data Flow Diagram for Order Verification

Customer Information File

Customer

Edit Order

Assemble
Requisition Warehouse to

Wareho use

Audio/Video Order

Audio/Video Order

Symbols used for E-R diagram.


Symbol
ENTITY WEAK ENTITY

Meaning

RELATIONSHIP

IDENTIFYING RELATIONSHIP

ATTRIBUTE

KEY ATTRIBUTE

MULTIVALUED

COMPOSITE ATTRIBUTE

ENTITY-RELATIONSHIP DIAGRAM OF LIBRARY DATABASE

Serial Number Direct or

Video_id Release_date Producer TotalTi me

Title

Price

VIDEO_ENTRY
Remark Actor Actress

Serial Number Addres s

Member Number

Name

Father_Name

City Pincode Sex MEMBER_ENTR Y Age Mobile_No Phone_No Email_Id State

Serial Number Direct or D_O_ I Member_Name

Video_id Issue

Video_Name

Member_Id

ISSUE

Serial Number D_O_ I Member_Name

Video_Id Director_ Name

Video_Name

Day Member_Id

RETURN

Fine

Return_Date

Serial Number

Video_Id Director_ Name Video_Name Day Member_Id

D_O_ I Member_Name

Fine
Type

Fine

Return_Date

DATABASE DESIGN

STRUCTURE OF DATABASE

NAME OF DATABASE VIDEO LIBRARY

Table Name
1. Video Entry 2. Member Entry 3. Issue 4. Return 5. Fine

Details
Details of Videos Details of Members Records of Video Issue Records of Video Return Fine Details

STRUCTURE OF TABLE
NAME OF TABLE ------ VIDEO ENTRY

S.NO

FIELD NAME

DATA TYPES

1. 2. 3. 4. 5. 6. 7. 8. 9. 8.

Serial_Number Video_Number Title Director Producer Release_Date Actor Actress Totaltime Remark

Text Text Text Text Text Date/Time Text Text Text Text

NAME OF TABLE --------- MEMBER ENTRY

S.NO

FIELD NAME DATA TYPES


Serial_Number Member_Number Name Father Name Address City Pin code State Sex Age Phone No. Mobile No. Email Add Text Text Text Text Text Text Text Text Text Text Text Text Text

1.
2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.

NAME OF TABLE ------------- VIDEO ISSUE

S.NO FIELD NAME DATA TYPES


1.
2. 3. 4. 5. 6. 7. 8.

Serial_No
Video_id Video_Name Director Member_id Member_Name D_O_I Issue

Text
Text Text Text Text Text Date/Time Text

NAME OF TABLE ------------ VIDEO RETURN

S.NO
1. 2. 3. 4. 5. 6. 7. 8. 9.

FIELD NAME DATA TYPES


Serial_No Video_id Video_Name Director_name Member_id Member_Name Return_date Fine Day Text Text Text Text Text Text Date/Time Text Text

NAME OF TABLE ---------- FINE


S.NO FIELD NAME DATA TYPES
Serial_No Video_id Video_Name Director_Name D_O_I Member_id Member_Name Return_Date Fine Day Text Text Text Text Date/Time Text Text Date/Time Text Text

1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

CONCLUSION
LIMITATIONS

We have made humble effort in preparing the software, so that it can be in the functioning condition. But due to lack of time some conditions cannot be applied. Another limitations is that software will not run under 3.11 operating system.
SCOPE

The future enhancement of the software can provide many more other facilities in the different areas like payroll, scheme human resources and development section of institute.

FURTHER IMPROVEMENTS

The further improvements can be done in project, are list can be generated in dfferent format as according to the requirements, printing of list on printer directly given the commands or by pressing the command button, backup of all the records in the database, searching for a particular record in the database giving the search command.

BIBLIOGRAPHY

WRITER

BOOK NAME PUBLISHING


MASTERING V.B B.P.B

EVANGELOS

PETROUTSOS RAMEZ ELMASRI SHAMKANT B. NAVATHE FUNDAMENTALS OF DATBASE SYSTEM VISUAL BASIC FROM C.M.S LTD. DAVID JUNG TECHMEDIA JOHN D CONLEY III JACK PURDUM LOREN EIDAHL LOWELL MAUER PIERRE BOUTQUIN ELIAS M. AWAD VISUAL BASIC 6 SUPER BIBLE

SAD

GALGOTIA PUBLICATION

BLACK BOOK

ABOUT US FORM

FORM VIDEO CONDITION DISPLAY

VIDEO ISSUE FORM

LOGIN FORM

MEMBER ENTRY FORM

CONDITION WISE MEMBER DISPLAY

MEMBER DISPLAY

MEMBER MODIFICATION FORM

PRINT FORM

VIDEO CASSATE ENTRY FORM

VIDEO DISPLAY FORM

VIDEO MODIFICATION ENTRY FORM

VIDEO RETURN FORM

MDI FORM

SPLASH FORM

FORM CUSTOMER DISPLAY

(Rajesh Kumar)

{Rajesh Kumar}

(SUNIL KUMAR)

{Sunil kumar}