CS1402 OOADLab Manual

OBJECT ORIENTED ANALYSIS AND DESIGN
RECOD NOTE BOOK

ANNA UNIVERSITY
DEPARTMENT OF INFORMATION TECHNOLOGY

INDIRA INSTITUTE OF ENGINEERING TECHNOLOGY
PANDUR, THIRUVALLUR DIST – 631 203
PRACTICAL RECORD
NAME:……………………………… REGISTER No:……………………..
YEAR:…………… SEM:…………….. SUBJECT :………………………….
1
OBJECT ORIENTED ANALYSIS AND DESIGN
RECOD NOTE BOOK
ANNA UNIVERSITY
BONAFIDE CERTIFICATE
NAME : …………………………. REGISTER NO ……………..
BRANCH : ……………………………. CLASS ……….………..
This is certified to be the bonafide record of work done

by the student in the OBJECT ORIENTED ANALYSIS AND DESIGN
Laboratory of Indira Institute of Engineering and Technology
Head of the Department Staff-In-Charge
SUBMITTED FOR PRACTICAL EXAMINATION HELD ON ….…………
Internal Examiner External Examiner
2
INDEX
S.NO DATE TOPIC P.NO SIGN
1. Study of UML
2. ATM System
3. Online Purchase System
4. Library Management System
5. E – Ticketing
6. Course Registration System
7. Quiz System
8. Student Marks Analyzing System
9. Email Client System
3
Ex. No 1
STUDY OF UML
AIM:-
To study the basic concepts of Unified Modeling Language.
UML NOTATION
• Unified Modeling Language.
• Set of notations and conventions used to describe and model an application.
• Universal language for modeling systems.
• Standard notation for OO modeling systems.
• Does not specify methodology to develop an application.
UML DIAGRAMS
• Class Diagram
• Use Case Diagram
• Behavioral Diagram
 Interaction Diagram
 Sequence Diagram
 Collaboration Diagram
 State Chart Diagram
 Activity Diagram
• Implementation Diagram
 Component Diagram
 Deployment Diagram
CLASS DIAGRAM
• Shows the static structure of the model.
• Collection of static modeling elements such as classes and their relationships
connected as a graph.
• Provides visual representation of objects, relationships and their structures.
4
Class:-
• A class is a set of objects that share a common structure and common behavior.
• It is represented as:
<Class Name>
<Attributes>
<Operations>
Interface:-
• Specifies the externally-visible operations of a class and/or component.
Association:-
• Model properties of associations.
• The properties are stored in a class and linked to the association relationship.
• Example,
Bank Account Person
Generalization:-
• A generalize relationship is a relationship between a more general class or use case
and a more specific class or use case.
• Example,
Vehicle
Bus Truck Car
5
USE CASE DIAGRAM
• Set of use cases enclosed by system boundary, communication association between
actors and use cases, and generalization among use cases.
Actors:-
• External factors that interacts with the system from the user's perspective.
Use Cases:-
• Set of scenarios that describe how actor uses the system.
• Represented as,
Relationship:-
• Communication – communications with the use case normally.
• Uses – Shown by generalization arrow from the use cases.
• Extends – Used when one case does more than another that is similar to it.
BEHAVIOR DIAGRAM
INTERACTION DIAGRAM
• Diagrams that describes how group of objects are collaborated.
SEQUENCE DIAGRAM:
• Describes the behavior of the system through interaction between the system and the
environment in time sequence.
• Two dimensions:
 Vertical dimension – represents time.
 Horizontal dimension – represents objects.
• Life line – Object's existence during the interaction.
6
Object 1 Object 2
<Event>
COLLABORATION DIAGRAM:
• An interaction diagram that shows the order of messages that implement an operation
or a transaction.
• Collaboration diagrams show objects, their links, and their messages.
Object 1 1. <Event> Object 2
Object:-
• An object has state, behavior, and identity.
• Objects interact through their links to other objects.
Link:-
• A link is an instance of an association, analogous to an object.
Message:-
• A message is the communication carried between two objects that trigger an event.
STATECHART DIAGRAM
• Models the dynamic behavior of individual classes or any other kind of object.
• Shows the sequences of states, events, and actions.
State:-
• Represents a condition or situation during the life of an object during which it satisfies
some condition or waits for some event.
<State>
7
Start State:-
• Shows the beginning of workflow.
End state::-
• Represents the final or terminal state.
ACTIVITY DIAGRAM
• Used for modeling the sequence of activities in a process
• Special case of a state machine in which most of the states are activities and most of
the transitions are implicitly triggered by completion of the actions in the source
activities.
Activity:-
• Represents the performance of task or duty in a workflow.
<Activity>
Swim lanes:-
• Represents organizational units or roles within a business model.
IMPLEMENTATION DIAGRAM
• Shows the implementation phase of system development.
• Two types of implementation diagrams:
 Component diagram
 Deployment diagram
COMPONENT DIAGRAM
Models the physical components in the design.
A graph of the design’s components connected by dependency relationships.
Includes concept of packages.
Package is used to show how classes are grouped together.
8
DEPLOYMENT DIAGRAM
• Shows the configuration of runtime processing elements and software components.
• It is a graph of nodes connected by communication association.
• Nodes are the components that are connected to other components through
dependencies.
• Used in conjunction with component diagrams to show the distribution of physical
modules.
RESULT:-
Thus the different conceptual models under UML have been studied.
9
Ex. No 2
ATM SYSTEMS
CONTENTS
1. ANALYSIS
1.1 Identifying the Actors
1.2 Identifying the Use Cases
2. REQUIREMENTS
2.1 System Requirements
2.2 Software Requirements
3. DESIGN
3.1 Use Case Diagram
3.2 Class Diagram
3.3 Sequence Diagram
3.4 Collaboration Diagram
3.5 State Chart Diagram
3.6 Component Diagram
10
ANALYSIS
Identifying the Actors

• Customer
• Bank Clerk
Identifying the Use Cases

• Insert Card
• Enter Account No & Pin
• Validate Account No & Pin
• Request for Cash
• Withdraw Money
• Request Balance
• Get Status
REQUIREMENTS
System Requirements
Processor : Pentium IV 1.7
RAM : 128 MB
Hard Disk : 40 GB
Software Requirements
CASE Tool : Rational Rose
Language : Visual Basic in Java
Front End : Visual Basic , Visual C++
Back End : MS Access , Oracle
Testing : Win Runner
11
ATM USE CASE DIAGRAM
InsertCard
EnterAccno&Pin
ValidateAccno&Pin
Customer RequestforCash
BankClerk
CheckforBalance
Withdraw Money
CheckBalance
<<extend>>
GetStatus
12
ATM CLASS DIAGRAM
ATM
Attrib utes
Operations
public ATM()
ATMScreen CashDispenser
CardReader Attrib utes Attrib utes
Attrib utes Operations private int cashbal
private int Cardno public ATMScreen() Operations
Operations public void deductAmt() public CashDispenser()
public CardReader() public void promptforPIN() public int getCashbal()
public int getCardno() public void enterAmt() public void setCashbal(int val )
public void setCardno(int val ) public boolean authorizePin() public void provideRept()
public void acceptCard() public void verifyAmt() public void provideCash()
public void readCard() public void enterPin()
public void ejectCard() public void initializeScreen()
1..* public void selectTransaction()
public void promtforTransaction()
public void promtforAmount()
public CardReader getCardReader()
Customer public void setCardReader(CardReader val )
Attrib utes
private int accno Account
private int Cardno Attrib utes
private string name private int accno
private string address private int PIN
private longint phone private int Cashbal
private float balance Operations
Operations public Account()
public Customer() public void setAccno(int val )
public int getAccno() public int getAccno()
public void setAccno(int val ) 1 1 public int getPIN()
public int getCardno() public void verifyPIN(int val )
public void setCardno(int val ) public int getCashbal()
public string getName() public void setCashbal(int val )
public void setName(string val ) public void openAccount()
public string getAddress() public void withdraw()
public void setAddress(string val ) public void deductAmt()
public longint getPhone() public void checkBalacne()
public void setPhone(longint val ) public void verifyAmt()
public float getBalance()
public void setBalance(float val )
13
ATM SEQUENCE DIAGRAM
: CardReader : ATMScreen : Account : CashDispenser
: Customer
public void acceptCard()

public void readCard()
public void openAccount()
public void promptforPIN()
public void verifyPIN(int val )

public void promtforTransaction()
public void promtforAmount()
public void w ithdraw ()
public void verifyAmt()
public void deductAmt()
public void provideCash()
public void provideRept()

public void ejectCard()
14
ATM COLLABORATION DIAGRAM
public v oid enterPin() public v oid enterA mt()
public v oid s elec tTrans ac tion()
: AT MS creen
public v oid v erif y PIN(int v al )
: C usto m er
public v oid ac c eptCard()
public v oid w ithdraw ()
public v oid c hec kBalac ne()
public v oid readCard()
public v oid deduc tA mt()
public v oid ejec tCard()
public boolean authoriz ePin()
: C ard R ead er : Acco u n t
15
ATM STATE CHART DIAGRAM
REQUEST PIN
PIN NUMBER
Wrong Pin
Accept Pin re-request Pin
Login Complete
16
CLASS CODE
public class CardReader()
{
private int Cardno
public CardReader()
{
}
public void acceptCard()
{
}
public readCard()
{
}
}
public class ATMScreen()

{
public ATMScreen()
{
}
public void enterPin()
{
}
public void selectTransaction()
{
}
public void verifyAmt()
{
}
}
17
public class Customer()
{
private int accno

private int Cardno
private String name
public Customer()
{
}
public int getAccno()
{
}
public int getCardno()
{
}
public void setName(String val)
{
name=val
}
}
RESULT:-
Thus the UML models for the ATM System have been developed and verified.
18
Ex. No 3
ONLINE PURCHASE SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.5 Activity Diagram
3.6 State Diagram
19
ANALYSIS

• Customer
• Software
• Banking
• Dealer
• Browse Catalog
• Select Item
• Request Item
• Payment Details
• Issue Details
• Authentication
• Check for validity
• Issue Goods
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
20
ONLINE PURCHASE USE CASE DIAGRAM
Onlin eP urchase
Brow se Ca tlog
S e le ct Ite m
S oftw are
C ustomer Re que st Ite m
Ask for P a ym e nt &

S hipping de ta ils
Issue De ta ils
Issue
Authoriz a tion
B anking
Che ck for
va lidity
De lie ve r Goods
D ealer
21
ONLINE PURCHASE CLASS DIAGRAM
C u s to m e r
S h o p p in g C a rd
A ttr ib u tes
A ttr ib u te s
private s tring addrtos hip
public float s ubtot al private s tring nam e
public float s ales m oney private s tring addrtobill
public float totalm oney private s tring em ailadd
O p er a tio ns private int c reditrating
public S hoppingC ard() O pe ra tion s
public float getS ubtotal() public C us tom er()
public void s etS ubtotal(float val ) public s t ring getA ddrtos hip()
public float getS ales m oney () public void s etA ddrtos hip(s tring val )
mCu s to me r
public void s etS ales m oney (float val ) public s t ring getN am e()
public float getTot alm oney () * 1
public void s etN am e(s tring val )
public void s etTotalm oney (float val ) public s t ring getA ddrtobill()
public void plac eO rder() public void s etA ddrtobill(s tring val )
public void rem oveO rder() public s t ring getE m ailadd()
public C us tom ervoid[0..*] getC us tom er() public void s etE m ailadd(s tring val )
public void s etC us tom er(C us tom er val[0. .*] ) public int getC reditrating()
public C reditC ardvoid[0..*] getC reditC ard() public void s etC reditrating(int val )
public void s etC reditC ard(C rdeitC ard val[0..*] ) public void dis play C ategory ()
mCu s to me r
public C us tom er[0..*] getC us tom er() public void s elec tItem ()
public void s etC us tom er(C us tom er val[0. .*] ) public void delieverItem ()
public C reditC ard[0..*] getC reditC ard() 1 public void rem oveO rder()
public void s etC reditC ard(C reditC ard val[0..*] )
1
mCre d itCa r d 1
*
C re d itC a rd
O pe ra tio ns P re ffe re d C u s to m e r
Ite m O fP u rc h a s e public C reditC ard() A ttr ib u tes
A ttr ib ute s public int getN um ber() private int dis c ountrate
private int quant ity public void s etN um ber(int val ) O p e r a tio n s
private float pric eperitem public date getE x piry date()
mPr e f f e r e dCu s to mepublic
r P refferedC us tom er()
O p e r a tio n s public void s etE x piry date(date val ) public int getD is c ountrate()
public Item O fP urc has e() public boolean getIs s ue() public void s etD is c ountrate(int val )
public int getQ uantity () public void s etIs s ue(boolean val ) * 1
public C us tom er getC us tom er()
public void s etQ uantity (int val ) public void authoriz eC harge() public void s etC us tom er(C us tom er val )
public float getP ric eperitem () public P reffered() public C us tom er getC us tom er1()
public void s etP ric eperitem (float val ) public Item O fP urc has e getItem O fP urc has e() public void s etC us otm er1(C us tom er val )
public C us tom er fetC us tom er() public void s etItem O fP urc has e(Item O fP urc has e val ) public C us tom er getC us tom er()
public void s etC us tom er(C us tom er val ) public P refferedC us tom er[0..*] getP refferredC us tom er() public void s etC us tom er(C us tom er val )
public P roduc t[0..*] getP roduc t() public void s etP refferredC us tom er(P refferedC us tom er val[0..*] )
public void s etP roduc t(P roduc t val[0..*] public
) P refferedC us tom er[0..*] getP refferedC us tom er()
public P roduc t[0..*] getP roduc t() public void s etP refferedC us tom er(P refferedC us tom er val[0..*] )
public void s etP roduc t(P roduc t val[0..*] )
mPr od u c t
P ro d u c t
A ttr ib u tes
O pe r a tion s
public P roduc t()
22
ONLINE PURCHASE SEQUENCE DIAGRAM
: Shoppingcart : creditcard
: Customer
public void browsecatalog()
public void displaycatalog()

public void selectItem()
public void getCreditRating()

public void getAddrToShop()
public void setCreditCard()
public void shipmentDetails()
public void authorizedCharge()

public void getExpiryDate()
validation
public void authorize()
public void setCrediting(int val )
public void setAddrToShip()
public void deleverItem()

public void rejected()
public void removeOrder()
23
ONLINE PURCHASE COLLABORATION DIAGRAM
: Customer
public void setAddrToShip()

public void browsecatalog()
public void deleverItem()

public void getCreditRating()
public void shipmentDetails()
public void getAddrToShop()
public void displaycatalog()

public void removeOrder()

public void setCreditCard()
public void setCrediting(int val )
: Shoppingcart
public void rejected()
public void authorize()
public void authorizedCharge()
: creditcard
public void getExpiryDate()
24
ONLINE PURCHASE ACTIVITY DIAGRAM
OnlinePurchase
Customer Shoppingcart Creditcard
Unnamed
Browse Displaying
Catlog Catlog
{ From OP_Activity } { From OP_Activity }
Selecting Displaying ....

Catlog
{ From OP_Activ... { From OP_Activity }
Validating
Selecting & Requesting
credit
{ From OP_Activit... { From OP_Activity } { From OP_Activity }
Issuing Accepting
payment delivery
Unnamed
Delievering Authorized
Item
Rejected
{ From OP_Activity }
Unnamed
25
ONLINE PURCHASE STATECHART DIAGRAM
CHECKING
PROCESS
WAITING DELIVERY
CANCELLING DISPATCH
EXIT
26
CLASS CODE
public class Customer()

{
private string name

private string addtoshop
private int creditrating
public Customer()
{
}
public void delieverItem()
{
}
{
}
public void removeItem()
{
}
}
public class ItemOfPurchase()

{
private int quantity

private flaot priceperitem
public ItemOfPurchase()
{
}
public float getPriceperItem()
{
}
public void setPriceperItem(float val)
{
Item = val
}
}
27
public class Product()
{
public Product()
{
}
}
RESULT:-
Thus the UML models for the Online Purchase System have been developed and verified.
28
Ex. No 4
LIBRARY MANAGEMENT SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
29
ANALYSIS

• Student
• Computer
• Publisher
• Librarian
• Login
• Request Book
• Book Details
• Collect Books
• Order Books
• Issue Books
• Database
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
30
USE CASE DIAGRAM
login
Request book
Student
Book details
Collect books
Publisher
Order books
Librarian
Issue books
database
Computer
31
CLASS DIAGRAM
Librarian
Student Attributes
Attributes Operations
private int scode public void issueBook()
private String sname public void orderBook()
Operations public void issueCard()
public Student() public void update()
1..*
public int getScode() public Librarian()
public String getSname() 1..*
public void setSname(String val )
public void viewBookStatus()
public void requestBook()
public void returnBook()
public void setScode(int val ) Database
Attributes
private int bookid
private String bookname
private String authorname
private int accessno
Operations
Publisher
public Database()
Attributes
public int getBookid()
private int orderno
public void setBookid(int val )
private String orderbookname
public String getBookname()
Operations public void setBookname(String val )
public Publisher() public String getAuthorname()
public int getOrderno() public void setAuthorname(String val )
public void setOrderno(int val ) public int getAccessno()
public void setOrderbookname(String val ) public void setAccessno(int val )
public String getOrderbookname()
32
SEQUENCE DIAGRAM
Database : Publisher :
Student :
Librarian :
public void orderBooks()

login
public void deliverbook()

login valid
public void updateNew Arrivals()
public void bookStatus()
bookavailable
validation
issueBook
publc void receiveBook()
update
33
ACTIVITY DIAGRAM
LibraryS yste m
S tudent Librarian C om put er
L og in
Vie w B oo k S tatu s
D atabase
R e tu rn bo oks
B ook A v a ilable
B o ok u pdation
R e qu e st for bo oks
Book no t Av ilable
R e ce iv in g B o oks
B o ok issue
34
STATE CHART DIAGRAM
Student ID
Enter Id number
SID
Wrong Id no.
Correct
Wrong ID- re-enter
Re-enter id
ID Accepted
ID accepted
Select frommain menu
select frommain menu
Prepare for next selection
Library Main Menu
35
SOURCE CODE
1. Student.java
public class Student
{
private int scode;
private String sname;
public Student()
{
}
public int getScode()
{
return scode;
}
public void setSname( String val )
{
sname = val;
}
public String getSname()
{
return sname;
}
public void viewBookStatus()
{
}
{
}
{
}
36
public void setScode( int val )
{
scode = val;
}
}
2.Librarian.java
public class Librarian
{
public void issueBook()
{ }
public void orderBook()
{
}
public void issueCard()
{
}
public void update()
{
}
public Librarian()
{
}
}
RESULT:-
Thus the UML models for the Library Management System have been developed and
verified.
37
Ex. No 5
E - TICKETING
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
38
ANALYSIS
• Passenger
• Clerk

• Update Customer DB
• Validation
• Service ATM
• Cash to Customer
• Bill to Customer
• Credit Cards
• Payment
• Reservation Form
• Reservation Chart
• Cash Mode
• Ticket Confirm
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
39
E-TICKETING USE CASE DIAGRAM
Up d ate
cu s to m e r DB
P a sse n g e r
V a lid a t io n
C as h to S e r v ic e A T M B ill t o c u s t o m e r
cu s to m e r
R e s e v a t io n
C r id it c a r d s Paym e n ts
Fo r m
Cas h m ode R e s e v a t io n
T ic k e t C o n f ir m C h art
C l e rk
40
E-TICKETING CLASS DIAGRAM
Train_Details
Attrib utes
private long no
Passenger Train_Seatdetails
private String destination
Attrib utes
private String tname Attrib utes
private s tring pname private String source private long tno
private long Age private lonf depatiretime private date DOJ
private s tring Sex private long arrivaltime private long seats
private date DOJ private int coaches
O perations
O perations
public Train_Details() O perations
public Passenger() public long getNo() public Train_Seatdetails()
public string getP name() 1..*
public void setNo(long val ) 1..* public long getTno()
public void setP name(string val ) public String getDestination() public void setTno(long val )
public long getAge() public void setDestination(String val ) public date getDOJ()
public string getS ex() public String getTname() public void setDOJ(date val )
public void setS ex(string val ) public void setTname(String val ) public long getS eats()
public date getDOJ() public String getSource() public void setSeats(long val )
public void setDOJ(date val ) public void setSource(String val ) public int getCoaches()
public void setA ge(long val ) public lonf getDepatiretime() public void setCoaches(int val )
1..* public long getArrivaltim e()
public void setArrivaltim e(long val )
public void setDepatiretime(lonf val )
R eservation
Attrib utes
private long tno 1..*
private date DOJ
private long seatno
private int nop
private int Coaches
O perations
Payment public Reservation()
public long getTno()
Attrib utes
public void setTno(long val )
private float Amount
public date getDOJ()
O perations
public void setDOJ(date val )
public Payment()
public long getSeatno()
public float getA mount()
public void setSeatno(long val )
public void setAmount(float val )
public int getNop()
public void setNop(int val )
public int getCoac hes()
public void setCoaches(int val )
public void reservatio()
41
E-TICKETING SEQUENCE DIAGRAM
: Reservation
: TrainDetails : Train Seat Details : Payment
: Passenger
public void reservatio()
public void gettraindetails()
public void checkavailability()
public void paymentcalc()
public void getpayment()
public void issueticket()
public void updatet_trainseats()
42
E-TICKETING COLLABORATION DIAGRAM
: T ra in _ S e a tD e ta ils
p u b lic lo n g g e tS e a tn o ()
p u b lic lo n g g e tTn o ( ) p u b lic v o id p a y me n tc a lc ( )

: T ra in _ D e ta ils : R e s e rv a tio n : p a y m e n ts
p u b lic v o id r e s e r v a tio ( )
: Passenger
43
E-TICKETING ACTIVITY DIAGRAM
Passenger R eservation TrainD eatails S eatdetails
C heck train Show train

details details
{ Fro m eticke ta ctivity }
{ Fro m e ticke ta ...
C heck seat
availability
{ From eticke ta...
R eserve
tickets
{ Fro m eticketa ...
R equest
P ayment
Make { Fro m eticke ta...
P aym ents
{ From e ticketactivi...
Issue
Ticket
{ Fro m e ticke t...
44
E-TICKETING STATE CHART DIAGRAM
REQUEST FOR CREDIT

CARD NUMBER
CREDIT AGENCY
VALIDATION
COMPLETED
TRANSACTION
OVER
45
E-TICKETING JAVA IMPLEMENTATION CODE
public class Train_Seatdetails

{
private long tno;
private date DOJ;
private long seats;
private int coaches;
public Train_Seatdetails()
{
}
public void setTno( long val )
{
tno = val;
}
public long getTno()
{
return tno;
}
public void setDOJ( date val )
{
DOJ = val;
}
public date getDOJ()
{
return DOJ;
}
public void setSeats( long val )
{
seats = val;
}
46
public long getSeats()
{
return seats;
}
public void setCoaches( int val )
{
coaches = val;
}
public int getCoaches()
{
return coaches;
}
}
RESULT:-
Thus the UML models for the E – Ticketing System have been developed and verified.
47
Ex. No 6
COURSE REGISTRATION SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
48
ANALYSIS
• Administrator
• Course
• Professor
• Student
• Billing

• Maintain Student Information
• Maintain Subject Information
• Done Registration
• View Report Card
• Register Course
• Select subjects to teach
• Submit grades
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
49
USE CASE DIAGRAM
v ie w re p o rt c a rd
c o u r s e ...
m a i n ta i n r e g i ste r fo r
stu d e n ts c o u r se
i n fo r m a ti o n
s tu d e n t
lo g in
m a i n ta i n sta ff
i n fo r m a ti o n
A d m in is tr a to r (C O E )
c l o se
r e g i str a ti o n
b illin g
se l e c t su b j e c ts
to te a c h
su b m i t g r a d e s
P r o fe s s o r
50
CLASS DIAGRAM
c o u r s e _ c a t lo g
s tu d e n t
A ttr ib u te s
A ttr i b u te s
p r i va t e S t rin g c o d e p r o fe s s o r
p r i va t e in t re g n o p r i va t e S t rin g c o u rs e _ n a m e
p r i va t e S t rin g n a m e p r i va t e S t r i n g o ffe r e d _ b y
A ttr ib u te s
p r i va t e S t rin g b ra n c h p r i va t e S t r i n g n a m e
p r i va t e d o u b le a m o u n t
p r i va t e S t rin g c o u rs e p r i va t e i n t i d
p r i va t e in t s e a t s
O p e r a tio n s p r i va t e S t r i n g d e p t
O p e r a tio n s
p u b lic s t u d e n t () 1 ..* p u b lic c o u rs e _ c a t lo g ()
O p e r a tio n s
p u b lic in t g e t R e g n o () p u b lic p r o fe s s o r ( )
p u b lic S t r i n g g e t C o d e ( )1 . . * 1
p u b lic vo i d s e t R e g n o ( i n t v a l ) 1 . . * p u b lic S t rin g g e t N a m e ()
p u b lic vo i d s e t C o d e ( S t r i n g v a l )
p u b lic S t rin g g e t N a m e () p u b lic vo i d s e t N a m e ( S t r i n g v a l )
p u b lic S t rin g g e t C o u rs e _ n a m e ()
p u b lic vo i d s e t N a m e ( S t r i n g va l ) p u b lic i n t g e t Id ( )
p u b lic vo i d s e t C o u r s e _ n a m e ( S t r i n g va l )
p u b lic S t rin g g e t b ra n c h () p u b lic vo i d s e t Id ( i n t v a l )
p u b lic S t r i n g g e t O ffe r e d _ b y ( )
p u b lic vo i d s e t b r a n c h ( S t r i n g v a l ) p u b lic S t rin g g e t D e p t ()
p u b lic vo i d s e t O ffe r e d _ b y ( S t r i n g v a l )
p u b lic S t rin g g e t C o u rs e () p u b lic vo i d s e t D e p t ( S t r i n g v a l )
p u b lic d o u b le g e tA m o u n t() 1 ..*
p u b lic vo i d s e t C o u r s e ( S t r i n g v a l ) p u b lic vo i d s e t A m o u n t ( d o u b l e va l )
1 ..* p u b lic in t g e t S e a t s ()
p u b lic vo i d s e t S e a t s ( i n t va l )
1
1
1 a d m in is t r a t o r
A ttr ib u te s
p r i va t e i n t i d
O p e r a tio n s
p u b lic a d m in is t ra t o r()
p u b l i c i n t g e t Id ( )
p u b l i c vo i d s e t Id ( i n t va l )
51
SEQUENCE DIAGRAM
: Registrar : Professor
Student : : CourseCatalog
public void addStudent()
public void addProfessor()
public void getCourseOffered()
public void addCourse()
public String[] getCourse()
public boolean isAvailable(String id )
public Stringvoid regForCourse(int id, String code )
public void updateSeat(String code )
public void calculateBill()
52
COLLABORATION DIAGRAM
public void addP r ofes s or ( )
: R e g is tr a r : P r o fe s s o r
public void g etC our s eoffer ed( )
public void c alc ulateBpublic

ill( ) void addS tudent( )
public S tr ing ( our s eer C R U nnam ed ) public void updateS eat( S tr ing c ode )
public void g etC our s e( )
: S tu d e n t : C o u r s e C a tlo g
53
ACTIVITY DIAGRAM
S tu d e n t C o u r se R e g i str a ti o n
S tudent P ro f e s s o r R e g is t r a r
U nnam ed
O fffe r C o u r se
{ F r o m A c tiv ity C o u r s e } C h e c k / U p d a te
R e g i ste r fo r C a ta l o g
C o u r se { F r o m A c tiv ity C o u r s e }
{ F r o m A c tiv ity C o u r s ...
V ie w R e p o rt
S u b m it R e p o rt
{ F r o m A c tiv ity C o u r s ...
{ F r o m A c tiv ity C o u r s e }
54
STATE CHART DIAGRAM
P ro fe s s o r
o ffe rs S t u d e n t E n r o llm e n t
c o u rs e C a t lo g
C h e c k in g
R e g is t r a r
R e g is t e r s B illin g
55
CLASS CODE
public class student()

{
private regno
private String name
private String card
public student()
{
}
public getRegno()
{
}
public String name()
{
}
}
public class course_catalog()

{
private String code

private int seats
public course_catalog()
{
}
public String Code()
{
}
public get Seats()
{
56
public class professor()
{
private int ic
private String name
public Professor()
{
}
public String name()
{
}
public void subject()
{
}
}
RESULT:-
Thus the UML models for the Course Registration System have been developed and verified.
57
Ex. No 7
QUIZ SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
58
ANALYSIS
• Administrator
• Course
• Professor
• Student
• Billing

• Register Course
• Submit grades
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
59
USE CASE DIAGRAM
60
CLASS DIAGRAM
61
SEQUENCE DIAGRAM
62
63
ACTIVITY DIAGRAM
64
STATECHART DIAGRAM
65
CLASS CODE
public class quiz()

{
String name
String user id
public opname()
{
}
}
public class user()

{
String name
String userid
String course
}
public class questformat()

{
String Format
public displayQuery()
{
}
public questFormat()
{
}
}
public class topic()

{
String general
String technical
String science
String sports
66
public store()
{
}
public topic()
{
}
}
RESULT:-
Thus the UML models for the Quiz System have been developed and verified.
67
Ex. No 8
STUDENT MARKS ANALYSIS SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
68
ANALYSIS
• Administrator
• Course
• Professor
• Student
• Billing

• Register Course
• Submit grades
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
69
USE CASE DIAGRAM
70
CLASS DIAGRAM
71
SEQUENCE DIAGRAM
72
73
ACTIVITY DIAGRAM
74
STATECHART DIAGRAM
75
CLASS CODE
public class MarksRegister

{
private int StringRegno;
private int intMaxmarks;
private int intMinmarks;
private int intMarksobtained;
/**
@roseuid 46D9020F0017
*/
public MarksRegister()
{
/**
@roseuid 46D901BF027C
*/
public void checkRegno()
{
/**
@roseuid 46D901C501FF
*/
public void checkSubjectCode()
{
/**
@roseuid 46D901CC0395
*/
public void setResults()
{
}
}
RESULT:-
Thus the UML models for the Student Marks Analysis System have been developed and
verified.
76
Ex. No 9
EMAIL CLIENT SYSTEM
CONTENTS
1. ANALYSIS
2. REQUIREMENTS
3. DESIGN
3.2 Class Diagram
3.6 State Diagram
77
ANALYSIS
• Administrator
• Course
• Professor
• Student
• Billing

• Register Course
• Submit grades
REQUIREMENTS
System Requirements
RAM : 128 MB
Hard Disk : 40 GB
78
USE CASE DIAGRAM
79
CLASS DIAGRAM
SEQUENCE DIAGRAM
80
81
ACTIVITY DIAGRAM
82
STATE CHART DIAGRAM
83
CLASS CODE
84
public class client()
{
String user id
public password()
{
}
}
public class idAccount()

{
String id
String name
public create()
{
}
public login()
{
}
public idAccount()
{
}
}
public class website()

{
String address
String state
public website()
{
}
}
public class composer()

{
Byte mes
Byte text
Byte images
public edit()
{
}
public send()
85
{
}
public composer()
{
}
}
public class checkmail()

{
String readReply
public check()
{
}
public delete()
{
}
}
RESULT:-
Thus the UML models for the Email Client System have been developed and verified.
86

CS1402 OOADLab Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS1402 OOADLab Manual

Uploaded by

Copyright:

Available Formats

OBJECT ORIENTED ANALYSIS AND DESIGN

RECOD NOTE BOOK

DEPARTMENT OF INFORMATION TECHNOLOGY

NAME:……………………………… REGISTER No:……………………..

YEAR:…………… SEM:…………….. SUBJECT :………………………….

NAME : …………………………. REGISTER NO ……………..

BRANCH : ……………………………. CLASS ……….………..

This is certified to be the bonafide record of work done

Head of the Department Staff-In-Charge

SUBMITTED FOR PRACTICAL EXAMINATION HELD ON ….…………

Internal Examiner External Examiner

S.NO DATE TOPIC P.NO SIGN

3. Online Purchase System

4. Library Management System

6. Course Registration System

8. Student Marks Analyzing System

9. Email Client System

Bank Account Person

Bus Truck Car

Object 1 1. <Event> Object 2

Identifying the Actors

Identifying the Use Cases

: CardReader : ATMScreen : Account : CashDispenser

public void acceptCard()

public void openAccount()

public void promptforPIN()

public void verifyPIN(int val )

public void promtforAmount()

public void w ithdraw ()

public void verifyAmt()

public void deductAmt()

public void provideCash()

public void provideRept()

public v oid enterPin() public v oid enterA mt()

public v oid s elec tTrans ac tion()

public v oid ac c eptCard()

public v oid w ithdraw ()

public v oid c hec kBalac ne()

public v oid readCard()

public v oid deduc tA mt()

public v oid ejec tCard()

public boolean authoriz ePin()

: C ard R ead er : Acco u n t

private int Cardno

public class ATMScreen()

private int accno

Identifying the Actors

C ustomer Re que st Ite m

Ask for P a ym e nt &

public void displaycatalog()

public void getCreditRating()

public void setCreditCard()

public void shipmentDetails()

public void authorizedCharge()

public void authorize()

public void setCrediting(int val )

public void setAddrToShip()

public void deleverItem()

public void removeOrder()

public void setAddrToShip()

public void deleverItem()

public void getAddrToShop()