JackNJill School wanted to computerize their library management system and has

come up with some basic requirements as below.

1.

Both Students and staff members of the school should register themselves

as a new user for first time.

a.

Everyone who wants to access the library should fill out the register

form (like Name, student or emp #, phone number, address, etc) and

get them registered for the first time.

b.

Once registration is complete, they will receive a library ID card.

2.

Once registered, users (both students and staff members) will be able to do

the following

a.

Authenticate themselves

b.

Reserve a Book (This includes searching for a book) only if the book is

available in the library.

c.

If the book is not available in the library, then request for a new

book.

d.

Renew a book (In addition, renewal is not valid for more than 2 times

for any book).

e.

They will also pay fine if the book is not returned within the end date.

3.

The librarian of the school is responsible for many things such as

a.

Adding a new book to the library

b.

Delete a book from library

c.

Updating the online catalog with the new and deleted books

d.

Maintaining the students and staff accounts.

e.

Send the overdue notifications to those who did not return book by

due date.

f.

Send the reservation confirmation to the users.

g.

Send the reservation cancellation to the users.

 

 

 

 

 

 

 

Part A- UML Use Case Diagram (50 Points)

With the above information, create UML use case diagram. Make sure to show all

the actors, use cases, the include and exclude relationship and use cases and its

respective system boundaries.

Part B

-

Class Diagram (50 Points)

The system should be able to store the following information

•

For each book, the system should store elements such as bookid, author,

name, price, rack_num, status, edition, dateofPurchase. The books entity

includes Journals, Magazines, Study books, CD-ROM, etc

•

For each user, the system should store userID, user Type(Student or staff),

date of Registration, emaild, phone Number, DOB, etc)

•

Similarly for the librarian, the system should store name, password,

empnum and various operations or methods such as searchBook,

verifyMember, issueBook, calculateFine, etc.

•

For every or book taken by the user, the librarian store the following

information as transactionRecords (transactionID, UserID, bookid, date of

issue, dueDate, etc). Also includes the operations or methods such as

createTransaction(), RetriceTransaction(), deleteTransaction().

•

The Librarian issues one or more books to users. He or she creates the

transactions or bills to users. The users will pay the bill.

With the above information, create UML

class diagram

. Make sure to show all the

classes, associations (generalizations or specializations), multiplicity

Notes:

•

Please draw the diagrams using Visual Paradigm tool only.

•

Please save the diagrams and upload the files as attachments (one for Class

diagram and one more for use case diagram).

•

Also please take a screenshot of the diagrams and paste them in another

document and upload the screenshots.