Documente Academic
Documente Profesional
Documente Cultură
Operator Can enter details related to a particular book. Can provide membership to members. Admin Can read and write information about any member. Can update, create, and delete the record of membership as per requirement and implementation plants.
SCOPE The different areas where we can use this application are: Any education institute can make use of it for providing information about author, content of the available books. It can be used in offices and modifications can be easily done according to requirements. Reception activities. Sales transactions. Accounting system. Book store follow up. Using Internet facilities to connect all branches together.
5. Integrating the front-end with the database The front-end developed in the earlier milestone will now be able to update the books/journal database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing. 6. Testing The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). 7. Final Review Issues found during the previous milestone are fixed and the system is ready for the final review.
ACTION PLAN (To avoid risk) Proper communication between development team and user. Regular discussions between the teams. Provide professional trainers. Planning day to day activities keeping in mind slacks and float. Continuous database up gradation and checking.
7. Allocate resources
Hardware requirements PC with 2 GB hard-disk and 256 MB RAM
PROJECT SIMULATION The developed software is being tested through simulations before real implementation. The software is tested for integration of different modules and the cohesion and coupling of modules so as to ensure proper functioning of the system. The system is installed and test cases and input are given to test the validity of system so as to find any inconsistency or functional errors by cross checking the produced outputs against the output desired in test cases.
PROJECT DOCUMENTATION Starting from the planning stage through requirement analysis, feasibility study, design of library management system all the report/Outputs of each stage of software development process are recorded in Project documentation. For library management system the documentation will contain
1) Business case for library management System. 2) Requirement Specification report. 3) Detailed Design Report
Logical Design Physical Design
4) Business Process Report for Library Management System 5) Implementation Plan Documentation including the methodology and constraints specifications.
Project Simulation
The developed software is being tested through simulations before real implementation. The software is tested for integration of different modules and the cohesion and coupling of modules so as to ensure proper functioning of the system. The system is installed and test cases and input are given to test the validity of system so as to find any inconsistency or functional errors by cross checking the produced outputs against the output desired in test cases.