Download GDN and TDN-Enterprise Applicatio Development-Lecture Handout and more Exercises Software Development in PDF only on Docsity!
Table of Contents
- GDN & TDN
- Class Diagram
- Activity Diagrams
- Sequence Diagrams.......................................................................................................................................
- Update book:
- Borrow Book:
- Return Book:
- Delete Book:............................................................................................................................................
GDN & TDN
GDN for Member Interface Module
Now we write the TDN for the Member Interface Module
TDN for Member Interface Module
module MemberInterface
uses SearchBook, Register, Login, BorrowBook, ReturnBook
exports
procedure ShowGUI_Interface();
This module does all the member management. It shows a GUI with all the options for a registered member.
end MemberInterface
Member
Interface
Register
Login
Borrow
Book
Return
Book
Search
Book
Class Diagram is as follows:-
There are total 5 classes in our library Management System.
- LMS This class uses the function ShowInterface(). It acts as an interface for the user. Using this interface, the user can log-in to the Library System as a Member or Administrator.
- Librarian When the user enters as an administrator to the system, he can use the functions of this class. It is one of the most important class of library system.
- Member When the user of the system logs in as a member, the LMS shows the functions of this class. The user of this class has limited rights.
- DataBase This class is used to interact with the database. Both the librarian class and the member class uses the functions of this class.
- Book This class is used to view the book.
Activity Diagrams are as follows:-
Explanation:
To enter a new member of the system, first all information like name, id, address of the new member is entered to the form and then the function ValidateUser() is called. If all the information is correct and the member is not already present in our database, then a success message is returned otherwise the request is rejected.
Explanation:
Suppose that the library buys some new books. Now to enter these books in the database the user will have to log-in as an administrator. Then he will use the function AddBook(). This function will first check whether the book is already present in the database or not. If the book is not present in the database then it will be added in our database.
Sequence Diagrams are as follows
Add a book:
Explanation:
This is the sequence diagram for adding a new book to the database. First the user uses the LMS interface and enters as a Librarian. Then the librarian uses the function AddBook() of the database to make entry of a new book. When the entry is made the control is transferred back to the librarian. Now he can enter more books or he logs out.
Borrow Book:
Explanation:
Now, when a members borrows a books , he asks the librarian to issue the book. The librarian issues the book to the member using the issueBook() function.
Return Book:
Explanation:
This diagram shows the control sequence of returning a book. The member returns the book to librarian.
