STUDY OF UML DIAGRAMS

Aim:
To study the UML Diagrams.
Introduction:
CASE tools known as Computer-aided software engineering tools is a kind of
component-based development which allows its users to rapidly develop information
systems. The main goal of case technology is the automation of the entire information
systems development life cycle process using a set of integrated software tools, such as
modeling, methodology and automatic code generation. Component based
manufacturing has several advantages over custom development. The main advantages
are the availability of high quality, defect free products at low cost and at a faster time.
The prefabricated components are customized as per the requirements of the customers.
The components used are pre-built, ready-tested and add value and differentiation by
rapid customization to the targeted customers. However the products we get from case
tools are only a skeleton of the final product required and a lot of programming must be
done by hand to get a fully finished, good product.

Characteristics of CASE:
Some of the characteristics of case tools that make it better than customized
development are;
It is a graphic oriented tool.
It supports decomposition of process.
Some typical CASE tools are:
Unified Modeling Language
Data modeling tools, and
Source code generation tools
Introduction to UML (Unified Modeling Language):
The unified modeling language (UML) is a standard language for writing software blue
prints. The UML is a language for
Visualizing
Specifying
Constructing
Documenting

The artifacts of a software system:

UML is a language that provides vocabulary and the rules for combing words in
that vocabulary for the purpose of communication.
A modeling language is a language whose vocabulary and rules focus on the
concept and physical representation of a system. Vocabulary and rules of a language tell
us how to create and real well formed models, but they dont tell you what model you
should create and when should create them.

Visualizing

The UML is more than just a bunch of graphical symbols. In UML each symbol
has well defined semantics. In this manner one developer can write a model in the UML
and another developer or even another tool can interpret the model unambiguously.

Specifying

UML is used for specifying means building models that are precise,
unambiguous and complete. UML addresses the specification of all the important
analysis, design and implementation decisions that must be made in developing and
deploying a software intensive system.
Constructing

UML is not a visual programming language but its models can be directly
connected to a variety of programming languages. This means that it is possible to map
from a model in the UML to a programming language such as java, c++ or Visual Basic
or even to tables in a relational database or the persistent store of an object-oriented
database. This mapping permits for-ward engineering. The generation of code from a
UML model into a programming language. The reverse engineering is also possible you
can reconstruct a model from an implementation back into the UML.

Documenting

UML is a language for Documenting. A software organization produces all sorts

of artifacts in addition to raw executable code. These artifacts include Requirements,
Architecture, De-sign, Source code, Project plans, Test, Prototype, and Release. Such
artifacts are not only the deliverables of a project, they are also critical in controlling,
measuring and communicating about a system during its development and after its
deployment.

The UML Basic Building Blocks.

The Rules that direct how those building blocks may be put together. Some
common mechanisms that apply throughout the UML. As UML describes the real time
systems it is very important to make a conceptual model and then proceed gradually.
Conceptual model of UML can be mastered by learning the following three major
elements:

Things

Relationships

Diagrams
Things:
There are four kinds of things in the UML:

1. Structural nouns of UML models.

2. Behavioral dynamic (verbal) parts of UML models.
3. Grouping organizational parts of UML models.
4. Annotational explanatory parts of UML models.

Relations:
1. Association

2. Dependency

3. Generalization

4. Realization

In addition to this there are

1. Directed Association

2. Aggregation and

3. Composition

1. Association:
An association is a structural relationship that specifies the relation between two objects
when they are at the same level (peer level systems).
An Association can specify the relationship, role of the class and Multiplicity.
An Association used in class diagram, Component diagram, deployment diagram,
usecase diagrams.

The multiplicity can be represented as 1-1..*,*,01.

It is represented as follows:

Directed Association:
Links a semantic association between two classes in the UML diagram.

Directed association is used in class diagram, Component diagram, deployment

diagram, usecase diagrams.
Symbol:

Aggregation:
Links a semantic association between two classes in the UML diagram.

Aggregation is used in class diagram

Symbol:

Links a semantic association between two classes in the UML diagram.

Composition is used in class diagram.

Symbol:

2. Generalization:
Generalization is a specification relationship in which objects of the specialized
element (the child) are substitutable for objects of the generalization element (the
parent).It is used in class diagram.
Symbol:

3. Dependency:
 A dependency is a semantic relationship in which if there is any change occurred
in one object that may affect other object.
Dependency is used in class diagram, Component diagram, deployment diagram,
use-case diagrams.
Symbol:

4. Realization:
Realization is a Specified tool that can be represented by providing a relationship
with classifier.
Dependency is used in class diagram, Component diagram, deployment diagram,
use-case diagrams.
Symbol:

Structural modeling core relationships:

DESCRIPTION:

The heart of object-oriented problem solving is the construction of a model. The

model abstracts the essential details of the underlying problem from its usually
complicated real world. Several modeling tools are wrapped under the heading of the
UML, which stands for Unified Modeling Language. The purpose of this course is to
import knowledge about UML.
At the center of the UML are its nine kinds of modeling diagrams, which we describe
here
1. Class diagram

2. Use-case diagram

3. Behavior diagram

3.1. Interaction diagram

3.1.1. Sequence diagram

3.1.2. Collaboration diagram

3.2. State chart diagram

3.3. Activity diagram

4. Implementation diagram

4.1 component diagram

4.2 deployment diagram

1. 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.

Example Screen Shot:

2. CLASS DIAGRAM:
The UML class diagram is also known as object modeling. It is a static analysis
diagram. These diagrams show the static structure of the model. A class diagram is a
connection of static model elements, such as classes and their relationships, connected as
a graph to each other and to their contents.
Example Screen Shot:

3. 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. The objects involved in the operation
are listed from left to right according to when they take part in the message sequence.
Each vertical dotted line is a lifeline, representing an object exist. Each arrow is a
message call. An arrow goes from the sender to the top of the activation bar of the
message on the receivers lifeline. The activation bar represents the duration of
execution of the message.
 A
Create B

Return
Lifeline X
Deletion

Creation
Create message
Object life starts at that point
Activation
Symbolized by rectangular stripes
Place on the lifeline where object is activated.
Rectangle also denotes when object is deactivated.
Deletion
Placing an X on lifeline
Objects life ends at that point
Example Screen Shot:
4. COLLOBORATIION DIAGRAM :
In the end of sequence diagram by pressing F5 function key we get the Collaboration
diagram are also interaction diagrams. They convey the same information as sequence
diagrams, but they focus on object roles instead of the times that messages are sent. In a
sequence diagram, object roles are the vertices and messages are the connecting links.
Collaboration diagram consists of the numbered sequences of actions involved in a use
case. The numbering may be simple numbering system or decimal numbering system.
The collaboration diagram is very useful for large applications as they include only the
order of sequence of actions happening in use cases.
Example Screen Shot:
5. STATE CHART DIAGRAM:
It consists of state, events and activities. State diagrams are a familiar technique
to describe the behavior of a system. They describe all of the possible states that a
particular object can get into and how the object's state changes as a result of events that
reach the object. In most OO techniques, state diagrams are drawn for a single class to
show the lifetime behavior of a single object.

Example Screen Shot:

6. ACTIVITY DIAGRAM:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior
that has a lot of parallel processing. An activity is a state of doing something: either a
real-world process, or the execution of a software routine.
Basic Activity Diagram Symbols And Notations:
Initial State
A filled circle followed by an arrow represents the initial action state.

Final State
An arrow pointing to a filled circle nested inside another circle represents the final action
state

Action states
Action states represent the no interruptible actions of objects. You can draw an action
state in Smart Draw using a rectangle with rounded corners.

Action Flow
Action flow arrows illustrate the relationships among action states

States
States represent situations during the life of an object. You can easily illustrate a state in
Smart Draw by using a rectangle withrounded corners.
Transition
A solid arrow represents the path between different states of an object. Label the
transition with the event that triggered it and the action that results from it.

Synchronization and Splitting of Control

A short heavy bar with two transitions entering it represents a synchronization of control.
A short heavy bar with two transitions leaving it represents a splitting of control that
creates multiple states.

Fork & Join

Object Flow
Object flow refers to the creation and modification of objects by activities. An object
flow arrow from an action to an object means that the action creates or influences the
object. An object flow arrow from an object to an action indicates that the action state
uses the object.

Branching
A diamond represents a decision with alternate paths. The outgoing alternates should be
labeled with a condition or guard expression. You can also label one of the paths "else."

Decision & Merge Symbol

Synchronization
A synchronization bar helps illustrates parallel transitions. Synchronization is also called
forking and joining.
Swim lanes
Swim lanes group related activities into one column.

ATM TRANSACTION SYSTEM

AIM:

Develop a ATM transaction system using UML design.

SOFTWARE DESCRIPTION:

ATM machine is widely used for withdrawing amount at any time and
any place.
The main advantage of the ATM system is the transaction is made very
fast and effective.
 The ATM system is totally inter -connected with all the banks, by which
we can withdraw cash or check the balance within few minutes globally.
With the help of this system we can save time instead of standing in
queue for withdrawing a cash from the bank.
Thus the ATM system provides better efficiency for withdrawing the
cash.

USE CASE DIAGRAM

 CARD VERIFICATION

LANGUAGE SELECTION

USER BANK DB

TRANSACTION TYPE

TRANSACTION PROCESS

CARD VRIFICATION:

It is one of the processes in ATM system. In this system, it checks

whether the user pin no is a valid pin no or invalid pin no.

LANGUAGE SELECTION:

In this processes, the user have to select the language type before he/she
going to do some activities on the ATM system.

TRANSACTION TYPE:

In the transaction type, the user have to select which type of transaction is to be
processed on the ATM system either the transaction will be enquiry or withdrawing the
cash.

TRANSACTION PROCESS:
 In this process, tells whether the user has made some process on the ATM
system or not.

CLASS DIAGRAM

bank db

bank db()
+theUser

user
id : int +theAtmmachine
pinNo : int atmmachine

user()
atmmachine()
login()
exit()
username()
+theAccount +theTransprocess

transprocess
account
pro_id : int
accNo : int
+theAccount pro_Type : char
pro_Date : Date
account()
amount : Long
Addnew()
updateacc()
transprocess()

+theSvings +theCrent
svings crent
accNo : int accNo : int

svings() crent()
update() update()

CLASS DESCRIPTION:

1. CLASS NAME: user

CLASS ATTRIBUTE: id, password

CLASS OPERATIONS: login, exit, withdraw

Login- used to verify the pin no and provides authentication.

 Exit- to finish the transaction.
Withdraw- used to withdraw the cash from the account.
2. CLASS NAME: account

CLASS ATTRIBUTE: accno

CLASS OPERATIONS: addnewacc, update

Addnewacc- used to add new account to bank database.

Update- used to update the user account details in the bank database.

3. CLASS NAME: process

CLASS ATTRIBUTE: pro_id, pro_type, pro_date, amt

Pro_id- transaction id.

Pro_type- specify the transaction type

Pro_date- specifies the current date that the transaction is made.

Amt- transaction amount.

4. CLASS NAME: bank

Maintaining all the information about the users account details.

5. CLASS NAME: ATM machine

It acts as an interface between the users and the bank.

SEQUENCE DIAGRAM
CARD VERIFICATION

USER ATM BANK DB

MACHINE
INSERTING A CARD

ENTER PIN NO

USER ENTERING PIN NO

VERIFYING PIN NO

ACCESS PERMITED

LANGUAGE SELECTION

USER ATM
MACHINE

SELECT A LANGUAGE

USER SELECTED A LANGUAGE

LANGUAGE SELECTED
TRANSACTION TYPE

USER ATM
MACHINE

CHOOSE THE TYPE OF TRANSACTION

USER SELECT A TYPE

TRANSACTION TYPE SELECTED

TRANSACTION PROCESS

USER ATM BANK

MACHINE

REQUESTING GENERAL INFORMATION

SEARCHING THE DETAILS

RESPONDING TO THE REQUEST

VIEWING THE INFORMATION

WITHDRAW

ENTER THE AMOUNT

USER ENTERING THE AMOUNT

CHECK FOR BALANCE

SUFFICIENT BALANCE

COLLECT CASH
 ACTIVITY DIAGRAM

INSERT CARD

LANGUAGE
SELECTION

ENTER PINNO

INCORRECT PINNO
PINNO VERIFICATION

VALID PINNO

SELECT THE TRANSACTION

TYPE

ENQUIRY WITHDRAW
CHECK THE TYPE

DISPLAY THE AVAILABLE ENTER THE WITHDRAW

BALANCE DETAILS AMOUNT

PRINT RECEIPT
NO YES
CHECK BALANCE

INSUFFICIENT WITHDRAW
BALANCE CASH

DO U WANT TO YES
CONTINUE

NO
 COURSE REGISTRATION SYSTEM
AIM
To create a system through which students can register to the courses desired
by them.

PROBLEM STATEMENT
The system is built to be used by students and managed by an administrator.
The student and employee have to login to the system before any processing can
be done.
The student can see the courses available to him and register to the course he
wants.
The administrator can maintain the course details and view all the students who
have registered to any course.

SYSTEM REQUIREMENTS
Microsoft visual basic 6.0 is used as the front end of our project and ms-access as
the back end.

USE-CASE DIAGRAM:
The course registration system has the following use-cases
Login
View course details
Registration
Display details
Maintain course details
Logout

The actors involved in the system are

1. Student
 2. Administrator
Use-case name: Login
The user enters the username and password and chooses if the user is student or
administrator. If entered details are valid, the users account becomes available. If it is
invalid, an appropriate message is displayed to the user.
Use-case name: View course details
In this use case, a student can search all the courses available to him and choose
the best course he wants. The student can view the course duration, faculty and
department of the courses he may choose.

Use-case name: Registration

When a student has successfully chosen a course, he can register to that course.
Upon registration, the students details are stored in the database.

Use-case name: Display details

After registration to any course, the student may see the details of his current
course. He may wish to know details about fees and other information. The administrator
also has the privilege to display details of the the students and the corresponding course
for which they have registered.

Use-case name: Maintain course details

The administrator has to perform the duties of maintaining the course details.
Any change to the course structure is maintained by the administrator.

Use-case name: Logout

After all the desired transactions are made, the user may choose to logout from
the system to save all he changes they have made.
USE-CASE DIAGRAM

LOGIN

VIEW COURSE DETAILS

STUDENT ADMIN
REGISTRATION

DISPLAY DETAILS

MAINTAIN COURSE DETAILS

LOGOUT

CLASS DIAGRAM:
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.
The course registration system makes use of the following
classes:
1. Stud(student details)
2. Administrator
1) Stud
It consists of the details of all the students present in the database. The
attributes present in this class are student id, password, name, age, sex, course
and attendance. The object of this class is created as soon as the student
registers to a course. The operations available to this class are login (), logout
(), confirmation (), register (), and view course details ().
2) Administrator
It consists of details of all the courses available to the student. The
attributes present in this class are username, password, course fees, fees due,
marks, and attendance. The operations available to this class are login (),
logout (), ma course details (), display course (), and confirmation ().

STUDENT
ADMINISTRATOR
Sid : integer
userid : integer
Passwd : string
passwd : string
Name : string
course fees : integer
age : int
feesdue : string
sex : string
marks : integer
Course : string
attendance : integer
attendence : integer
1..*
login()
login()
logout()
logout()
course details()
confirmation()
display course()
register()
confirmation()
view course details()

SEQUENCE DIAGRAM:
A sequence diagram represents the sequence and interactions of a given usecase
or scenario. Sequence diagrams can capture most of the information about the system.
Most object-to-object interactions and operations are considered events and events
include signals, inputs, decisions, interrupts, transitions and actions to or from users or
external devices. An event also is considered to be any action by an object that sends
information.
The event line represents a message from one object to another, in which the
from object is requesting an operation be performed by the to object. The to object
performs the operation using a method that the class contains. It is also represented by
the order in which things occur and how the objects in the system send message to one
another. The sequence diagram for each use-case that exists when a user logs in, adds,
views, updates or deletes records in the system.

: ADMIN : STUDENT

displaycourse details logout

login registration details

login( )

login( )

view course details( )

register( )

confirmation( )

view course details( )

logout( )

logout( )

Users have to first login to the system before performing any operation. The

user has to provide the necessary details to the system for login.

When the necessary operations have been performed on the system, the user
may choose to save the changes and logout from the system.

After login, the student has to register to a course of his choice. The
 student can view all the courses available to him and register to a course suitable to
him. The student may view the course details before registration.
A student may wish to view course details before registration. For this, the
student has to first login and select the course details he wishes to see.

Course details may be changed as per the requirement every year. So the
administrator can edit the details of the course as necessary.

COLLABORATION DIAGRAM:

Through the collaboration diagram we get the complete flow of work.

1: login( ) login
3: view course details( )
7: view course details( )

: ADMIN 5: confirmation( ) displaycourse

details

2: login( )
9: logout( ) 6:

registration
details
4: register( )

8: logout( )
logout

: STUDENT
ACTIVITY DIAGRAM

login

AMINISTR STUDENT
ATOR

DISPLAY COURSE VIEW COURSE

DETAILS DETAILS

CONFIRM REGISTER
ATION COURSE

MAINTAIN
COURSE

LOGOUT
 INVENTORY SYSTEM

AIM:

To develop an inventory system using UML design.

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.
USECASE DIAGRAM

Purchase

Supplier Purchase order

Stock Details

Vendor

Sales

Customer

Invoice

Generate Reports

EXPLANATION:
PURCHASE:

Purchasing the necessary goods from the supplier to maintain an inventory stock.

PURCHASE ORDER

A purchase order (PO) is a commercial document issued by a buyer to a seller,

indicating types, quantities, and agreed prices for products or services the seller
STOCK DETAILS:

The purchased goods are stored in the Warehouse and maintained.

SALES:

The goods are sold according to the customer requirements.

INVOICE:

An invoice or bill is a commercial document issued by a seller to a buyer,

indicating the products, quantities, and agreed prices for products or services the seller.

GENERATE REPORTS:

The Vendor maintains daily reports and annual reports according to the
transaction done in the inventory.
CLASS DIAGRAM:

InventorySystem

InventorySystem()

1..*

Suppliers
Supplier
Name
CompanyNo 1..* Address
CompanyName
Phone No.
Address
PhoneNo
* Purchase()
Sales()
Sales()
Stock()
Suppler()
Vendors()

Billing
Stock
BillNo
1..* ItemNo
Customers Date
ItemName
CustomerId Quantity
+theStockQuantity
CustomerName Price
Insert()
Purchase() DailyReport()
Delete()
Customers() MonthlyReport()
Update()
YearlyReport()
Stock()
Billing()

Class name: Inventory System

Description: This class is used as a mediator between user & DB.

Class name: Customers

Attributes: CustomerId, CustomerName.

Operations: Purchase(), Customers().

Class name: Suppliers

Attributes: Name, Address, Ph_no.

Operations: Purchase (), Sales (), Stock (), Vendors().

Class name: Stock

Attributes: Item no, Item Name, Quantity.

Operations: Insert(), Delete(), Update(), Stock().

Class name: Supplier.

Attributes: Comp_no, Comp_name, Address, Ph_no.

Operations: Sales(), Supplier().

Class name: Billing.

Attributes: Bill_no, Date, Price, Quantity.

Operations: Daily Report(),Monthly report(), Yearly Reports(), Billing().

SEQUENCE DIAGRAM:

Customer Supplier Vendor Stock

Request For Product

Providing Product
Store in Stock

Request Product

Availablity Checking

Not Available

Order a Product

Available

Selling into Customer

Bill Generated

Maintaining Transaction Record

Ledger

Balance Sheet
COLLABORATION DIAGRAM:

Customer

Supplier

9: Selling into Customer

10: Bill Generated
1: Request For Product
7: Order a Product

4: Request Product

11: Maintaining Transaction Record

12: Ledger
13: Balance Sheet 2: Providing Product

3: Store in Stock
5: Availablity Checking
Vendor Stock

6: Not Available
8: Available
SEQUENCE DIAGRAM:

Requesting
Product Details

Puchase

Stock
Maintanence
No

Purchase
Customer

Stock Checking

Yes

Sales Billing

Delete Generate
Stock Report
 ONLINE EXAMINATION WITH RESULT
AIM:

To design a Online Examination with Result.

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:

Login for Examination

Add Questions

Edit Questins

Change Password
User
Admin

Add Subject

Delete Subject

Reports

Results
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.

User Exam Exam
CHANGE PASSWORD: DataBase

This option is used to change the password by the user and examiner.

ADD SUBJECT:
Enter User-Name and Password

It is used to add the subject by the examiner.

User-name and Password is Entered
DELETE SUBJECT:
Check is it Valid User
It is used to delete subject by the examiner.

REPORTS: Not Valid User

ThisPlease
optionCheck
is usedU to
r show the all user results to the examiner.
User name & Password

RESULTS: Valid User

This option is used to user to see there results.

U ar Permitted to Atten the Exam

Display Exam Instruction

Display Exam Questions

Answer the Question

SEQUENCE DIAGRAM 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()
Class name: User1

Attributes: User ID, Name, Age, Sex, Address.

Operations: Select_Answere(), View_result().

Class name: Admin

Attributes: AdminID, Name, Age, Sex, Address.

Operations: Create_quesiton(), Edit_question(), Delet_Qustion, Change_password,

Display_result().

Class name: Exam DB

Operations: Select_userdatabase(), Select_questiondatabase().

Class name: Userdatabase

Attributes: User ID, User password.

Operations: Display().

Class name: questiondatabase

Attributes: subject1, subject2, subject3.

Operations: display_question(), question_database().

 ABC MATRIMONIAL SYSTEM
AIM:

To design a matrimonial system using UML diagram.

DESCRIPTION:

This matrimonial system was created using UML diagram. It enables the user to
view the details about the system. The user can register their details. The registered user
can enter into the system using login user id & password. The user can maintain the
profile. They can search for a match. The user can request the match and they will get
the response from their match.

USE CASE DIAGRAM:

View Home Page

Register

Login

View Profile
User Admin

Search the Match

Request the Match

Response to the user

EXPLANATION:

VIEW HOME PAGE:

This option is used to visit the home page without registering in the site.

REGISTER

This is used for making registration to access the information without any
restriction.

LOGIN:

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

VIEW PROFILE:

This is used to view the profile of other persons.

SEARCH THE MATCH:

It is used to search the match for a person.

REQUEST & RESPONSE TO THE MATCH:

This option is used to request for a selected & person will give a response to that.
SEQUENCE DIAGRAM:

VIEW HOME PAGE:

User ABC Matrimonial Info DB

System

Requesting the Page

Searching the Page

Responding with the Page

Viewing the Page

REGISTER:

User ABC Matrimonial Info DB

System

Request to Registration

Enter your Details

Filling the Details

Details Getting Stored

Successfully Completed
LOGIN:

User ABC Matrimonial Info DB

System

Enter UID & Password

Entering UID & Password

Checking for authorization

Right Person

Access Granted

VIEW PROFILE:

User ABC Matrimonial Info DB

System

Requesting a profile

Searching the Request

Responding to Request
SEARCH THE MATCH:

User ABC Matrimonial Info DB

System

Search The Match

Retrieving the Page

Match Found

Process Completed

REQUEST THE MATCH:

User ABC Matrimonial Info DB

System

Request the Match

Transaction

Response to the Request

Request Accepted
ACTIVITY DIAGRAM:

Home
Page

No View
Register
Details

Yes
Registration

Login No

UID & Not a Valid

Password User

Yes
Valid User

View
Profile

Request for
Match

Communicate
with Match
CLASS DIAGRAM:

ABCMatrimonialSystem

User
InfoDB
Username : String
UserID : String
Password : String
UserProfile : String
UserDetails : String
SearchForProfile()
Login()
SendProfileToUser()
UpdateProfile()
DeleteProfile()
RequestForMatch()
Search
SearchKeyword : String

SearchForProfile()
RequestTheMatch()
Search()

Visitor

SearchProfile()
Visitor()

Class name : ABC Matrimonial System

Description : This class is used as a mediator between user & DB.

Class name : User

Attributes : Username, Password, UserDetails.

Operations : Login(), Update Profile(), Request for Match().

Class name : Info DB

Attributes : User ID, User Profile.

Operations : Search for Profile(), Send Profrile to User(), Delete Profile().

Class name : Search

Attributes : SearchKeyword

Operations : Search(), Search for Profile(), Request the Match().

Class name : Visitor.

Operations : Search Profile(), Visitor().

 FRIENDS NETWORK ORKUT SIMULATION
AIM:

To design Friends Network Orkut Simulation using UML diagram.

DESCRIPTION:

This sytem is mainly used to communicate, chat and keep in touch with friends.
We can add friends to our list id we wish.
We can upload photos, data and we can share those with our friends who are in
the network.
We can create community and can share photos to that community memberes.
Messages and scrap can be send to the community members that we had joined.
User can make privacy to their data i.e., photos ,profile, messages or scrap,
personel information about them, etc..
Can able to give rights to the privacy data to some of their friends too.
User can view other peoples profile or detail if not protected by them who are in
the same network.

USE CASE DIAGRAM :

 Log In

Register

Request Friends

Add Friends

Delete Friends

User Or Member Friends Network

View Friends List Administrator

Create or Join
Community

View or Send
Scrap Messages

Update Profile

Upload Data

LOG IN:

The Friends Network members can logs-in into Friends Network by endtering
their userid and password, if they are already a member of the network.

REGISTER:
 If the person is new to the network he/she can enter into the network by
registering themselves by giving their details or creating profile.

REQUEST FRIEND:

The logged in member can add their friends to the friends list by giving their
friends username. Then a request is send to that particualar person, if he/she add as
friend then only they can communicate.

ADD FRIENDS:

Member can add a friend that has been came as request to his/her request list.

DELETE FRIENDS:

The member have the rights to delete the added friends in the list.

VIEW FRIENDS LIST:

The Member can see any of the persons details in the network by searching on
the name.

CREATE OR JOIN COMMUNITY:

Any Member of this network can create a community and can add any number of
persons to the community. Anyone in the network can join in any of the community that
has been created.

VIEW OR SEND MESSAGE:

The user can view the received messages from his/her friends and can reply to
that. Also the user can create a new message and send to any of the friends.

UPDATE PROFILE:

The Member/User can update his/her profile at anytime.

UPLOAD DATA:

The Members can upload data such as photo, video,etc. and can make privacy to
those data.

SEQUENCE DIAGRAM:
 Member or User Friends Network Friends Network
System Database

1: Enter Username and Password

2: Verifying Username Password

3: Invalid Re-Enter Username Or Password

4: Username Password are Valid

5: Friend Name to Search

6: Searching For Requested Name

7: Displayin the Friends List

8: Request to Friends

9: Request From Friends

10: Add Friends

11: Friend Added to Database

12: Friend Added

13: View Message or Scrap

14: Send Message or Scrap

15: Upload Files

16: Stored in Database

17: Database Updated

18: Update Profile

19: Stored in Database

20: Database Updated

ACTIVITY DIAGRAM:
 Home Page

New User
User Type Registration

Member

Log In

Re-Enter

Verify Username
Password

Valid

Request
Friend

Add Friends

Join in
Community

Create
Community

Scrap
Messages

Upload Files

Update Profile

CLASS DIAGRAM:
 Friends Network System

User
uid : int
pwd : char Community
name : string
add_frnd() no_mem : int
req_frnd() type : string
send_scrap()
view_scrap() cre_comm()
join_comm() del_comm()
Profile
cre_comm() acc_mem()
del_frnd() uid : int rem_mem()
uplo_file()
new()
update()
delete()

Personel Detail
Primary Details uid : int
name : char add : string
uid : int pin : int
pwd : char alt_mail : string
dob : int
search() gender : char
get_det()
send_det()

Class name : Friends network system.

Description : This class is the mediator of whole system

Class name : User

Attributes : Uid, Password.

Operations : add_frnd(), req_frnd(), send_S crap(), view_S crap(), join_comm(),

cre_comm(), del_frnd(), uplo_file().

Class name : community

Attributes : name, no_mem, type.

Operations : cre_comm(), del_comm, acc_comm(), rem_mem.

Class name : Primary

EMPLOYEE INFORMATION SYSTEM

AIM:
To maintain the employee details.
DESCRIPTION:

Employee information system is used for maintaining employee detail and

performs salary details. In employee details general information about employee are
maintained. General information is employee id, name, age, gender, designation, date of
birth, date of join, and basic pay of each employee.

In salary details allowances and detections of employee also maintained to

calculate and generate pay slip for each employee.

USE CASE DIAGRAM:

Login

Employee details

Search employee details

Acountant Payroll preparation Database

Generate payslip

View salary details

CLASS DIAGRAM:
 Payroll preparation

Employee
Attendance
Salary Id : int
Id : int
name : string
Name : string Id : int
D.O.B : date
Desig : string Name : string
Age : int
Total_days : int W_days : int
Sex : string
W_days : int W_hours : int
Desig : string
W_hours : int Basic_pay : double
D.O.J : date
Basic_pay : double
getdata() getdata()
cal_lop() putdata()
getdate()
putdata()
putdate()

Daily_wages Monthly_wages
Id : int Id : int
Name : string Name : string
Desig : string Desig : string
W_hours : int W_days : int
Net_pay : double Basic_pay : double
Allowances : double
getdata() Detections : double
cal_sal() Net_pay : double
putdata()
getdata()
cal_lop()
cal_detection()
cal_sal()
putdata()

Class : Payroll preparation

Description : To control the system.

Class : Attendance.

Attributes : Id, name, Desig, total_days, W_days, W_hours.

Operation : getdata(), cal_lop(), putdata().

Class : Employee

Attributes : Id, name, DOB, age, sex, desig, DOJ, Basic_Pay.

Operation : getdate(), putdate()

Class : Daily_Wages

Attributes : Id, name, design, W_hours, net_pay

Operation : getdata(), cal_sal(), putdata().

Class : Monthly_wages

Attributes : Id, name, design, W_days, Basic_pay, allowances, detections,

net_pay.

Operation : getdata(), cal_lop(), cal_detection(), cal_sal(), putdata()

ACTIVITY DIAGRAM:
LOGIN:

Accountant Employee info Database

system

1: Request to add employee details

2: Enter details

3: Information stored

4: Acess granted

EMPLOYEE DETAILS:

Accountant Employee info Database

system

1: Request to add employee details

2: Enter details

3: Information stored

4: Process completed

SEARCH RECORD:
 Accountant Employee info Database
system

1: Enter employee id

2: Search particular employee record

3: IF not found display no such record

4: Ask for correc emplyee id

5: Display information

PAYROLL CALCULATION:

Accountant Employee info Database

system

1: Entering the attendance details

2: Accountant entering the details

3: Processing details and stored

PAYSLIP GENERATION:
 Accountant Employee info Database
system

1: Enter employee id

2: Accountant entering id

3: Checking if correct

4: Display payslip details

5: Details provided to accountant

SALARY DETAILS:

Accuntant Employee info Database

system

1: Ask for final salary detials

2: Selecting salary after calculation

3: Provided details

4: Display details

ACTIVITY DIAGRAM:
 loign

Checking
for No
authorizaiton

Yes
view all emp
details

search records

checking No
for id

Yes

display emp
details

enter emp
attendance

processign payroll
calculation

enter Id for particular

employee

checking
for emp
Id

display salary details

of employee