Book Exchange UML

The Wauwatosa Book Exchange has asked you to help them design a Java application as part of a technology initiative. The book exchange is a non-profit place where customers can borrow and lend books for others to read. At this point, the IT management staff has asked you to provide them with UML design diagrams, including a class diagram, a use-case diagram, and a sequence diagram, that will help them understand what your application will do. The IT management staff has already completed a list of requirements for the application. They are listed below.

The requirements for the application are:

• The application will act as a support system for the book exchange.
• The book exchange lends books to borrowers, who are registered in the system. The books are also registered.
• The book exchange handles the purchase of new titles. Many copies of popular titles are bought. Books and magazines are given away when they are out of date or in bad condition.
• An employee of the book exchange interacts with the customers. The employee's work is supported by the system.
• Modifications to information such as titles and customers can be made easily by using the application.
• The application is able to run under most operating systems, including UNIX and Windows, and has a modern graphical user interface.
• The application is designed for future growth.
• A book may be reserved.

The actors in the book exchange will be identified as the employees and the borrowers. The employees are the users of the system and the borrowers are the customers, although occasionally, an employee or another book exchange may be a borrower as well. The borrower is not intended to directly interact with the system. The borrower's functions are done on behalf of the borrower by the librarian.

First, create a class diagram of the book exchange application from these requirements. Your classes will correspond to Borrower, Item, etc. Each will be a class. You can use any UML tool you have access to or you may use Word to create the diagram - just make sure it is legible.

Second, identify what the book exchange system will be used for and who will be using it. These are the use cases and actors, respectively. All use cases must begin with an actor, and some will end with an actor as well. Actors are people or other systems that are outside of the system you are working on. Prepare a use case diagram.

Finally, identify the major actors in the book exchange system and then create a use case diagram of the book exchange system. Each of the use cases should be completely documented. At a very minimum, your documentation should include the following: Use case name, description, actors in the use case, and sequence diagrams. Here are a few use cases to get you started:

• Lend a Book
• Return Book
• Remove Book
• Add Customer
• Update or Remove Customer

Use Visio to create your diagrams. The UML templates (in Software and Database) should prove to be very useful. Once you have your diagram created, save it as a Visio file and then save it again as an image. Copy that image into your Word document. The Word document should include your Visio design of your class diagram, use case, and sequence diagram. Remember to include text in your document that explains each of your diagrams. Submit your work to the Submit folder. The Word document should include a title page with a Running head, abstract/introduction, content body information, conclusion and references list in the Word document. The style of the document should not be a numbered Q&A list of items. It should be like a report using headers and subheaders. Your Word document should be double-spaced. The document must be in APA format. Refer to the APA citation Center in the Library if you are unclear about APA reports. There, you will find some sample papers. Do not forget to cite your sources and include in-text references. If there are no in-text citations and/or your references are not included, a 25% deduction could be applied.