A Modern Graphical User Interface in the Windows Operating System - Assignment Example

This document provides concrete details concerning the Object Oriented Modeling (OOM) through Unified Modeling Language (UML) design diagrams. The document contains graphical representation of class diagram, use case diagram and sequence diagram along with their theoretical description. These diagrams are produced as per the requirements identified and provided by our Professor. The intended audience of this document is primarily the software development team/programmers of the Library Management System, but it also addresses all other parties that might have an interest in the software under development. The overall objective of preparing this document is to understand user requirement gathering, analysis and design process. The Library Management System would facilitate the employees and librarian in managing and organizing the books in a library through automated catalog system. The system is intended to develop in Java computer language and would be able to execute on UNIX and Windows Operating System having a modern graphical user interface. Keywords: Unified Modern Language (UML), Use Case Diagram, Class Diagram, Sequence Diagram, User Requirements, Object Oriented Modeling Class Diagram Description of Class Diagram In an object oriented application, the class diagram describes the basic structure of the system that is developed to represent the classes within a model having attributes or variables, operations or functions and relationships of one class with other classes (Martin, 2002). The class diagram of Library Management System has been given above, the entity or class name “Employee” illustrated with rectangle divided into three sections, the first section contains the name of the class i-e “Employee”, the second section contains the attributes or variables of the class, whereas, the third section contains the functions or methods of the class. In the above diagram, a customer can perform four operations that includes the customer has to be registered member of Library through the employee of Library for borrowing book, returning book, and he has also right of canceling/removing registration. As these classes are inherited classes therefore, these can perform the same operations as the Borrower. The variables or attributes of a customer class contains CustomerID, RegistrationDate, Email, Address and ContactInfo. The relationships between classes are represented by a straight line. For example, the relationship between the Borrower class, Library/Employee class and Customer class is determined by a straight line specifying that Borrower is the main class, whereas, Library/Employee and Customer are inherited classes of the Borrower class. Furthermore, same is the case with catalog, book and Magazine classes. This concept is also known as Generalization. Use Case Diagram Description of Use Case Diagram The above diagram shows the Use Case of Library Management System, developed as per requirement specification provided by our Professor. The Use Case Diagram is a methodology that classifies, simplifies and categorizes the users’ requirements by using functions’ (use cases) interaction with actors (Rouse, 2007). In the above diagram, there are two main types of actors are given; the first is “Employee” that will not only interact with the second actor “Borrower” but also with other use cases. Basically, the actor “Borrower” can be classified into three actors known as Library, Employee (wanted to borrow book/magazine) and Customer as identified in the requirement specification document. In the above Use Case Diagram, I have identified in total fourteen (14) use cases from which ten (10) would be utilized by the Employee actor whereas the other four (4) are the functions of Borrower actor. The Borrower actor can interact with four use cases along with the other actor Employee, the four use cases includes the customer has to be registered member of Library through the employee of Library for borrowing book, returning book, and he has also right of canceling/removing registration. In order to do any of the above function the Borrower has to interact with the Employee, he cannot interact with the system directly. Whereas, the use cases of an “Employee” actor include add employee, update employee, add member (customer, library, employee to lend a book), update member, remover, reserve and issue book, search and update catalog. It is pertinent to mention here that the “Employee” actor can perform the same functions of book to the magazine as well. Sequence Diagram Description of Sequence Diagram The Sequence Diagram consists of actors (identified in use case diagram), system/database, and their interaction (sequence of actions) with respect to time. A sequence diagram is an critical part utilized in procedures of analysis and design documentation of user requirements. A sequence diagram is a tool of UML that represents interaction of different actors with the system in order to get a result/response. (Bell, 2004) As per the above given sequence diagram of Library Management System and the definition, the actors that were identified in Use Case Diagram are utilized in Sequence Diagram as well. The first actor is Borrower that would only interact with the actor Employee and the Employee would interact with the system or database. As shown in the above figure, all the interaction with the system is through the Employee. Initially, the Borrower would register himself with the Library through the Employee, in this process, the Employee would provide the registration form and ask to fill and submit. The borrower would submit the registration form to the employee enter the information to the system would provide a registration ID. However, once the borrower is registered with the system does not need to re-register or this process. In order to borrow a book or magazine, the borrower has to provide the registration ID to the employee would check and made it verified through the system. Once the registration ID got verified, the borrower would ask for the book or magazine title from the employee would search it through the system, if he found the book or magazine, the same would be provided to the borrower; else, the process may again be initiated to borrow the book or magazine. Whereas, while returning the book, the borrower just need to return the book to the employee would update the system to get a receipt. The receipt would be provided to the borrower as evidence. References Robert C. Martin. (2002). UML – Tutorial: Part 1 – Class Diagrams. Retrieved from http://www.objectmentor.com/resources/articles/umlClassDiagrams.pdf SmartDraw. (2009). What is UML Class Diagram?. Retrieved from http://www.smartdraw.com/resources/tutorials/uml-class-diagrams/ Margaret Rouse. (2007). Use Case. Retrieved from http://searchsoftwarequality.techtarget.com/definition/use-case Kirill Fakhroutdinov. (2008). Use Case Diagrams. Retrieved from http://www.uml-diagrams.org/use-case-diagrams.html Altova UModel. (2012). UML Sequence Diagram. Retrieved from http://www.altova.com/umodel/sequence-diagrams.html Donald Bell. (2004). UML basics: The sequence diagram. Retrieved from http://www.ibm.com/developerworks/rational/library/3101.html Read More