In other words, only those use cases are listed that actors will need to do when they are using the system to solve the customer’s problem. Each task is called a use case because it represents one particular way the system will be used. More details mentioned here InterfaceĪfter determining the actors, the second step in use case analysis is to determine the tasks that each actor will need to do with the system. This class removes the bidirectional dependency between HoldRequest and Book.
Note: After Refactoring, new Class 'HoldRequestOperations' is added to the above structure which lies in between the HoldRequest class and Book class. The class diagram file can be opened using Star UML. The Class Diagram of the project is also provided along with the Database Schema file. This project was designed during the course 'Object Oriented Analysis and Design CS309'. Minimal Code is written in the GUI and the entities are decoupled as well.
A Library Management System made using the concepts of Object Oriented Analysis and Design.
