Task 1: Project planning
1.1 Draw a Gantt chart showing the project planning across the whole assignment process.
1.2 Create a Trello board for managing your assignment, and maintain the Trello board across the whole
assignment process. Submit a set of snapshots for the Trello board showing the updating process.
Task 2: Requirements Documentation
Write a requirement, in plain English, for the scenario “Pay Fine”. You may need to make creative
assumptions for assignment purposes, and pretend you have conducted requirements elicitation with the
Your requirements will be assessed based on whether they:
• are verifiable, non-ambiguous, modifiable, traceable, consistent, and complete
• form a set of conditions, not only a series of operations / process descriptions
• relate to system requirements, not only business process
Hint: This is a potentially large task if you let your imagination run away with you. Try to keep your
requirements to the minimum – you are not being assessed on creativity or system knowledge, just your
ability to write a requirement!
Task 3: Use case diagram
You should provide one use case diagram that includes all actors and use cases within scope. Your diagram
must include a use case named ‘Pay Fine’, as documented in Task 2. Your diagram will be assessed based
• Consistency with the scope including the specific functionality requested
• Appropriate use of actors, includes/extends, and generalization
• Appropriate use of UML notation
Task 4: Use case textual description
Borrowing a book is the key function of this system. This functionally includes searching, borrowing and
returning book to the library. Develop a description of the use case using “Template – Use Case textual
description” as per Appendix. Document Preview:

Assignment – Library System Suppose that you are required to document a library system, particularly focusing on the functionality at the back end. The scope the system’s back end is defined as follows: • You should include all system functions and data, such as borrowing items, accessing both physical and electronic items, renewing loans, viewing a borrower’s account (including overdue items and fines), searching catalogues for various items, renewing loans, login, and asking a librarian. Note that this list is not exhaustive. • Some functionality (such as book rooms, access databases, borrow ebooks) is provided by applications integrated with the UNI library system. As such, you will need to show that the functionality is captured, but that no structural data is retained in this system. • Front-end content, such as ‘getting started in the library’, information pages (with static HTML content), the ‘About’ section, reference guides, and general information, is out of scope, and thus is not required to be included in your work. Some specific functionality is not necessarily apparent from public or student views, but should be included: • An ITS officer uploads a list of lists of active borrowers each year. The list contains staff, student and ‘others’. On this list: a. staff have a staff ID, barcode, name, DOB, and department b. students have a student ID, barcode, name, DOB and department c. others have a borrower ID, name, DOB, address & license number • The uploaded list is compared to existing borrowers by the system. If a person have left the university, his/her account will be removed if they have no unpaid fines. Otherwise, their borrower status is changed to inactive, and their record is retained. A new borrower account is created for a new person on the list • Librarians can also add borrowers. They create a borrower account with a name, DOB, and an expiry date. • If borrowers do not have a card with a barcode (such as those…