Scenario: University Library System Requirements
The library contains books and journals as library material. It may have several copies of a given book or journal. All library material has an id #, a title and one or more authors. Further the library categorizes all library material as reference-only items or regular items. Referenceonly items can be loaned for 2hrs and can’t be removed from the library. Regular items may be borrowed by any library member for three weeks. Only members of staff may borrow journals. Members of the library can normally borrow up to six items at a time, but members of staff can borrow up to 12 items at a time. New books and journals arrive regularly, and old ones are sometimes disposed of. Details of these are managed by the librarian.
It is essential that the system keeps track of when books and journals are borrowed and returned. The new system should also produce reminders when a book is overdue. There may in future be a requirement for users to be able to extend the loan of a book if it is not reserved. Anybody can browse in the library. Staff and students are library members.
The following events were identified for this case:
Event
1. A library member borrows a book copy.
2. A member of staff borrows a journal copy.
3. A library member returns the book copy.
4. A member of staff returns the journal copy.
5. A library member browsers library catalog.
6. Librarian updates details on books and journals.
7. A library member wishes to extend a book loan.
8. Time to produce overdue book reminder.
1. Create a use case diagram for the University Library System capturing all the functional requirements.
2. Draw a class diagram for the description above. Make sure to show attributes, multiplicities and aggregations/compositions, where appropriate. No need to show any methods.
HERE ARE THE DIAGRAMS...COMMENT FOR ANY QUERIES
PLEASE GIVE AN UPVOTE
Get Answers For Free
Most questions answered within 1 hours.