Business Overview Library Management

Question: Discuss about the Business Overview for Library Management. Answer: Business overview Goals The goal of the project is to prepare an automated library management system in 6 months with a budget of $20,000. Objectives The key objectives of the proposed system are as follows: Accurate catalogue to inform clients of any kind of video help. Avoid incorrect lending videos to defaulters. Study of borrowing patterns of users. Avoid inconsistent data and data redundancy of data. Current situation and Problems The current system runs on traditional system with most of the work being done manually. This results in inconsistent data and administrator lose track on number of videos being issued to which user and whether the borrower is a legitimate member of the library. Gaps The current system is not able to automate the reminders to be sent to the users. Also, it looses out the customers by not studying their pattern of borrowing. It is also not able to add trending videos in the library and hence gets its market share reduced by considerable number. Opportunities With the help of proposed system, the library will attract new customers by upgrading library from time to time. Data gathering Following are key data gathering methods: Registration - Registers and licenses are used specifically for complete enumeration. This will help finding out the number of users file for membership monthly. Questionnaire - This includes a form which contains a set of questions arranged in a logical order. It is distributed to the end users for their responses. It is a good option as the end users are co-operative. Interviews - This method will interview the end users. However, this method is complex than questionnaire. It will be used for high level management. Meeting - This method will help in finalizing the design of proposed system. It includes providing a demo to the end users and get feedbacks from the end users of the library. Logical process modelling Data modelling and Normalization Tbl_Branch Attribute name Data type branchNo Number address String telephone Number manager Number Tbl_Staff Attribute name Data type staffNo Number firstName String lastName String position String salary Number Tbl_Category Attribute name Data type code String name String description String Tbl_Video Attribute name Data type videoNo String copyNo String title String category String dailyRental Number cost Number categoryNo Number Tbl_Customer Attribute name Data type memberNo Number firstName String lastName String street String State String zipcode Number dateOfRegistration Date branch Number Tbl_Publisher Attribute name Data type publicationNo Number firstName String lastName String licenseNo Number city String country String Feasibility analysis Feasibility study provides an overview of key issues which are related to proposed system. The system can be analysed using following types of feasibility: Economic feasibility - This type of feasibility measures the proposed system on the basis of cost and benefit. As per the given scenario, the library indeed has enough funds to conduct complete system investigation. In addition to this, funds are available for purchasing hardware and software for the proposed system. It is performed by interview technique. Technical feasibility - This type of feasibility measures the proposed system on the basis of available technology. It is based on the outline of the requirements of system - inputs, outputs, procedures and programs. The proposed system has enough existing technology to implement the system and the system can also be scaled in future. It is performed by interview technique and record view technique. Operational feasibility It will include following criterias to be considered during operational investigation. The system has good number of users who are going to use it. The library functioning will get enhanced by the implementation of new automated system. The new system is beneficial from operational point of view and hence it can be concluded that it is operational feasible. Requirement specification Following are key functional requirements: The customer should be able to register in the system. The customer should be able to make request for borrowing a video. The customer should be able to return the video. The customer should be able to request for adding new video in the system. The customer should be able to browse through the catalogue. The customer should be able to filter the videos on the basis of categories. The customer should be able to view data on single video. The customer can extend the hold on a video. Following are key non-functional requirements: The system should be reliable i.e. 24x7 available. The system should have low learning curve. All users should be able to complete tasks without any guidance. The system should be able to prompt users for next set of actions. The system should be able to display appropriate message in order to allow users to perform next step in the transaction. The text should be displayed in a manner which is easily understable by the end users. The system allows only authenticated users to access the system. Proposed solution The proposed solution is an automated video library management system which will allow users manage the lending and returning of videos to the library. It provides platform to manage the accurate information about the videos and users and hence avoiding the data inconsistency in the system. The system will also allow management to analyse the patterns of members in order to update the library collection to retain the customers. It will also allow administrator to check for costs involved in the purchase of video and purchase order details. The proposed solution will be installed in all the stores and will have a centralized database. Implementation issues Following are key issues which may arise post-development of the system: The employees of library are reluctant to adapt to the new system. Economic fluctuations in the cost of the systems to be installed after the development of the system. The end users of the organization are not provided with enough training to use the system. References George, J. (2004).Object-oriented systems analysis and design. Upper Saddle River, N.J.: Pearson Prentice Hall. Hoffer, J., George, J. and Valacich, J. (1999).Modern systems analysis and design. Reading, Mass.: Addison-Wesley. Kroenke, D. (2009).MIS essentials. Upper Saddle River, NJ: Prentice Hall. Marmel, E. (2004).Microsoft Office Project 2003 bible. New York: Wiley. Valacich, J., George, J. and Hoffer, J. (2001).Essentials of systems analysis and design. Upper Saddle River, N.J.: Prentice Hall.