Saturday, 13 July 2013

UML LAB-LIBRARY MANAGEMENT SYSTEM

LIBRARY MANAGEMENT SYSTEM

AIM: To Create UML diagrams of Library Management System.
1. Problem Statement: To model Library Management System in which for the purpose of monitoring and controlling the transactions in a library.
2. Functional Requirements:
    1. The Librarian will have a complete access to the system as listed below.
       1.1 Permits to login with unique register id.
       1.2 Can add new items to database, can delete damaged items from data base.
       1.3 Check on transactions of borrowers and ensure charges for overdue items, damaged
           and lost items are paid. Ensure delays in returning borrowed items are not repeated.                  
    2. The Members (Staff and Students) have to login into the system and they can search
         for a particular book. They can borrow a book, renewal a book.
3. Modeling a LIBRARY MANAGEMENT SYSTEM
Step 1: Construction of Use case Diagram:


Step 2: Construction of Class Diagram:


Step 3: Construction of Sequence Diagram:


Step 4: Construction of Collaboration Diagram:


Step 5: Construction of Activity Diagram:


Step 6: Construction of State Chart Diagram:

Step 7: Construction of Component Diagram:


Step 8: Construction of Deployment Diagram:

UML LAB- ATM SYSTEM

ATM SYSTEM


AIM: To Create UML diagrams of ATM Application.
1. Problem Statement: To model automatic teller machine in which a customer uses his/her ATM card to perform basic banking activities from ATM.
2. Functional Requirements:
The ATM must be able to provide the following services to the customer:
1. Withdrawal of an amount
2. Money transfer between two account
3. Deposit of cash in an envelope
4. Enquiry of Balance
5. Abort a transaction in progress by pressing the cancel key
6. Display an explanation, if a transaction fails.
7. Verification of each transaction with the bank.
8. Provide a printed receipt of each transaction to the customer with date, time, etc..,.
9. Maintain an internal log of transactions to receive in case of failures.
3. Modeling an ATM System
Step 1: Construction of Use case Diagram:

Step 2: Construction of Class Diagram:

Step 3: Construction of Sequence Diagram:

Step 4: Construction of Collaboration Diagram:

Step 5: Construction of Activity Diagram:

Step 6: Construction of State Chart Diagram:

Step 7: Construction of Component Diagram:

Step 8: Construction of Deployment Diagram: