Professional Documents
Culture Documents
NAME: T. JAHNAVI
ROLL NO: 1220609110
NAME OF THE
SNO EXPERIMENT PAGE REMARKS
NO
1 UML
INTRODUCTION
A POINT-OF-SALES
2 SYSTEM
ONLINE
3 BOOKSHOP
AN AUCTION
4 APPLICATION
A MULTI THREADED
5 AIRPORT SIMULATION
6 A SIMULATED
COMPANY
UML INTRODUCTION
STUDY OF UML
AIM:
DESCRIPTION:
CLASS
OBJECT
ABSTRACTION
ENCAPSULATION:
For example, the Dog class has a bark () method. The code for the
bark() method defines exactly how a bark happens (e.g., by inhale()
and then exhale(), at a particular pitch and volume). Timmy, Lassie's
friend, however, does not need to know exactly how she barks.
Encapsulation is achieved by specifying which classes may use the
members of an object. The result is that each object exposes to any
class a certain interface — those members accessible to that class.
POLYMORPHISM:
INHERITANCE:
At the center of the UML are its nine kinds of modeling diagrams,
which we describe here.
Class diagrams:
UML class notation is a rectangle divided into three parts: class name,
attributes, and operations. Names of abstract classes, such as
Payment, are in italics. Relationships between classes are the
connecting links.
Multiplicities Meaning
Sequence diagrams
Collaboration diagrams:
Activity diagrams:
A transition may fork into two or more parallel activities. The fork and
the subsequent join of the threads coming out of the fork appear in
the diagram as solid bars.
HISTORY
2. cashier
USECASES:
1. Bar code scanning
2. Process sale
3. Close sale
4. Pay Bill.
5. Tax calculation
6. Buy product
7. Update Inventory
ALGORITHMIC PROCEDURE:
Class diagram:
Point of
scale
RESULT:
Objectives:
Scope:
References:
Amazon.com, BN.com, Tigris.com
Functionality:
Multiple users must be able to perform work
concurrently. The user must be notified about the stock of books in the
inventory.
Usability:
The desktop user-interface shall be Windows 95, 98
compliant.
Reliability:
The system shall be available 24 hrs a day and 7 days a
week.
Performance:
The system shall support large number of simultaneous users
against the central database at any time.
The system shall provide access to catalog database with no
more then ten seconds latency.
The system must be able to complete 80% of all transactions
within 2 minutes.
UNIFIED MODELING LANGUAGE Page no:
GITAM INSTITUTE OF TECHNOLOGY
NAME: T. JAHNAVI
ROLL NO: 1220609110
Supportability:
None
USE CASE
The use case model describes the proposed functionality of
the system. A use case represents a discrete unit of interaction
between a user and the system. A use case is a single unit of
meaningful work. Each use case has a description which describes the
functionality that will be built in a proposed system. A use case may
‘include’ another use case functionality or ‘extend’ another use case
with its own behavior.
USE CASES:
Registration
Login
Create order
Book catalog
Manage cart and payments
Order status
Inventory
RELATIONSHIPS USED:
Association
Dependency
Composition
1. Draw the lines around the system and actors lie outside
the system.
Identify the actors which are interacting with the
system.
2. Separate the generalized and specialized actors.
3. Identify the functionality the way of interacting actors with
system and specify the behavior of actor.
4. Functionality or behavior of actors is considered as use
cases.
5. Specify the generalized and specialized use cases.
6. Se the relatonship among the use cases and in between
actor and use cases.
Adorn with constraints and notes.
7. If necessary, use collaborations to realize use cases.
UNIFIED MODELING LANGUAGE Page no:
GITAM INSTITUTE OF TECHNOLOGY
NAME: T. JAHNAVI
ROLL NO: 1220609110
CLASS DIAGRAM:
A Class is a standard UML construct used to detail the pattern
from which objects will be produced at run time. A class is a
specification- an object is an instance of a class. Classes may be
inherited from other classes, have other classes as attributes, delegate
responsibilities to other classes and implement abstract interfaces.
The class diagram for the proposed system has several
classes. These classes have attributes and operations. The description
for each of them is described clearly.
PACKAGES:
PACKAGE-1: BOOKSHOP
This package consists of following classes:
1. Bookshop staff
2. Book
3. Bookshop
4. Item
PACKAGE-2: CUSTOMER
This package consists of following classes:
1. Customer
2. Address
3. Billing Address
4. Shipping Address
CLASS DIAGRAM:
customer registration login create order book catalog inventory bookshop cart shippment payment consortinum database
staff details
1: login request
2: manages
3: updates
4: update
5: verify
6: register first
8: verify
9: logon successful
12: verify
13: stock ok
17: payment
COLLOBORATION DIAGRAM:
selections
ACTIVITY DIAGRAM:
display
welcome msg
get login
accept
selection more selections
completed
display create order
order for cart
acceptance rejected
ship to
customer
COMPONENT DIAGRAM:
address.ja order.java
va
book.java
central server.java
bokshop.java
address.cl bookstaff.java
ass
central
server.class/.dll item.java
item.class order.class
book.class
central
database
bookshop.
class
address.db order.db
bookstaff.c
lass
books.db
items.db
RESULT:
Thus various UML Diagrams were generated for ONLINE BOOK SHOP
and the corresponding code was generated using Visual Basic.
Overview:
Conceptualization:
Assumptions:
The users are allowed to register and give user id’s to have
identification.
The users are allowed to bid for any price according to their
wish provided it’s more than the minimum price of auction.
The fixed cut-off price is decided and confirmed for every
product.
The auctioneer requesting the product for the cut-off price is
given priority.
UNIFIED MODELING LANGUAGE Page no:
GITAM INSTITUTE OF TECHNOLOGY
NAME: T. JAHNAVI
ROLL NO: 1220609110
The auctioneer bidding the maximum price is given the
product.
Inputs:
Outputs:
Key Terms:
An Auction Simulation:
Actors:
1. Purchaser
2. Seller
1. Login
2. Seller
3. Purchaser
4. Chatting
5. Select Method of bidding
6. Select Method of Auction
7. Buy Goods
8. Register for goods
9. Select history of database
1. Validate User
2. Record chatting.
ALGORITHMIC PROCEDURE:
DIAGRAMS:
1. Draw the lines around the system and actors lie outside
the system.
2. Identify the actors which are interacting with the system.
3. Separate the generalized and specialized actors.
4. Identify the functionality the way of interacting actors with
system and specify the behavior of actor.
5. Functionality or behavior of actors is considered as use
cases.
6. Specify the generalized and specialized use cases.
7. Se the relationship among the use cases and in between
actor and use cases.
8. Adorn with constraints and notes.
9. If necessary, use collaborations to realize use cases.
login
request/send details
BIdder
Auctioner
: BIdder
login
search
get details
display details
pay price
logout
s:site
1: login
12: logout
8: check for product
2: search
p:product
5: display details
: BIdder 9: give ackn if suitable for selling
4: get details
3: request product details
a:auctione
r
log on to the
site
request details
bid the final price and if final fixed price bid for the
buy the product yes suitable no product
sell/buy the
product
wait to update
bid price
wait for
payment
COMPONENT DIAGRAM:
name
list of prices
central
server java
web host
customer
Central
database
product.db
AN AIRPORT SIMULATION
Actors:
ATC Controller
Use Cases
1. ATC Controller
2. Decision Support System
3. Planning
4. Emergency
5. Sensor
6. Gateway
7. Runway
8. Terminal
9. Available
10.Waiting Queue
Algorithmic Procedure:
Conceptualization
Assumptions;
All take offs take the same amount of time and all landings take
the same amount of time (through these two times may be
different).
Planes arrive for landing at random times, but with a specified
probability of a plane arriving during any given minute.
Planes arrive for take off at random times, but with a specified
probability of a plane arriving during any given minute
Landings have priorities over takeoffs.
Key terms:
Aircraft simulation.
Airport: runways, terminals, planes, control room.
Aircraft: passengers, model no. cockpit, pilots.
Function points:
1. Transmit/receive signals.
2. Pilot sends signals for takeoff/landing.
3. Loop
- Check status of each runway.
- Finalize a free runway.
- Assign the runway to the plan.
4. Update status of runway and terminal.
5. Get the plane landed safely.
6. Check if time left for next departure.
7. Loop
- Check the status of each terminal.
- Validate if terminal suitable for particular aircraft.
- Assign terminal to aircraft.
UNIFIED MODELING LANGUAGE Page no:
GITAM INSTITUTE OF TECHNOLOGY
NAME: T. JAHNAVI
ROLL NO: 1220609110
8. Get the plane parked in the terminal.
9. Update status of terminal.
Requirement Analysis:
Textual Analysis:
This covers the requirements and diagrams of the project. The
complete simulation of airport control system as follows
Actors:
These are who are involved in interaction of the whole process.
1. Technical head: He is the person who supervises the controls
the ground traffic on runway. He checks the status of runways
and assigns the free runways and terminals for takeoff and
landing.
2. Pilot: He is the person who controls the aircraft. He transmits or
receives signals regarding the free runways, and terminal from
the control room. He is responsible for the safe landing or
takeoffs the planes.
Use cases:
The steps involved in the whole process are indicated as use
cases.
Transmit/receive signals.
Check availability of runways.
Land the plane.
Check if time left for next departure.
Check for free terminal.
Update status of runway, terminal.
1. Transmit/receive signals: The pilot in the aircraft transmits
signals for requesting a free runway to takeoff or land. The
control room on the ground receives these signals from the
aircrafts.
2. Check availability of runway: The status of each runway in
the airport is checked if it’s free and its going to be free until the
particular aircraft is landed or takeoff. If this is going to be free
then runway number is transmitted to the pilot on aircraft.
3. Land the plane: The plane is landed safely on the airport as per
directions given by the control room regarding runway and
timings.
Classes:
The classes contain the attributes and operations related to them
the main classes classified in this solution are:
1. Control Room: he is the person who supervises the controls the
ground traffic on runway. He checks the status of runways and
assigns the free runways and terminals for takeoff and landing.
2. Plane Cockpit: He is the person who controls the aircraft. He
transmits or receives signals regarding the free runways and
terminals from the control room. He is responsible for the safe
landing or takeoff of the plane.
3. Runway: This is the part the planes use to land or takeoff only
one plane can use runway at a time to takeoff or land.
4. Terminal: This is the place where the planes are parked until
the next departure. The terminal is to be parked in it.
5. Takeoff/land: The leaving of planes is called takeoff and
coming back to runway is called landing. The runway is used for
either purpose.
Diagrams:
Class Diagram
A Class is a standard UML construct used to
detail the pattern from which objects will be produced at run time. A
class is a specification- an object is an instance of a class. Classes may
be inherited from other classes, have other classes as attributes,
delegate responsibilities to other classes and implement abstract
interfaces.
Classes of airport simulation are:
Sequence diagram
Collaboration Diagram
Activity Diagram
Component Diagram
Deployment Diagram
Class Diagram:
send/receive signal
land / aircraft
park aircraft
Sequence Diagram:
Airport Simulation
2: send signal
4: send acknowledgement
6: wait signal
7: send signal
8: send ack
p:prane
Cockpit 10: if time is for next dep send req
1: request signal
11: if terminal is free send terminal no
6: wait signal
7: send signal 14: update status of terminal
8: send ack
12: send terminal
13: land aircraft
T:termin
: control room
al
5: check avaliable for run way
9: update runway status
2: send signal
4: send acknowledgement
R:runwa
y 3: Check Weather conditions
W:Weather
Dept
landing
give aircraft
info to lock s/m
lock system
checking for ks
acquire
runway lock landing on
another runway
aircraft at acquire
take off area terminal lock
takeoff
give aircraft
info to lock s/m
checks
for locks
acquire takeoff
area lock
acquire
taxiing lock
aircraft at acquire
takeoff area runway lock
req runway no
wait for
runway no
avail
not avail
wait for
terminal no
not avail
avail
halt
Component Diagram:
terminal
lock.java
central
landing.jav
server java
a
takeofflock
.java
taxiinglock.
central server java
.class / .dll
terminalloc
k.class
landing.cla
ss
takeofflock
.class
taxiinglock.
class
airport.db
central
database
priority.db
Deployment Diagram:
<<DATA BASE>>
central database
<<SERVER>>
central server
<<WIRELESS COMMUNICATION>>
<<DEVICE>>
<<DEVICE>> <<DEVICE>> <<DEVICE>> control manager
aircarft controlor lockmanager taxiing
manager
Result:
The various UML diagrams were drawn for AIRPORT
SIMULATION SYSTEM application and the corresponding code was
generated.
A SIMULATED COMPANY
A SIMULATED COMPANY
Conceptualization:
Assumptions:
The company has to take the loan and repay the loan.
It has to purchase machinery and start the production.
The sales person has to sell the foods and update the details in the
record.
The sales has to submit the record and stock details required.
The performance department has to prepare record statistics as given
by marketing department.
The performance department has to get collected details from all the
departments and submit to the company.
Inputs:
Outputs:
Key Terms:
1. Draw the lines around the system and actors lie outside
the system.
2. Identify the actors which are interacting with the system.
3. Separate the generalized and specialized actors.
4. Identify the functionality the way of interacting actors with
system and specify the behavior of actor.
5. Functionality or behavior of actors is considered as use
cases.
6. Specify the generalized and specialized use cases.
Sequence Diagram:
Collaboration Diagram:
Activity Diagram:
<<Application>>
Simulated
company
RESULT:
Thus various UML Diagrams were generated for SIMULATED
COMPANY and the corresponding code was generated using Visual
Basic.