Uploaded byImdad Ul Haq
Library management system
The document describes a proposed library management system that would allow librarians and members to manage books and member accounts. It would have two main user types: librarians, who could add, delete, and update book information as well as manage member accounts and check books in/out; and members, who could view account details, borrowed books, and payment history. The document outlines relevant functional requirements like registration, login, search, and payment, as well as non-functional requirements regarding performance, security, accuracy, reliability, and maintainability. It proposes using a Model-View-Controller framework and includes class, state, and other diagrams to conceptualize the logical and physical views of the system.
More Related Content
Similar to Library management system
![PROJECT_SRS[1].hgxfsdheth,vgxergdtrcxfpdf](https://cdn.slidesharecdn.com/ss_thumbnails/projectsrs1-241215082732-4afe27f3-thumbnail.jpg?width=640&height=640&fit=bounds)
Library management system
- 1.
- 2. Introduction Library management systemis a kind of system which provide the facility to the librarian in order to add , delete and update books as well as facilitate the students to read or rent the book from library. Library Management System will have two end . Librarian and Members. Librarian will be able to check member’s details, check in or check out books from the library, manage the books. Members would be able to view their account, check for their details such as list of books borrowed, view the due date, and view the payment history.
- 3. Requirements There are twotypes of requirements: 1)Functional requirements 2)Non-Functional requirements
- 4. Functional requirements Members: 1) Registration 2)Login 3) Search 4) Manage/View account 5) Payment Librarian: 1) Admin access 2) Registered members 3) Manage accounts
- 5. Non-Functional Requirements 1) Performance: Databaseshould be updated. Search should be fast. Login should be validate with in 1 second. 2) Security: Payment information should be protect and encrypted. Communication between server and user should be secure. 3) Accuracy: The system should accurately provide real time information taking into consideration various concurrency issues.
- 6. Continue 4) Reliability The systemhas to be 100% reliable due to the importance of data and the damages that can because by incorrect or incomplete data. 5) Maintainability: The system should provide automatically notification to patrons by e-mail about item's overdue, reservation results, availability of reserved item and etc.
- 7.
- 8. 4+1 view 1) Logicalview: For end-user class diagram
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. Continue View book detailView student/member detail
- 16.
- 17.
- 18. Continue Scenario: Use cases: Add newstudent Delete/update student
- 19.
- 20.
- 21.