Complete Record

Gayatri Vidya Parishad College of Engineering
Madhurawada,Visakhapatnam- 530 041
JNTU Regd.No
CERTIFICATE
Certified that this is a bonafied record of

practical work done by _______________ of
____________B. Tech ____Semester in the
______________________________________Lab of
Department of _________________________________
during the academic year _____________
No. of experiments done and certified:
Signature of Examiners Signature of

Laboratory In charge
1) External:
2) Internal:
Signature of H.O.D
ACKNOWLEDGEMENT
I would like to express my deep sense of

gratitude and indebtedness to my esteemed
institute “Gayatri Vidya Parishad College of
Engineering”, which has provided me an
opportunity to fulfill the most cherished desire to
reach my goal.
I owe project to Mr. K. Koteswara Rao, Asst

Prof who has been my project’s guide. I sincerely
thank him for the support and guidance which he
has given me.
My sincere thanks to Asst Prof Mr. SRM

Krishna Department of Computer Science and
Engineering
2
Contents
UNIFIED MODELING LANGUAGE.............5
INTRODUCTION................................................................................................... .....5
MODEL............................................................................................................. ........5
MODELING............................................................................................. ..................5
VISUAL MODELING.......................................................................................... .........5
WHY DO WE MODEL?........................................................................................ .......5
AIMS OF MODELING................................................................................. ................5
VISUAL MODELING USES.........................................................................................6
HISTORY OF UML.....................................................................................................6
WHERE UML CAN BE USED?....................................................................................6
UML Diagrams................................................................................. ........................7
BEHAVIORAL DIAGRAMS..........................................................................................7
STRUCTURAL DIAGRAMS......................................................................................... .9
INTRODUCTION TO RATIONAL ROSE.....11

USECASE VIEW......................................................................................................12
LOGICAL VIEW.......................................................................................................13
COMPONENT VIEW............................................................................................... ..13
DEPLOYMENT VIEW...................................................................................... ..........14
UNIFIED LIBRARY APPLICATION...........14

INTRODUCTION ................................................................................................ .....14
TEXTUAL ANALYSIS................................................................................................15
USECASE DIAGRAM.......................................................................................... ......16
3
ACTIVITY DIAGRAM................................................................................................17
INTERACTION DIAGRAM.........................................................................................18
SEQUENCE DIAGRAM.............................................................................................18
COLLABORATION DIAGRAM.............................................................................. ......19
CLASS DIAGRAM.............................................................................. ......................20
STATE CHART DIAGRAM.........................................................................................21
STIMULUS RESPONSE DIAGRAM.............................................................................23
FORWARD ENGINEERING.......................................................................................24
REVERSE ENGINEERING.................................................................................. .......39
POINT OF SALE...................................48
INTRODUCTION ................................................................................................ .....48
USECASE DIAGRAM.......................................................................................... ......49
CLASS DIAGRAM.............................................................................. ......................53
MULTITHREADED AIRPORT SIMULATION

.........................................................57
INTRODUCTION ................................................................................................ .....57
USECASE DIAGRAM.......................................................................................... ......58
CLASS DIAGRAM.............................................................................. ......................62
4
SIMULATED COMPANY.........................65
INTRODUCTION ................................................................................................ .....65
USECASE DIAGRAM.......................................................................................... ......66
CLASS DIAGRAM.............................................................................. ......................70
UNIFIED MODELING LANGUAGE

INTRODUCTION
UML stands for Unified Modeling Language. UML is a
language for visualizing, documenting the artifacts of software
intensive system.
MODEL
James Rumbaugh defined Model as a simplification of reality
MODELING
Modeling is captures essential parts of the system.
VISUAL MODELING
Visual modeling is a modeling with standard graphical notation
WHY DO WE MODEL?
We build models so that we can better understand the system we
are developing
AIMS OF MODELING
5
• Models help us to visualize a system as it is or as we want to be
• Models permit us to specify the structure of system
• Models give us a template that guides us in constructing system
• Models can document the decisions we have made
VISUAL MODELING USES
• Visual modeling captures business process
• Visual modeling is a communication tool
• Visual modeling manages the complexity
• Visual modeling promotes reuse
HISTORY OF UML
In the late 1980s and early 1990s there were 3 methodologies:
Booch Methodology: This was designed by Grady Booch which is great
in design
OMT (Object Modeling Technique) Methodology: This was designed
by James Rumbaugh et’ al which is great in analysis
OOSE (Objectory) Methodology: This was designed by Ivar Jacobson
which is heart of UML i.e., use case
In 1994, James Rumbaugh joined in Rational with Booch and
worked together and this is the beginning of unification method. In
1995, Jacobson joined in Rational with Booch and Jim. In 1996,
matured unified method was released. In 1997, in January UML 1.0 was
released. In 1997 on November 14th UML was accepted by OMG and
accepted as a standard language.
WHERE UML CAN BE USED?
• Enterprise information system
• Banking and Financial services
• Telecommunications
6
• Transportation
• Defense
• Retail
• Modeling Electronics
• Scientific
• Distributed Web services
UML Diagrams
Diagram is a graphical representation of elements. UML diagrams
can be classified into two types
1. Structural Diagrams
2. Behavioral Diagrams
Structural Diagrams:
These can be divided into 4 types:
i. Class Diagram
ii. Object Diagram
iii. Component Diagram
iv. Deployment Diagram
Behavioral Diagrams:
These can be classified into 5 types:
i. Use case diagrams
ii. Sequence diagram
iii. Collaboration diagram
iv. State Chart Diagram
v. Activity Diagram
BEHAVIORAL DIAGRAMS
7
i. Use case Diagram:
Use case diagram is created to visualize the interaction of our system
with the outside world. The components of use case diagram are:
Use Case: Scenarios of the system
Actor: Someone or something who is interacting with the system
Relationship: Semantic link between use case and actor. The forms of
relationship are:
a. Association
b. Dependency
c. Generalization
ii. Activity Diagram
Activity diagram shows the flow of events within our system. The
components are:
a) Start State
b) End State
c) Transition
d) Decision Box
e) Synchronization Bar
f) Swim Lane
iii. Interaction Diagram
An interaction diagram models the dynamic aspects of the system
by showing the relationship among the objects and messages they
may dispatch. There are two types of interaction diagrams:
1. Sequence Diagram
Sequence diagram shows the step to step what mush happen to
accomplish a piece of functionality provided by the system. The
components are:
8
a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control
2. Collaboration Diagram
Collaboration diagram displays object interactions organized around
objects and their links to one another. The components are:
a) Actor
b) Object
c) Link
iv. State chart Diagram

State chart diagram show a life cycle of a single class. The state is a
condition where the object may be in. The components are:
a) Start state
b) End state
c) State
d) Transition
STRUCTURAL DIAGRAMS
i. Class Diagram
Class diagram shows structure of the software system. The class
diagram shows a set of classes, interfaces and their relationships. The
components are:
a) Class
b) Relationship:
9
The forms of relationship are:
1. Association
2. Aggregation
3. Generalization
4. Composition
5. Dependency
ii. Component Diagram
Component is a smallest individual physical replaceable part of the
system. Component diagram shows the organization and dependencies
among software components. The components present are:
a) Component
a. Runtime component(.dll)
b. Software components(.h)
c. Executable components(.exe)
b) Dependency
c) Interface
iii. Object Diagram
Object diagram shows objects and links among objects. The
components are:
a) Object
b) Link
The object diagram cannot be model in rational rose.
iv. Deployment Diagram
Deployment diagram visualizes distribution of components across the
enterprise
10
INTRODUCTION TO RATIONAL
ROSE
Rational Rose is a software where the UML can be model. Here,

Rational is the name of the software, ROSE stands for Rational Object
Software Engineering.
To draw the UML Diagram in Rational Rose:
Step 1: Start Rational software, in that Rational Rose Enterprise
Edition. After that Rational Rose Enterprise Edition will be activated.
The Rational Rose window contains 5 parts.
1. View Table
It contains:
a. Use case view
b. Logical view
c. Component view
11
d. Deployment view
2. Diagram Tool Bar
This can contain the tools of the corresponding diagram in
which we are going to draw
3. Diagram Window
In this window we can draw the diagram
4. Message Window
It contains the message of documentation of the
corresponding diagram
5. Log Window
This is the place where the errors can be displayed when we
are drawing the diagram
USECASE VIEW
In this view we can draw two diagrams:
1. Use case diagram
2. Activity Diagram
Steps to draw diagram:

1. Select use case view and then right click on use case view
2. Select New, in that select use case/activity diagram
3. Name the diagram
4. After double clicking on the diagram name, the corresponding
use case/activity will be opened
5. We can draw the diagram by drag and drop the components of
the corresponding diagram
12
LOGICAL VIEW
In this view we can model:
a. Class diagram
b. Sequence diagram
c. Collaboration diagram
d. State Chart diagram
To draw the diagram:

1. Select logical view and then right click on the logical view
2. Select new in that select class/ state chart/ sequence diagram
3. Name the diagram
diagram will be opened
5. We can draw the diagram by drag and drop the components of
the corresponding diagram
COMPONENT VIEW
In this view we can model
a. Component Diagram
To draw the diagram:
1. Select component view and then click on the component view
2. Select New, in that select component diagram
3. Name the diagram
4. After double clicking on the diagram, the corresponding
5. We can draw diagram by drag and drop the components of
corresponding diagrams
13
DEPLOYMENT VIEW
In this we can model deployment diagram
To draw diagram:
1. Select deployment view, then right click on deployment view
2. Select New, in that select deployment diagram
3. Name the diagram
5. We can draw diagram by drag and drop the components of
corresponding diagrams
UNIFIED LIBRARY APPLICATION

INTRODUCTION
Unified Library Application System emphasizes on the online reservation,
issue and return of books. This system globalizes the present library system. Using
this application the member can reserve any book from anywhere in the world. Still
in nascent stages, this application soon revolutionizes present library system.
Let us just have an overview of the unified library application system:

• Librarian lends books and magazines
• Librarian maintains the list of all the members of library
• Borrower makes reservation online
• Borrower can remove reservation online
• Librarian issues books to the borrower
• Librarian calculates dues to be paid by the borrower
• Borrower issues/returns books and/or magazines
14
• Librarian places order about the requirements to the master librarian
• Librarian updates system
• Master librarian maintains librarians
TEXTUAL ANALYSIS
(a)ACTORS
i. Librarian
ii. Borrower
iii. Catalog
iv. Master Librarian
(b)VERBS
i. Borrower:
1. Logs into the system
2. Browses/searches for books or magazines
3. Makes/removes reservation
4. Views results and reports from the unified library application system
ii. Librarian:
1. Manages and validates members
2. View reports from the system
3. Issues books
4. Calculates dues
5. Takes books
6. Places orders to the master librarian
7. Maintains list of books and magazine
iii. Master Librarian
1. Maintains other librarians
15
USECASE DIAGRAM
relationship are:
a. Association
b. Dependency
c. Generalization
16
ACTIVITY DIAGRAM
Activity diagram shows the flow of events within our system.
The components are:
a) Start State
b) End State
c) Transition
d) Decision Box
f) Swim Lane
17
INTERACTION DIAGRAM
SEQUENCE DIAGRAM
components are:
18
a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control
COLLABORATION DIAGRAM
a) Actor
b) Object
c) Link
19
CLASS DIAGRAM
components are:
a) Class
b) Relationship:
1. Association
20
2. Aggregation
3. Generalization
4. Composition
5. Dependency
STATE CHART DIAGRAM

State chart diagram show a life cycle of a single class. The state is
a condition where the object may be in. The components are:
a) Start state
b) End state
c) State
21
d) Transition
Member:
Librarian
22
Library Administrator
STIMULUS RESPONSE DIAGRAM
23
Stimulus Response Diagram emphasizes on describing the life cycle of entire
system as a whole. The components are:
a) Start state
b) End state
c) State
d) Transition
FORWARD ENGINEERING
24
a. Step1 – Project Specification
b.Step2 – Set Path
25
26
27
28
c.Step4 – Select the classes to be forward engineered
29
d. Step 4 :- Select Tools -> Java/J2EE -> Generate Code to
forward engineer.
30
The code is generated at the specified path that is specified under Project
Specification part as:
Administrator:
//Source file: C:\\Documents and Settings\\Administrator\\My
Documents\\kiShAn\\administrator.java
public class administrator

{
private String name;
private String ID;
public Librarian theLibrarian;
/**
* @roseuid 47171E65029F
*/
public administrator()
{
/**
* @return String
* @roseuid 47171A5C030D
*/
public String receive_order()
{
return null;
}
/**
* @roseuid 47171A6102DE
*/
public void manage_librarians()
{
31
/**
* @roseuid 47171A6703D8
*/
public void purchase_new_stock()
{
}
}
Catalog

Documents\\kiShAn\\catalog.java
public class catalog

{
private String version;
private String type;
private String design;
/**
* @roseuid 47171E6302DE
*/
public catalog()
{
/**
* @return String
* @roseuid 47171C310290
*/
public String store_member_details()
{
32
return null;
}
/**
* @return String
* @roseuid 47171C3901D4
*/
public String store_book_details()
{
return null;
}
/**
* @return String
* @roseuid 47171C3F035B
*/
public String give_return_messages()
{
return null;
}
}
Librarian
Documents\\kiShAn\\Librarian.java
public class Librarian

{
private String name;
private String ID;
public ulas theUlas;
public catalog theCatalog;
public LibraryMember theLibraryMember;
public administrator theAdministrator;
/**
33
* @roseuid 47171E660177
*/
public Librarian()
{
/**
* @return Integer
* @roseuid 47171AD00280
*/
public Integer calculate_dues()
{
return null;
}
/**
* @return String
* @roseuid 47171AD60242
*/
public String view_reports()
{
return null;
}
/**
* @roseuid 47171ADA0280
*/
public void issue_take_books()
{
/**
* @roseuid 47171AE002BF
*/
public void update_database()
{
34
}
/**
* @roseuid 47171AE500BB
*/
public void place_order_for_new_stocks()
{
/**
* @return Boolean
* @roseuid 47171BCB002E
*/
public Boolean validate()
{
return null;
}
}
Library Member
Documents\\kiShAn\\LibraryMember.java
public class LibraryMember

{
private String Name;
private String ID;
public ulas theUlas;
/**
* @roseuid 47171E650000
*/
35
public LibraryMember()
{
/**
* @return String
* @roseuid 471719C402CE
*/
public String login()
{
return null;
}
/**
* @return String
* @roseuid 471719CB0290
*/
public String search_browse()
{
return null;
}
/**
* @return Boolean
* @roseuid 471719D201C5
*/
public Boolean make_remove_reservation()
{
return null;
}
/**
* @return Integer
* @roseuid 471719DE01E4
*/
public Integer pay_dues()
{
36
return null;
}
/**
* @roseuid 471719E401C5
*/
public void take_return_book()
{
/**
* @return String
* @roseuid 47171A02037A
*/
public String view_reports()
{
return null;
}
}
ULAS

Documents\\kiShAn\\ulas.java
public class ulas

{
private String owner;
private String url;
private String type;
public LibraryMember theLibraryMember;
/**
37
* @roseuid 47171E62003E
*/
public ulas()
{
/**
* @return Boolean
* @roseuid 47171A3200AB
*/
public Boolean validate_users()
{
return null;
}
/**
* @return String
* @roseuid 47171A3801E4
*/
public String show_results()
{
return null;
}
/**
* @return String
* @roseuid 47171A3D004E
*/
public String show_reports()
{
return null;
}
}
38
REVERSE ENGINEERING
Step 1 :- Open new project -> Class Diagram under Logical

View.
39
Step2 :-
Select Tools -> Java/J2EE -> Reverse
Engineer to reverse engineer the code.
40
Step3 :-
Specifiy the path of code to reverse engineer .
Select the code files to be reverse engineered.
41
42
Step4 :-
After adding all code files click Select All and
then click Reverse.
43
44
Step 5:-
The classes generated in the tree window. Drag
all the classes to the required area. The associations
among the classes is generated automatically.
45
46
Finally , the reverse engineering is complete.
47
POINT OF SALE
INTRODUCTION
Shops are the integral part of any civilization. They are present in
every culture since ages. This application emphasizes on the transaction going on
between the customer and shop keeper during sale of product.
The customer approaches the shop keeper/ sales boy and places his
order. The shop keeper forwards the order to sales boy who fetches the required
goods from inventory. Then the shop keeper calculates bill and issues to the
customer. The customer on paying the bill takes goods from the shop keeper. In
turn, shop keeper fetches goods from supplier
Let us just have an overview of point of sale:
• Customer places order to the shop keeper/sales boy

• Sales boy collects goods and forwards them to shop keeper
• Shop owner calculates bill and forwards to the customer
• Customer on paying the bill receives goods from shop keeper
• Shop keeper places order to supplier and receives goods
TEXTUAL ANALYSIS
(a)ACTORS
i. Customer
ii. Shop Owner
iii. Sales boy
iv. Supplier
(b)VERBS
i. Customer:
1. Places order to shop owner/sales boy
2. Receives bill from shop owner
3. Pay the bill
48
4. Receive goods
ii. Shop Owner:
1. Receives order from customer
2. Forwards order to sales boy
3. Receive goods from sales boy
4. Calculates bill
5. Receives payment
6. Places orders to supplier
7. Maintains inventory
iii. Supplier
1. Receives order from shop owner
2. Delivers goods to shop owner
USECASE DIAGRAM
relationship are:
a. Association
b. Dependency
c. Generalization
49
ACTIVITY DIAGRAM
The components are:
a) Start State
b) End State
c) Transition
d) Decision Box
f) Swim Lane
50
51
INTERACTION DIAGRAM
SEQUENCE DIAGRAM
components are:
a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control
52
a) Actor
b) Object
c) Link
CLASS DIAGRAM
components are:
a) Class
b) Relationship:
1. Association
2. Aggregation
3. Generalization
4. Composition
5. Dependency
53
STATE CHART DIAGRAM
a) Start state
b) End state
c) State
d) Transition
Customer
54
Shop Owner
Supplier
55
Sales boy

a) Start state
b) End state
c) State
d) Transition
56
MULTITHREADED AIRPORT
SIMULATION
INTRODUCTION
Everyday number of airplanes lands and takes off from airport. It is
the responsibility of the Air Traffic Control (ATC) to regulate these planes. The
aim of this simulation is to reconstruct the events occurring during landing or take
off.
Whenever plane enters the RADAR space, RADAR signals the ATC
about the plane. Then the pilot sends the plane details. ATC checks the runway and
decides priority. ATC signals the pilot whose plane is having highest priority to
land/take off. Then the pilot performs the corresponding command.
Let us just have an overview of the multithreaded airport simulation:
• RADAR senses the plane and signals the ATC

• Pilot sends plane details to the ATC
• ATC checks runway
• ATC decides priority and gives signal to corresponding pilot
• Pilot then lands/ takes off as per signal from the ATC
TEXTUAL ANALYSIS
(a)ACTORS
i. RADAR
ii. ATC
iii. Runway
iv. Pilot
(b)VERBS
i. RADAR
57
1. Senses plane within its space
2. Sends signal to the ATC
ii. ATC
1. Receives signal from RADAR
2. Receives plane details from pilot
3. Checks runway
4. Decides priority
5. Gives signal to plane with highest priority
iii. Pilot
1. Sends plane details to the ATC
2. Receives signal from ATC
3. Land/Take off the plane
USECASE DIAGRAM
relationship are:
a. Association
b. Dependency
c. Generalization
58
ACTIVITY DIAGRAM
The components are:
a) Start State
b) End State
c) Transition
d) Decision Box
59
f) Swim Lane
INTERACTION DIAGRAM
SEQUENCE DIAGRAM
60
components are:
a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control
a) Actor
b) Object
c) Link
61
CLASS DIAGRAM
components are:
a) Class
b) Relationship:
1. Association
2. Aggregation
3. Generalization
4. Composition
5. Dependency
62
STATE CHART DIAGRAM
a) Start state
b) End state
c) State
d) Transition
ATC
63
Pilot

a) Start state
b) End state
c) State
d) Transition
64
SIMULATED COMPANY
INTRODUCTION
Companies are emerging like mushrooms nowadays. It is necessary for
us to examine how a company runs and the basic transactions taking place in a
company. This project emphasizes on the working of company with main actors
being managing director, marketing manager and catalog
Director collects capital and then starts company by installing
machinery and appointing labor. He then starts the production activity. After
production marketing manager along with managing director decides the price of
product which is then marketed by marketing manager. He then submits reports to
the director about the sales which are analyzed by the director. All these
activities are updated into the catalog from time to time
Let us just have an overview of point of sale:
• Director collects capital from various sources
• Director installs machinery and employs labor to begin production activity
• Director along with managing director decides price
• Marketing manager does marketing and submits reports to the director
TEXTUAL ANALYSIS
(a)ACTORS
i. Director
ii. Marketing Manager
iii. Catalog
(b)VERBS
i. Director:
1. Collects capital
2. Installs machinery
3. Employ labor
4. Begin Production
65
5. Decide price
6. Analyze reports
ii. Marketing Manager:
1. Decide price
2. Do marketing
3. Submit reports
4. Update catalog
iii. Catalog
1. Stores reports
USECASE DIAGRAM
relationship are:
a. Association
b. Dependency
c. Generalization
66
ACTIVITY DIAGRAM
The components are:
a) Start State
b) End State
c) Transition
d) Decision Box
67
f) Swim Lane
68
INTERACTION DIAGRAM
SEQUENCE DIAGRAM
components are:
a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control
69
a) Actor
b) Object
c) Link
CLASS DIAGRAM
components are:
a) Class
b) Relationship:
1. Association
70
2. Aggregation
3. Generalization
4. Composition
5. Dependency
STATE CHART DIAGRAM

a) Start state
b) End state
c) State
d) Transition
71
Director
Marketing Manager
72
Catalog

a) Start state
b) End state
c) State
d) Transition
73

Complete Record

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Complete Record

Transféré par

Droits d'auteur :

Formats disponibles

Gayatri Vidya Parishad College of Engineering

Madhurawada,Visakhapatnam- 530 041

Certified that this is a bonafied record of

No. of experiments done and certified:

Signature of Examiners Signature of

I would like to express my deep sense of

I owe project to Mr. K. Koteswara Rao, Asst

My sincere thanks to Asst Prof Mr. SRM

INTRODUCTION TO RATIONAL ROSE.....11

UNIFIED LIBRARY APPLICATION...........14

MULTITHREADED AIRPORT SIMULATION

UNIFIED MODELING LANGUAGE

iv. State chart Diagram

Rational Rose is a software where the UML can be model. Here,

Steps to draw diagram:

To draw the diagram:

UNIFIED LIBRARY APPLICATION

Let us just have an overview of the unified library application system:

STATE CHART DIAGRAM

STIMULUS RESPONSE DIAGRAM

b.Step2 – Set Path

public class administrator

//Source file: C:\\Documents and Settings\\Administrator\\My

public class catalog

public class Librarian

public class LibraryMember

//Source file: C:\\Documents and Settings\\Administrator\\My

public class ulas

Step 1 :- Open new project -> Class Diagram under Logical

• Customer places order to the shop keeper/sales boy

STIMULUS RESPONSE DIAGRAM

• RADAR senses the plane and signals the ATC

STIMULUS RESPONSE DIAGRAM

STATE CHART DIAGRAM

STIMULUS RESPONSE DIAGRAM

Vous aimerez peut-être aussi