Demo Project for BBA IV students Library Management Information System Introduction: Zip Zap Zoom B-school is situated

d on the outskirts of New Jersey, US. This school has been rated as one of the best B-school by UMR rating agency. As such, the school is required to maintain necessary infrastructure in terms of Computer labs and a well equipped library. As a part of the management objective, they want to develop computer software which will address the day to day requirements of the library. Thus, following requirements are to be addressed and which should be included in the software. Cosmetic Requirements A front end user friendly interface (i.e. the forms) which will be used for keying in the data. A well formatted report display on the screen which would include appropriate headings A well formatted query output screen which would generate the queries as required by the user of the software Functional Requirements i) Database requirements Book Master Table There should be a provision for entering the master data for books in a separate table named as Book-master table. This table should include the following fields o Book Id Char(5) it should be a unique id i.e. primary field o Book Name char(20) o Author Char (20) o Book Type char(20) Example of this could be Book Id : J1050 Book Name: Fundamentals of Marketing Author: Dr. Philip Kotler Book Type: Marketing Management Note Book Type has to be any of the following: Production Operations Management, Advertising, Corporate Governance. Enter at least 20 records in the above table. This should include various amounts of Marketing, Advertising, POM and Corporate Governance.

Student Master Table o There should be a provision for entering master data for students in a separate table named as student-Master table. The contents of this table should be

o Student ID Char(5) it should be a unique id i.e. primary field o Student Name char(20) o Course Char (6) o Contact No. (10) Example of this could be Student Id : FIB01 Student Name: XYZ Course: BBAIV Contact No: 9898989898 Note : Enter At least 10 records Book Issue Table o There should be a provision for entering the books which are issued to the students in a separate table name as book-issue table The contents of this table should be Book Id Char(5) it should be a unique id i.e. primary field Book Name char(20) Student ID Char(5) Contact No. (10) Book-Issue-Date Date Book-Return-Date Date Note: Do not enter any records in this table ii) Functional Requirements Appropriate validations and checks are to be incorporated in the system The values such as student-id, Contact No & book-name in Book Issue table are required to be populated from their respective tables. Once when these have been populated, then this record is to be saved after entering the book issue date as well as book return date. Book return date has to be 15 days from the issue date iii) Miscellaneous Reports and Queries Reports The following report should be generated

a. List of Master Books with the format as given below b. List of Book Issue Books with the format as given below c. List of Students with the format as given below Queries The following queries should be generated a. The list of the students who have their books overdue b. The list of students who have taken the books on particular subjects such as Marketing Management c. The list of the students who have returned the books in time Appendix Software Requirements Input / Output screens

Report Format

Query Formats

Project File Structure a. Cover Page

A Project Report on Library Management System Prepared by ABC, BBA 5th Semester Roll No. XXXX

b. Acknowledgement Page c. Table of Contents d. Introduction: About the project (A brief of the Project i.e. what this project is all about) System Requirements of the Project o Hardware Requirements o Software Requirements Functional Requirements of the system o Master Book Requirements o Master Student Requirements o Book Issue Requirements e. Software Design & Analysis o Flow Charts of the process o Table Structure o Fields Description o Major Field Properties descriptions from the property sheets such as checks and constraints etc. f. Layouts (Screen Shots) Input Screens Output Screens Report Formats Query Screens g. Conclusions : o Future Enhancements to the software h. References Books, websites referred etc.