Академический Документы
Профессиональный Документы
Культура Документы
Unit Code & Title : F/601/1528– Unit 41 - Programming in Java (No 41)
Assessment Title & No’s : “Read with Us” – Library Management System - (JAVA – 16 – 001)
Date of Submission:
I hereby, declare that I know what plagiarism entails, namely to use another’s work and to
present it as my own without attributing the sources in the correct way. I further understand
what it means to copy another’s work.
When a person wants to borrow, read or reserve a book, he /she must first have to register with the
LMS. Registration process will be conducted by the librarian. Member details should be recorded and
each member will get a unique member ID and a password which can be used at the login process of
the LMS.
Once a member borrows a book, the librarian should be able to record the borrowing book and
member details, borrowed date and return date should be recorded. Maximum number of books can
be borrowed at a time is 2. At the returning process, system should check whether the member has
any overdue fine charges. If so Rs.5/- should be charged for each book per day. Lending period for 2
books are 14 days.
Book and the author details should be recorded in the LMS. Available book quantity should be
updated. Librarian should be able to view member details, search, view borrowed book details and
fine payment details.
Using the desktop application members should be able to login to the LMS. Once they logged they
can search for books, view book details and reserve books. Maximum number of books can be
reserved is 2. Member should be able to check their borrowed book details and their overdue book
details.
2.1. Design the given scenario using - UML Diagrams (LO 2.1)
2.1.1. Use case Diagram
2.1.2. Class Diagram
2.1.3. Sequence Diagram
2.1.4. Activity Diagram
Write a short description in plain English for each class in class diagram and each use case in
use case diagram.
2.2. Design the given scenario using- Designing Diagrams (LO 2.2)
2.2.1. ER Diagram
2.2.2. Data flow diagram
Write a short description in plain English for each entity in ER Diagram.
3.1. Implement an Object Oriented solution for the given scenario using Netbeans IDE. Java
Solution must be based on the prepared design given in task 02. (LO3.1) (M1)
3.2. Define relationships between objects to implement design requirements. You must
provide the possible evidences for polymorphism, inheritance, encapsulation,
aggregation in your implementation (LO3.2)
3.3. Explain control structures used in the solution with examples. (LO3.3)
3.4. Identify and implement opportunities for error handling and reporting. (LO3.4)
3.5. Provide the list of examples how you experienced user-friendliness of Integrated
Development Environment (IDE) (LO3.5)
4.1. Provide suitable test plan to critically review and test the developed system. (LO 4.1)
4.2. Provide suitable test cases to analyze the expected test results against actual outputs to identify
discrepancies. (LO 4.2)
4.3. Evaluate independent feedback on your system from various users and make valid
recommendations based on the feedback to improve your system. (LO 4.3)
4.4. Create user documentation for the developed java program solution. (LO4.4)
4.5. Create a technical document to provide good understanding of the program and its functions.
(LO 4.5)
Comments:
Assessor Name :
Date :
Signature :
2.2 Explain the components and data and file structures required to Task 2.2
implement a given design
3.5 Make effective use of an Integrated Development Environment (IDE) Task 3.5
including code and screen templates
4.2 Analyze actual test results against expected results to identify Task 4.2
discrepancies
4.3 Evaluate independent feedback on a developed Java program solution Task4.3
and make recommendations for improvements
4.4 Create user documentation for the developed Java program solution Task 4.4
4.5 Create technical documentation for the support and maintenance of a Task 4.5
Java program solution.
1. Take responsibility for managing and organizing activities Gantt chart must be provided at the
D2.3 Activities have been managed appendix section and submit the
work on time
Strengths: Weaknesses: