32 lines
2.7 KiB
Markdown
32 lines
2.7 KiB
Markdown
# Domain Description
|
|
|
|
## Entities
|
|
* Book
|
|
* Shelf
|
|
* BookInstance
|
|
* Member
|
|
* LendRecord
|
|
## User Stories
|
|
|
|
### Book count
|
|
In the morning the librarian has to count the books in 1 shelf. There are several shelfs. Every day the librarian checks the status of the books in one shelf that they haven't done in the longest time.
|
|
Upon book count complete a report will be generated telling the librarian what books are missing. In case there are any books missing they can do an investigation on their own. However this investigation will not be tracked through this software and is considered out of scope. The book if not found will be marked as lost. If the librarian ever finds this book again will have the option to unmark the book from lost status.
|
|
|
|
### Reading Time
|
|
The members are allowed to come in and read any book of their liking within the library. If they want to put the book back it is recommended to give the book to the librarian and they can put it back in the shelf it needs to be in. The system idealy has a way to scan the book and get the shelf name very quickly and always available so that librarian doesn't have to spend alot of time thinking about where the book goes. </br>
|
|
Ideally there will be a bulk option as well in case the librarian is busy with work. When in this pannel the books scanned will change status to put aside. The putaside pannel will organize books by shelf number so that the librarian can group the books and move them together to each shelf in groups.
|
|
|
|
### Lending Pannel
|
|
While normal operations is running members can bring books to the librarian and ask for them to be lended. The books will have an attached physical history writen with pen and paper. Along with the members first name the lend record number/code will be writen down as verification.This code should be randomly generated and unique for each lend record, idealy short so as to not write down a long code.
|
|
|
|
### Registration
|
|
The librarian will need to register new members as they walk in. They will need to fill in a form will all their information. We will collect their name, phone and email for late fee notifications and reminders.
|
|
|
|
### Books and instance registration
|
|
When the new books arrive they will be kept in storage until the book and their instances can be created and distrubuted to correct shelves ordered by the librarian according to their discretion.
|
|
|
|
### Librarians Registration
|
|
When a new librarian is hired another librarian will have to register the new librarian and setup a password for them.
|
|
|
|
# Library Technical Decisions
|
|
It is my belief that a web application will best fit the job as it can be mobile friendly. If a librarian needs to quickly check something they can do it over the phone without having to rush back to the computer to do so. |