![]() In this article, I have explained how to draw a Use Case Diagram of Library Management System in Star UML. The last Use Case is Update Member Details, which will be done by the Librarian when anything needs to be updated. The thirteen Use Case is Return Book, which will have the 14th use case Charge fine, which will be given to the member when He/She returns them late. The twelfth Use Case is Issue Book, when a member will need a book the librarian will issue it to them. ![]() It will have Include Relationship between Librarian and the Use Case. The seventh Use Case is Issue Membership Card, that is very important for the member as He/She cannot issue a book or get it.Įighth Use Case is Maintain Book Record which includes three mandatory steps that a Librarian will perform that are 9th, 10th, and 11th use cases: Add Book, Remove Book, and Delete Book. If the Member do not need the membership further then He/She can request for Membership cancellation and the Librarian will cancel it. Sixth Use Case for The Librarian is Cancel Membership. It is optional and that’s why it is added using the Extend Relation.įifth Use Case is Search Book that is very important one in a Library Management System. This is the Fourth Use Case that is optional and comes under the Request for Book Return Use Case. Now if the user Returns the Book Late, He/She needs to Pay Fine. A use case describes a sequence of actions that provide something of measurable value to an actor. Your Computer actor is in fact internal system therefore should not be modeled as an actor. Third Use Case is Request for Book Return, as the member after reading the booking needs to return then before that He/She needs to request for it. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. This is also done by the Member When He/She needs a book and will need to request for it. Second Use Case is Request for Book issue. The First Use Case is Inquiry for Membership which a Member will do when he comes to the Library Management System. ✦ Add Use Cases for Library Management System:įollowing are the Necessary Use Cases in Library Management System: There are basically two Actors in Use Case Diagram of Library Management system: As the following figure illustrates, an extend relationship is displayed in the diagram editor as a dashed line with an open arrowhead pointing from the extension use case to the base use case. Just Click and Drag it on the White Board and give it the name as Library Management System.Īfter this Draw an Actor by selecting it from the left. In UML modeling, you can use an extend relationship to specify that one use case (extension) extends the behavior of another use case (base). To start with the Use Case Diagram of Library Management System, you need to add a Use Case Subject from the left. There is another problem, How to make the endpoints of the association line connect directly to a actor or a use case. ![]() Step 2: Draw a Use Case Diagram ✦ Add Use Case Subject Thx, it works, now I can add a use case diagram. Go to Model -> Add Diagram -> Use Case Diagram ![]() Steps to Draw Use Case Diagram of Library Management System: Step1: Add Use Case Diagram If you like to read and look at it, then you can proceed to the article below. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |