$1.$ Brief Task Descrip$$on

A small library needs a system to track the details of their available books and members. They provided

you with the data source CSV file. The file contains details of all books that are available for members

to borrow and return within three days. It is made available to you for implementa$$on and tes$$ng$,$

but the system should allow any file to be used $-$ a different file will be used for your CW marking $($do

NOT hardcode the filename$).$ You have been provided with the UML diagram in Figure $1$ to design the

so$$ware and must implement the classes as shown $$ any devia$$on will be marked down. You must

use the Git version control system with regular commits pushed to a repository on either Bitbucket or

GitHub.

You should NOT use any third$-$party libraries or code as a part of your solu$$on and all code must be

wri$$en by you, e$.$g$.,$ not automa$$cally generated by an A$.$I. or IDE. Do not use any non$-$standard code

or libraries or system calls in your program.

$2.$ Submission

The submission will be done via submi$$ng a link to your Bitbucket or GitHub repository. The online

repository MUST consist of all$-$required source code; a single MP$4$ video file of a screencast

presenta$$on and a single PDF file of the presenta$$on slides. The deadline is $5$:$30$pm on Friday, $12$th

January $2024.$

The repository should include:

$$ C$++$ source code files of your program.

$$ C$++$ source code of $$Catch$2$ tests which test your code.

$$ a makefile to compile your program.

In the presenta$$on you should show your slides while you describe each sec$$on$.$ Full details of what

should be included in the presenta$$on are given below. The video should be a maximum of $6$ minutes

long. If the video is longer, only the first $6$ minutes will be marked. The video must also include a short

demonstra$$on of your so$$ware where you demonstrate understanding of the implementa$$on $($note:

just running the program will not demonstrate any knowledge of the implementa$$on$).$

Notes:

$$ Only the required files MUST be included in your repository, no other files $($any other files

will not be used when marking your work$).$

$$ If code does not compile and run, it will severely limit your marks for the code.

$$ Do not use any non$-$standard or OS specific libraries or system calls, which will prevent your

program from working correctly when being marked.

$$ Do not make any further commits to the repository once you have made the submission $$

the date of commits will be monitored and anything commi$$ed a$$er the deadline will be

ignored.

$$ Requests to $$pre$-$assess$$ summa$$ve assessment will be $($politely$)$ refused.

$2$

Figure $1$: The UML class diagram for the library system.

$3$

$3.$ Scenario

A small library has these types of books that are available to borrow for members only:

$1.$ Science fic$$on

$2.$ Sa$$re

$3.$ Drama

$4.$ Ac$$on and Adventure

$5.$ Romance

$6.$ Mystery

$7.$ Horror

$8.$ Health

$9.$ Guide

$10.$ Diaries

$11.$ Comics

$12.$ Journals

$13.$ Biographies

$14.$ Fantasy

$15.$ History

$16.$ Science

$17.$ Art

All books have an id$,$ name, author, type, and page count.

The program will only be used by the librarian at the library $($not by customers$/$members$)$ and will not

take payment details.

The system should include the following func$$onality:

$$ Add a member $$ the librarian should be able to create a new member and display the new

member$$s details directly following the crea$$on of the member.

$$ Issue a book to a member $$ the librarian should be able to issue a book to an individual

member with a valid due date from the date of issue $(3$ days$).$

$$ Return a book $$ the librarian should be able to return a book from an individual member.

$$ Display all books borrowed by any individual member $$ the librarian should be able to display

all books borrowed by an individual member.

$$ Calculate a fine for any individual member for overdue book$($s$)$ upon the return of a book, if

the book$$s due date has expired, a fine should be calculated based on a rate of $1$ per day

overdue.

Your program must have input valida$$on to ensure it performs correctly and helpful error messages

informing the user of any incorrect input. It should be intui$$ve$,$ i$.$e$.,$ the user shouldn$$t need to read

the source code or a$$end training to know how to use the system.

$4$

$4.$ Detailed Descrip$$on

It is recommended that you complete the tasks in the following order as the later sub$-$tasks will require

the earlier ones.

$4\mathrm{.}1.$ Plan So$$ware

Begin by planning which classes you need and how the so$$ware will work using the provided UML

diagram.

You should include:

$$ use case diagram$($s$)$

$$ we provided you with the class diagram$($s$)$

$$ ac$$vity diagram$($s$)$

$4\mathrm{.}2.$ Create a Git Repository

Create a Git repository for your coursework on Bitbucket or GitHub. As you create new files, you

should add them to the Git repository. Commit regularly with clear, useful commit messages. You will

need to submit the URL for your Git repository