casetools lab material
TRANSCRIPT
-
8/10/2019 Casetools Lab Material
1/70
EXP NO. ONLINE TICKET RESERVATION SYSTEM
DATE:
AIM:
To Study and draw the UML diagram for online Ticket Reservation System
Using rational rose software.
ABSTRACT:
The Objective of this roject is to develo an alication which can rovide the detailed
reorts and easier way to reserve booking online by assenger. The reort will contain the
location details for the journey! fare descrition! etc.! "t is clearly a client server system. "t is an
online system to indicate details about ticket and assenger details.
The main aim of the roject is to reduce the burden of the assenger for waiting in the long
#ueue in railway station. "n addition to which the railway station system database are
automatically udated as and when new entries are booked. This allows Scheduling reservations!
waiting list! $ancellation of tickets etc.!
The reort details contain assenger details and train details . %assenger details may contain
name! age! &umber of ersons etc.! Train details may contain attributes of a train! train number!time! cash details and tye to reservation.
The front end used is 'isual (asic and the back end used is MS )cess. *ere MS )cess acts as
the database to store the data and will give all the information when ever re#uired.
+henever a new assenger reserves a ticket! a ticket is reared for his,her based uon the fare
and the ersonal details of the customer. The udation can be made easily as comared to that of
reorts maintained manually. -inally! the reared bill is handed over to the customer.
-
8/10/2019 Casetools Lab Material
2/70
USE CASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
3/70
ACTIVITY DIAGRAM:
FOR LOGIN:
FOR INFORMATION:
-
8/10/2019 Casetools Lab Material
4/70
FOR DATABASE:
FOR BILLING:
-
8/10/2019 Casetools Lab Material
5/70
FOR TICKET:
CLASS DIAGRAM:
FOR LOGIN:
-
8/10/2019 Casetools Lab Material
6/70
FOR INFORMATION:
FOR DATABASE:
-
8/10/2019 Casetools Lab Material
7/70
FOR BILLING:
FOR TICKET:
-
8/10/2019 Casetools Lab Material
8/70
SEQUENCE D IAGRAM:
FOR LOGIN:
FOR INFORMATION:
-
8/10/2019 Casetools Lab Material
9/70
FOR DATABASE:
FOR BILLING:
-
8/10/2019 Casetools Lab Material
10/70
FOR TICKET:
OUTPUT:
UML to Java V5.
!"#$%&&$a''Loginform ()t(*+'Login$ontroller
!"#$%&String get&ame/0
,, begin1user1code
,(t",*name2,, end1user1code
3
!"#$%&vo%+set&ame/String the&ame0
,, begin1user1codename 4 the&ame2
,, end1user1code
3
!,%vat(String wd2
-
8/10/2019 Casetools Lab Material
11/70
!"#$%&String get%wd/0
,, begin1user1code
,(t",*wd2
,, end1user1code
3
!"#$%&vo%+set%wd/String the%wd0 ,, begin1user1code
wd 4 the%wd2
,, end1user1code
3
!"#$%&vo%+)ccet/0
,, begin1user1code,, TODO)uto1generated method stub
,, end1user1code
3
!"#$%&vo%+Reject/0
,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code
3
ublic class Login$ontroller e5tends db6
rivate String &ame2
ublic String get&ame/0 ,, begin1user1code
return &ame2
,, end1user1code3
!"#$%&vo%+7nter/0
,, begin1user1code
,, TODO)uto1generated method stub
-
8/10/2019 Casetools Lab Material
12/70
,, end1user1code
33
!"#$%&&$a''Ticket-orm ()t(*+'Ticket$ontroller
!,%vat(String&ame2
!"#$%&String get&ame/0
,, begin1user1code
,(t",*&ame2,, end1user1code
3
!"#$%&vo%+set&ame/String the&ame0
,, begin1user1code&ame4 the&ame2
,, end1user1code
3
!,%vat("nteger Seat&o2
!"#$%&"nteger getSeat&o/0
,, begin1user1code
,(t",*Seat&o2,, end1user1code
3
!"#$%&vo%+setSeat&o/"nteger theSeat&o0
,, begin1user1codeSeat&o4 theSeat&o2
,, end1user1code
3
!"#$%&vo%+7nter8etails/0
,, begin1user1code
-
8/10/2019 Casetools Lab Material
13/70
,, TODO)uto1generated method stub
,, end1user1code3
3
!"#$%&&$a''Ticket$ontroller ()t(*+'8(
!,%vat(String Tname2
!"#$%&String getTname/0
,, begin1user1code
,(t",*Tname2,, end1user1code
3
!"#$%&vo%+rint/0 ,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code
3
3
RESULT:
Thus the analysis design activity for Online Ticket Reservation System is comleted
Successfully.
-
8/10/2019 Casetools Lab Material
14/70
-
8/10/2019 Casetools Lab Material
15/70
USECASE DIAGRAM:
ACTIVITY DIAGRAM:
FOR LOGIN:
-
8/10/2019 Casetools Lab Material
16/70
FOR MEDICINAL INFORMATION:
FOR PREFER MEDICINE:
-
8/10/2019 Casetools Lab Material
17/70
FOR RETRIEVE INFORMATION;
CLASS DIAGRAM:
FOR LOGIN:
FOR MEDICAL INFORMATION:
-
8/10/2019 Casetools Lab Material
18/70
FOR PREFER MEDICINE:
FOR UPDATE:
FOR RETRIEVE INFORMATION:
-
8/10/2019 Casetools Lab Material
19/70
SEQUENCE DIAGRAM:
FOR LOGIN:
FOR MEDICINAL INFORMATION:
-
8/10/2019 Casetools Lab Material
20/70
FOR PREFER MEDICINE:
FOR RETRIEVE INFORMATION:
-
8/10/2019 Casetools Lab Material
21/70
FOR UPDATE:
RESULT:
Thus the analysis and detail activity for 75ert System is $omleted Successfully.
-
8/10/2019 Casetools Lab Material
22/70
E)! No. QUI- SYSTEM
Dat(:
AIM:
To Study and draw the UML diagram for
-
8/10/2019 Casetools Lab Material
23/70
USE CASE DIAGRAM:
ACTIVITY DIAGRAM:
CLASS DIAGRAMS:
-
8/10/2019 Casetools Lab Material
24/70
SEQUENCE DIAGRAM:
OUTPUT:
UML to Java V5.
-
8/10/2019 Casetools Lab Material
25/70
!"#$%&&$a''#ui="nterviewer
!,%vat(Object teamname2
!"#$%&Object getTeamname/0
,, begin1user1code
,(t",*teamname2
,, end1user1code
3
!"#$%&vo%+setTeamname/Object theTeamname0
,, begin1user1codeteamname 4 theTeamname2
,, end1user1code
3
!,%vat(Object time2
!"#$%&Object getTime/0
,, begin1user1code
,(t",*time2
,, end1user1code
3
!"#$%&vo%+setTime/Object theTime0 ,, begin1user1code
time 4 theTime2
,, end1user1code3
!,%vat(Object rounds2
!"#$%&Object getRounds/0 ,, begin1user1code
,(t",*rounds2
,, end1user1code3
-
8/10/2019 Casetools Lab Material
26/70
!"#$%&vo%+setRounds/Object theRounds0
,, begin1user1code
rounds 4 theRounds2,, end1user1code
3
!,%vat(#ui=articiant #ui=articiant2
!"#$%ui=articiant get
-
8/10/2019 Casetools Lab Material
27/70
Dat(:
AIM:
To Study and draw the UML 8iagrams for )TM System using Rational Rose Software.
ABSTRACT:
The Objective of this roject is to develo an alication which can rovide user fast access
to their account. "n this System the user can deosit,withdraw money from their account
whenever necessary. This System can be used by the customer ?@AB! thus making the work much
easier.
This System starts when the user enter a card. The assword is then asked by the system and is
verified. "f the assword is correct! the user is granted access to the System. The user selects the
transaction tye.
"f the transaction tye is 8eosit! the entered money is added to the account of the user. "f the
transaction tye is withdraw! the entered money is deducted from the user account. (efore
udation! the transaction is aroved by the )TM System.
The front end used is 'isual (asic and the back end used is MS )ccess. *ere MS )ccess acts
as the database to store the data and will give all the information whenever re#uired.
Since this system is an online system! thus it rovides a user friendly environment and makes
the user work easier and simler.
USESCASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
28/70
ACTIVITY DIAGRAM:
FOR LOGIN:
FOR SELECT TRANSACTION TYPE:
-
8/10/2019 Casetools Lab Material
29/70
FOR SAVING TRANSACTION ISTORY:
FOR DEPOSIT AMOUNT:
-
8/10/2019 Casetools Lab Material
30/70
FOR /ITDRA/ AMOUNT:
FOR APPROVAL PROCESS:
FOR ATM SYSTEM:
-
8/10/2019 Casetools Lab Material
31/70
FOR SELECT TRANSACTION TYPE:
FOR SAVING TRANSACTION ISTORY:
FOR DEPOSIT AMOUNT:
-
8/10/2019 Casetools Lab Material
32/70
FOR /ITDRA/ ACCOUNT:
FOR APPROVAL PROCESS:
FOR ATM SYSTEM:
-
8/10/2019 Casetools Lab Material
33/70
SEQUENCE DIAGRAM:
FOR LOGIN:
FOR SELECT TRANSACTION TYPE:
-
8/10/2019 Casetools Lab Material
34/70
FOR SAVING TRANSACTION ISTORY:
FOR DEPOSIT AMOUNT:
-
8/10/2019 Casetools Lab Material
35/70
FOR /ITDRA/ AMOUNT:
FOR APPROVAL PROCESS:
-
8/10/2019 Casetools Lab Material
36/70
FOR ATM SYSTEM:
OUTPUT:
UML to Java V5.
!"#$%&&$a''Oeration ()t(*+'Login
-
8/10/2019 Casetools Lab Material
37/70
!,%vat(String "nsert$ard2
!"#$%&String get"nsert$ard/0
,, begin1user1code
,(t",*"nsert$ard2,, end1user1code
3
!"#$%&vo%+set"nsert$ard/String the"nsert$ard0
,, begin1user1code
"nsert$ard4 the"nsert$ard2
,, end1user1code3
!"#$%&vo%+Load/0
,, begin1user1code,, TODO)uto1generated method stub
,, end1user1code
3
!"#$%&vo%+)ccet/0 ,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code3
!"#$%&vo%+Reject/0
,, begin1user1code,, TODO)uto1generated method stub
,, end1user1code3
3
RESULT:
Thus! the analysis design activity for )TM System is comleted Successfully.
EX NO. PAYROLL SYSTEM
DATE:
-
8/10/2019 Casetools Lab Material
38/70
AIM:
To Study and draw the UML 8iagram for %ayroll System using Rational Rose
ABSTRACT:
The Objective of the roject is to relace the manual task involved in calculating the salary of
every emloyee. This System enhances the seed of calculation and makes it much easier to
maintain the details regarding every emloyee.
The System mainly rovides service to emloyee by automation to salary. The System
administrator handles the %ayroll System. The System also generates an overall reorts with the
emloyee details such as deartment!designation!etc.! The ayroll system designed enables the
users to just enter the emloyee id which enables them to retrieve data with much accuracy and
seed.
The front end used is 'isual (asic and the back end is MS )ccess. *ere MS )ccess acts as a
database to store the data and will give all the information whenever re#uired.
The maniulatation task becomes much easier in this system and hence the deletion and
udations are made with much ease. )lso information is collected from the end user so that it
satisfies the re#uirement of the end user better.
The emloyee salary is calculated as
GROSSPAY0BASIC PAY1ALLO/ANCES2DEDUCTIONS
)llowance include 8)!*R)!M)!S)!etc.!
8eductions include C%-!-(-!S%-!*andloom!*ealth -und!L"$ etc.!
USECASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
39/70
ACTIVITY DIAGRAMS:
FOR LOGIN:
FOR CALCULATE SALARY;
-
8/10/2019 Casetools Lab Material
40/70
FOR SALARY:
FOR EMPLOYEE INFORMATION:
-
8/10/2019 Casetools Lab Material
41/70
FOR ALLO/ANCES:
FOR DEDUCTIONS:
CLASS DIAGRAMS:
-
8/10/2019 Casetools Lab Material
42/70
FOR LOGIN:
FOR CALCULATE SALARY:
FOR SALARY:
-
8/10/2019 Casetools Lab Material
43/70
FOR EMPLOYEE INFORMATION:
FOR ALLO/ANCES:
-
8/10/2019 Casetools Lab Material
44/70
FOR DEDUCTIONS:
SEQUENCE DIAGRAM:
FOR LOGIN:
FOR CALCULATE SALARY:
-
8/10/2019 Casetools Lab Material
45/70
FOR SALARY:
FOR EMPLOYEE INFORMATION:
-
8/10/2019 Casetools Lab Material
46/70
FOR ALLO/ANCE:
-
8/10/2019 Casetools Lab Material
47/70
FOR DEDUCTION:
OUTPUT:
UML to Java V5.
ublic class LOC"&-ORM e5tends LOC"&$O&TROLL7R
rivate String &ame2
ublic String get&ame/0
,, begin1user1code
return &ame2
,, end1user1code3
ublic void set&ame/String the&ame0 ,, begin1user1code
&ame 4 the&ame2
,, end1user1code3
-
8/10/2019 Casetools Lab Material
48/70
rivate String %wd2
ublic String get%wd/0
,, begin1user1code
return %wd2
,, end1user1code3
ublic void set%wd/String the%wd0
,, begin1user1code
%wd 4 the%wd2,, end1user1code
3
ublic void )ccet/0
,, begin1user1code,, TO8O )uto1generated method stub
,, end1user1code
3
ublic void Reject/0
,, begin1user1code,, TO8O )uto1generated method stub
,, end1user1code3
3
RESULT:
Thus the analysis design activity for %ayroll System is $omleted Successfully.
E)! No. STOCK MAINTAINANCE
Dat(:
-
8/10/2019 Casetools Lab Material
49/70
AIM:
To study and draw the UML diagram for Stock Maintenance System using Rational Rose
Software.
ABSTRACT:
The Objective of the roject is to relace the manual task involved in maintaining the record
of the store. This system enhances the seed of maintaining the details regarding every material.
The urose of the system is to manage the materials used by an organi=ation. +henever a
material is urchased by an organi=ation! it has to be registered in the system.
Suosed a demand of a articular item is raised! it is checked in the store. "f available it is
issued to the resective authority and necessary udating rocess is carried out in the log to kee
track of the material. "f unavailable! then item is urchased and it is added in the log. )fter that
the item is issued to the demanding )uthority.
The front end used in visual(aisc and the back end used is Ms)cess. *ere Ms acess )cts as the
database to store dataand will give all the information whenever re#uired.
The maniulation task becomes much easier in this system and in this system and hence the
detection and udation are made with ease.
USE CASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
50/70
ACTIVITY DIAGRAM:
FOR LOGIN:
FOR CECK:
-
8/10/2019 Casetools Lab Material
51/70
FOR DEMAND:
FOR ISSUE:
FOR PURCASE
CLASS DIAGRAMS:
Fo, Lo3%*:
-
8/10/2019 Casetools Lab Material
52/70
Fo, C4(&:
Fo, D(6a*+:
Fo, I''"(:
Fo, P",&4a'(:
-
8/10/2019 Casetools Lab Material
53/70
SEQUENCE DIAGRAM:
FOR LOGIN:
FOR CECK:
FOR DEMAND:
-
8/10/2019 Casetools Lab Material
54/70
FOR ISSUE:
-
8/10/2019 Casetools Lab Material
55/70
-OR %UR$*)S7;
OUTPUT:
UML to Java V5.
!"#$%&&$a''Login-orm ()t(*+'Login$ontroller
!,%vat(String&ame2
!"#$%&String get&ame/0
,, begin1user1code
,(t",*&ame2
,, end1user1code3
!"#$%&vo%+set&ame/String the&ame0
,, begin1user1code&ame4 the&ame2
-
8/10/2019 Casetools Lab Material
56/70
,, end1user1code
3
!,%vat(String %wd2
!"#$%&String get%wd/0
,, begin1user1code
,(t",*%wd2
,, end1user1code
3
!"#$%&vo%+set%wd/String the%wd0
,, begin1user1code
%wd4 the%wd2,, end1user1code
3
!"#$%&vo%+)ccet/0 ,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code3
!"#$%&vo%+Reject/0
,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code
3
3
RESULT:
Thus! the analysis design activity for Stack Maintenance System is comleted
successfully.
E)! No.: COURSE REGISTRATION SYSTEM
Dat(:
-
8/10/2019 Casetools Lab Material
57/70
AIM:
To Study and draw the UML diagrams for $ourse Registration System Using Rational Rose
System.
ABSTRACT:
The objective of this roject is to develo an online alication which contains
detailed reort of various activities of an institution. The $ourse Registration
System contains the details about the various courses offered by the institution.
) user who log into the system can register to the course and before registering
he can view the academic records! which slows the revious academic
erformance of the college.
This is the online system which manages the different course details offered by
the institution. This system has to be regularly udated so as to kee track of the
institution activity.
The front end used 'isual (asic and the back end used MS )cess. *ere MS
)ccess acts as the database to store the data and will give all the information when
ever re#uired.
The udation rocess is simle as it doesnDt involve any manual tasks. The
whole system is managed by the administrator. )ny student wish to join a course
can register online.
USECASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
58/70
ACTIVITY DIAGRAMS:
FOR LOGIN:
FOR ACADEMIC DETAILS:
-
8/10/2019 Casetools Lab Material
59/70
FOR COURSE DETAILS:
FOR REGISTER:
-
8/10/2019 Casetools Lab Material
60/70
CLASS DIAGRAM:
FOR LOGIN:
FOR ACADEMIC DETAILS:
-
8/10/2019 Casetools Lab Material
61/70
FOR COURSE DETAIL:
FOR REGISTER:
SEQUENCE DIAGRAM:
FOR LOGIN:
-
8/10/2019 Casetools Lab Material
62/70
FOR ACADEMIC DETAIL:
FOR COURSE DETAIL:
-
8/10/2019 Casetools Lab Material
63/70
FOR REGISTER:
OUTPUT:
UML to Java V5.
-
8/10/2019 Casetools Lab Material
64/70
!"#$%&&$a''Loginform ()t(*+'Login$ontroller
!,%vat(String&ame2
!"#$%&String get&ame/0
,, begin1user1code
,(t",*&ame2,, end1user1code
3
!"#$%&vo%+set&ame/String the&ame0 ,, begin1user1code
&ame4 the&ame2
,, end1user1code3
!,%vat(String %wd2
!"#$%&String get%wd/0
,, begin1user1code
,(t",*%wd2,, end1user1code
3
!"#$%&vo%+set%wd/String the%wd0
,, begin1user1code
%wd4 the%wd2,, end1user1code
3
!"#$%&vo%+)ccet/0 ,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code
3
!"#$%&vo%+Reject/0 ,, begin1user1code
,, TODO)uto1generated method stub
,, end1user1code
3
3
-
8/10/2019 Casetools Lab Material
65/70
!"#$%&&$a''Login$ontroller
!,%vat(String&ame2
!"#$%&String get&ame/0
,, begin1user1code,(t",*&ame2
,, end1user1code
3
!"#$%&vo%+set&ame/String the&ame0
,, begin1user1code
&ame4 the&ame2,, end1user1code
3
!,%vat(String %wd2
!"#$%&String get%wd/0 ,, begin1user1code
,(t",*%wd2
,, end1user1code3
!"#$%&vo%+set%wd/String the%wd0
,, begin1user1code%wd4 the%wd2
,, end1user1code
3
!"#$%&vo%+'erify/0
,, begin1user1code,, TODO)uto1generated method stub
,, end1user1code
33
RESULT:
Thus the analysis design activity for $ourse Registration System is $omleted Successfully.
E)!.No.: STUDENT MARK ANALYSIS
Dat(:
-
8/10/2019 Casetools Lab Material
66/70
AIM
To study and draw the UML diagram for student Mark analysis system using rational rose
software.
ABSTRACT:
The Objective of this roject is to develo an alication which can rovide the detailed
reort of all students in an institution. The reort will contain the marks of all students in an
institution. The reort will contain the marks of all students and according to the marks! the
ercentage is calculated.The result /either ass or fail0 will be dislayed on the basis of
ercentage obtained by the student.
The main aim of the roject is to dislay the marks of the student 9 the result of the student as
ass or fail. +hen a student gets out of the education institution that student record should be
deleted and when the student joins in an institution the record will be added to the database.
The student can serve the alication to verify the marks but they cannot edit the details. "n
simler sense they donDt have any access to the database.
The front end used is 'isual (asic and the back end used is MS )ccess . *ere MS )ccess acts
as the database to store the data and will give all the information whenever re#uired.
The student mark anlaysis system will give all the records of student marks along with eachstudent details. The database can be udated whenever re#uired.
USECASE DIAGRAM:
-
8/10/2019 Casetools Lab Material
67/70
ACTIVITY DIAGRAMS:
CLASS DIAGRAM:
-
8/10/2019 Casetools Lab Material
68/70
SEQUENCE DIAGRAM:
OUTPUT:
UML to Java V5.
-
8/10/2019 Casetools Lab Material
69/70
ublic class student
rivate Object name2
ublic Object get&ame/0
,, begin1user1code
return name2
,, end1user1code
3
ublic void set&ame/Object the&ame0
,, begin1user1code
name 4 the&ame2
,, end1user1code
3
rivate Object collegecode2
ublic Object get$ollegecode/0
,, begin1user1code
return collegecode2
,, end1user1code
3ublic void set$ollegecode/Object the$ollegecode0
,, begin1user1code
collegecode 4 the$ollegecode2
,, end1user1code
3
rivate Object regno2
ublic Object getRegno/0
-
8/10/2019 Casetools Lab Material
70/70
,, begin1user1code
return regno2
,, end1user1code
3
ublic void setRegno/Object theRegno0
,, begin1user1code
regno 4 theRegno2
,, end1user1code
3
ublic void dislayresult/0
,, begin1user1code
,, TO8O )uto1generated method stub
,, end1user1code
3
3
RESULT:
Thus the analysis design activity for Student Marks )nalysing System is $omleted
Successfully.