JAVABased on the Library Management System Project Description, write a Requirements document that encompasses the considerations that must be made before implementing the system. Your Requirements document should address the following:

Introduction $($purpose$,$ project scope, etc.$)$

Functional Requirements

Non$-$Functional Requirements

Use Cases and User Stories

Your requirements document should include a user story and UML use case diagram for each task of the project description.

Data Requirements $($the types of data the system needs to store, manage, and process$)$

User$-$Interface design

Eventually, you will add a GUI to this project. What should it look like, and how will the user experience it$?$ Think of the text boxes, text fields, buttons, etc that might be used.

Constraints $$ identify any limitations or restrictions that may impact the system$$s design or implementation

Glossary $/$ Appendices $$ add as needed

Project Introduction

For the rest of the term, we will implement the SDLC by designing an expanded version of the Library Management System project you were assigned in the previous module. We will implement the entire software development life cycle of this project, piece by piece, as we continue the course. We will also implement a fully functioning LMS application, which will contain a GUI and an SQL database. Once the project is complete, you will turn it in $-$ along with a finalized software development plan $-$ at the end of the semester. In the meantime, you'll be asked to work on a portion of your software development plan, and your code, with each remaining module in the course. As you update another piece of the project $($code and$/$or software development plan$)$ you'll be asked to turn it in$,$ and I'll give you feedback.

download.jpg

The rest of the assignments in this course are a large part of your overall grade, and each subsequent assignment depends on the one prior to it$.$ Every submission indicated on Canvas is required. You cannot get points for a past development plan or project checkpoint, once the due date arrives. However, if you miss a certain checkpoint along the way, that work is still required for future submissions. Any work that is missed along the way must be made up in order to finish the project.

Please e$-$mail me with questions along the way!

download$-1.$png

Library Management System Project Description

You have been assigned to write a library management system application for a local library. The system must hold the following information for each book in the library$$s collection: title, author, barcode number, genre, status, and due date. The LMS must be able to complete the following tasks:

Add books to the LMS$.$ To populate the LMS database:

Phase $1$ and $2$: the user will supply a comma$-$delimited text file that contains all the info for each book to be cataloged. Your application must read the data from the text file and add each book to the LMS$.$

Phase $3$: In the final version of this project, the user will supply a SQLite database instead of a text file with the info for each book to be cataloged.

Remove a book from the database, by barcode number or title. The barcode number or title will be supplied by the user.

Check out a book from the LMS$.$ When a book is checked out, its status is changed to $$checked out$$ and its due date is $4$ weeks from the current date. An error message must display if a book is already checked out. The title of the book to be checked out will be supplied by the user.

Check$-$in a book from the LMS$.$ When a book is checked in$,$ its status is changed to $$checked in$$ and its due date is $$null$.$ The title of the book to be checked in will be supplied by the user.

Display the contents of the database on the screen.