Sunteți pe pagina 1din 169

EX NO:

DATE:
EXPERT SYSTEMS
AIM
To analyze, design and develop code for Expert system using Rational
Rose software.

PROJECT SCOPE
The main scope of the project is to develop a system which effectively
manages the purchase and selling of an item and update them regularly
through the authenticated users.

OBJECTIVE
The main objective of developing and designing a Expert system is to
enable the administrator or any other authenticated person to record, view or
upgrade the purchased and sold items in the Database. This system is specially
meant to keep the records of items that have purchased from supplier and the
sold items to the customer.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor: Pentium IV
 Hard disk: 40 GB(min)
 Ram: 256 MB(min)

SOFTWARE REQUIREMENTS
 Rational Rose software
EXPERT SYSTEMS

ABSTRACT

The Expert Systems is very important because of its common usage


in most of the Shops, Pharmacies and even in Hospitals. It proves to be
the commonest system as it finds its application in almost all the organizations
irrespective of its strength and location. The maintenance of this system
proves to be challenging as it has many cases to concern.
In the existing system all the processing are done manually. These
systems will have to maintain the data in a hard file. While searching any data
it is too difficult to find those.
Maintaining too many data about products in separate files are too
complicated. Similarly, it is too difficult to maintain the data for each and
every activity. So, the time utilization will be more for this manual system. In
order to overcome these problems we have to propose the system which
overcomes the problem of the existing method.
The developed system would perform all the functions of the manual
system. Using this system we can save time and the operations will be
performed with ease comparatively.
MODULAR DESCRIPTION

PASSWORD MODULE
This module enables the authenticated users to login for purchasing or
selling of an item. This is the most important module because it is the
protection for the records which is made updated day to day. In this module
after giving the username and password should choose whether he/she is
selling or purchasing the item.

PURCHASING ITEM MODULE


This module enables us to purchase an item. For that we have to enter
the item to be purchased. Then if the user has to add an item, the concern
item is added to item list, if it is not view the report. This is the purchase
module.

SELLING ITEM MODULE


This module enables to sell an item. For that the user has to enter the
item to be sold, if there is any items to be sold remove the items from the
Database. If it is not back to the items check whether any other item to be
sold. This is the selling of an item module.
USECASE DIAGRAM FOR
[EXPERT SYSTEMS]

Username SellingItem

Login

Password PurchaseItem
ACTIVITY DIAGRAMS FOR
[PURCHASE MODULE]

Enter username and


password

Check username
and password

Login

Purchase Item Selling Item


ACTIVITY DIAGRAM FOR
[PURCHASING ITEM]

Enter the
purchase item

Item

Yes
Add Item

No

View Report
ACTIVITY DIAGRAM FOR
[SELLING ITEM]

Enter the selling


Item

Items

No
Sold Item

Yes

Remove item from


DB
CLASS DIAGRAM FOR
[EXPERT SYSTEMS]

Purchase Item3
nameofitem
quantityofitem
costperitem
totalcost

add_item()
Login Detail
selling_item()
username
password

Login()
Cancel() selling item3
nameofcustomer
address
noofitem
totalcost

nextitem()
ok()
SEQUENCE DIAGRAM FOR
[PURCHASING ITEM]

Purchase item DB Control

User

Login

Add data
Put data in DB
COLLABRATION DIAGRAM FOR
[PURCHASING ITEM]

3: Put data in DB

User DB Control

2: Add data
1: Login

Purchase item
SEQUENCE DIAGRAM FOR
[SELLING ITEM]

S elling detail DB c ontrol

Login

S elling Item s
Rem ove item from DB
COLLABRATION DIAGRAM FOR
[SELLING ITEM]

3: Remove item from DB

DB control

2: Selling Items

1: Login

Selling detail
COMPONENT DIAGRAM FOR
[EXPERT SYSTEMS]

<<stand and EXE>>

EXPERT SYSTEMS
CODING:
PASSWORD MODULE

#ifndef Login_Detail_h
#define Login_Detail_h 1

//##ModelId=48933F3B034B
class Login_Detail
{
public:

//##ModelId=48933F550109
void Login ();

//##ModelId=48933F58032C
void Cancel ();

private:

//##ModelId=48933F480167
char username;

//##ModelId=48933F4E0119
char password;

};

#endif
PURCHASING MODULE:

#ifndef Purchase_Item3_h
#define Purchase_Item3_h 1

//##ModelId=48933F5F0167
class Purchase_Item3
{
public:

//##ModelId=48933F8F002E
void add_item ();

//##ModelId=48933F9602CE
void selling_item ();

private:

//##ModelId=48933F6A0242
char nameofitem;

//##ModelId=48933F74006D
int quantityofitem;

//##ModelId=48933F7C02BF
float costperitem;

//##ModelId=48933F8901B5
float totalcost;

};

#endif
SELLING MODULE:

#ifndef selling_item3_h
#define selling_item3_h 1

//##ModelId=48933FA50232
class selling_item3
{
public:

//##ModelId=48933FE10119
void nextitem ();

//##ModelId=48933FE70000
void ok ();

private:

//##ModelId=48933FBA0242
char nameofcustomer;

//##ModelId=48933FCA0138
string address;

//##ModelId=48933FCF036B
int noofitem;

//##ModelId=48933FD70186
float totalcost;

};

#endif
RESULT:
Thus the “EXPERT SYSTEM” is done using Rational Rose Software
and code generated by ANSI C++.
EXP NO:
DATE:
REALTIME SCHEDULER

AIM:
To analyze, design and envelope code for Real-Time Scheduler using
Rational Rose software.

PROJECT SCOPE
The scope is to introduce a Real-Time Scheduler system for the
convenience of the passenger. This system helps the passenger to find the
platform for their concern Departure train.

OBJECTIVE
Platform assignment system for the trains in railway system reduces the
complexity maintaining and updating the platform for different trains in
same platform. The passengers can easily trains details in the system the
updating of platform assignment are also done automatically. The
platform assignment system is also provided with passengers to see train
details through online.
INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor(256 MHz),Pentium sequels
 RAM (256 MB)
SOFTWARE REQUIREMENTS
 Rational Rose software
REALTIME SCHEDULER

ABSTRACT

The Real-Time Scheduler system for the assignment of the platform is


very important for the railways and also it is useful for the passengers too. It
proves to be the valuable application for the railways. The maintenance of this
system proves to be challenging as it has many cases to concern.
In the existing system all the processing are done manually. These
systems will have to maintain the data in a hard file. While searching any data
it is too difficult to find those.
The time utilization will be more for this manual system. In order to
overcome these problems we have to propose the system which overcomes the
problem of the existing method. This existing method which is developed will
take less time and also the detail gets updated automatically.
We have proposed a system that would modernize the activities of the
Real-Time Scheduler for Platform assignment system. The developed system
would perform all the functions of the manual system. Using this system we
can save time and the operations will be performed with ease comparatively.
MODULAR DESCRIPTION

MAIN MODULE
This module acts as a gateway for the other modules present in
project through this module the user can move into various other
modules. This provides various options such as train list, platform-I,
platform-II, add Trains, ECT...

TRAINLIST
This module enables user to assign the platform in different trains.
This module gives details such as train name, arrival time, leaving time,
source, destination, platform no, date.

PLATFORM-I
This module helps the user to know about the current platform
train details. The modules are updated every time when trains are
added. This provides the individual details about the each trains and
class.

PLATFORM-II
This module helps the user to know about the current platform
train details. These modules are updated every time when trains are
added. This provides the individual details about the each trains and
class.
PLATFORM-III
This module helps the user to know about the current platform
train details. These modules are updated every time when trains are
added. This provides the individual details about the each trains and
class.

PLATFORM-IV
This module helps the user to know about the current platform
train details. These modules are updated every time when trains are
added. This provides the individual details about the each trains and
class.

ADD TRAIN DETAILS


This module helps to add the information about the train details in
the list. This information helps the passengers for their easy verification.
USE CASE DIAGRAM FOR
[REAL-TIME SCHEDULER]

PLATFORM 1

PLATFORM 2

PASSENGER

PLATFORM 3

PALTFORM 4
ACTIVITY DIAGRAM FOR [REAL-TIME SCHEDULER]

start

ENTER TNAME,SOURCE,DESTINATION,TIME OF
ARRIVAL AND LEAVING

PLATFORM
LIST

YES NO
CHECK
PLATFORM 1

PLATFORM 1 CHECK
PLATFORM 2
YESS NO

CHECK
PLATFORM 2
PLATFORM 3
YES
NO

PLATFORM 3 PLATFORM 4
CLASS DIAGRAM FOR
[REAL-TIME SCHEDULER]

PLATFORM 1
TRAIN LIST TNAME
TNAME SOURCE
SOURCE DESTINATION
DESTINATION ARRIVAL TIME
ARRIVAL TIME LEAVING TIME
LEAVING TIME
PLATFORM ADD TRAIN()
SET ARRIVAL()
PLAT_ASSIGNMENT()
PLATFORM 2
TNAME
SOURCE
DESTINATION
ARRIVAL TIME
LEAVING TIME

ADD TRAIN()
SET INTERVAL()

PLATFORM 3
PLATFORM 4 TNAME
TNAME SOURCE
SOURCE DESTINATION
DESTINATION ARRIVAL TIME
ARRIVAL TIME LEAVING TIME
LEAVING TIME
ADD TRAIN()
ADD TRAIN() SET INTERVAL()
SET INTERVAL()
SEQUENCE DIAGRAM FOR
[REAL-TIME SCHEDULER]

TRA IN LIS T DA TA B A S E P LA TF O R M
: P AS SE NGE R

G E T THE TRA IN DE TA IL

A DD DA TA TO DB

A S S IG N TRA IN TO P LA TF O R M
COLLOBRATION DIAGRAM FOR
[REAL-TIME SCHEDULER]

1: GET THE TRAIN DETAIL


TRAIN
LIST

: PASSENGER

2: ADD DATA TO DB

3: ASSIGN TRAIN TO PLATFORM


DATABA PLATFO
SE RM
COMPONENT DIAGRAM FOR
[REAL-TIME SCHEDULER]

< < s ta n d a n d E XE > >


R E AL TIME
SCHED ULER
CODING:

TRAIN LIST

//##ModelId=48B65ACA0148
TRAIN LIST::PLAT_ASSIGNMENT ()
{

PLATFORM 1

//##ModelId=48B65AF400AB
PLATFORM 1::ADD TRAIN ()
{
}

//##ModelId=48B65AF802DE
PLATFORM 1::SET ARRIVAL ()
{
}

PLATFORM 2

//##ModelId=48B65B5E033C
PLATFORM 2::ADD TRAIN ()
{
}
//##ModelId=48B65B630251
PLATFORM 2::SET INTERVAL ()
{
}

PLATFORM 3

//##ModelId=48B65B900203
PLATFORM 3::ADD TRAIN ()
{
}

//##ModelId=48B65B9401F4
PLATFORM 3::SET INTERVAL ()
{
}

PLATFORM 4

//##ModelId=48B65BC60290
PLATFORM 4::ADD TRAIN ()
{
}

//##ModelId=48B65BC90280
PLATFORM 4::SET INTERVAL ()
{
}

RESULT
Thus the “REAL-TIME SCHEDULER” is done using Rational Rose
software and code generated by ANSI C++.
EX NO:
DATE:
REMOTE CALL IMPLEMENTATION
PROCEDURE

AIM:
To analyze, design and envelope code for Remote Call Implementation
procedure using Rational Rose software.

PROJECT SCOPE
The scope is to introduce a Remote Call Implementation Procedure
invocation system. It is used to execute the client and server process.

OBJECTIVE
The main objective of the Remote Call Implementation Procedure is to
give request from client to the server, and the server will response for the
request which is given by the client.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor(256 MHz),Pentium sequels
 RAM (256 MB)
SOFTWARE REQUIREMENTS
 Rational Rose software
REMOTE CALL IMPLEMENTATION
PROCEDURE

ABSTRACT:
Remote Call Implementation Procedure is a process in which include a
server and client. The process is taken place between the server and the client.
This process is known as Remote Call Implementation Procedure.
Generally to transfer some information from one desk to another desk
by manually, it requires files, place for storing it etc.
To overcome this remote call procedure is implemented. It takes place
with two commands request and response. Request is client to server and
response is from server to client.
In request module it contains the requisitions from client to transfer the
required information from the server.
In order to respond to this request the response module will respond to
the client whether it has the required files in it or not and whether the
transaction is possible or not. Then follow the corresponding transactions
required by the client
MODULAR DESCRIPTION

This process contains two modules they are as follows


 Request
 Response

REQUEST:
The request module tells us how the process takes place between the
Client and the Server. Request process is carried out from Client to the
Server. Client should request the Server first for the connection for further
process such that transferring of files and searching of the required files etc.

RESPONSE:
The response module tell us how the server responding to the Client’s
request. First it responds that whether the connection should be exist or not.
After that server will search for the files in it required by the Client and if it is
exist the Server will transfer the files to the client. Thus the response module
is defined
USECASE DIAGRAM FOR REMOTE
PROCEDURE CALL

REQUEST

CLIENT SERVER

RESPONSE
ACTIVITY DIAGRAM FOR REQUEST

user name

password

NO

IS PASSWORD
CORRECT

YES

give server
name

port number
NO

IS SERVER
CONNECTED
YES

searching for files

required files not YES transformation for transformation


found request files complete
NO
ACTIVITY DIAGRAM FOR REPONSE
get
grade

check allowance
no allowance error
message
yes
get
allowance

add
allowance

total incentive
profit

incentive for
respective grade

add
incentive

CLASS DIAGRAM FOR REMOTE PROCEDURE CALL


class request
class response
username
ip address
password
port no
server ip address
files
server port no
response()
sending_request()
connection searching()
connection()
transfer()
searching connection()

SEQUENCE DIAGRAM FOR REPONSE


server client files transfer

request for connection

searching file

server connected

file exist

request to transfer file

short transfering

connection aborted

SEQUENCE DIAGRAM FOR REQUEST


CLIENT USERNAME PASSWORD ADMIN IP ADDR PORT NO

USER NAME

PASSWORD

PASSWORD IS CORRECT

SERVER PORT NO

CLIENT REQUESTING FOR SERVER


COLLOBRATION DIAGRAM FOR REQUEST

CLIENT
USERN
AME

PASSW
ORD

5: CLIENT REQUESTING FOR SERVER

4: SERVER PORT NO
1: USER NAME

2: PASSWORD
3: PASSWORD IS CORRECT

PORT
NO

IP ADDR
ADMIN

COLLOBRATION DIAGRAM FOR REPONSE


6: FILE TRANSFERED
SERVE
R CLIENT

1: REQUEST FOR CONNECTION


4: FILE EXIST
7: CONNECTION ABORTED

5: START TRANSFERING
2: SERVER CONNECTED
3: SEARCHING FOR FILES

TRANSF
ER
FILES
COMPONENT DIAGRAM FOR REMOTE PROCEDURE CALL

REMOTE PROCEDURE CALL


SYSTEM

CODING:
RESPONSE DETAILS:
#include RESPONSE.h
//##ModelId=4C64D3010350
RESPONSE::RESPONSE()
{
}
//##ModelId=4C64D30701AA
RESPONSE::CONNECTION()
{
}
//##ModelId=4C64D30B00FE
RESPONSE::SEARCHING()
{
}
//##ModelId=4C64D30F0071
RESPONSE::TRANSFER()
{
}
//##ModelId=4C64D31300CF
RESPONSE::DISCONNECTION()
{
}

REQUEST:
#include REQUEST.h
//##ModelId=4C64D2C40333
REQUEST::SENDINGREQ()
{
}
//##ModelId=4C64D2CB0361
REQUEST::CONNETION()
{
}
//##ModelId=4C64D2D200D1
REQUEST::DISCONNECTION()
{
}
RESULT
Thus the “REMOTE CALL IMPLEMENTATION PROCEDURE”
Is done using Rational Rose Software and code generated by ANSI C++.

EX NO:
DATE:
ATM SYSTEM

AIM:
To analyze, design and envelope code for Automated Teller Machine
system using Rational Rose software.

PROJECT SCOPE
The main scope of the project is to perform the transactions and to
update our account balance using ATM machine systems.

OBJECTIVE
The main objective of designing and implementing an ATM system is to
enable the customer to have the easy transaction of money at any time without
standing or waiting in the queue.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor: Pentium IV
 Hard disk: 40 GB(min)
 Ram: 256 MB(min)

SOFTWARE REQUIREMENTS
 Rational Rose software

ATM SYSTEM
ABSTRACT
ATM stands for Automatic Teller Machine. It is nothing but immediate
aspect of getting money by using simple card.
User can simply insert ATM card into the ATM machine and follow the
simple instructions provided by the machine to get the required amount of
money from his/her own account. To protect their account from other users to
access, password is provided which is called as pin number and is provided
uniquely for each user. ATM machines acts as an excellent technical
development which provides money for those users who required money at
whatever time they required.
Various concepts that are taken care are
 Password Denied
 Re-enter Password
 Account number
 Withdrawal
 Balance
 Exit

MODULAR DESCRIPTION
VERIFICATION OF ATM CARD
For the verification of ATM card by the system, the user will enter the
secret code. The pin number or code number is verified with the database of
the customers. If the code exactly is matched with database of that of the
customers then transaction can be performed. If the code does not match with
the database of the customer then the user is required again to re-enter the
pin number of the access card and is continued further.

TRANSACTION
In this module, the necessary transaction to be performed by the user is
displayed as option by the system. The transaction options are withdrawal,
balance enquiry, mini statement, pin change. The users can withdraw the
amount from their account if the amount is available in their account. This
module helps the users to check their balance in their account through
balance enquiry and also they can get the mini statement for recent
transaction done over their account. This module allows the users to change
their pin number if they need.

DISPLAY AND RECEIPT


In this module, after the transaction process is performed by the user,
the system displays the balance amount available in the account and the
amount withdrawn by the user through receipt. The receipt will be provided
at the end of the transaction process.

USECASE DIAGRAM FOR


ATM

s es s io n

a dm ini s tra tor


us er

bank in g

pin c hang e pas s w ord

t ra ns actio n

m ini s tatem ent


en quiry dep os it w ithdrawl
rejec t

ACTIVITY DIAGRAM FOR ATM


[BALANCE ENQUIRY]

banking

enter the pin

is the pin valid no invalid pin

yes

balance enquiry

saving account current account

balance
checking chec king
balance

print the print the


balance balance

ACTIVITY DIAGRAM FOR ATM


[PIN CHANGE]

banking

enter the pin

no invalid pin
is pin valid

yes

pin change

enter the new


pin

reenter the new


pin

pin changed

ACTIVITY DIAGRAM FOR ATM


[CASH WITHDRAWAL]

customer
session

banking

Enter the pin

no invalid pin
is pin valid

yes

cash drawl

savings account current account

enter the enter amount


amount

transaction transaction
process

collect the cash collect cash

ACTIVITY DIAGRAM FOR ATM


[MINISTATEMENT]

banking

enter the pin

no invalid pin
is pin valid

yes

mini statement

saving account current account

last 15 days
transacxtion details

print the details

SEQUENCE DIAGRAM FOR


ATM

customer ATM administrator savings print receipt

insert card

pass word

pass word enter

verified

cash withdrawl

current

savings

savings

enter the amount transaction print

balance statement

COLLABRATION DIAGRAM FOR


ATM
1: insert card
3: pass word enter
5: cash withdrawl
8: savings
9: enter the amount ATM

custome
r 2: pass word

4: verified
6: current
10: transaction savings
7:

administ
12: balance statement rat or

savings 11: print

print
receipt

COMPONENT DIAGRAM FOR


ATM

<<Standard and exe>>

ATM

CODING:
WITHDRAWAL DETAILS:

#include WITH DRAWAL.h

//##ModelId=4C526357004F
WITH DRAWAL::WITH DRAW()
{
}
#ifndef WITHDRAWAL_H_INCLUDED_B3ADC91E
#define WITHDRAWAL_H_INCLUDED_B3ADC91E

//##ModelId=4C5262CA0072
class WITH DRAWAL
{
public:
//##ModelId=4C526357004F
WITH DRAW();

private:
//##ModelId=4C5263440272
INT ACC;

//##ModelId=4C52634A0011
INT CURRENT ACC;

//##ModelId=4C5263510253
INT SAVE;

};

#endif /* WITHDRAWAL_H_INCLUDED_B3ADC91E */

BALANCEENQUIRY DETAILS:

#include TRANSCATION.h

//##ModelId=4C5263BB032B
TRANSCATION::TRANSCATTION()
{
}
#ifndef TRANSCATION_H_INCLUDED_B3ADEAF2
#define TRANSCATION_H_INCLUDED_B3ADEAF2

//##ModelId=4C5262D1039F
class TRANSCATION
{
public:
//##ModelId=4C5263BB032B
TRANSCATTION();

private:
//##ModelId=4C5263AE02DD
INT DATA;

//##ModelId=4C5263B300E9
INT TRANS ID;

};

#endif /* TRANSCATION_H_INCLUDED_B3ADEAF2 */

MINISTATEMENT:

#include RECEIPT.h

//##ModelId=4C52632C037D
RECEIPT::BALANCE ENQUIRY::ENQUIRY()
{
}

//##ModelId=4C52637D0271
RECEIPT::RECEPIT()
{
}
RESULT
Thus the “ATM” is done using Rational Rose software and code
generated by ANSI C++.

EX NO:
DATE:
STOCK MAITENANCE SYSTEM

AIM:
To analyze, design and envelope code for Stock Maintenance system
using Rational Rose software.

PROJECT SCOPE
The main scope of the project is to provide a exhaustive, flexible and
reliable Stock Maintenance system which would be beneficial for both stock
manager and retailer.

OBJECTIVE
The main objective of designing and developing a Stock Maintenance
system is to provide with a system which proves to be manually beneficial i.e.,
it benefits both the Stock Manager and the retailer. The complete activities
and the process right from product’s manufacture till the product gets sold
out, every single activity is incorporated in this system.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor(256 MHz),Pentium sequels
 RAM (256 MB)
SOFTWARE REQUIREMENTS
 Rational Rose software
STOCK MAITENANCE SYSTEM

ABSTRACT:
The Stock Maintenance System is highly unique because of its
distinguished activities and behavior. It sounds to be different because of its
classified nature. It starts right from the manufacture of a product and its
covers up the entire life cycle till the product as purchased by the customer.
The maintenance of these stocks proves to be challenging as it has many cases
to concern
The special cases arise from this stock maintenance system such as
handling the damaged and expired stock are appropriately designed to match
the needs of the real world
In the existing system all the processing are done manually. These
systems will have to maintain the data in a hard file. While searching any data
it is too difficult to find those.
Maintaining too many data about produce in separate files are too
complicated. Similarly, it is too difficult to maintain data for each and every
activity. So, the time utilization will be more this manual system. In order to
overcome these problems we have to propose the system which overcomes the
problem of the existing method.
We have proposed a system that would modernize the activities of stock
maintenance system. The developed system would perform all the functions of
the manual system. Using this system we can save time and the operations will
be performed with ease comparatively.
MODULAR DESCRIPTION

PRODUCT & PURCHASE MODULE:


This module describes how to purchase a product after checking
expiry date. It also describes the quantity of the product to be purchased.
And also gives information about cost of the product. Here the code is
placed on the product for easy billing purposes. This is the product and
purchase module.

STOCK CHECK MODULE:


This module describes how to check the availability and unavailability
of stocks and to take appropriate actions. If there is nay demand any one of
the product immediately the product should be purchased from the dealer.
Inventory is taken for every month of the year. This is the stock check
module.
EXCESS & EXPIRED STOCK MODULE:
This module describes how to check the number of excess and expired
stocks and to make appropriate actions. If there is any expired product is
there it gets disposed or returns to the dealer. And if there is any excess
product it is also gets return back to the dealer or it is sold out in low price.
This is the excess and expired module.
USE CASE DIAGRAM FOR
[STOCK MAITENANCE SYSTEM]

product
(fro m Use C ase V ie w )

c us tom er
(fro m Use C ase V i e w )

product purc hes


(fro m Use C ase V ie w )

stock chec k
(fro m Use Ca se V ie w ) retailer
s tock m anager
(fro m Use C ase V ie w )
(fro m Use Ca se V ie w)

ex ces s & ex pired stock


(fro m Use Ca se V ie w )

dam aged stock


(fro m U se Ca se V i e w )
ACTIVITY DIAGRAM FOR STOCK MAINTENANCE
[PRODUCT AND PURCHASE]

start

enter product
code

errored result check


no availability

check MFD expired errored result2

enter count

buy product
ACTIVITY DIAGRAM FOR STOCK MAINTENANCE
[STOCK CHECK]

start

enter the
product code

don't buy the check stock


product
sufficient

insufficient

buy the product


ACTIVITY DIAGRAM FOR STOCK MAINTENANCE
[EXCESS AND EXPIRED]

start

enter product
code.

return expired check MFD.


stock

return excess check count


stock

display/report
CLASS DIAGRAM FOR
[STOCK MAITENANCE SYSTEM]

product
expire & excess stoc
amount product id
pro_avail pro_mfd
pro_count pro_count
id : product pro_id
pro_mfd
avail() check_mfd()
check count()
check_count()
check mfd()
SEQUENCE DIAGRAM FOR
[STOCK MAITENANCE SYSTEM]

s to c k m a n a ge r c h e c k p ro d uc t ret ailer e n ter p rod u c t c h ec k c o unt c hec k M FD b uy p rod u c t ret urn e x c e


c us to m e r ex p ired s t
availa b ility c ode

p ro d u c t
ex c ess

a vailab le

prod u c t c o d e n o o f p ro d uc t a va il
e x p ired

c h e c k pro d u c t

u n ava ila ble

e x p ired

n o t en ou g h

a vaila b le
COLLABRATION DIAGRAM FOR
[STOCK MAITENANCE SYSTEM]

return excess or
expired stock

5:
8: expired check
buy MFD
product
12:
3:

11:

2: excess
enter product
code retailer

check 7: no of product avail


count 10: check product
9: 16:

15: not enough


13: unavailable
17: available
custome
r
check product 6: product code
availability 14: expired

1: product
4: available

stock
manager
COMPONENT DIAGRAM FOR
[STOCK MAINTENANCE]

<<s ta n d a n d e xe >>
s to ck m a in ta n e n cce
CODING:
EXPIRED OR EXCESS STOCK.cpp

#include expired or excess.h


Expired or excess stock::check MFD()
{
}
Expired or excess stock::check count()
{
}

EXPIRED OR EXCESS STOCK.h

#indefEXPIREDOREXCESSSTOCK_H_INCLUDED_B5A22
#define EXPIREDOREXCESSSTOCK_H_INCLUDED_B5A22C99
Class expired or excess stock
{
Public:
Check MFD();
Check count();
Private:
Pro_MFD;
Pro_count;
Product id;
};
#endif

STOCK CHECK.cpp

#include stockcheck.h
Stockcheck::check avail()
{
}
STOCKCHECK.h

#indefSTOCKCHECK_H_INCLUDED_B5A22
#defineSTOCKCHECK_H_INCLUDED_B5A22C99
Class stock check
{
Public:
Check avail();
Private:
Product id;
}’
#endif

PRODUCTPURCHASE.cpp

#include productpurchase.h
Product purchase ::check count()
{
}
Product purchase::check MFD()
{
}

PRODUCTPURCHASE.h

#indefPRODUCTPURCHASE_H_INCLUDED_B5A22
#definePRODUCTPURCHASE_H_INCLUDED_B5A22C99
Class product purchase
{
Public:
Check count();
Check MFD();
Private:
Product id;
Pro_avail;
Pro_count;
Pro_MFD;
};
#endif
RESULT:
Thus the “STOCK MAINTENANCE SYSTEM” is done using Rational
Rose Software and the is code generated by ANSI C++ .
EX NO:
DATE:

ONLINE RESERVATION SYSTEM

AIM:
To analyze, design and envelope code for Online Reservation System using
Rational Rose software.

PROJECT SCOPE:
The main scope of the project is to perform the reservation, modifications
and cancellations for train tickets with ease.

OBJECTIVE:
The main objective of designing and developing an Online Reservation
system is to make the reservation and other related processes of this system more
flexible and easier for the end users and without waiting in the long queue for the
above mentioned processes.

INFRASTRUCTURE:

HARDWARE REQUIREMENTS
 Processor(256 MHz),Pentium sequels
 RAM (256 MB)
SOFTWARE REQUIREMENTS
 Rational Rose software
ABSTRACT

In the existing system all the transactions are done manually. These
systems will have to maintain the data in a hard file. While searching any data
is too difficult to find those.
Maintaining too many passenger details and ticket details in separate
files are too complicated. Similarly, it is too difficult to maintain the data for
each and every manual transaction. So, the time utilization will be more for
this manual system. In order to overcome these we have to propose the
software for the existing method.
We have proposed system that would modernize the activities of
reservation system. The developed system would perform all the functions of
the manual system. Using this system we can save time and the operations will
be performed with ease comparatively.
MODULAR DESCRIPTION

ENQUIRY MODULE:
This module enables the end users to know about the vacancy details of
the particular train on a particular date. This module forms the basic medium
through which the user can communicate with the reservation officer to know
about the vacancy details.

RESERVATION MODULE:
This module allows the user to reserve tickets for a particular train on a
particular date if there is any vacancy. The user can know about the vacancy
details of the train through the enquiry module.

MODIFICATION MODULE:
This module permits the user to modify the date of journey or the
number of persons of journey or passenger details, etc., through the
reservation officer (System).

CANCELLATION MODULE:
This module allows the user to cancel the tickets to a train for a
particular date through the reservation officer (System). This module permits
the user to know the status of the reserved ticket before and after cancellation.

All these modules together prove to be a flexible Online Reservation


System and it provides complete flexibility and reliability to the end users and
it assures the desired performance.
USE CASE DIAGRAM

ENTER THE WEB SITE

ENQUIRY

RESERVATION
PASSANGER SYSTEM

MODIFY

CANCEL
ACTIVITY DIAGRAM

ENTER THE
WEB SITE

SPECIFY SOURCE
AND DESTINATION

CHOOSE
TRAIN

SPECIFY
USER DETAILS

SEATS
AVILABLE

NEXT TRAIN
VALID CARD
SPECIFY CARD
NUMBER

CONFIRM
TICKET

DISPLAY THE
TICKET
CLASS DIAGRAM

RESE RVA TION


ENQUIRY INT DA TE M O DIFY
INT TICKETS CHA R P LACE IN T DATE
CHAR PA SSENGE R INT CA RD_NO IN T PAS SE NGER

STA TUS OF TICKE TS() DATE OF JOURNEY() CHAN GE D ATE()


PASS ENGER() CHE CKS THE P LACE() IN T PAS SE NGER()
CHE CK CRE DIT CARD_NO()

W EBSITE
CANCEL
CHAR W EB
IN T TICKE TS
S EAR CH W EB ()
CANC EL TICK ETS ()
SEQUENCE DIAGRAM

P A SSE NGER S Y S TE M LO GIN E N Q U IR Y R E S E R VA TIO M O D IF Y CA NCE L


N

E N TE R ID A N D P A S S W O R D

L O G IN

S TS TU S O F TR A IN TIC K E T

A V A IL A B LE O F TIC K E TS

E N TE R TH E D E T AIL S O F JO U RN E Y
E N TE R TH E C R E D IT D A R D N U M B E R

IS S U E TR A IN TIC K E T

M O D IF Y TH E JO U R N EY D E TA IL S

C A N C E L TH E TR A IN TIC K E TS
COLLABORATION DIAGRAM

E NQUIR
Y
LOGIN

S Y S TE
M

CA NCE L

4: A V A ILA B LE OF TICK E TS
2: LOG IN 3: S TS TUS OF TRA IN TICK E T

1 : ENTE R ID A ND P AS S W ORD

M O DIFY
9: CA NCE L THE TRA IN TICKE TS

8: MO DIFY THE JOU RNE Y DE TA ILS


7: IS S UE TRA INTICK E T PASS EN
GE R
RE S E RV
A TION 5: E NTE R THE DE TA ILS OF JOURNE Y
6: E NTE R THE CRE DIT DA RD NUM B E R
COMPONENT DIAGRAM

<<s tand andEXE>>


ONLINE
R ESERVATION
CODING:
ENQUIRY:

#include "enquiry.h"

//##ModelId=4C5143CB0177
enquiry::Stop of ticket()
{
}

//##ModelId=4C5143CB0178
enquiry::Passenger()
{
}
MODIFY
#include "modify.h"

//##ModelId=4C5143CB0160
modify::change of date()
{
}

//##ModelId=4C5143CB0161
modify::change of passengers()
{
}
RESERVATION
#include "reservation.h"

//##ModelId=4C5143CB016B
reservation::date of journey()
{
}

//##ModelId=4C5143CB016C
reservation::destination place()
{
}
WEBSITE

#include "Website.h"

//##ModelId=4C5143CB0182
Website::search website()
{
}
RESULT:
Thus the online reservation system has been designed using Rational
Rose Software and code is generated by ANSI C++.
EX NO:
DATE:

STUDENT MARK ANALYSIS SYSTEM

AIM
To analyze, design and develop code for Student Mark Analysis system
using Rational Rose software.

PROJECT SCOPE
The main scope of the project is to develop a system which effectively
manages the marks and grades of the students and update them regularly
through the authenticated users.

OBJECTIVE
The main objective of designing and developing a Student Mark
Analysis system is to enable the administrator or any other authenticated
person to record, view or upgrade the marks and grades of the students. This
system is specifically meant to manipulate and manage the marks and grades
of the students but not to get into the personal details of the students.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor: Pentium IV
 Hard disk: 40 GB(min)
 Ram: 256 MB(min)
SOFTWARE REQUIREMENTS
 Rational Rose software
STUDENT MARK ANALYSIS SYSTEM

ABSTRACT
The Student Mark Analysis System is very important because of its
common usage in most of the academic institutions. It proves to be the
commonest system as it finds its application in almost all the educational
institutions irrespective of its strength and location. The maintenance of this
system proves to be challenging as it has many cases to concern.
In the existing system all the processing are done manually. These
systems will have to maintain the data in a hard file. While searching any data
it is too difficult to find those.
Maintaining too many data about products in separate files are too
complicated. Similarly, it is too difficult to maintain the data for each and
every activity. So, the time utilization will be more for this manual system. In
order to overcome these problems we have to propose the system which
overcomes the problem of the existing method.
We have proposed a system that would modernize the activities of the
student mark analysis system. The developed system would perform all the
functions of the manual system. Using this system we can save time and the
operations will be performed with ease comparatively.
As System Analysts, we analyzed the existing system and found the
following modules required to computerize the operations.
a) Record Grades Module – To record the grades of each and every
student.
b) View Grades Module – To view the grades of any student.
c) Update Grades Module – To update the grades of any student.
d) Distribute Report Cards Module – To maintain the details of the
students who have been distributed their respective report cards.
MODULAR DESCRIPTION

RECORD GRADES MODULE


This module enables the authenticated users to record the marks and
thereby their respective grades in a database. This is the most important
module as it maintains the details of the marks scored by the students in the
database and it is the first and the foremost step in this system.
VIEW GRADES MODULE
This module permits the respective users to view their grades as and
when necessary after identification through their login name and password.
This module proves to be the simplest as it does not allow the user to modify
or update any information except viewing them.
UPDATE GRADES MODULE
This module enables the authenticated users to update the grades of the
students after each and every test in order to update the data to the present
existing grades of the students. This module just allows the user to modify or
update the grades of the students alone but not their personal details. This
module does not allow any user just like that; only authenticated users are
allowed to update the necessary data after their identification through their
login name and password.
DISTRIBUTE REPORT CARDS MODULE
This module is used to maintain the details of the students who have
been issued their respective report or record or record cards in order to avoid
confusion with that of those students who have not been issued.
All these modules together proves to be a flexible Student Mark
Analysis system and it provides complete flexibility and reliability to the end
users and it assures of the desired performance
USECASE DIAGRAM
STUDENT MARK ANALYSIS
student details
(from Use Case Vi e w)

p ass p erc entage


(from Use Case Vi e w)

failure perc entage


students sy stem
(fro m Use Case V i ew)
(from Use Ca se Vi e w) (fro m Use Ca se V i ew)

grades
(f ro m Use Ca se V ie w)

updating m ark s
(f ro m Use Ca se V ie w)
student details
(from Use Case Vi e w)

p ass p erc entage


(from Use Case Vi e w)

failure perc entage


students sy stem
(fro m Use Case V i ew)
(from Use Ca se Vi e w) (fro m Use Ca se V i ew)

grades
(f ro m Use Ca se V ie w)

updating m ark s
(f ro m Use Ca se V ie w)

ACTIVITY DIAGRAM FOR STUDENT MARK ANALYSIS


[STUDENT DETAILS]
Enter user name
and pass word

check user nam e an d pass word


no Invalid user

yes
Enter the
student number

chec k t he student nu mber


no invalid user

yes

St udent Mark Bi o data


detai l

ACTIVITY DIAGRAM FOR STUDENT MARK ANALYSIS

[PASS PERCENTAGE]
enter the user
name and data

check user name


no Invalid

yes

calculate the
pass percentage

save
ACTIVITY DIAGRAM FOR STUDENT MARK ANALYSIS

[FAILURE PERCENTAGE]

Enter User name


and pass word

check user name and pass word


no Invalid User

yes

Calculate student
failure percentage

SAVE

ACTIVITY DIAGRAM FOR STUDENT MARK ANALYSIS

[GRADES]
Enter user name &
pass word

INVALID
User

Student
mark

if mark>75 Grade A Save.

no
if mark >60>75 yes
Grade B save.

no

if mark<60 yes

no Grade C Save,

ACTIVITY DIAGRAM FOR STUDENT MARK ANALYSIS

[UPDATE]
Enter User Name
And P as s W ord

InValid

Student
Details

mark Update save,


marks
CLASS DIAGRAM FOR

STUDENT MARK ANALYSIS

Student Details
char stu_nam e Grades
int stu_no Updating m arks Pass Perc entag e Fail ure
Percentage int pass_marks
int stu_mark int stu_marks int stu_marks
ichar grade A
char stu_add int new_marks int pass_marks int stu_marks
char grade B
char stu_dob int fail_m arks
char grade C
char stu_dept update_m ark() stu_pass()
stu_fail()
grades()
stu_details()

SEQUENCE DIAGRAM FOR

STUDENT MARK ANALYSIS


staff Student details Update marks Pass Failure Grade
Percentage percentage

Enquery

Updating marks

Calculate pass percentage

Calculate Failure percent age

Grade the student marks

COLLOBRATION DIAGRAM FOR


STUDENT MARK ANALYSIS

Update Student
marks details

1: Enquery

2: Updating marks

5: Grade the student marks


staff
Grade

4: Calculate Failure percentage

3: Calculate pass percentage

Pass
Percentage Failure
percentage
COMPONENT DIAGRAM FOR

STUDENT MARK ANALYSIS

<<Stand and EXE>>


Student mark
Analysis

CODING:

UPDATINGMARKS:

#ifndef UPDATINGMARKS_H_INCLUDED_B39B4BCF
#define UPDATINGMARKS_H_INCLUDED_B39B4BCF
//##ModelId=4C64BDAF0018
class UPDATING MARKS
{
//##ModelId=4C64BDBD0019
INT MARKS;

//##ModelId=4C64BDC8006E
INT NEW MARKS;

//##ModelId=4C64BDD003C3
name;

};

#endif /* UPDATINGMARKS_H_INCLUDED_B39B4BCF */

STUDENT DETAILS

#include "STUDENT DETAILS.h"

//##ModelId=4C64BD9B0288
STUDENT DETAILS::STUD_DETAILS()
{
}
#ifndef STUDENTDETAILS_H_INCLUDED_B39B5FCA
#define STUDENTDETAILS_H_INCLUDED_B39B5FCA

//##ModelId=4C64BD7401C7
class STUDENT DETAILS
{
public:
//##ModelId=4C64BD9B0288
STUD_DETAILS();

private:
//##ModelId=4C64BD820120
CHAR NAME;

//##ModelId=4C64BD8701C3
INT NO;

//##ModelId=4C64BD8A03B0
INT MARK;

//##ModelId=4C64BD8E01B5
CHAR ADD;

//##ModelId=4C64BD930192
CHAR DOB;

};

#endif /* STUDENTDETAILS_H_INCLUDED_B39B5FCA */

PASS PERCENTAGE

#include "PASS %.h"

//##ModelId=4C64BE2C002C
PASS %::PASS()
{
}

FAILURE PERCENTAGE:

#include "FAILURE.h"

//##ModelId=4C64BE4D02AC
FAILURE::FAIL()
{
}
GRADES
#include "DGRADES.h"

//##ModelId=4C64BE8503D7
GRADES::GRADE()
{
}
RESULT
Thus the “STUDENT MARK ANALYSIS” is done using Rational
Rose software and code generated by ANSI C++.
EX NO:
DATE:
QUIZ SYSTEM
AIM:
To analyze, design and envelope code for Quiz system using Rational
Rose software.

PROJECT SCOPE
The main scope of the project is to provide a user friendly online quiz
system which enables the participant to take part in online quiz system and
make the best of it.

OBJECTIVE
The main objective of designing and developing an online Quiz system is
to enable the participant i.e. the end users of this system to gain the complete
wisdom through this flexible and reliable system. This system has been
developed in such a way that there exists a two way communication between
the participant i.e., the end user and the coordinator. The questions, their
answers and the grades and scores of the participants are stored in a database
and retrieved as and when required.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor(256 MHz),Pentium sequels
 RAM (256 MB)
SOFTWARE REQUIREMENTS
 Rational Rose software
QUIZ SYSTEM

ABSTRACT:
The quiz competition has made an impressive role among the students
of various schools and colleges. By far it is the most powerful tool to kindle the
IQ flames of the students and this has shown a quiet a bit of twist in the sense
that it does need changes and improvement as each and every object of this
real world needs to survive in this peer pressure world.
In the existing system all the processing are done manually. These
systems will have to maintain the data in a hared file. While searching any
data it is too difficult to find those.
Maintaining too many questions and answers in separate files are too
complicated. Similarly, it is too difficult to maintain the data for each and
every activity. So, the time utilization will be more for this manual system. In
order to overcome these problems we have to propose the system which
overcomes the problem of the existing method.
We have proposed a system that would modernize the activities of
online quiz system. The developed system would perform all the functions of
the manual system. Using this system we can save time and the operations will
be performed with ease comparatively.

MODULAR DESCRIPTION

REGISTRATION MODULE:
This module enables the end users to register themselves to the online
quiz competition through two way communication between the coordinator
and the participant. This is the most important module as it maintains the
details of the participants in the database and it is the preliminary stage of the
online quiz system.

DISPLAY MODULE:
This module provides the user with the fields i.e., the questions for
which they have to answer and it displays the answers of those questions when
required by the coordinator.

EVALUATION MODULE:
This module evaluates the answers which are given by the users i.e., the
participants with that of the corresponding answers in the database . Either
they are correct or wrong, in both the cases, the scores of the corresponding
participant or team will be updated accordingly.

ANNOUNCEMENT MODULE:
This module is used to display the results of the quiz competition
irrespective of the status of the result and it also displays the scores acquired
by each participant or team at the end.

All these modules together prove to be a flexible Online Quiz system


and it provides complete flexibility and reliability to the end users and it
assures of the desired performance.
USE CASE DIAGRAM FOR
QUIZ SYSTEM
REGISTRATION

DISPLAY OF QUES

PARTICIPANT DATABASE
ANSWER THE QUES

DISPLAY THE SCORE CARD

CO-ORDINATOR

WINNER LIST

ACTIVITY DIAGRAM FOR QUIZ


[FIELD SELECTION]
START

DISPLAY OF
FIELD

SELECT THE
FIELD

ACTIVITY DIAGRAM FOR QUIZ


[DISPLAY OF QUESTION]
START

ACCEPT THE
FIELD

DIS THE QUES INVALID FIELD

GET THE
ANSWER

STORE RHE
ANSWER

STORE THE
FIELD

ACTIVITY DIAGRAM FOR QUIZ


[EVALUATION OF SCORES]
START

ACC THE
ANSWER

VERIFY THE
ANSWER

UPDATE THE
SCORE

ACTIVITY DIAGRAM FOR QUIZ


[UPDATING OF SCORE]
START

ACCEPT
ANSWER

CKECK
ANSWER

NEGATIVE
POSITIVE POINT
POINT

UPDATE THE
POINT

CLOSE THE
FIELD

ACTIVITY DIAGRAM FOR QUIZ


[ANNOUNCEMENT OF RESULT]
START

GET THE ANSWER


FROM DATABASE

ANNOUNCE
THE RESULT

CLASS DIAGRAM FOR


QUIZ SYSTEM
PRGM EXECUTIVE
CANDIDATE
CHAR NAME
CHAR NAME
INT MARKS
INT AGE
INT TIME
CHAR QUALIFICATION
INT RANK
RESUME()
ACCEPT()
FIELD()
VERIFY CERTIFICATE()

SEQUENCE DIAGRAM FOR


QUIZ SYSTEM
CANDIDATE. PGM EXECU QUIZ MASTER

accept reg form


display of ques

verify

select field of int


update the score

answer the question


announcement of result

COLLABRATION DIAGRAM FOR


QUIZ SYSTEM
4: select field of int
6: answer the question
3: verify

1: accept reg form


CANDID
ATE. PGM
EXECU

2: display of ques
5: update the score
7: announcement of result

QUIZ
MASTER

COMPONENT DIAGRAM FOR


QUIZ SYSTEM
<<Standard and exe>>
QUIZ

CANDIDATE DETAILS:

#include "CANDIDATE.h"
//##ModelId=4C490FC1007D
CANDIDATE::RESUME()
{
}

//##ModelId=4C490FC4033C
CANDIDATE::FIELD()
{
}

#ifndef CANDIDATE_H_INCLUDED_B3B6B1E3
#define CANDIDATE_H_INCLUDED_B3B6B1E3

//##ModelId=4C490F9B03C8
class CANDIDATE
{
public:
//##ModelId=4C490FC1007D
RESUME();

//##ModelId=4C490FC4033C
FIELD();

private:
//##ModelId=4C490FA60109
BYTE NAME;

//##ModelId=4C490FAC0280
INT AGE;

//##ModelId=4C490FB003B9
BYTE QUALIFICATION;

};

#endif /* CANDIDATE_H_INCLUDED_B3B6B1E3 */

PROGRAM EXECUTION DETAILS:

#include "PROGRAM EXECUTION.h"


//##ModelId=4C49101500AB
PROGRAM EXECUTION::ACCEPT()
{
}

//##ModelId=4C49101901B5
PROGRAM EXECUTION::CERTIFICATE VERIFY()
{
}
#ifndef PROGRAMEXECUTION_H_INCLUDED_B3B6DA4C
#define PROGRAMEXECUTION_H_INCLUDED_B3B6DA4C

//##ModelId=4C490FE2038A
class PROGRAM EXECUTION
{
public:
//##ModelId=4C49101500AB
ACCEPT();

//##ModelId=4C49101901B5
CERTIFICATE VERIFY();

private:
//##ModelId=4C490FFC0271
BYTE NAME;

//##ModelId=4C49100001F4
INTEGER MARKS;

//##ModelId=4C4910060119
INTEGER TIME;

//##ModelId=4C49100B03C8
INTEGER RANK;

};

#endif /* PROGRAMEXECUTION_H_INCLUDED_B3B6DA4C */
RESULT:
Thus the “QUIZ SYSTEM” is done using Rational Rose Software and
code generated by ANSI C++.
EX NO:
DATE:
COURSE REGISTRATION SYSTEM

AIM
To analyze, design and envelope code for Course Registration System using
Rational Rose software.

PROJECT SCOPE
The main scope of the project is to perform the registration, cancellation,
modification of the course that is selected by the student.

OBJECTIVE
The main objective of designing and implementing this course registration
system is to enable the administrator to provide a mutually beneficial system which
benefits both students and administrators.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor: Pentium IV
 Hard disk: 40 GB(min)
 Ram: 256 MB(min)

SOFTWARE REQUIREMENTS
 Rational Rose software

PROBLEM STATEMENT
Course Registration system is used for the students to register their courses
before joining their college. It also makes registration easier.
In the system the student has to enquire about the courses, college and about
the fee details to the administrator in turn will provide the details that are required
by the students.
The students can also modify their courses with the help of the system, for
which the administrator has to accept the request sent by the student.
The system also provides the facility for canceling the courses that are
registered already.
All these processes are done very easily without any difficulty with the help
of the course registration system.

COURSE REGISTRATION SYSTEM


ABSTRACT

The most important phase in developing software for a customer is the


analysis phase. As it is said that most strong and tall buildings in the world stands
still now just because of the reason that have strong foundation, this works well
with software concept also. The analysis phase proves to be the foundation for the
software development proceeds. In our topic, the course registration system is
concerned with the process of choosing and joining the course in educational
institutions.
The “COURSE REGISTRATION SYSTEM” should be more flexible for
the students (end users). Our topic is constrained to the admission process of
educational institutions. There are primarily two main actors involved in this
course registration system and they are
 Students.
 Administrator.
It is highly a tedious job to analyze the major modules involved in this system.
Since this particular system deals with educational institutions (i.e., academics) the
analysis and the development of this system must be dealt with utmost care
because if anything goes wrong the students are going to be the ultimate sufferers.
This system is designed in such a way that it is completely flexible in providing a
two way conversation between the student and the administrator. Each and every
activities have been seriously considered and they have been implemented, keeping
in mind the future enhancements of this system and utmost care has been taken to
solve almost all the special cases which arises due to any special situation in this
system.
This registration system provides complete flexibility to the students to
choose the courses according to their desire and it also provides room for
modification and cancellation of any information or process. It also allows the
administrator to a great extent to handle process the information provided by the
student in an effective manner which makes this system further more effective

MODULAR DESCRIPTION

This system involves four major modules primarily and they are,
• Enquiry module.
• Admission module.
• Modification module.
• Cancellation module.

ENQUIRY MODULE
This is the first and the foremost module or step involved in course
registration system. The enquiry step includes the activities of listing courses
available, the fee structure for the corresponding courses, result analysis of course,
accreditation for the infrastructure of the lab and college, placement facilities, etc.

ADMISSION MODULE
This module forms the crux of the course registration system. It includes
getting the application form by students from admin, filling in the application
forms and submitting it to the admin, the admin evaluates the student’s application
forms and his/her school certificates, then the admin prepares the admission results
and details of the fee payment, etc.

MODIFICATION MODULE
If any of the alteration takes place after the admission process, it includes
change of the course; modification of the information provided in application form,
etc., every single modification is covered by this modification module.

CANCELLATION MODULE
This is one of the special cases of Course Registration system; it includes
dropping out from the college because of any personal reason. Then the necessary
step to be taken by the administrator is designed appropriately till returning the
certificates of the students to them.
The above listed modules form the basis for the “COURSE
REGISTRATION SYSTEM”. Each module has its own characteristics and
features. Each step in a module is to be treated crucially as this deal with the career
of students.

USECASE DIAGRAM FOR


COURSE REGISTRATION SYSTEM
enquiry

application no

regi stration

student
administrator

modification

cancellation

ACTIVITY DIAGRAM FOR COURSE REGISTRATION SYSTEM


[ENQUIRY]
enter the
name

enter the
degree

enter the
course no

enter the
fees

yes

ACTIVITY DIAGRAM FOR COURSE REGISTRATION SYSTEM


[APPLICATION ISSUE]
Enter theno
Application

Enter the number of


Original certificates

Entername
Course the

Enter the
College

Enter the
Amount

Enter name
Student the

Enter the student


Address

Enter the application


Register(y/n)

ACTIVITY DIAGRAM FOR COURSE REGISTRATION SYSTEM


[REGISTRATION]
student
eligibility

enter the
application no

enter the
course name

enter the
college

ACTIVITY DIAGRAM FOR COURSE REGISTRATION SYSTEM


[MODIFICATION]
enter the
application no

enter the
course name

enter the
college

enter the
fees

ACTIVITY DIAGRAM FOR COURSE REGISTRATION SYSTEM


[CANCELLATION]
enter the
application no

enter the
course

enter the
college

return
amount

CLASS DIAGRAM FOR


COURSE REGISTRATION SYSTEM
registration
applicat ion issue modification
application
percentage application no
certificate
applicat ion no course
course
course no set
college
college college
student name
fees amound
student address
applicat ion()
modify()
register()

enquiry
student name cancellation
degree application no
course course
fees verify

enquiry() cancel()

SEQUENCE DIAGRAM FOR


COURSE REGISTRATION SYSTEM
s tud e n t a d m in is tra to r e n q u iry p as s a p p lic a tio n u s e re gis tra tio n m o d i fy c a n c ella tio n

COLLABRATION DIAGRAM FOR


COURSE REGISTRATION SYSTEM
administ
rat or
pass
2:

applicatio 1:
n use

enquiry
3:
4:

student

5:

6: 7:
modify registrati
on

cancellat
ion
COMPONENT DIAGRAM
COURSE REGISTRATION SYSTEM

<<Stand and EXE>>


Course registration

CODING:

COURSE DETAILS:

#include "COURSE DETAILS.h"


//##ModelId=4C41275A031C
COURSE DETAILS::COURSE()
{
}

EXAM DETAILS:

#include "EXAM DETAILS.h"

//##ModelId=4C4127CF031C
EXAM DETAILS::EXAM()
{
}

FEE DETAILS:

#include "FEE DETAILS.h"

//##ModelId=4C41279E006D
FEE DETAILS::FEE()
{
}

STUDENT DETAILS

#include "STUDENT DETAILS.h"

//##ModelId=4C4127170280
STUDENT DETAILS::STUDENT()
{
}

#ifndef STUDENTDETAILS_H_INCLUDED_B3BEA560
#define STUDENTDETAILS_H_INCLUDED_B3BEA560

//##ModelId=4C4126EB005D
class STUDENT DETAILS
{
public:
//##ModelId=4C4127170280
STUDENT();

private:
//##ModelId=4C4126F50280
CHAR NAME;

//##ModelId=4C4126FA03A9
INT AGE;

//##ModelId=4C41270000FA
CHAR QUALI;

};

#endif /* STUDENTDETAILS_H_INCLUDED_B3BEA560 */
RESULT
Thus the “COURSE REGISTRATION” is done using Rational
rose software and code generated by ANSI C++.
EX NO:
DATE:
PAYROLL SYSTEM
AIM:
To analyze, design and envelope code for Payroll system using Rational
Rose software.

PROJECT SCOPE:
The main scope of the project is to calculate the salary of the
employee only by receiving his employee id number.

OBJECTIVE:
The main objective of designing and implementing this PAYROLL
SYSTEM is to enable the administrator to provide a mutually beneficial
system which benefits both employee accounts.

INFRASTRUCTURE

HARDWARE REQUIREMENTS
 Processor (256 MHz), Pentium sequels.
 RAM (256 MB).
SOFTWARE REQUIREMENTS
 Rational Rose software.

PAYROLL SYSTEM

ABSTRACT:
Normally the payroll calculation is much hard is manual, because if
needs a lit of information to be considered while calculating the payroll of a
employee for e.g., tax for salary, incentives, increments and a lot.
To reduce the burden on the administrator of payroll in payroll
calculation we declare to create a payroll calculation system which will
calculate with less work of user.
The system gets the employee id no of the employee to whom we have to
consider all factors incentives, increments and all other facts and calculate the
gross pay of the employee.
There is a conflict that can we considered payroll system for the
organizations like college, hospital, corporate companies and the others. We
planned to develop software that can be used for all kind of field.

MODULAR DESCRIPTION

BASIC PAY:
It calculates how many amounts are given for each person per month
and that allocates as respect with position of the workers.

ALLOWANCE:
It allocates proper order with respect some of doctrine concept that
describe evolved person of the workers.

LOSS OF PAY:
It describes the correct position of the salary allocation process which
contains some of the working process.

TAXES AND EDEUCTION:


It refers to be allocating the salary for person with according to tax and
deduction.

INCENTIVES:
Most of the payroll process is based on the rolling to some or many level
project which based on the constrains of the process.

PF AND LOAN:
Most context present with some of the configuration like loan and PF
that should be possible in every one of the payroll system aspects.

USE CASE DIAGRAM FOR


[PAYROLL SYSTEM]
ADD EMP LOYEE TO PAYROLL

CALCULATE AND PRINT


<<extend>>
PAYROLL

<<extend>>

REMOVE EMPLOYEE FROM


MAINTAIN EMPLOYEE DETAILS PAYROLL

<<extend>>
PAYROLL
OPERATOR

MODIFY PAYROLL AMOUNT


EDIT EMPLOYEE WITHIN
PAYROLL

MANAGE TAX RATES

ACTIVITY DIAGRAM FOR


[MODIFY PAYROLL AMOUNT]
START

EMPLOYEE
DETAILS

PROMOTION YES CALCULATE


INCREMENT
BASIC PAY GROSS SALARY.

NO

DEMOTION YES CALCULATE


DECREMENT
BASIC PAY GROSS SALARY..

NO

SUSPENSION CALCULATE AMOUNT FOR


SUSPENDED DAYS
YES

NO

CALCULATE REDUCE AMOUNT FROM


GROSS SALARY PAYROLL

MODIFY
PAYROLL

ACTIVITY DIAGRAM FOR


[MAINTAIN EMPLOYEE DETAILS]

START

EMPLOYEE ID

EMPLOYEE
NAME BASIC PAY

EMPLOYEE DEPT. &


ALLOWANCES
DESIGNATION

PERS ONAL REBATES &


DETAILS CONCESSION

GROSS
SALARY

ACTIVITY DIAGRAM FOR


[MANGE TAX RATES]
START

EMPLOYEE
DEATILS

YES<
BASIC PAY NO TAX CALCULATE
RS 5000 TAX AMOUNT.

NO

YESBASIC
RS 5000< TAX=10% OF CALCULATE
PAY < RS 10,000 AMOUNT INCOME TAX AMOUNT..

NO

BASIC YES
PAY > TAX=20% OF
RS 10,000 ANNUAL INCOME

NO

CALCULATE
TAX AMOUNT

ENTER THE DETAILS IN


PAYROLL

UPDATE
DATABASE

ACTIVITY DIAGRAM FOR


[ADD EMPLOYEE PAYROLL]
START

NEW
YES
APPOINTMENT

NO

DEPT. TRANSFER
ADD DETAILS OF NEW
(INTERNAL)
EMPLOYEE TO DATABASE
YES

NO

BRANCH
YES
TRANSFER

NO

NO NEW
APPOINTMENT

ACTIVITY DIAGRAM FOR


[REMOVE EMPLOYEE FROM PAYROLL]
S TA RT

E M P LOY E E
DE TA ILS .

S E RV ICE
YES RE TIRE M E NT
NO
RE M OV E DE TA ILS V OLUNTA RY
FROM DA TA B A S E RE TIRE M E NT
YES
NO

DE P T. B RA NCH YES UP DA TE THE TRA NS FE R


TRA NS FE R DETAILS IN DA TA B A S E

NO

NA TURA L
A CCIDE NTA L DE A TH
YES

NO

NO RE M OV A L
OF DE TA ILS

ACTIVITY DIAGRAM FOR


[EDIT EMPLOYEE WITHIN PAYROLL]
START

UPDATE INDIVIDUAL
EMPLOYEE DETAILS

UPDATE DEPT.
EMPLOYEE DETAILS

UPDATE BATCH-WISE
EMPLOYEE DETAILS

UPDATE THE EDITED


EMPLOYEE DETAILS

MAINTAIN EMPLOYEE
RECORDS WITHIN DATABASE

ACTIVITY DIAGRAM FOR


[PRINT PAYROLL DETAILS]
START

EMPLOYEE
DETAILS...

WORKING
DAYS

CALCULATE THE CALCULATE


OVER TIME YES
AMOUNT FOR OT HRS GROSS SALARY,
HRS

ADD AMOUNT TO
NO NET SALARY

YES CALCULATE THE AMOUNT


FOR LEAVE DAYS

NO

CALCULATE ADD/ SUB AMT TO


GROSS SALARY... NATURE OF LEAVE

PRINT GROSS
SALARY

CLASS DIAGRAM FOR


[PAYROLL SYSTEM]
ADD EMPLOYEE DETAILS
MAINTAIN EMPLOYEE DETAILS
NEW_APPOINTMENT
EMP_NAME
DEPT_TRANSFER
EMP_ID
BRANCH_TRANSFER
DEPT_DEGN
PERSONAL_DET
ADD EMP_DET()
PAY_DET

MAINTAIN DET()
MAINTAIN SALARY()
MANAGE TAX RATES REMOVE EMPLOYEE DETAILS
BASIC_PAY RETIREMENT
TRANSFER
TAXAMOUNT() DEATH
CALCULATE AND PRINT PAYROLL
EMP_DET REMOVE EMP_DET()
WORKING_HRS
OT_HRS
LEAVE_TAKEN

ADD OT() EDIT EMPLOYEE DETAILS


ADD/SUB LEAVE AMT() INDIVIDUAL_DET
GROSS SALARY() DEPT_DET
BRANCH_DET

UPDATE DATABASE()

MODIFY PAYROLL AMOUNT


EMP_DET
WORKING_HRS
OT_HRS
LEAVE TAKEN

ADD OT()
ADD/SUB LEAVE AMT()
GROSS SALARY()

SEQUENCE DIAGRAM FOR


[PAYROLL SYSTEM]
EMPLOYEE PAYROLL
OPERATOR
ACEPT EMPLOYEE DETAILS

VERIFY EMPLOYEE DETAILS

MAINTAIN EMPLOYEE DETAILS

CREATE EMPLOYEE DETAILS

CALCULATE PAYROLL DETAILS

MANAGE TAX RATES

PRINT PAYROLL DETAILS

ADD/REMOVE EMPLOYEES

EDIT DETAILS IN DATABASE

MODIFY & PRINT PAYROLL DETAILS

VERIFY PAYROLL CALCULATION

ISSUE SALARY

COLLABRATION DIAGRAM FOR


[PAYROLL SYSTEM]

2: V E RIFY E M P LOY E E DE TA ...


3: M A INTA IN EM P LOY E E DETA...
4: CRE ATE E M P LOY E E DETAILS
9: E DIT DE TA ILS IN DA TA B A S E
11: V E RIFY P A Y ROLL CA LCULA TION

1: A CE P T EM P LOY E E DE TA ILS
E M P LO YE E P A Y ROLL
OP E RATOR
5: CA LCULA TE P A Y RO LL DE TA ILS
6: M A NA GE TA X RA TE S
7: P RINT P A YROLL DETA ILS
8: A DD/REM OV E E M P LOY E E S
10: M ODIFY & P RINT P A Y RO LL DE TA ILS
12: ISS UE S A LA RY

COMPONENT DIAGRAM FOR


[PAYROLL SYSTEM]

<<stand and EXE>>


PAYROLL

CODING:

EMPLOYEE DETAILS:
#include "ADD EMPLOYEE DETAILS.h"

//##ModelId=4C3FD317031C
ADD EMPLOYEE DETAILS::ADD EMP_DET()
{
}
#ifndef ADDEMPLOYEEDETAILS_H_INCLUDED_B3C0767D
#define ADDEMPLOYEEDETAILS_H_INCLUDED_B3C0767D

//##ModelId=4C3FD2CE0213
class ADD EMPLOYEE DETAILS
{
public:
//##ModelId=4C3FD317031C
ADD EMP_DET();

private:
//##ModelId=4C3FD2DE00CB
NEW_APPOINTMENT;

//##ModelId=4C3FD2EA036B
EPT_TRANSFER;

//##ModelId=4C3FD2FC038A
BRANCH-TRANSFER;

};

#endif /* ADDEMPLOYEEDETAILS_H_INCLUDED_B3C0767D */

CALCULATE AND PRINT PAYROLL:

#include "CALCULATE AND PRINT PAYROLL.h"

//##ModelId=4C3FD35602EE
CALCULATE AND PRINT PAYROLL::ADD OT()
{
}

//##ModelId=4C3FD4ED003E
CALCULATE AND PRINT PAYROLL::ADD/SUB LEAVE AMT()
{
}

//##ModelId=4C3FD4F70271
CALCULATE AND PRINT PAYROLL::GROSS SALARY()
{
}

#include "D:/VM 2976/EDIT EMPLOYEE DETAILS.h"

//##ModelId=4C3FD4970119
EDIT EMPLOYEE DETAILS::UPDATE DATABASE()
{
}

MAINTAIN EMPLOYEE DETAILS

#include "MAINTAIN EMPLOYEE DETAILS.h"

//##ModelId=4C3FD2B40196
MAINTAIN EMPLOYEE DETAILS::MAINTAIN DET()
{
}

//##ModelId=4C3FD2BE03C8
MAINTAIN EMPLOYEE DETAILS::MAINTAIN SALARY()
{
}

MANAGE TAX RATES DETAILS:

#include "MANAGE TAX RATES.h"


//##ModelId=4C3FD2510109
MANAGE TAX RATES::TAX AMOUNTS()
{
}

MODIFY PAYROLL DETAILS:

#include "MODIFY PAYROLL DETAILS.h"


//##ModelId=4C3FD3F50242
MODIFY PAYROLL DETAILS::ADD OT()
{
}

//##ModelId=4C3FD3FE00FA
MODIFY PAYROLL DETAILS::ADD/SUB LEAVE AMT()
{
}

//##ModelId=4C3FD40800BB
MODIFY PAYROLL DETAILS::GROSS SALARY()
{
}
RESULT:
Thus the “PAYROLL SYSTEM” is done using Rational Rose Software
and code generated by ANSI C++.

S-ar putea să vă placă și