Cycle I

INDEX
CYCLE - I
EX. NO.
DATE
NAME OF THE EXERCISE
PAGE NO.
SIGN.
1.
Study of UML
2.
On - line Purchase System
3.
Library Management System
4.
E Ticketing System
5.
Quiz System
6.
Student Mark Analysis System
7.
E Mail Client System
8.
Course Registration System
9.
On - Line Banking System
10.
On Line Aptitude Test System
Ex. No. : 1
STUDY OF UML
AIM:
To study the basic concepts of Unified Modeling Language.
UML NOTATION:

Unified Modeling Language. Set of notations and conventions used to describe and model an application. Universal language for modeling systems. Standard notation for OO modeling systems. Does not specify methodology to develop an application.
UML DIAGRAMS:
Class Diagram Use Case Diagram Behavioral Diagram
Interaction Diagram Sequence Diagram Collaboration Diagram State Chart Diagram Activity Diagram Implementation Diagram
Component Diagram Deployment Diagram
CLASS DIAGRAM:
Shows the static structure of the model. Collection of static modeling elements such as classes and their relationships connected as a graph. Provides visual representation of objects, relationships and their structures.
Class: A class is a set of objects that share a common structure and common behavior. It is represented as, <Class Name> <Attributes> <Operations>
Interface: Specifies the externally-visible operations of a class and/or component.
Association: Model properties of associations. The properties are stored in a class and linked to the association relationship. Example, Bank Account Person
Generalization: A generalize relationship is a relationship between a more general class or use case and a more specific class or use case. Example,
Vehicle
Bus
Truck
Car
USE CASE DIAGRAM:

Set of use cases enclosed by system boundary, communication association between actors and use cases, and generalization among use cases. Actors:-
External factors that interacts with the system from the user's perspective.
Use Cases: Set of scenarios that describe how actor uses the system. Represented as,
Relationship: Communication communications with the use case normally. Uses Shown by generalization arrow from the use cases. Extends Used when one case does more than another that is similar to it.
BEHAVIOR DIAGRAM:
INTERACTION DIAGRAM: Diagrams that describes how group of objects are collaborated.
SEQUENCE DIAGRAM: Describes the behavior of the system through interaction between the system and the environment in time sequence. Two dimensions: Vertical dimension represents time. Horizontal dimension represents objects.
Life line Object's existence during the interaction.
Object 1
Object 2
<Event>
COLLABORATION DIAGRAM: An interaction diagram that shows the order of messages that implement an operation or a transaction. Collaboration diagrams show objects, their links, and their messages. Object 1 1. <Event> Object 2
Object: Link: A link is an instance of an association, analogous to an object. A message is the communication carried between two objects that trigger an event. STATECHART DIAGRAM: State: Represents a condition or situation during the life of an object during which it satisfies some condition or waits for some event. Models the dynamic behavior of individual classes or any other kind of object. Shows the sequences of states, events, and actions. Message:An object has state, behavior, and identity. Objects interact through their links to other objects.
<State>
Start State: Shows the beginning of workflow.
End state:: Represents the final or terminal state.
ACTIVITY DIAGRAM: Used for modeling the sequence of activities in a process Special case of a state machine in which most of the states are activities and most of the transitions are implicitly triggered by completion of the actions in the source activities. Activity: Represents the performance of task or duty in a workflow. <Activity> Swim lanes: Represents organizational units or roles within a business model.
IMPLEMENTATION DIAGRAM:
Shows the implementation phase of system development. Two types of implementation diagrams: Component diagram Deployment diagram COMPONENT DIAGRAM: Models the physical components in the design. A graph of the designs components connected by dependency relationships. Includes concept of packages. Package is used to show how classes are grouped together.
DEPLOYMENT DIAGRAM:
Shows the configuration of runtime processing elements and software components. It is a graph of nodes connected by communication association. Nodes are the components that are connected to other components through dependencies. Used in conjunction with component diagrams to show the distribution of physical modules.
RESULT:Thus the different conceptual models under UML have been studied.
Ex. No. : 2
ONLINE PURCHASE SYSTEM
AIM: To create a UML model for On-Line Purchase System. 1. ANALYSIS: 1.1 Identifying the Actors Customer Software Banking Dealer Browse Catalog Select Item Request Item Payment Details Issue Details Authentication Check for validity Deliver Goods
1.2 Identifying the Use Cases
2. REQUIREMENTS: 2.1 Hardware Requirements Processor: Pentium IV 1.7 RAM: 256 MB Hard Disk: 40 GB 2.2 Software Requirements CASE Tool: Rational Rose Enterprise Edition Programming Languages: Visual Basic 6.0 or Java Database: MS-Access
3. DESIGN
3.1 Use Case Diagram
Online Purchase
Browse catlog
customer
Select item
Request item
software
Ask for payment and shipping details
Issue Details
Banking issue authorization
Check for validity
Dealer Deliver goods
3.2 Class Diagram
Shopping Cart subtotal : Double salesm oney : D ouble totalmoney : D ouble shopping cart() getsubtotal() getsubtotal() getsales() getsalesmoney() gettotalm oney() settotalm oney() placeorder() remov eorder() customer[0..*]getcustom er() setcustomer() creditcard[0..*]() customer[0..*]getcustom er() setcustomer() setcreditcard() +1 C ustomer addtoship : String nam : String e addtobill : String em ailadd : String creditrating : Integer customer() getaddtoship() setaddtoship() getname() setname() getaddtobill() setbill() getemailadd() setemailadd() getcreditrating() setcreditrating() displaycatlog() selectitem() deliv eritem() remov eorder() C redit card creditcard() getnumber() setnumber() getexpirydate() setexpirydate() getissue() setissue() authorisechange() preffered() getitemofpurchase() setitemofpurchase() [0..*]getprefferedcustomer() setprefferedcustomer() [0..*]getprefferedcustomer() setprefferedcustomer()
+1 m creditcard +1
+* Item of purchase quantity : Integer priceperitem : D s ouble Item of purchase() getquantity() setquantity() getpriceperitem () set priceperitem () get custom er() setcustomer() product[0..*]getproduct() setproduct() getproduct() setproduct()
m Custom er
m Product nPrefferedC ustomer
Product product() Preffered customer discountrate prefferedcustomer() getdiscountrate() setdiscountrate() getcustomer() setcustomer() getcustomer() setcustomer() getcustomer() setcustomer()
3.3 Sequence Diagram
customer
shopping card
credit card
public void brow secatalog()
public void display catalog() public void selectitem() public void getcreditrating() public void getaddtoship() public void setcreditcard() publ;ic void shipmentdetails() public void authorizedcharge() public void getexpirydate() validation
public void authorize() public void setcrediting(int val) public void setadddtoship() public void delieveritem() public void rejected()
public void removeorder()
3.4 Collaboration Diagram
1: public void brow secatalog() 3: public void selectitem() 6: public void setcreditcard() 7: publ;ic void shipmentdetails() customer 2: public void display catalog() 4: public void getcreditrating() 5: public void getaddtoship() 12: public void setcrediting(int val) 13: public void setadddtoship() 14: public void delieveritem() 16: public void removeorder() shopping card
11: public void authorize() 15: public void rejected()
8: public void authorizedcharge()
9: public void getexpirydate() 10: validation
credit card
3.5 Activity Diagram
Customer
Shopping Card
Credit card
Browse Catalog
Displaying Catalog
Selecting Catalog
Display
Selecting
Requesting
Validating credit
Issuing payment
Accepting delivery
Delivery item
Authorized
Rejected
3.6 State chat Diagram
CHECKING
WAITING
PROCESS
DELIVERY DELIVERY DISPATCH DISPATCH
CANCELLING CANCELLING
EXIT
RESULT: Thus the UML models for the Online Purchase System have been developed and verified.
Ex. No. : 3
LIBRARY MANAGEMENT SYSTEM
AIM: To create a UML model for Library management System. 1. ANALYSIS: 1.1 Identifying the Actors Student Computer Publisher Librarian Login Request Book Book Details Collect Books Order Books Issue Books Database
3. DESIGN 3.1 Use Case Diagram
Login
Request Book
Student
Book details
Collect books
Order books
Publisher
Issue books
Computer
Database
Librarian
3.2 Class Diagram
student scode : Integer sname : String student() getscode() getsname() view bookstatus() requestbooks() returnbook() setscode() setsname() +1..*
librarian issue books() orderbooks() issuecard() update() librarian() +1..*
publisher orderno orderbookname publisher() getorderno() setorderno() setorderbookname() getorderbookname()
database bookid : Integer bookname : String authorname : String accessno : Integer database() getbookid() setbookid() getbookname() setbookname() getauthorname() setauthorname() getaccessno() setaccessno()
Student: Database: login
Librarian:
Publisher:
public void orderbooks() public void delliverbook()
login valid public void update new arrivals()
public void bookstatus() bookavailable
validation issue books public void receive book() public void returnbook()
update

Database:
1: login 6: public void bookstatus()
Student:
4: login valid 7: bookavailable 10: public void receive book()
5: public void update new arrivals() 9: issue books 12: update 11: public void returnbook()
8: validation
3: public void delliverbook() Librarian: Publisher:
2: public void orderbooks()
student
librarian
computer
Login
ViewBook Status
Database
Return books
Book Available Request for books
Book updation
Book not available Receiving Books
Book issue

Student ID
Enter Id number
SID
Wrong id number Wrong ID-re-enter
Correct
ID Accepted
Re enter id
ID accepted
select from main menu Select from main menu
Prepare for next selection Library Main menu
RESULT: Thus the UML models for the Library Management System have been developed and verified.
Ex. No. : 4
E TICKETING SYSTEM
AIM: To create a UML model for E Ticketing System. 1. ANALYSIS: 1.1 Identifying the Actors Passenger Clerk Update Customer DB Validation Service ATM Cash to Customer Bill to Customer Credit Cards Payment Reservation Form Reservation Chart Cash Mode Ticket Confirm
Update Customer DB
Passenger Validation pname : String Age : Long sex : String DOJ : Date Bill to Customer Cash to Customer Service ATM passenger() getPname() setPname() getAge() setAge() getSex() setSex() getDOJ() setDOJ()
Credit Card
Payments
Reservation Form
Ticket Confirm Clerk
Cash mode
Reservation chart
3.2 Class Diagram
+1..* Passenger
(from Use Case Vi ew)
pname : String Age : Long sex : String +1..* DOJ : Date passenger() getPname() setPname() getAge() setAge() getSex() setSex() getDOJ() setDOJ()
Train Details no : Long destination : String tname : String source : String departureTime : Long arrivalTime : Long train_details() getNo() setNo() getDestination() setDestination() getTname() setTname() getSource() setSource() getDeparture() setDeparture() getArrival() setArrival()
+1..* Train_SeatDetails tno : Long DOJ : Date seats : Long coaches : Integer train_SeatDetails() getTno() setTno() getDOJ() setDOJ() getSeats() setSeats() getCoaches() setCoaches()
Payments amount : Double payments() getAmount() setAmount()
Reservation tno : Long DOJ : Date seatno : Long +1..* nop : Integer coaches : Integer reservation() getTno() setTno() getSeatno() setSeatno() getNop() setNop() getCoaches() setCoaches() reservation()
:Passenger
:Reservation
:Train Details
:Train Seat Details
:Payments
Public void reservation()
Public void getTrainDetails()
Public void CheckAvailability()
Public void payment()
Public void getPayment()
Public void IssueTicket() Public void update train_details()
:Passenge r
1: Public void reservation() 5: Public void getPayment() 6: Public void IssueTicket() 3: Public void CheckAvailability() 7: Public void update train_details() :Payment s 4: Public void payment() :Reservati on :Train Seat Details
2: Public void getTrainDetails()
:Train Details

Passenger Reserv ation Train Details Seat details
Check Train Details(From E-Ticket Activity) Check Seat Availabilty(From E-Ticket Activity)
Show Train Details(From E-Ticket Activity)
Reserve Tickets(From E-Ticket Activity) Request Payment(From E-Ticket Activity) Make Payments(From E-Ticket Activity)
Issue Tickets(From E-Ticket Activity)
Request for Credit Card Number
CREDIT AGENCY Validation Completed
Transaction Over
RESULT: Thus the UML models for E - Ticketing System have been developed and verified.
Ex. No. : 5
QUIZ SYSTEM
AIM: To create a UML model for Quiz System. 1. ANALYSIS: 1.1 Identifying the Actors Quiz participant Coordinator
1.2 Identifying the Use Cases Login Select Option Score Board Participant Information Winner List
login
Quiz Participant
Select Option
Score Board
Participant Information Co-Ordinate Winner List
3.2 Class Diagram
Quiz name userid course of study name of institution opname()
User name userid course of study Timing Constraints answer the question timer used()
Topic general technical scientific sports store the topic() topic()
Question Format display format display question() question format()
Database details about quiz display total score() db()
User
Database
Topic
Timining Constrains
Question Format
Enter Personal Information()
Select the Topic()
Store the topic in db
read the question and answer them
Check for the right answer
Allot Time
Display score
Database 1: Enter Personal Information()
User
7: Display score
2: Select the Topic()
3: Store the topic in db
Topic
5: Check for the right answer
4: read the question and answer them
6: Allot Time Timining Constrains Question Format
Enter Details
Store in Db
Choose Topic
Answer the question
The mes to answer
Set the timer
Display the score
Enter Personal Information
Store info
Choose Any topic set timer
Answer Question
Display Score
RESULT: Thus the UML models for Quiz System have been developed and verified.
Ex. No. : 6
STUDENT MARK ANALYSIS SYSTEM
AIM: To create a UML model for Student Mark Analysis System. 1. ANALYSIS: 1.1 Identifying the Actors Student Analyzer
1.2 Identifying the Use Cases Enter Marks Validate Marks Allot Grades Validate Grades Save Status
Enter marks
Student name : String Regno : String Enter marks() retrive results() students()
Validate marks Analyzer
Allot grades
Validate grades
Save status
3.2 Class Diagram
+the marks register Student

(from Use Case Vi ew)
name : String Regno : String Enter marks() retrive results() students()
Marks Register regno : String maxmarks : Integer minmarks : Integer marks obtained : Integer checkregno() checksuubjectcode() setresults() marksregister()
: Student
: Analyzer
Enter details
Validate
Check result
Allot grades
Retrieve results
6: 1: Enter details 2: Validate 5: Retrive results :Student 3: Check result 4: Allot grades :Analyzer
Enter marks in register
find out average
allot grades
max/min marks
marks obtained
show results
Student Details
Verify entries
Generate Results
Validate results
Print result
RESULT: Thus the UML models for the Student Mark Analysis System have been developed and verified.
Ex. No. : 7
E-MAIL CLIENT SYSTEM
AIM: To create a UML model for E-mail Client System. 1. ANALYSIS: 1.1 Identifying the Actors Client User Server
1.2 Identifying the Use Cases Login Read in Registration form Compose
Lo gin
read in C lient us er R egis t rat io n form S e rve r d b
C om p os e
3.2 Class Diagram
WebServer
Website address state website() website()
Client userid password() id Account id name create() id Account() id Account() login()
the website
the compose
the check mail Check Mail readreply check() delete() save() checkmail() checkmail()
Compose mes text images edit() send() compose() compose()
user
webserver
database
enter web address
display web pages
new user
create id id created
enter password
existing user password accepted
display inbox reg
display inbox
check mail
compose mail
send mail
check valid id
valid id
message sent
logout
user
6: enter password 7: existing user 9: display inbox reg 13: send mail 17: logout 1: enter web address 3: new user
2: display web pages 16: message sent 4: create id 11: check mail 12: compose mail 5: id created 10: display inbox webserver
8: password accepted 15: valid id
14: check valid id
database
Display the web page
Id and password verification
Display the details of user Composer
Read e-mail
Send /Receive mail
Logout of site
Webpage display
Enter id and password
Display work
Send/Rece ive mail
Logout
RESULT: Thus the UML models for the E-mail Client System have been developed and verified.
Ex. No. : 8
COURSE REGISTRATION SYSTEM
AIM: To create a UML model for Course Registration System. 1. ANALYSIS: 1.2 Identifying the Actors User Administrator
1.2 Identifying the Use Cases Course Selection Information Timing Selection Pay fees Checks Eligibility Process student Details Confirmation of Course
course selection infon
timing selection user
pay fees
checks eligibility
administrator
process student details
confirmation of course
3.2 Class Diagram

user view course details() user(registration) name : string add : string mark in HSC : integer mark in SSLC : integer eligibility() USER(Disconnect ) Disconnect() COURSE CONFIRMATION course name : string confirm()
ELIGIBILITY CONDITION mark in HSC : Integer mark in SSLC : Integer Eligibility() TIMING CONFIRM timing : Integer T confirm()
PAYMENT CONFIRM amount : Integer P confirm()
DATABASE course detail() ADMINISTR ATOR maintain database() process payment infon()

CHECKING ELIGIBILITY USER view course details SYSTEM ADMINISTRAT OR
display course details
require user details enter details check eligibility eligibility is confirmed or not display information

CHECKING ELIGIBILITY
1: view course details 4: enter details USER 2: display course details 7: display information SYSTEM
6: eligibility is confirmed or not
3: require user details
5: check eligibility
ADMINISTR ATOR

COURSE CONFIRMATION user system view offered courses administrator database
display courses
select courses process information check seats availability seats available or not sends infon display infon
1: view course details 4: enter details USER 2: display course details 7: display information SYSTEM
6: eligibility is confirmed or not
3: require user details
5: check eligibility
ADMINISTR ATOR

TIMING CONFIRMATION user view timing infon display timtin infon select timing process timing infon check availablity of seats in selected timing seats available or not sends infon display infon system administrator database
TIMING CONFIRMATION
1: view timing infon 3: select timing user 2: display timtin infon 8: display infon 7: sends infon 4: process timing infon 5: check availablity of seats in selected timing administra tor 6: seats available or not database system

PAYMENT CONFIRMATION user system administrator database
view fees details display fees details
pay fees store payment infon sends fee infon
join the course
PAYMENT CONFIRMATION
1: view fees details user 2: display fees details 3: pay fees 6: join the course 4: store payment infon administra tor 5: sends fee infon database system
start
view course details c
check eligilibity conditions register
disconnect
select coarse
check availability of seats select timings
confirm timings
payment details
confirm registration payment confirmation
join course
exit
COURSE DETAILS
ELIGIBILITY CONDITIONS
SEATS AVAILABILITY
TIMTING INFORMATION
REGISTRATION CONFIRMATION
PAYMENT CONFIRMATION
JOIN CONFIRMATION
EXIT
3.13 Component Diagram

USER INTERFACE
UPDATE DATABASE
3.14 Deployment Diagram

ADMINISTRATOR
USER
RESULT: Thus the UML models for the Course Registration System have been developed and verified.
Ex. No. : 9
ON LINE BANKING SYSTEM
AIM: To create a UML model for On Line Banking System. 1. ANALYSIS: 1.3 Identifying the Actors Client Bank Administrator
1.2 Identifying the Use Cases Account Creation Login Accounting Transaction
account creation
login Bank adminstrator client accounting
transaction
3.2 Class Diagram
online banking
Bank administrator
Customer1 account no password accounting()
account maintanance account creation account status update()
transaction approval payee account status receipient amount transfer() account update()
Account customer name customer ID customer password account status() transaction history()
transaction approval payee account status receipient amount transfer() account update()
ACCOUNT CREATION Customer visit Website Account Bank administrator
request for login or creation
request creating form
request form
fill and send form
saved in administrator
request amount amount to bank
create account
send ID and password
login 7 days
ACCOUNT CREATION
1: visit 3: request creating form 4: request form 5: fill and send form 11: login 7 days Website 2: request for login or creation
Customer
8: amount to bank
6: saved in administrator
7: request amount 10: send ID and password
Account 9: create account
Bank administrator

LOGIN Customer Request login Website Account Bank administrator
enter login
enter password check password and login
authentication
refer related account
send account details

LOGIN 2: enter login 3: enter password Customer 1: Request login Website
4: check password and login 7: send account details 5: authentication
Account 6: refer related account
Bank administrator

ACCOUNTING Customer request kind of transaction Website Account Bank administrator
enter kind of transaction
request transaction detail
enter recipient account no & amount
checking account status
request for transaction
transaction approved
amount transfered
message to customer
ACCOUNTING Customer
2: enter kind of transaction 4: enter recipient account no & amount Website 1: request kind of transaction 3: request transaction detail
8: amount transfered
9: message to customer 5: checking account status
7: transaction approved Bank administrator 6: request for transaction Account

TRANSACTION Customer Website Account Bank administrator
request account or transaction
enter account
request account details
display account details enter transaction
request history of transaction
display completed transaction
message for pending transaction
TRANSACTION
2: enter account 5: enter transaction Customer 1: request account or transaction Website
7: display completed transaction 8: message for pending transaction 4: display account details 6: request history of transaction
3: request account details Bank administrator
Account
Visit the website
New account creation
Enter account no
Enter password Enter personal details Password not accepted Initial amount received in 7days Password accepted Amount not received in 7days
Application expired Checking account status Administrator refer personal Error message to customer Message to customer Application not accepted Preform transaction
Application Accepted
Send account no & code to customer
Contact customer
Account not access in 3days
Account access in 3 days
Account creation completed
logout

visit website
Account creation
Login
Accounting
Transactio n
logout

USER INTERFACE
UPDATE DATABASE

ADMINISTRATOR
USER
RESULT: Thus the UML models for the On Line Banking System have been developed and verified.
Ex. No. : 10
ON LINE APTITUDE TEST SYSTEM
AIM: To create a UML model for On Line Aptitude Test System. 1. ANALYSIS: 1.4 Identifying the Actors User Administrator
1.2 Identifying the Use Cases Registration Login Trail Assessment Aptitude Test Time Limits Result
Registration
Login User
Trial Assessments
Time Limits Aptitude test
Result
Admin
3.2 Class Diagram

Registration name address phone no email id enter user name() enter()
Login user name password Open ID()
Final Apps test Questions Time Answer the Question() Time Display()
Trials questions Time Answer the questions() Time Display()
Result Databases Marks Calculate Marks()

REGISTRATION User Enter Database System Administrator
Register
Accepted
Unique id
Password
REGISTRATION
1: Enter Database User System
3: Accepted
4: Unique id 5: Password
2: Register
Administra tor

LOGIN User System Administrator
Enter Userid
Enter password
Verify details
Proceed
Show Home page

LOGIN 1: Enter Userid 2: Enter password User 5: Show Home page 4: Proceed System
3: Verify details Administra tor
TRIAL User System Administration
Login
Model questions
Request
Question paper
Display
Answers
Verify
Result
Display

TRIAL 2: Model questions 6: Answers User 5: Display 9: Display System
1: Login
4: Question paper 8: Result 3: Request 7: Verify
Administra tion

APTITUDE TEST User System login Administrator
Question paper
Display with time
Answers with time
Logout
Result
Display

APTITUDE TEST
4: Answers with time User 3: Display with time 7: Display 2: Question paper 6: Result 5: Logout System
1: login
Administra tor
RESULTS User System Administrator
Validate answers
send marks
display
logout
RESULTS
User 3: display 2: send marks
System
4: logout
1: Validate answers
Administra tor

Start
Registration
Login
Trial Assessments
Aptitude test
Result
New State

USER INTERFACE
UPDATE DATABASE

ADMINISTRATOR
USER
RESULT: Thus the UML models for the On Line Aptitude Test System have been developed and verified.

Cycle I

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cycle I

Hochgeladen von

Copyright:

Verfügbare Formate

INDEX

NAME OF THE EXERCISE

On - line Purchase System

Library Management System

Student Mark Analysis System

E Mail Client System

Course Registration System

On - Line Banking System

On Line Aptitude Test System

To study the basic concepts of Unified Modeling Language.

Component Diagram Deployment Diagram

Interface: Specifies the externally-visible operations of a class and/or component.

USE CASE DIAGRAM:

Life line Object's existence during the interaction.

Start State: Shows the beginning of workflow.

End state:: Represents the final or terminal state.

ONLINE PURCHASE SYSTEM

1.2 Identifying the Use Cases

3.1 Use Case Diagram

Ask for payment and shipping details

Banking issue authorization

Check for validity

Dealer Deliver goods

3.2 Class Diagram

m Product nPrefferedC ustomer

3.3 Sequence Diagram

public void brow secatalog()

public void removeorder()

3.4 Collaboration Diagram

11: public void authorize() 15: public void rejected()

8: public void authorizedcharge()

9: public void getexpirydate() 10: validation

3.5 Activity Diagram

3.6 State chat Diagram

DELIVERY DELIVERY DISPATCH DISPATCH

LIBRARY MANAGEMENT SYSTEM

1.2 Identifying the Use Cases

3. DESIGN 3.1 Use Case Diagram

3.2 Class Diagram

librarian issue books() orderbooks() issuecard() update() librarian() +1..*

publisher orderno orderbookname publisher() getorderno() setorderno() setorderbookname() getorderbookname()

3.3 Sequence Diagram

Student: Database: login

public void orderbooks() public void delliverbook()

login valid public void update new arrivals()

public void bookstatus() bookavailable

3.4 Collaboration Diagram

1: login 6: public void bookstatus()

4: login valid 7: bookavailable 10: public void receive book()

3: public void delliverbook() Librarian: Publisher:

2: public void orderbooks()

3.5 Activity Diagram

Book Available Request for books

Book not available Receiving Books

3.6 State chat Diagram

Wrong id number Wrong ID-re-enter

select from main menu Select from main menu

Prepare for next selection Library Main menu

1.2 Identifying the Use Cases

3. DESIGN 3.1 Use Case Diagram

Ticket Confirm Clerk

3.2 Class Diagram