SOCIAL NETWORKING SITE (CRACK BUDDIES)

AIM:
Develop a social networking site using UML diagrams

DESCRIPTION:

Crack buddies site is a social networking site that aims at bringing people
nearer in todays busy word where nobody has time to talk to their known
people over a telephone.
The main advantage of crack buddies site is that it allows working people to
communicate with their friends or family without any difficulties.
It has instant messaging facilities which makes real time communication
uploading of photos, videos and many more facilities are available to its user

USECASE DIAGRAM:

A usecase is an interaction between users and system; it captures the goal

of the users and the responsibility of the system to its users.

Actors:
1.User

2.Admin

User: User is the person who actually interacts or uses the system services.

Admin: Admin is the person who acts behind the scene that is he monitors the
system working and ensures the proper working of the system.

Registration:
This usecase mainly deals with registration or signup of a new user in this site.

Login:
In this usecase username and password are authenticated by the administrator.
 registration

login

friend request

instance messaging

newsfeed

admin
NewClass
status upload/update

profile settings

application

feed back blocking

communities

system-updates
Friend requests:
This usecase mainly deals with finding friends, accepting friend requests,
seeing suggested friends by site.

Instant messaging:
This usecase deals with the users messages that is send messages, receive
messages, group chat, spam messages, archived messages.

Newsfeed:
In this all the posts of the friends, family, members are shown on the home
page of the user from time to time.

Status updates/uploads: It consists of posting of status, uploading photos,

albums, videos etc.

Profile settings: It consists of profiles privacy settings, editing of profile.

Applications: In this usecase games and other crack buddies apps are
available.

Feedback and blocking:

In this usecase, feedback from users about the site. Blocking deals with filtering of
unwanted or spam content from the users timeline. This usecase also deals with
blocking of other users also, if there are suspicious or threat full activities by them.

Communities:
This usecase diagram deals with groups such as closed or secret groups to open
groups, fans page, liked pages other communities.

System updates:
If any new releases, then it is updated by the administrator.
SEQUENCE DIAGRAM:
UML sequence diagrams are an easy and initiative way of describing the
behavior of a system by viewing the interaction between the system and its
environment.

User Crack Buddies Database

Register as a user

Registered

Login Successfull

Find Friends

Display Suggestions

Instant Messaging

Messages stored

Receive messages

Upload photos, videos or as album

Updated and stored

Edit profile

Profile updated

Status updates

Update and show

Objects used:
1. User
2. Crack buddies
3. Database
ACTIVITY DIAGRAM:
It is a variation or special case of a state machine, in which the states are
activities representing the performance of operations and the completion of the
operation.
CLASS DIAGRAM:
A class diagram is a static object diagram. It shows snapshot of the detailed state
of the system ata point in time.

Classes used: User, Admin,Contents,Crack Buddies

 ATM BANKING SYSTEM

AIM:
To develop the ATM-BANKING SYSTEM using UML diagram

DESCRIPTION:
The automatic teller machine (ATM) is an automatic banking macine(ABM)
which allows customer to complete basic transactions without any help of
bank representatives.

There are two types of ATM:

The basic one allows the customer to only draw cash and receive a
report of the account balance.
Another one is a more complex machine which accepts the deposit.
ATM is an electronic machine/device which is used by bank customers to
process account transactions.
The user access their account through special type of plastic card-encoded
with user information on a magnetic strip.
The user insert the card into ATMs to access a/c and process their account
transaction.

USECASE DIAGRAM:
A usecase is a methodology used in system analysis to identify,clarify,and
organize system requirements.
The usecase is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a
particular goal.

PROCESSING:
System Maintenance:
o The ATM system maintenance was controlled by admin which
includes system reporting and system shutdown process.
Login:
o To perform transactions by the customer login is required.
 <<include>>

Repairs
System maintance
admin
<<extend>>

Wrong pin number

Login

Withdraw cash
Bank database

bank customer Check balance

Deposit

Other function

Transfer money

Withdraw Cash
o To withdraw cash from bank as per the customer wish.
Check Balance
o To check the balance in the customer account.
Deposit
o It is used to save the cash in customers account.
Other Functions
o To perform enquires, print receipt, checking current account etc.
Transfer Money
o To transfer money from one account to another account.

SEQUENCE DIAGRAM
 A sequence diagram represents object collaborations and is used to define
event sequences between objects for a certain outcome.
A sequence diagram is an essential component used in processes related to
analysis, design and documentation.

customer ATM machine Bank database

Insert card

Request pin
Verify

Valid
Transaction option

Withdraw
Reuest amount
Withdraw from account

Withdraw successful
Enter amount

Dispense cash

ASk receipt needed

Enter yes

Print receipt issued

ACTIVITY DIAGRAM
 An activity diagram is a graphical representation of an executed set of
procedural system activities and considered a state chart diagram variation.
It describe parallel and conditional activities, use cases and system functions
at a detailed level.

Enter pin
number

Incorrect Handle Incorrect pin

check
pin number

Ask for amount

Amount not available Prepare to print

receipt
Dispense cash

Not resolved

Finish transaction and print receipt

CLASS DIAGRAM:
 Class diagram is UML structure diagram which shows structure of the
designed system at level of classes and interfaces, shows their features,
constraints and relationships-associations, generalizations, dependencies, etc.

ATM Machine
Customer
ATM_Branch name
Pin number
Status
Amount
Transaction
Check_card()
Insert card()
Make_deposite()
Deposite amount()
Make_withdraw()
Withdraw_amount()
Check_balance()
Check_balance()
Generate_receipt()

Bank Database
Bank name
Place

Update account()
Store transaction()

Deposite Withdrawal

INVENTORY MANAGEMENT SYSTEMS

AIM:

To create an Inventory Management System using UML Diagram.

DESCRIPTION:

The inventory maintenance system is mainly used for maintaining a stock level.
With the help of inventory system we can know the details of Purchase, Sales
and Stock in hand .
This will helps to monitor all the transactions that take place and also it is used
to prepare a day - to day reports and forecast about the stock details.
USE-CASE DIAGRAM:
The functionality of a system can be described in a number of different use-
cases, each of which represents a specific flow of events in a system.
It is a graph of actors, a set of use-cases enclosed in a boundary,
communication, associations between the actors and the use-cases, and
generalization among the use-cases.

Explanation:
The Actors involved in the System:
1) Customer.
2) Supplier.
3) Manager.
Customer:
Customer can purchase the stock, check availability of stock, and purchase
the item.
Supplier:
Supplier the stock to manager.
Manager:
Manager can check the availability of stock, purchase stock, check
availability of stock, generate invoice, maintain stock and generate Report.
 Login

Check availability of stack

Purchase items

CUSTOMER Purchase stack

MANAGER

Generate Invoice

SUPPLIER Main stack

Report generation
SEQUENCE DIAGRAM:

A sequence diagram is an interaction diagram that details how operations are

carried out, what messages are sent and when.
Sequence diagrams are organized according to time.
The time progresses as we go down the page
Object used:
1) Customer.
2) Manager.
3) Supplier.
4) Database.

CUSTOMER MANAGER SUPPLIER DATABASE

LOGIN

LOGIN SUCCESSFULLY

CHECK AVAILABILITY STOCK

STOCK AVAILABLE

PURCHASE STOCK

PURCHASE ITEM
RETURN STOCK

MAINTAIN STOCK

GENERATE INVOICE

RETURN PAYMENT

REPORT GENERATION
ACTIVITY DIAGRAM:

Activity diagram is a variety special case of state machine.

These States are activities, that representing the performance of operations.

Login

Item details

Check
Availability

Item available
yes
Purchase the No Check
item no.of.Items

No.of .items available

Sales the items

Update
database

Get updated
report

Transaction Generate
Enquiry Report

Get transaction
Report
CLASS DIAGRAM:
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.
Class Diagram is a static object diagram.

Inventory
Item_name
Item_id
Quantity
Expiry_date
Price

Purchase()
Sales()
Transaction()
Pay_tax()

Purchase
Transaction Report
Item_name Sales
Customer_name
Item_id Item_name Item_name
Customer_name Item_id Item_id
Trans_date Quantity Itemdate
Trans_time Customer_name Trans_time
Amount Trans_date Quantity
Trans_time
Get_details() Amount Generate_report()
Submit_report()
Submit_report()
Get_details()
Submit_details()
 AIRLINE RESERVATION SYSTEM

AIM:
Develop a Airline Reservation System using UML diagrams

DESCRIPTION:
The manual system of ticket reservation takes more time and the number of
reservation per day is limited.
To increase the efficiency of the process, we go for online ticket reservation
system. This system supports online ticket booking.
This system is built for used to directly access the system online to book
details.
The user can book, print, delete tickets without help of a clerk.
The administrator has control over the adding flights available for booking
and has control over deleting flights that are not necessary.
The administrator and user can both enter the system using their respective
login details.

Use-case Diagram:
The functionality of a system can be described in a number of
different use-cases, each of which represents a specific flow of events in a system. It
is a graph of actors, a set of use-cases enclosed in a boundary, communication,
associations between actors and use-cases.

Login:
The user can give username and password to enter into the registration.

Registration:
The user can register their personal details.

Book Ticket:
The passenger is allowed to book a ticket on the flight requires date and time
is necessary for the user.

Cancel Ticket:
The passenger can decide to cancel after the ticket is booked.
Payment:
The user can pay the money for journey or refund the money

.Print Ticket:

The user can take print ticket for journey.

View Flight Details:

The user and admin can view the flight details.

View Passenger Details:

The user and admin can view their own details.

Add Flight:
The admin can add the flight on which ticket can be booked by the user.

Delete Flight:
The admin can delete the flight on which ticket can be deleted by the user.
Sequence Diagram:
Sequence diagram are an easy and interactive way of describing the behavior
of a system.

Passenger
Admin
Database

BOOKING:

CANCEL:
ADD:

DELETE:
Activity Diagram:
It is a variety or special case of a state machine. The states are activities
representing the performance of operations.
Class Diagram:
It is a static object diagram. It shows snapshot of the detailed state of system.

Passenger
Flight Details
Database
 ONLINE EXAMINATION SYSTEM

AIM:
To Develop a Online Examination System using UML diagrams.

DESCRIPTION:
 This Online Examination with Result was created using UML diagram. It enables
the user must login to online examination using Username and Password and they attend the
exam and get their results. And the Examiner has rights to upload the question or edit the
question or delete the question. And also the examiner can delete the user.

USE CASE DIAGRAM:

A usecase is a methodology used in system analysis to identify,clarify,and
organize system requirements.

The usecase is made up of a set of possible sequences of interactions

between systems and users in a particular environment and related to a
particular goal.

EXPLANATION:

Login for examination:

This option is used to Login by using username and password.
Add questions:
This option is used to Add the question by the Examiner.
Edit question:
This option is used to exit the questions by the examiner.
Change password:
This option is used to change the password by the user and examiner.
Add subject:
It is used to add the subject by the examiner.
Delete subject:
It is used to delete subject by the examiner.
Reports:
This option is used to show the all user results to the examiner.
Results:
This option is used to user to see there results.
Sequence Diagram

User Exam Exam

DataBase

Enter User-Name and Password

User-name and Password is Entered

Check is it Valid User

Not Valid User

Please Check U r
User name & Password

Valid User

U ar Permitted to Atten the Exam

Display Exam Instruction

Display Exam Questions

Answer the Question

Check if the Answer is Correct or not

Display Results

Activity Diagram:
 Get User-Name Re-Login
and Password

Check its
Valid user No
name and
password

Yes

Show Exam
Instruction

Display
questions

Show
Results

Log Out

Class Diagram:
 OnlineExam

+theOnlineExam

User1 ExamDataBase
UserID : Integer Admin1
Name : String Select_UserDatabase()
Admin_ID : Integer
Age : Integer Select_questionDatabase()
Name : String
Sex : String Age : Integer
Address : String Sex : Single
Address : Single
Select_Answer()
View_Results() Create_Question()
User1() Delete_Question()
Edit-Quesion()
Create_NewUSer()
Change_Password()
Display_Result()

QuestionDatabase
UserDataBase
subject1
user_id : Integer subject2
user-password : String subject3

display() display_question()
QuestionDatabase()

RAILWAY TICKET RESERVATION SYSTEM

AIM:
 To model the Railway Ticket Reservation using the software Rational Rose
with various UML diagrams.

DESCRIPTION:

Railway Ticket Reservation System is a system used for booking tickets over
Internet.
Any Customer can book tickets for different trains.
Customer can book a ticket only if the tickets are available.
Customer searches for the availability of tickets by initially filling details in a
form.
Tickets can be booked in two ways i-ticket or by e-ticket booking.
In case of i-ticket booking customer can book the tickets online and the
tickets are couriered to particular customer at their address.
But in case of e-ticket booking and cancelling tickets are booked and
cancelled online sitting at the home and customer himself has to take print of
the ticket but the cases amount for tickets are deducted from customers
account.
For Cancellation of ticket the customer has to go at reservation office than
fill cancellation form and ask the clerk to cancel the ticket than the refund is
transferred to customer account.
After booking ticket the customer has to checkout by paying fare amount to
clerk.

USE CASE DIAGRAM:

A Use Case Diagram at its simplest is a representation of a users

interaction with the system that shows the relationship between the user and the
different use cases in which the user is involved.

Update Train Details:

This Use Case is used to update the train details by the Administrator.

Reserve Ticket:

Reserve Ticket Use Case is used for reserve the Train Ticket by the
Passenger.

Cancel Ticket:

The Passenger cancel the reserved ticket in this Use Case.

View Ticket Fare:

 View Ticket Fare Use Case is used for viewing the Train details by the
Passenger.

View Train Details:

This Use Case is used for viewing the Train details by the Passenger.

Enquiry Ticket Availability:

This Use Case is used for view the Ticket Availability.

Update train detials

Reserve ticket

Cancel ticket

Passanger
Adminstrator

Refund Money

View Ticket Fare

View Train Details

Enquiry Ticket Availability

SEQUENCE DIAGRAM:

A sequence diagram is an interaction daigram that shows how process opreate

with one another and what is their order. It is a construct of a Message sequence
chart.
 Passanger Admin Database

view train details checking

Reserve the ticket Checking

Issue ticket

Store in data base

Request for cancellation

checking

Issuing ticket cancellation

Store in database

ACTIVITY DIAGRAM:

Activity diagrams are graphical representation of work flows

of stepwise activities and actions with support for choice, iteration and concurrency.
 Start

Reserve cancel
Ticket ticket

View
Details Check for
reservation list
Yes

Give Form
Fill Form
Inform
Customer No

check for seat reservation

Return
Yes Payment

Give
Details

Submit
Form

Issue
Ticket

Stop

CLASS DIAGRAM:

A Class diagram in the UML is a type of static Structure diagram that

describes the structure of a system by showing the systems classes, their attributes,
operations, and the relationships among objects.
 Passenger
Train Name
Address
Train no 1..* Age
Train name 0..1
Gender

SearchTrain()
BookTIcket() 1..* RailwaySystem
1 CancelTicket() Id
PayCharges() 1
ModifyForm() 1 Response()
1
makes

book
cancel

1
Payment
Amount
1..*
Ticket
pnr no
Stautus
No.of Persons
1..* ChargeType

NewTicket()
DeleteTicket()

ONLINE MATRIMONIAL SYSTEM

AIM:
 To design a matrimonial system using UML diagram.

PROBLEM STATEMENT:

This matrimonial system was created using UML diagrams.

It enables the user to register their details in this site.
The registered user can enter into the system using login user id &
password.
The users can maintain their profile. They can search for a match.
They can request the match and they can get response from their
match.

USE CASE DIAGRAM:

The matrimonial system contains the following use cases:

Registration
Verify user details
Payment for registration
Login
Edit profile
Search match
Chat online
User profile maintenance
Match

Registration
When a groom or bride decides to get registered in matrimony
website, he/she should meet the registration agent near to them and get
prior permission to get registered.
User Details
Here the agent checks all the files provided by the concerned
person and then instruct them about the registration rules and
regulations, personal services etc

Payment For Registration

The approaching person should pay the fee to the agent

Login

It is used to check whether the person is an authorized user or not.

And to check whether the logged in user is a registered individual or
admin.

Edit Profile
 The groom/bride can now personalize their profile along with
personal and professional details

Search A Match

People can search for match regarding upon their personal wish
and desires

Chat Online

Online chat among people is available so that sharing of thoughts

is made easy and individuals can know each other and share their future
plans.

User Profile Maintenance

The website administrator may maintain user profiles and update

all the modifications. He may remove a profile form website or add a
profile.

Match

Provide details on liked or searched profile. And checks whether

the matches are compatible
 Registration

payment for registration

verify user details

registration admin

login

edit profile

users

search profile

website admin

chat online

user file maintanence

provide profiles
SEQUENCE DIAGRAM:

users registration website admin

admin
registration()

pay money()

login()

view profile()

edit profile()

provid profile()

logout()
ACTIVITY DIAGRAM:

login

user id and
password
check

authorised
person

upload photos,status
and profssional details

view profiles

request for
match

communicat
with match
CLASS DIAGRAM:

The class diagram is a graphical representation of all the classes

used in the system and their operations, attributes and relationships.

The friends system makes use of the following classes:

Login/logout
User details
website Admin
registration admin

user details
profile no
name
address matrimony website admin
qualification profile no
occupation username
religion
case addprofile()
star delete profile()
status update profile()
match profiles()
provide details() matrimony admin details()
register() opname()
pay()
edit profile()
search()
chatting()

matrimony registration admin

name
amount
profile no

verify user details()

send details to admin()
registration admin details()
 HOSPITAL MANAGEMENT SYSTEM

AIM:
To develop the Hospital Management System using UML diagram.

DESCRIPTION:
If a doctor will be seeing patients in an office for a full day,
morning and afternoon hours should be clearly demarcated.
Doctors need to arrive in the office on time and begin seeing
patients immediately when they arrive. When these simple practices are not
followed, there is invariably an adverse impact on patient flow for the rest of the
patient day.
Instructions for appointment scheduling need to be established by the doctors,
set forth in writing, and clearly communicated to the staff who do the scheduling.

USECASE DIAGRAM:
A usecase is a methodology used in system analysis to identify,clarify,and
organize system requirements.
The usecase is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a
particular goal.

Schedule Patient Appointment:

Patients on hold or make them wait in silence while you flip through your
paper appointment book. With Patient Appointment Manager, the on-screen calendar
lets you see whos available and when. You can quickly search for patients and their
appointment details or find available appointment times by employee.
Schedule Patient Admission:
The hospital staff for entry to each patient detail and admission card or sleep
to produce hospital.
Patient Registration:
Each patient are register for name, address, phone no and etc.
Inpatient Hospital Admission:
Medicare will cover care you get in a skilled nursing facility (SNF)
following your hospital stay.
Youre an inpatient starting when youre formally admitted to a hospital with
a doctors order. The day before youre discharged is your last inpatient day.
Outpatient Hospital Admission
In outpatient if youre getting emergency department services, observation
services, outpatient surgery, lab tests, X-rays, or any other hospital services, and the
doctor hasnt written an order to admit you to a hospital as an inpatient. In these
cases, youre an outpatient even if you spend the night at the hospital.
Bed Allotment:
Emergency case admit the bad and one or two weeks admit .then patient recover
discharge the patient.
SEQUENCE DIAGRAM
A sequence diagram represents object collaborations and is used to define
event sequences between objects for a certain outcome.
A sequence diagram is an essential component used in processes related to
analysis,design and documentation.
ACTIVITY DIAGRAM
An activity diagram is a graphical representation of an executed set of
procedural system activites and considered a state chart diagram variation.
It describe parallel and conditional activities,use cases and system functions
at a detailed level.
 Patient Takes
Appointment

receptionist checks for data

Doctor is not
available
no
yes

Patient Consult
Doctor

patient needs to be operated Doctor Attains

patient
no

yes

Undergoes Surgeon
Operated operates patient

Patient Gets Nurse assist

Operated Surgeon

no
patient ok

Discharge

CLASS DIAGRAM:

Class diagram is UML structure diagram which shows structure of the

designed system at level of classes and interfaces,shows their
features,constraints and relationships-
associations,generalizations,dependencies,etc.
 Doctor
Doctor Patient
Receptionist
Name Id
Id
Department Name
Name
Specialization Tel_no
Ph_no Checks Address Give Appointments
Check Room Availability()
Address Age
Book Room()
Gender
Generate Bill()
Prescribe Medicine() Room_no
Maintain Patient Details()
Check Report()
Draw Salary()
Prescribe Tests() Paybills()
Draw Salary()
Pays Bill
Generates
BelongsTo Alotted To

Department Staff
Bill
Id Id
Name Ward Bill No
Name
Doctor Patient Name
Ward No Type
Do Cleaning Amount
Ward Name Section
AddDepartment() Room No
DeleteDept() Location Draw Salary()
AddDoctor() Add Person()
DeleteDoctor() Delete Person()
Edit Person()

COLLEGE INFORMATION SYSTEM

AIM:
To model the College Information System using the software Rational
Rose with various UML diagrams.

DESCRIPTION:
 College information system is system where student and staff
interact with admin.
Staff can login with their username and password they can
manage the student details and their personal details.
Student can pay their fees and staff are paid salary.
Student can know their course details duration, eligibility and the
courses available in the institution.
In student blog students can post their query and get reply to it.
The whole system is controlled by the admin.

USE CASE DIAGRAM:

A Use Case Diagram at its simplest is a representation of a users

interaction with the system that shows the relationship between the user and the
different use cases in which the user is involved.

Login
The user enters the username and password. If entered details are valid, the
users account becomes available. If it is invalid, an appropriate message is
displayed to the user.
Manage Staff
The staff details are entered by him and they are managed by admin
Manage Student

The student details are gathered and entered they are managed by the staff
details may be name, date of birth, gender, contact details, etc

Accounts

Fees and salary details are managed here

Course Details

Courses offered by the college details about the course eligibility, duration
and other details

Student Blog

In student blog students can post their query and get reply to it.
SEQUENCE DIAGRAM:

A sequence diagram is an interaction daigram that shows how process opreate

with one another and what is their order. It is a construct of a Message sequence
chart.
ACTIVITY DIAGRAM:

Activity diagrams are graphical representation of work flows

of stepwise activities and actions with support for choice, iteration and concurrency.

Yes No

Course Details
Enter Username
& Password
Student Blog

No Yes
Enter Your
Details

No Yes
Manage
Student

Enter student
details Post Your
Query
Modify Student

Delete Student
Detail
CLASS DIAGRAM:

A Class diagram in the UML is a type of static Structure diagram that

describes the structure of a system by showing the systems classes, their attributes,
operations, and the relationships among objects.