Library Information System Essays

Library Information System Essays Library Information System Essay Library Information System Essay Information System: We are living in the 21st century which is known as the †computer age†, where almost every kind of work is carried out with the help of computer. From the smallest work to the most critical works are carried out with the help of computers. What is more, now with increasing popularity of the internet many important applications have sprung up to make use of this wonderful technology. Many important applications have been designed with the view to communicate information to people all around the world. An information system is an open system that allows input and facilities interaction with the user. In our case †Library Information System† is an open system which allows taking input from the user provide interactive environment to have di? erent output according to user’s need. The library information system maintains the record of Library for the following purpose: 1. For day to day issuing of library books. 2. For fast retrieval of books information. 3. Maintaining information about journals, magazines ,newspapers etc. 4. Information about the vendor’s of books ,journals,newspaper. 5. To produce di? rent reports against di? erent query as per our need. 6. Information about the students and sta? to whom books has been issued. 7. Maintain the record of ? nes. 8. Maintain the record of billing the newspapers, journals etc. 9. Maintain the record maintenance of books. 10. Record of bindings of journals. 1 2. 1Introduction to Initial Investigation: Initial i nvestigation determines whether an alternative system can solve the problem. 2. 2Existing System The present library management system of AEC is to keep record of various books, journals, newspapers, magazines etc to whom they are issued and the vendors and ? es related to the books. The present Library system of AEC is manual, means the librarian maintain the various records in ? les. There is no computer based information system. 2. 3Drawback of the Existing System: The present library system of AEC keeps all its records in paper ? les, which lead to maintaining a lot of ? les and document. This take a lot of time, e? ort and space from the cost involved in it. The addition and maintenance of personnel details of new student to whom books are issued at the beginning of every session as well as the old students who are promoted to the next class, in paper ? es is tiresome, time consuming and costly a? air. The information is kept in an unstructured and unsystematic manner and scatt ered among huge number of ? les. So ? nding of speci? c information needs going through a lot of papers, as proper indexing system is not there. Apart from these, billing of newspapers, journals, calculating total ? ne collected at the end of the month ,year needs a lot of calculation. Then for generating reports separate manual type machine is employed. 2. 4Proposed System: The proposed system aims at making the above system automated and online. The computerized system allows the librarian to calculate the ? ne, the bill by just click of a mouse. The status of a book could be known by knowing the title or author or the accession number of the book. The library form can also be downloaded from it. The software is required to perform the tasks as narrated below: 1. Online membership. 2. Keeps the track of issues and submission of books. 3. Status of b book. 4. Status of a member. 5. Status of the student who has taken the book. 6. Status of the book yet to be returned. 7. Calculation of ? ne. Also various reports will be generated on these topics. The system is also required to provide for 3 levels of access. These are as follows: General User: They have permission to search books in library, change their own password, and can view their own details. Librarian: The librarian is allowed to add, delete and modify the various records related to books and members. He/she can issue books to users. In brief we can say that he/she can maintain the information of the system. Administrator: The administrator has the highest level of access. He/she can creates, modify and delete the account of a member. FEASIBILITY AND REQUIREMENT ANALYSIS 3. 1Introduction Feasibility study is carried to check the workability of the candidate system. It’s impact on the organizational ability to meet the user need and the e? ective use of the system. The object of the feasibility study is not to solve the problem but acquire a sense of its scope. During the study of the de? nition is centralized and aspect of the problem to be included in the system are determined. Consequently cost bene? ts are with great accuracy at this stage. The result of this feasibility study is a normal proposal. There are three key considerations involve in the feasibility study analysis. They are as follows: 3. 1. 1Economic Feasibility Economic Feasibility looks at the ? nancial aspects of the project. It is most frequently used technique for evaluating the e? ectiveness of a proposed system. Economic feasibility is more common known as Cost Bene? t Analysis. The procedure is to determine the bene? ts and savings that are expected from a proposed system and compare them with cost. It bene? t outweighs costs, a decision is taken to design and implement the system. Otherwise, further justi? cation or alternatives in the proposed system will have to be made if it to have a chance of being approved. The proposed system, no doubt require some initial investigation , but it will bene? t the organization in its long run in the form of reduce total number of employees, quick decision making capacity to the management to capture the market occur etc. So, we can say that our project will help the organization in ? nancial gaining at its long run and so it is economically feasible. So, the bene? t expected from the system is much more compared to the cost incurred in computerizing. Hence the system is economically feasible. 3. 1. 2Technical Feasibility Technical Feasibility determines whether the technology needed by the proposed system is available and how this technology can be integrated within the organization. The technical needs of the system may vary considerably but might include: 1. The facility to produce output in a given time 2. Response time under certain conditions 3. Ability to process a certain volume of transaction at a particular speed. 4. Facility to communicate data to distant location During examining the technical feasibility, we have given more importance to the con? guration of the system than the actual make of the hardware con? guration. It provides us a complete picture about our system requirements; like how many workstations are required, how these units are interconnected so that they could operate and communicate smoothly, what speed of input is achieved at particular quality of printing. The proposed system is technically feasible as it examined that the hardware and software is enough at the workplace to carry out the system and also can support addition. The proposed system presents a technically feasible picture since all the resources necessary for the developments of the system under considerations are present in the AEC Library. 3. 1. Operational Feasibility Proposed project are bene? cial only if they can be turned into information systems that will meet the operating requirements of the organization. In general, people resist to changes and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user sta? is likely to have towards the development of a comp uterized system. It is common knowledge that computer installations have something to do with turnover ,transfer, retaining and changes in employee job status. Therefore it is understandable that the introduction of a candidate system requires special e? rt to educate, sell and train the sta? on new ways of conducting business. With the co-operation and understanding of the project development, the whole endeavor becomes not only di? cult but meaningless too. Hence, the operational feasibility is one of the vital factors for the overall success of the project. The proposed system is operationally feasible as: 1. Suitable codes are used to generate reports and queries 2. Although the client organization has not computerized the proposed system but most of the employees are quite familiar with the computer as they have other system already computerized. Moreover, we are providing user manual and help for better understanding and operating system. So , the proposed system is operationally feasible. 3. 1. 4Conclusion From the observation made in the feasibility study described above, it was recommended that proposed system is feasible and justi? ed that the feasibility study could be followed by the system analysis phase. 3. 2Requirement Analysis Information gathering is usually is the ? rst phase of software development project. The purpose of this is to identify and document the exact requirements for the system within the framework of the organization. The requirement analysis must be based upon the user need, the developer and the organization. 3. 2. 1Information Analysis There are four strategies available for determining information requirement. They are as follows: 1. Asking (interviewing) 2. Deriving from the existing information system 3. Review the written documents 4. Synthesizing from the characteristics of the running system In the purpose system the strategies asking and reviewing of the written documents has used for requirement analysis. Presently in the existing system all record are maintained manually. For the development of the proposed system review written documents has done the requirement analysis. Again rule and regulation of the management information system are determined by asking strategy to implement in the proposed system. 4. 1Hardware Requirements: 1. System Type : IBM compatible PC’s 2. Processor: Intel(R) Pentium(R) 4 processor 3. RAM: 512 MB 4. HDD: 40 GB 5. Monitor: Any standard color monitor 4. 2 Software Requirements: 1. Platform: Asp. Net 2. Language Used: C# 3. IDE Used: Microsoft Visual Studio 2008 4. Database: SQL Server 2005 5. OS Used: Windows XP 6. Internet Browser: Any web browser . 3 Technology and Tools Used Microsoft Visual Studio 2008 In computing, Microsoft Visual Studio is an Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for al l platforms supported by Microsoft Windows, Windows Mobile, Windows CE, . NET Framework, . NET Compact Framework and Microsoft Silver light. Visual Studio includes a code editor supporting IntelliSense as well as code re factoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designer and database schema designer. It accepts plug-ins that enhance the functionality at almost every levelincluding adding support for source-control systems and adding new toolsets like editors and visual designers for domain-speci? c languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer). Visual Studio supports di? erent programming languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-speci? c service exists. Built-in languages include C/C++ (via Visual C++), VB. NET (via Visual Basic . NET), C# (via Visual C#), and F# (as of Visual Studio 2010). Support for other languages such Python, and Ruby among others is available via language services installed separately. It also supports XML/ XSLT, HTML/ XHTML, JavaScript and CSS. Individual language-speci? versions of Visual Studio also exist which provide more limited language services to the user: Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++. Microsoft provides †Express† editions of its Visual Studio 2010 components Visual Basic, Visual C#, Visual C++, and Visual Web Developer at no cost. Visual Studio 2010, 2008 and 2005 Professional Editions, along with languagespeci? c versions ( Visual Basic, C++, C#, J#) of Visual Studio 2005 are available for free to students as downloads via Microsoft’s Dream Spark program. Visual Studio 2010 is recently released. Designer Visual Studio includes a host of visual designers to aid in the development of applications. These tools include: Windows Forms Designer The Windows Forms designer is used to build GUI applications using Windows Forms. It includes a palette of UI widgets and controls (including buttons, progress bars, labels, layout containers and other controls) that can be dragged and dropped on a form surface. Layout can be controlled by housing the controls inside other containers or locking them to the side of the form. Controls that display data (like textbox, list box, grid view, etc. can be data-bound to data sources like databases or queries. The UI is linked with code using an eventdriven programming model. The designer generates either C# or VB. NET code for the application. WPF Designer The WPF designer, codenamed Cider, was introduced with Visual Studio 2008. Like the Windows Forms designer it supports the drag and drop metaphor. It is used to author user interfaces targeting Wi ndows Presentation Foundation. It supports all WPF functionality including data binding and automatic layout management. It generates XAML code for the UI. The generated XAML ? le is compatible with Microsoft Expression Design, the designer-oriented product. The XAML code is linked with code using a code-behind model. Web designer/development Visual Studio also includes a web-site editor and designer that allow web pages to be authored by dragging and dropping widgets. It is used for developing ASP. NET applications and supports HTML, CSS and JavaScript. It uses a codebehind model to link with ASP. NET code. From Visual Studio 2008 onwards, the layout engine used by the web designer is shared with Microsoft Expression Web. There is also ASP. NET MVC support for MVC technology as separate download and Dynamic Data project available from Microsoft Class designer The Class Designer is used to author and edit the classes (including its members and their access) using UML modeling. The Class Designer can generate C# and VB. NET code outlines for the classes and methods. It can also generate class diagrams from hand-written classes. Data designer The data designer can be used to graphically edit database schemas, including typed tables, primary and foreign keys and constraints. It can also be used to design queries from the graphical view. Mapping designer From Visual Studio 2008 onwards, the mapping designer is used by LINQ to SQL to design the mapping between database schemas and the classes that encapsulate the data. The new solution from ORM approach, ADO. NET Entity Framework, replaces and improves the old technology. Properties Editor The Properties Editor tool is used to edit properties in a GUI pane inside Visual Studio. It lists all available properties (both read-only and those which can be set) for all objects including classes, forms, web pages and other items. Object Browser The Object Browser is a namespace and class library browser for Microsoft . NET. It can be used to browse the namespaces (which are arranged hierarchically) in managed assemblies. The hierarchy may or may not re? ect the organization in the ? le system. Solution Explorer In Visual Studio parlance, a solution is a set of code ? les and other resources that are used to build an application. The ? les in a solution are arranged hierarchically, which might or might not re? ect the organization in the ? le system. The Solution Explorer is used to manage and browse the ? les in a solution. Team Explorer Team Explorer is used to integrate the capabilities of Team Foundation Server, the Revision Control System into the IDE (and the basis for Microsoft’s Code Plex hosting environment for open source projects). In addition to source control it provides the ability to view and manage individual work items (including bugs, tasks and other documents) and to browse TFS statistics. It is included as part of a TFS install and is also available as a download for Visual Studio 2005 and 2008. Team Explorer is also available as a stand-alone environment solely to access TFS services. Data Explorer Data Explorer is used to manage databases on Microsoft SQL Server instances. It allows creation and alteration of database tables (either by issuing T-SQL commands or by using the Data designer). It can also be used to create queries and stored procedures, with the latter in either T-SQL or in managed code via SQL CLR. Debugging and IntelliSense support is available as well. Server Explorer The Server Explorer tool is used to manage database connections on an accessible computer. It is also used to browse running Windows Services, performance counters, and Windows Event Log and message queues and use them as data source. Microsoft SQL Server 2005 SQL Server 2005 (codenamed Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it de? ned an xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is veri? ed against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; CLR Integration was the main features with this edition where one could write SQL code as Managed Code these are those code which are being executed by CLR (Common Language Runtime). SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also de? nes a new extension to XQuery, called XML DML that allows querybased modi? cations to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML. For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms and better error recovery systems. Data pages are check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more e? cient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the . NET Framework. SQL Server 2005 introduced †MARS† (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes. 5. 1Introduction: The design process translates requirements into a representation of the software that can be assessed for quality before coding begins. Once the requirements have been collected and analyzed, it is necessary to identify in detail how the system will be constructed to perform the necessary tasks. The design activity is often divided into 2 separate phases. One is system design and the other is detail design. System Design: System design aims to identify the modules that should be in the system, the speci? cation of these modules and how they interact with each other to produce the desired result. System design describes what components are needed. Detail Design: During detail design the internal logic of the modules speci? ed in the system design is decided. Detail design focuses on designing the logic of each of the modules. Detail design describes how the components identi? ed during system design can be implemented on the system. 5. 2System Design The web enable system for Asaam Engineering College Library has at present three modules with a number of sub modules. The following system design documents focuses detail on these modules and the speci? cation of these modules. The software modules of this web enable system are : Administrator Module 1. Create and delete account 2. System backup 3. View record Member Module 1. View record 2. Compile record 3. Enter record 4. Update record 5. Delete record 6. Generate reports User Module 1. View record 5. 3Detail Design During detailed design the internal logic of each of the modules speci? ed in system design is decided. The main aim of the detail design is to explain how the system work or how the ? ow of data takes place within the system. Detailed design deals with system speci? cation. 5. 3. 1 Abstract Representation of the proposed system Before making the detailed design of a system, ? rst the most abstract representation of the problem is worked out. The following use case diagram gives the working of the proposed system. 5. 3. 2The Uni? d Modeling Language: The uni? ed modeling language (UML) is a language just as sure as C, C++, Pascal, German, English etc. And the UML is probably the newest languages invented by human kind, invented around 1997. The UML is used to build models that will later be used to build real products, in our case Software. A model is a collection of text and diagram that represents something. A model is to software that a blueprint is to a house. Models are valuable for many speci? c reasons. Models are valuable because they consist of pictures to a large extent and even simple pictures can convey a lot of message then a lot of text. The UML is an o? cial de? nition of a pictorial language where there are common symbols and relationships that have one common meaning. The UML supports all aspects of SDLC from requirements gathering to design to development. There are mainly types of diagrams in the UML. The major types are: 5. 3. 1. 1Use Case Diagrams: Use case diagrams are a part of the requirements gathering process and are used in highlevel design to identify fundamental requirements of a system. It describes the participants and is also helpful in developing test plans. A use case’s main symbols are the actor and the use case oval. Use case diagrams are called the mother of all other diagrams of the UML. It gives the static view of a system and focuses on goals not processes. 5. 3. 1. 2Activity Diagram: Activity diagram are like ? ow charts but are more ? exible by supporting parallel application and by dividing areas of responsibility into swim lanes. Activity diagrams are used to analyze processes and if necessary, perform re-engineering. 5. 5 Data Tables A database is a collection of inter-related data, stored with minimum redundancy to serve many users quickly and e? ciently. The primary objectives of a database are fast response time to queries, more information at low cost, control redundancy, clarity and ease of use, accuracy and integrity of the system, fast recovery, privacy and security of information, data and program independence and availability of powerful end user language. The heart of a database is the DBMS. System analysis clears that all data used by process must be derived directly from input documents and reports are to be retrieved from the database ? les. The database of Library Information System† is a collection of di? erent types of information. So it has di? erent tables to access the information easily and e? ciently. Also the data redundancy is checked in the database. To get a nice understanding of the database, we have divided the database into several tables which are as follows. 1. Book Information: The Book Information store the all related information regarding a book. Table 1: Book Information ELEMENT NAME DATA TYPE CONSTRAINT Accession no nvarchar Not null Title nvarchar Not null Author nvarchar Not null Publisher nvarchar Not null Volumme nvarchar Not null Edition year nvarchar Not null nvarchar Not null Source 2. Member Information: Member Information table store the details of a member. The member may be a student, stu? or the librarian. 3. Card Inforamtion: This table stores the information regarding a card. 4. Transaction Table:: This table stores the transaction information of a book. Table 2: Member Information ELEMENT NAME DATA TYPE CONSTRAINT Member id nvarchar Not null nvarchar Not null Roll no Name nvarchar Not null nvarchar Not null Branch Session nvarchar Not null Town/Vill nvarchar Not null nvarchar Not null Dist Table 3: Card Information ELEMENT NAME DATA TYPE CONSTRAINT Card no nvarchar Not null nvarchar Not null Issue date Due date nvarchar Not null Table 4: Transaction Table ELEMENT NAME DATA TYPE CONSTRAINT User id nvarchar Not null Accesion no nvarchar Not null Issue date nvarchar Not null Return date nvarchar Not null Due date nvarchar Not null 5. User Login Form: This table contains data regarding log in information. Table 5: Transaction Table ELEMENT NAME DATA TYPE CONSTRAINT User id nvarchar Not null nvarchar Not null password roles nvarchar Not null Database normalization for the Library Information System The Library Information System is normalized up to BCNF (Boyee Coded Normal Form). st Normal Form: No column in the database contains multiple values, so the database is in the 1st Normal Form. 2nd Normal Form: Every Non key attributes fully functionally dependant on the primary key. Hence it is in 2nd Normal form. 3rd Normal Form: All non key columns do not depend on any other columns . Hence the database is in 3rd Normal Form. 4th Normal Form: A relation R is in BCNF if and only if every determinant is a candidate ke y. All the tables in the Library Information System ful? ll the condition. Hence the database is in BCNF. 6. 1Introduction: A system should always be tested thoroughly before implementing it with regards to its individual programs, the system as a whole, user acceptance etc. This is because implementing a new system is a major job which requires a lot of manpower, time and other resources. There are many levels of testing which ultimately leads to an error free system. The testings which are carried out is described below: 6. 1. 1 Program Testing: The program testing is carried out during the programming stages itself to test the logical and syntax error. 6. 1. 2 Unit Testing: In the unit testing di? rent modules were tested against the speci? cation produced during design of the module. When this testing was done with di? erent modules, some errors were detected and debugged and when modules were found to be working properly independently, next round of testing was followed. 6. 1. 3 String Testing: String testing is a method in which each program is tested to see whether it conforms to the related progra ms in the system. Each portion of the library management system was tested against the entire module with both test and live data before the entire system is ready to test. 6. 1. 4 System Testing: It was done to uncover the weakness that was not found during string testing. The whole system tested to see whether it works properly with valid and invalid data. The system was also tested for recovery after various major failures such as power failure etc. 6. 1. 5 Acceptance Testing: It is the system testing and performance tests performed by the customer to determine whether or not to accept the system. The library information system was accepted by the system. Implementation includes those activities that take place to convert the older system to the new one. The new system may be totally new or replacing an existing. In either case proper modi? cation is essential to provide a reliable system to meet the organization requirements. System implementation describes how the di? erent parts of the system are interacting with each other to give us a feasible software solution. The project is implemented on 3-tier architecture. It is installed on SQL server and which can be accessed by all users. This application is secured by putting user name and password, a user has to enter login details to the system. Figure 1: How the Application works The web server receives a request for some processing. Depending on the sent request the web server passes the request is forwarded to the respective request handler class and after the processing is done. The required data is fetched from the database, the required result i. e. response is passed to the client. Any further request from the client to the server goes through the same procedure. Once the software is developed, delivered and deployed, it enters the maintenance phase. Changes are inevitable when computer based systems are built, therefore mechanism for evaluating, controlling, and making modi? cations has to be adopted. These are called the maintenance activities they include: 1. Corrective Maintenance 2. Adaptive Maintenance 3. Perfective Maintenance or enhancement 4. Perfective Maintenance or reengineering Software may have some errors or bugs remaining in the system that must be removed as they are discovered. This is called corrective maintenance. Once the software system is deployed, the environment in which it operates changes. The software must adapt to the changed environment. The maintenance due to this phenomenon is called the adaptive maintenance. Software must be upgraded and enhanced to include more features and provide more services. As a result new versions of the software are released. This is called perfective maintenance or software enhancement. Reengineering is a rebuilding activity for added functionality, better performance and reliability, and improved maintainability of the software product. Unmaintainable software is subjected to rebuild following a reengineering process model. CONCLUSION 9. 1Introduction: The main concerns of the software development are software quality, programmer’s productivity and increase job satisfaction. The fundamental problems of software development are control of complexity, the lack of physical constraints, and boundaries in software and tendency to mix concerns that belong to di? rent level of abstraction. Finally, it is a people intensive activity for developing software for its use by other people. The †Library Information System† is designed and developed to satisfy the organization needs as far as possible. The Library Information System has built after an extensive research and evaluation of the existin g manual system. The main aim of the system is to maintain the records of the membership registration and the book issued to the member with the very best of accuracy and e? ciency. The purpose system is economically, technically and behaviorally feasible and is incorporated with some security measure so hat only authorized personal can manipulate the record. While developing this software we have tried to consider all the points, may be due to time constraint we may miss some valuable points for which we apologize to the concerned people. Any comments or suggestion that can improve the software are welcome. 9. 2 Overview of the System The proposed system covers the following area and processes: 1. Member’s registration 2. To maintain the record of individual member’s in detail 3. Status of the book. 4. No. of books available subject wise. 5. User friendly interfaces. Limitation of the Propose System The limitations of the purpose system are as follows: 1. † The system cannot give information about the vendors. 2. The data implementation with SQL server. 3. Security consideration and implementation is left to the database . administrator. 4. Need the help of manual system. 9. 4Scope and Further Enhancement of the Propose System: 1. The process of maintaining the detail information of the vendor can be included. 2. More enhancements can be identi? ed when the system is in the operation or used by di? rent users. ABSTRACT This report describes our group’s implementation of an online library information system. We used the Entity-Relationship model to design a database that will store and organize the library’s data. We have created the database using SQL and populated it with some sample data. The system can keep track of library cards, users, librarians, administrator, books and the relationships betwee n them. Using ASP. NET with C#, we have created an Internet-based graphical user interface that allows users and librarians to access the system remotely