EXPT NO:

DATE:

CREDIT CARD PROCESSING

PROBLEM STATEMENT: The system developed should contain the following features:The Customer has to login into the system using Credit Card or Debit Card number and Pin Number. The system should check for validation. The System queries the customer for the type of account either Savings Account or Current Account. After getting the type of account,the system shows the list of items such as balance enquiry, withdrawal ,cancel options. when the customer select the balance enquiry option, then the system shows the balance that left in the account and prints as receipt.when the customer select the withdrawal option then the system should ask the amount.The minimum amount in the savings account should be 5000,if the customer violates the n the system should give a warning message.The minimum amount of current account should be 1000,if violates give warning message. Then print the transaction amount in the receipt after withdrawal process. The maximum transaction amount should be 20,000. If the customer select the cancel option, then stop all the process and eject the card.

1. INTRODUCTION: This project is aimed at developing a credit card processing system by creating details about customers and provide transaction. 1.1 PURPOSE: Manual maintenance of customer details is a tedious process considering the to the large number of customers. Hence, this system is used for easy registration and maintenance of database. 1.2. SCOPE: The credit card processing is used to specify a certain procedure to the customers for quick and easy transaction. 1.3. DOCUMENT CONVENTIONS: Manager - The person who has the full authority over the system. He can view all registered users. Customer-The person who registers and obtains books from the Book bank. Bank-The entire System comprising of the customers, manager, staff and other elements. 1.4. REFERENCES: www.rec.in 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient credit card processing.

2.3 TOOLS TO BE USED Rational Rose 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the customers to know the procedure to access transaction. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Seperate and unique ids must be provided for each and every user so that no user can access the resources available to other users. GANTT CHART:

UML DAIGRAMS USE CASE DIAGRAM:

login

register customer customer service

bank details

customer details

payment details

CLASS DIAGRAM:

bank verify details() accept details()

CUSTOMER DETAILS CID CNAME address phno name getdetails() display details() payment details()

PAYMENT DETAILS acc_no cname cid amt payment mode() cardn stmt generation()

SEQUENCE DIAGRAM:

ACTIVITY DIAGRAM:

COLLABORATION DIAGRAM:

STATE CHART DIAGRAM: (PAYMENT)

LO G IN

EN T ER M O D E

EN T ER AM T

PAY

G EN ER AT E ST M T

PACKAGE DIAGRAM:

COMPONENT DIAGRAM:
BANK

CUSTOMER

PAYMENT

DEPLOYMENT DIAGRAM:

DATABASE

CUSTOMER

CUSTOMER SERVICE

RESULT: Thus the UML models for the credit card processing have been developed and verified.
EX NO: DATE :

EBOOK

Problem Analysis:
The problem is to find out the book that we need with reference to the prescribed author .The books will be categorized in to various sections . Some of the sections include Novels,Love and Romance etc. Ebooks of various author can be found in ease. SOFTWARE REQUIREMENT SPECIFICATION 1. INTRODUCTION: The statement of the system is to group the books in various categories according to users comfort.The main objective is to provide all the versions of book. PURPOSE: The system is designed with end user requirements as main criteria. It includes front end tool to receive data needed and to validate the entries. It has backend access to store validate data for future reference.To analyze and design a EBOOK based on Object Oriented Analysis and Design concept. 1.2. SCOPE: The system designed is capable of providing functional requirements based on book we chose and the Author we wish. Non-functional requirements are clarity,text decoration ,simple language etc. DOCUMENT CONVENTIONS: Administrator - The person who has the full authority over the system. He can view all registered users. Job Seekers - the person who registers in the system in search of jobs. Company - A company can register itself, select the required employees and provide information about the result. 1.4. REFERENCES: www.timesjob.com: 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient recruitment process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the visitors or job seekers do their enrollment. The back end is managed by the administrator effectively 2.3 TOOLS TO BE USED Rational Rose Enterprise Edition, AgroUML 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the job seeker to apply for job. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the user types the book, a list of possible e-books has to be displayed along with other details 3.1.3 FUNCTIONAL REQUIREMENTS:

REQ1: Only registered users can search and download. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Password for registered accounts are stored securely in a hash, the uploads made by the user must be checked and then accepted. GANTT CHART:

use case diagram

CLASS DIAGRAM:

sequence diagram:

Activity diagram

Collaboration diagram

STATECHART:

Package diagram

COLLABORATION DIAGRAM:

DEPLOYMENT DIAGRAM:

RESULT: Thus the UML diagrams for EBOOK management system were developed and verified.

EXPT NO: DATE:

E-TICKETING

PROBLEM STATEMENT: Here the passenger who used to login, who used to view the train details and they can able to cancel the tickets. The system administrator who used to manage the users and the security. The railway database which is getting include by all the passenger details like view train details and cancel the ticket. In extra of the railway database they can reserve the tickets which was enroll by the passenger. SOFTWARE REQUIREMENT SPECIFICATION: 1. INTRODUCTION: This project which aims to reserve the ticket using the login form. The passenger can able to view the train details and cancel the booked ticket if they dont need. 1.1 PURPOSE: The main purpose of E-Ticketing is that the travelling passenger need not go to the railway station and book the ticket. The main advantage of the E-Ticketing is that the passenger can able to book the ticket by using internet. 1.2. SCOPE: The scope of the E-Ticketing is that the passengers time is saved and we can able to book the seat which can be comfortable for us, and we can view the seats which are available when booking. 1.3. DOCUMENT CONVENTIONS: Passenger- who can be able to login, view the train details, and cancel the tickets. Railway database- the data which is reserved by the passenger can be included by the database. System admin- the system admin which can manage the user and the security. 1.4. REFERENCES: www.ticketbooking.com: 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient E-TICKETING process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the system admin or passenger do their enrollment. The back end is managed by the railway database effectively. 2.3 TOOLS TO BE USED

Rational Rose 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the passenger to book the seats. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the passenger login, the seats which are available to book can be viewed to book. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: The passenger should enroll some personal details so that no cheating can be made in booking the seats. GANTT CHART:

USE CASE DIAGRAM:

Login

Train Details Adm inis trator <<us es >> <<extend>> Update Reports

Pas s enger

<<us es >>

Cancellation <<extend>>

<<us es >> Seat Availability Res ervation

CLASS DIAGRAM:

Login username : String password : String get_data() verify() display() 1

Journey board : String start_pt : String end_pt : String fare : Float seat_no : Integer date : Date time get_journ_details() print_journ_details() * 1 User address : String age : Integer sex : String get_details()

Train train_no : Integer train_name : String start_pt : String end_pt : String seat_capacity : Integer reservd_seats : Integer unreservd_seats : Integer get_train_details() print_train_details() 1 * Report reserv_ticks : Integer unreservd_ticks : Integer train_name : String train_no : Integer canceld_ticks : Integer generate_daily_report()

Passenger p_name : String p_id : Integer tick_no : Integer pin_no : Integer pnr_no : Integer get_pas_details() print_pas_details()

Administrators a_name : String a_id : Integer salary : Float Desigantion : String get_a_details() print_a_details()

ACTIVITY DIAGRAM:

Enter username and password

Validate username & password

[ Trial >3 ]

[ Trial <3 ]

[ Valid ] Login success

ID blocked temporarily
LOGIN

TRAIN DETAILS

Login into the system

Enter the source and destination

[ unavailabe ]

Display unavailabilty of train

[ available ]

Display requested details

UPDATE REPORTS

Login as administrator

Update database on completion of each transaction

Generate daily reports

SEAT AVAILABILITY

L o g in

E n te r tr a in n a m eo rn u m b e r

V ie ws e a t a v a ila b ility

RESERVATION:

Enter username and password

Validate username & password

[ Trial >3 ]

[ Trial <3 ]

[ Valid ] Login success

ID blocked temporarily

CANCELLATION:

User login's

Enter pnr and pin number

Vaildate entry

Reconfirm cancellation

[ Valid ]

[ Invalid ]

Display error

[ Re-Confirmed ]

[ Not Re-Confirmed ]

Cancel tickets

Go to main page

Update reports

SEQUENCE DIAGRAM: RESERVATION

:passenger enter name and password :Reservation System :Railway Database

verify

enter details

search for seat availability if available

send information seat available

enter credit card no. validate

if accepted

send information card accepted

issue ticket

store in database

SEQUENCE DIAGRAM: CANCELLATION

:Passenger :Reservation System Enter name and password :Railway Database

Verify

Display form for cancel

Enter PNR no

search for PNR no

if available

verify details

cancel Ticket

store in database

COLLABORATION DIAGRAM: LOGIN

4 : V a lid a t io n (P a s s e n g e r) 1 2 : V a lid a t io n (A d m in is t ra t o r) 2 : E n te r lo g in d e t a ils (P a s s e n g e r) 1 0 : E n t e r lo g in d e t a ils (A d m in is t ra t o r) USER S Y S TE M 3 : S e n d d a t a fo r va lid a t io n (P a s s e n g e r) 1 1 : S e n d d a t a fo r va lid a t io n (A d m in is tra t o r) D A TA B A S E

6 : L o g in s u c c e s s (P a s s e n g e r) 8 : L o g in F a ilu re (P a s s e n g e r) 9 : R e q u e s t lo g in d e t a ils (A d m in is t ra t o r) 1 4 : L o g in s u c c e s s (A d m in is t ra t o r) 1 6 : L o g in fa ilu re (A d m in is t ra t o r)

5 : V a lid (P a s s e n g e r) 7 : In va lid (P a s s e n g e r) 1 3 : V a lid (A d m in is t ra t o r) 1 5 : In va lid (A d m in is t ra t o r)

TRAIN DETAILS
5 : V a li d a t io n

USER

1 : L o g in t o t h e s y s t e m 3 : E n t e r re q u e s t e d d a t a 4 : S e n d d a t a fo r va lid a t io n S Y S TE M D A TA B A S E 2 : R e q u e s t s o u rc e a n d d e s t in a t io n 7 : D is p la y t ra in d e t a ils 9 : D is p l a y e rr o r m e s s a g e 6 : V a li d 8 : In va lid

UPDATE REPORTS
5 : u p d at io n c om p le te d

1 : L o g in a s a dm in 3 : S e le c t c o m p let e d t ra n s a c tion s USE R (ad m in is t ra t o r)

4 : U p d a te s ele c te d t ra n s a c tio ns D A TA B A S E 6 : C o m p let e d 8 : In c o m p le te

S Y S TE M

2 : D is p lay vario u s t ra n s a c tio n 7 : D is p lay s u c c e s s 9 : D is p lay e rro r

SEAT AVAILABILITY
5 : V a lid a t io n 1 : L o g in t o t h e s y s t e m 3 : E n t e r t h e re q u e s t e d d a ta USER : P ass enger S Y S TE M

4 : S e n d s d a t a to d a ta b a s e D A TA B A S E

2 : R e q u e s t t r a in d e t a ils 6 : S e n d s e a t a va ila b il it y d e t a i ls t o s y s t e m 7 : D is p l a y s e a t a va i la b ilit y

RESERVATION

6 : A va ila b le 1 3 : U n a va ila b le 1 : L o g in a s p a s s e n g e r 2 : C h e c k s e a t a va ila b ilit y 4 : E n t e r t ra in d e ta ils 9 : E n te r re q u e s t e d d e t a ils USER (p a s s e n g e r) S Y S TE M

5 : C h e c k a va ila b ilit y 1 0 : U p d a te d e t a ils A D M IN IS T R A T O R

3 : R e q u e s ts tra in & jo u rn e y d e t a ils 7 : T ic k e t s a va ila b le 8 : R e q u e s ts p a s s e n g e r d e t a ils 1 1 : T ic k e t s re s e rve d a n d u p d a t e d 1 2 : D is p la y s u c c e s s m e s s a g e 1 4 : T ic k e ts u n a va ila b le 1 5 : D is p la y fa ilu re m e s s a g e

CANCELLATION
5 : va lid 1 2 : in va lid 1 : L o g in a s p a s s e n g e r 3 : E n te r re q u e s t e d d e t a i ls 8 : R e c o n firm s USER (p a s s e n g e r)

4 : V a lid a t e 9: C anc el and update databas e D A TA B A S E 6 : V a lid e n t ry 1 0 : C a n c e le d 1 3 : In va lid e n t ry

S Y S TE M

2 : R e q u e s ts p n r a n d p in n u m b e r 7 : R e q u e s t s re c o n firm a t io n 1 1 : T ic k e ts c a n c e lle d 1 4 : T ic k e ts n o t c a n c e lle d

STATE CHART DIAGRAM

[T r ia l< 3] L O G I N e n tr y /L o g intos y s te m

[V a lid] V I E W d o /V ie w a v a ila b les e a ts d o /V ie w tr a ind e ta ils

[S e a ta v a ila b le]

[T r ia l< 2] B O O KT I C K E T S d o /R e s e r v etic k e tsif s e a tsa v a ila b le e x it/ U p d a tetic k e td e ta ils

[T ic k e tsm u s tb ea lr e a d yr e s e r v e d]

[N o tR e C o n f ir m e d] C A N C E LT I C K E T S e n tr y /C a n c e la lr e a d yb o o k e dtic k e ts ,if n o tn e e d e d e x it/ U p d a tetic k e td e ta ils

[T r a n s a c tio nc o m p le te d]

G E N E R A T ER E P O R T d o /G e n e r a ted a ilyr e p o r t d o /D is p la yr e p o r ts

PACKAGE DIAGRAM:

COMPONENT VIEW

Database Management

Ticket Updation

Train info

DEPLOYMENT VIEW

Server (system)

Printer

PC 1

PC 2

PC n

Printer 1

Printer 2

Printer n

RESULT: Thus the UML diagrams for e-ticketing have been developed and verified. EXPT NO:

DATE:

BOOK BANK

PROBLEM STATEMENT: Book Bank is used to issue books to customers which they have to return after a specific period of time. It is necessary that the customers register at the book bank by filling out an entry form with proper details and submit it to the manager along with the mentioned fees. After the manager verifies the details and deposit, he/she issues the id card and a book form.The registered customer then has to fill out the form with the names of books and the authors and submit it back.The staff at the book bank check the availability of the books and issue the available ones. SOFTWARE REQUIREMENT SPECIFICATION 1. INTRODUCTION: This project is aimed at developing a book bank system by creating details about customers and the available books. 1.1 PURPOSE: Manual maintenance of customer details is a tedious process considering the to the large number of customers. Hence, this system is used for easy registration and maintenance of database. 1.2. SCOPE: The Book Bank System is used to specify a certain procedure to the customers for quick and hassle free registration and acquire the necessary books. 1.3. DOCUMENT CONVENTIONS: Manager - The person who has the full authority over the system. He can view all registered users. Customer-The person who registers and obtains books from the Book bank. Book Bank-The entire System comprising of the customers, manager, staff and other elements. 1.4. REFERENCES: www.rec.in 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient book bank registration process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the customers register and get books. The back end is managed by the manager effectively. 2.3 TOOLS TO BE USED Rational Rose

3. SYSTEM FEATURES 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the customers to know the procedure to enrol l in a book bank. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the customer details are validated he is enquired of his book preferences and the books are issued. 3.1.3 FUNCTIONAL REQUIREMENTS: REQ1: Only registered customers can apply for issue of books. REQ2: The books need to be available in order to be issued. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Seperate and unique ids must be provided for each and every user so that no user can access the resources available to other users.

GANTT CHART:

USE-CASE DIAGRAMS:

classdiagram

SEQUENCE-DIAGRAM: Borrow books:

Return books:

ACTIVITY DIAGRAM:
member faculty Bood bank system

search books

Fill up the application form

get member card

Update transaction

Enter return date

Issue book

COLLABORATION DIAGRAM: Borrow books:

1: Presents Member Card and books :Member :Faculty of Book Bank

6: Dispaly Due Date 7: Invalid Member Card

4: getBookDetails(bookid) 2: Enter member Details 3: Enter Book Details 5: Update Transaction :System :Book Catalog

Return books:

1: Return Books 6: Pay fine :Member 7: Return Member Card :Faculty of Book Bank

5: Dispaly fine amount 3: Check return date 4: Check Fine Status 2: Enter Book Details

8: Update Transaction :System :Book Catalog

STATE CHART DIAGRAM: Borrow books:

Return books:

PACKAGE DIAGRAM:

DEPLOYMENT DIAGRAM:

COMPONENT DIAGRAM:

RESULT: Thus the UML diagrams for Book Bank was developed and verified. EXPT NO: DATE: Problem Statement Passport Automation System is used in the effective dispatch of passport to all of the applicants. This system adopts a comprehensive approach to minimize the manual work and schedule resources, time in a cogent manner. The core of the system is to get the online registration form (with details such as name, address etc.,) filled by the applicant whose testament is verified for its genuineness by the Passport Automation System with respect to the already existing information in the database. This forms the first and foremost step in the processing of passport application. After the first round of verification done by the system, the information is in turn forwarded to the regional administrator's (Ministry of External Affairs) office. The application is then processed manually based on the report given by the system, and any forfeiting identified can make the applicant liable to penalty as per the law. The system also provides the applicant the list of available dates for appointment to 'document verification' in the administrator's office, from which they can select one. The system forwards the necessary details to the police for its separate verification whose report is then presented to the administrator. The administrator will be provided with an option to display the current status of application to the applicant, which they can view in their online interface. After all the necessary criteria has been met, the original information is added to the database and the passport is sent to the applicant.

Passport Automation System

Software Resource Specification 1.0 Introduction Passport Automation System is an interface between the Applicant and the Authority responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of Passport and reduce the complexities involved in it to the maximum possible extent. 1.1 Purpose If the entire process of 'Issue of Passport' is done in a manual manner then it would take several months for the passport to reach the applicant. Considering the fact that the number of applicants for passport is increasing every year, an Automated System becomes essential to meet the demand. So this system uses several programming and database techniques to elucidate the work involved in this process. As this is a matter of National Security, the system has been carefully verified and validated in order to satisfy it. 1.2 Scope The System provides an online interface to the user where they can fill in their personal details and submit the necessary documents (may be by scanning). The authority concerned with the issue of passport can use this system to reduce his workload and process the application in a speedy manner. Provide a communication platform between the applicant and the administrator. Transfer of data between the Passport Issuing Authority and the Local Police for verification of applicant's information. Users/Applicants will come to know their status of application and the date in which they must subject themselves for manual document verification.

2.0 Overall Description 2.1 Product Perspective The PAS acts as an interface between the 'applicant' and the 'administrator'. This system tries to make the interface as simple as possible and at the same time not risking the security of data stored in.This minimizes the time duration in which the user receives the passport. 2.4 System Functions Secure Registration of information by the Applicants. Schedule the applicants an appointment for manual verification of original documents. Panel for Passport Application Status Display by the Administrator. SMS and Mail updates to the applicants by the administrator. Administrator can generate reports from the information and is the only authorized personnel to add the eligible application information to the database. 2.5 User Characteristics Applicant - They are the people who desires to obtain the passport and submit

the information to the database. Administrator - He has the certain privileges to add the passport status and to approve the issue of passport. He may contain a group of persons under him to verify the documents and give suggestion whether or not to approve the dispatch of passport. Police - He is the person who upon receiving intimation from the PAS, perform a personal verification of the applicant and see if he has any criminal case against him before or at present. He has been vetoed with the power to decline an application by suggesting it to the Administrator if he finds any discrepancy with the applicant. He communicates via this PAS. 2.6 Constraints The applicants require a computer to submit their information. Although the security is given high importance, there is always a chance of intrusion in the web world which requires constant monitoring. The user has to be careful while submitting the information. Much care is required. 2.7 Use Case Model Description 2.8 Assumptions and Dependencies The Applicants and Administrator must have basic knowledge of computers and English Language. The applicants may be required to scan the documents and send.

GANTT CHART:

USE CASE DIAGRAM

CLASS DIAGRAM

SEQUENCE DIAGRAM: ADMIN

SEQUENCE DIAGRAM:CHECK STATUS

SEQUENCE DIAGRAM : REGISTER

ACTIVITY DIAGRAM :ADMIN

ACTIVITY DIAGRAM: REGISTER

ACTIVITY DIAGRAM: CHECK STATUS

COLLABORATION DIAGRAM:ADMIN PANEL

COLLABORATION DIAGRAM: APPLICATION

COLLABORATION DIAGRAM: CHECK STATUS

PACKAGE DIAGRAM:

STATECHART: ADMIN PANEL

STATECHART: CHECK STATUS

STATE CHART: REGISTER

COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

RESULT: Thus the UML diagrams for Passport Automation System was developed and verified.

EXPT NO: DATE:

Exam Registration

PROBLEM STATEMENT The exam registration system allows the students to register for their exams. The administration of the university also can get the list of registered students with all their information. Once the student registers he/she receives an id, which helps him in further correspondence. A fees amount is received from the students for registration. This system makes the task of the students easier rather than waiting in queue for enrollment. This also reduces the time consumption for both for the students and administration. SOFTWARE REQUIREMENT SPECIFICATION 1. INTRODUCTION: This project aimed at developing a web-based exam registration system by storing application data and relevant information about the registered students. 1.1 PURPOSE: Registering for examinations is a tedious process for both the adminstration as well as the students. This system is specially designed to reduce the difficulty of students in registering for their examination.

1.2. SCOPE: This system helps the both the adminstration and the students to finish their work with more ease. 1.3. DOCUMENT CONVENTIONS: Administrator - The person who has the full authority over the system. He can view all registered students. Students - the person who registers in the system in search of jobs.. 1.4. REFERENCES: www.gre.org 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient exam registration. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the students do their enrollment. The back end is managed by the administrator effectively 2.3 TOOLS TO BE USED Rational Rose Enterprise Edition 3. SYSTEM FEATURES 3.1 REGISTERING FOR EXAMINATION: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the job seeker to apply for job. 3.1.2 FUNCTIONAL REQUIREMENTS: REQ1: Only registered users can register for examination. REQ2: The administrator has the right to recruit the candidates, not the system. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS:

Password for registered accounts are stored securely in a hash, the uploads made by the user must be checked and then accepted.

GANTT CHART:

USECASE DIAGRAM:

CLASS DIAGRAM

SEQUENCE DIAGARAM:

COLLABORATION DIAGRAM:

PACKAGE DIAGRAM:

ACTIVITY DIAGRAM:

ACTIVITY DIAGRAM:

STATECHART:

STATECHART:

COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

RESULT: Thus the use case diagrams for Exam Registration was developed and verified. EX-NO: DATE :

ONLINE COURSE REGISTRATION SYSTEM

PROBLEM STATEMENT:

All the processes involved in the course registration system are computerized. It must contain all the details about: Student, Course offerings, Registering a course, Availability of courses, Eligibility for Admission. This registration system enables the admission of candidates into the institution on the basis of their educational and social background.. The candidate has to register their desired branch from the available courses. The registration must include the following details: Application No, Student information, Course selected, course Availability, Eligibility. If a student wishes to change his/ her course, then the schedule is updated. If course is available then the change of course is permitted and changed, else include it in waiting list. To update a schedule, the student needs to be logged in. Then the student can select any other course from the available list of courses. And the schedule is submitted. If a student wishes to cancel his/her course, the students current schedule is retrieved and displayed first. Then the system prompts the user to confirm the deletion of schedule. If confirmed, the student is removed from the course offerings. SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION: This project is aimed at developing a Course Registration system by creating details about customers and the available courses.

1.1 PURPOSE: Manual maintenance of customer details is a tedious process considering the to the large number of customers. Hence, this system is used for easy registration and maintenance of database.

1.2. SCOPE: The Course Registration is used to specify a certain procedure to the customers for quick and hassle free registration of courses.

1.3. DOCUMENT CONVENTIONS: Manager - The person who has the full authority over the system. He can view all registered users.

Customer-The person who registers and gets registered.

1.4. REFERENCES: www.google.com

2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient online course registration process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the customers register and online courses. The back end is managed by the manager effectively. 2.3 TOOLS TO BE USED Rational Rose 3. SYSTEM FEATURES 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the customers to know the procedure to find the courses. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the customer details are validated he is enquired of his course preferences and the details about the courses are issued. 3.1.3 FUNCTIONAL REQUIREMENTS: REQ1: Only registered customers can apply for details of the courses. REQ2: The courses need to be available in order to be issued.

4. OTHER NON-FUNCTIONAL REQUIREMENTS:

4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Seperate and unique ids must be provided for each and every user so that no user can access the resources available to other users. 4.4 SYSTEM REQUIREMENTS Processor : Pentium IV 1.7 RAM : 128 MB Hard Disk : 40 GB 4.5 SOFTWARE REQUIREMENTS case tool : rational rose

GANTT CHART:

UMLDIAGRAMS

USECASE DIAGRAM:

V ie w c o u rs e s S TU D E N T R e g is t e r c o u r s e in c lu d e s e x te n d s

< < A c t o r> > R E G IS T R A T IO N D A T A B A S E

ee C h e c k c o u rs e a va ilaFbrili t y re g is t ra t io n

C a n c e l c o u r s e C h a n g e c o u rs e S Y S T E M A D M IN

< < A c t o r> > COURSE C A TA LO G

U p d a te c o u rs e

C h e c k e lig ib il it y

CLASS DIAGRAM:

ACTIVITY DIAGRAM:

STUDENT

REGISTRATION SYSTEM

Complete application

application

Check course availability

<<datastore>> courses

else

if available

<<datastore>> applications

Choose alternate course

accept/deny

Check applicant qualification

<<datastore>> students

SEQUENCE DIAGRAM:

s tu d e n t 1 .b r o w s ec o u r s e

u n iv e r s ity

c e n tr a lm a n a g e m e n t s y s te m

2 .s e le c tc o u r s e

3 .c h e c ka v a ila b ility

4 .a v a ila b le

5 .r e g is te r

6 .s u b m it d e ta ils

7 .v e r if yd e ta ils

8 .is s u ea p p r o v a l 9 .p a yf e e

1 0 .e n r o ll

COLLABORATION DIAGRAM:

1: browse course 2: select course student

5: register

6: submit details

9: pay fees universit y

10: enroll 3: check availability 7: verity details 8: issue approval 4: availability

cetral management

STATECHART

DIAGRAM:

PACKAGE DIAGRAM:

User Interface

Domain Forms Report Course

Student

Registration

College

Technical Services

Database

Logging

DEPLOYMENT DIAGRAM:

student universit y

central man...

COMPONENT DIAGRAM:

univers ity

student

central management

RESULT:Thus the domain model with UML diagrams for the Course Registration System have been developed and verified. EXPT NO:

RECRUITMENT SYSTEM

DATE:

PROBLEM STATEMENT: The recruitment system allows the job seekers to enroll their names through the process of registration. The employee also can get the list of available candidates and shortlist for their company requirement. Once the applicant enrolls he receives an id, which helps him in further correspondence. A fees amount is received from the job seekers for enrollment. This system makes the task of the job seeker easier rather than waiting in queue for enrollment. This also reduces the time consumption for both for the job seeker and employee. SOFTWARE REQUIREMENT SPECIFICATION 1. INTRODUCTION: This project aimed at developing a web-based recruitment system by creating details about vacancies, storing application data and interview process initiation. 1.1 PURPOSE: Manual recruitment is a tedious processing to the increasing number of job seekers. People around the world can apply for the online recruitment system and it is very convenient too. This system is specially designed for those seek the most demanding job and challenging positions in their own field. 1.2. SCOPE: Recruitment system allows the job seekers to find their dream job in the chosen field. This system helps the companies to recruit the right candidate for the job. This system serves as a common meeting ground for job seekers and employees, both locally and globally. 1.3. DOCUMENT CONVENTIONS: Administrator - The person who has the full authority over the system. He can view all registered users. Job Seekers - the person who registers in the system in search of jobs. Company - A company can register itself, select the required employees and provide information about the result. 1.4. REFERENCES: www.timesjob.com: 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient recruitment process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the visitors or job seekers do their enrollment. The back end is managed by the administrator effectively 2.3 TOOLS TO BE USED

Rational Rose 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the job seeker to apply for job. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the job seeker uploads his resume, the list of jobs matching the resume will be posted. 3.1.3 FUNCTIONAL REQUIREMENTS: REQ1: Only registered users can apply for the job. REQ2: The Company has the right to recruit the candidates, not the system. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Password for registered accounts are stored securely in a hash, the uploads made by the user must be checked and then accepted. GANTT CHART:

USE CASE

DIAGRAM

CLASS DIAGRAM

SEQUENCE DIAGRAM: REGISTER

SEQUENCE DIAGRAM: STATUS

SEQUENCE DIAGRAM:ADMIN PANEL

ACTIVITY DIAGRAM:

REGISTER:

ACTIVITY DIAGRAM: CHECK STATUS

ACTIVITY HR ENTRY

DIAGRAM: STATUS

COLLOBORATION DIAGRAM: REGISTER

COLLOBORATION DIAGRAM: STATUS

COLLOBORATION DIAGRAM : ADMIN PANEL

PACKAGE DIAGRAM:

DEPLOYMENT DIAGRAM:

COMPONENT DIAGRAM:

RESULT: Thus the UML diagrams for Recruitment system was developed and verified.
EXPT NO:

SOFTWARE PERSONNEL MANAGEMENT

SYSTEM
DATE:

PROBLEM STATEMENT: A SOFTWARE PERSONNEL MANAGEMENT SYSTEM refers to the systems and processes at the intersection between human resource management (HRM) and information technology. It merges HRM as a discipline and in particular its basic HR activities and processes with the information technology field, whereas the programming of data processing systems evolved into standardized routines and packages of enterprise resource planning (ERP) software. The linkage of its financial and human resource modules through one database is the most important distinction to the individually and proprietary developed predecessors, which makes this software application both rigid and flexible.

SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION: This project which aims to efficiently manage the personnel details of a software company which includes payroll details and other important functions. 1.1 PURPOSE: The HR function consists of tracking existing employee data which traditionally includes personal histories, skills, capabilities, accomplishments and salary. Also, each employee can access his/her own profile, that lets him view his salary, attendance and company related updates.

1.2. SCOPE: The scope of the Software Personnel Management System is that it allows the HR to view the entire employee Database conveniently and make updates. Similarly from an employee point of view, he/she can be able to view company related information easily.

1.3. DOCUMENT CONVENTIONS: Employees can view their personal details and other company information. They can send messages to any other employee of the organization. The HR has more features. He can view entire employee database, make payroll updates etc.

1.4. REFERENCES: www.infosys.com

2 OVERALL DESCRIPTIONS:

2.1 PRODUCT PERSPECTIVE:

This project is a self-contained project for convenient Software Personnel Management System.

2.2 PRODUCT FUNCTIONS: The front end of the project is where the HR or employee can login. The back end is managed by the organization database effectively.

2.3 TOOLS TO BE USED Rational Rose Enterprise Edition, Argo UML

3. SYSTEM FEATURES

3.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the employee to view his profile.

3.2 STIMULUS AND RESPONSE SEQUENCE: When the employee logs in, his or her personal details are displayed.

4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load.

4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking.

4.3SECURITY REQUIREMENTS: The employee is given a user id and password to ensure safety of personal information.

GANTT CHART:

UML USE-CASE DIAGRAM

Recruit

Training

HR Curriculum Vitae Monitor Employees Provide salary increment Motivate Recruit() Monitor() Increment() Motivation()

Salary

Employee Commitment Bank Accounts Regularity Training() Salary() Performance()

Monitor

Performance

Increment

Time Management

Motivation

UML CLASS DIAGRAM

HR C u rric u lu m Vita e M o n ito r E m p lo ye e s P r o vid e s a l a ry in c re m e n t M o ti va te R e c ru i t() M o n ito r() In c re m e n t() M o ti va tio n () E m p lo ye e C o m m itm e n t B a n k A c c o u n ts R e g u la rity T ra i n in g () S a la ry( ) P e rfo rm a n c e ()

T ra i n in g D e a tils P r o vid e e d u c a te d tra i n e e s T ra in in g ()

S a la r y D e ta ils c re a te b a n k Ac c o u n t to d e p o s i t s a l a ry s a la r y( )

ti m e m g m e n t tim e p e rio d o b s e rve d a c c o r d in g to tr a in in g d e ta i ls tim e m a n a g e m e n t()

UML SEQUENCE DIAGRAM

E m p lo ye e

HR

Tra in in g d e ta ils U p d a te S a la ry D e tails

S a la ry D e ta ils

Vie w S a la ry D e ta ils Tra in in g In fo rm atio n Tra in in g U p d a te P e rfo rm an ce Tra in in g Pe rio d Sa la ry In cre m e n t

UML ACTIVITY DIAGRAM

HR Login

Employee Name

Performance &Attendence

Fixed Salary

Salary Increment

HR Logout

UML COLLABORATION DIAGRAM

5 : P e rfo r m a n c e

3 : T ra in i n g In fo r m a ti o n E m p lo ye e : < A c to r H R : < Ac to r N a m e > Nam e> 2 : V ie w S a l a r y D e ta i ls 1 : U p d a te S a la r y D e ta il s 6 : T ra in i n g P e rio d 4 : T ra in i n g U p d a te 7 : S a la ry In c r e m e n t

T ra i n in g d e ta ils

S a la r y D e ta i ls

STATECHART:

P r o vid e In c r e m e n t

L o g in

E n te r E m p l o y e e C h e c k P e r f o r m a n c e Nam e a n d A tt e n d e n c e

Logout

D o n o t P ro vid e In c r e m e n t

PACKAGE DIAGRAM:

UML COMPONENT DIAGRAM

HR

P ro vid e s E m p lo ye e a n d H R w ith th e s a la ry d e ta ils S a la ra y D e ta ils

H u m a n R e s o u rc e s in vo lve s re c ru itm e n t,m o tiva tio n , m o n ito rin g o f e m p lo ye e s

p ro vid e s e m p lo ye e s w ith tra in in g d e ta ils w h ic h is u p d a te d by HR

T ra in in g D e ta ils

E m p lo ye e

e m p lo ye e s a re th o s e w h o a re re c u rtite d b y H R a n d w o rk fo r th e res p e c tive co m p a n y

UML DEPLOYMENT DIAGRAM

HR

H R r e c u r i ts th e e m p l o y e e fo r a g i v e n com pany

p r o v id e s e m p l o y e e w i th s a la r y d e t a i ls

S a la r y D e ta i l s

T r a i n in g D e a ta i l s

T ra in in g P e rio d is g i v e n to th e e m p l o y e e w i th tr a i n i n g p e r i o d

E m p lo ye e

E m p l o y e e r e c u r i te d b y H R U n d e rg o e s tr a i n in g b e fo r e a c tu a l l y w o r k i n g

RESULT: Thus the UML diagrams for Software Personnel Management System was developed and verified.

EXPT NO: DATE:

STOCK MAINTENANCE SYSTEM

PROBLEM STATEMENT The Stock maintenance system which allows the administrator to display the product details, purchase details, sales details, stock details, and the purchase the products. The customer which is used to purchase the product. The supplier who use to supply the product. Once they enter the login details the verifier check the details of availability and says whether the login is valid or not. Then enter the stock details, maintain and store it. SOFTWARE REQUIREMENT SPECIFICATION 1. INTRODUCTION: This project aimed at developing a web-based stock maintenance system by creating details about product, purchase, sales and stock details. 1.1 PURPOSE: This stock maintenance system which is used to say exactly how much product is in the stock and how much product is got saled. This also helps that how to purchase the product and how to supply the product. 1.2. SCOPE: The stock maintaining system which implements that how to supply and get increament in the sales. Before getting the demand of the particular product it is getting stocked so that in the demand period we can easily attain that product. 1.3. DOCUMENT CONVENTIONS: Administrator - The person who has the full authority over the system. He can view all registered users. Customer- The person who is going to purchase the product. Supplier- The person who is going to supply the product. 1.4. REFERENCES: www.stock maintain.com: 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient stock maintenance system process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the customers or suppliers do their enrollment. The back end is managed by the administrator effectively.

2.3 TOOLS TO BE USED Rational Rose 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the customer to purchase the product. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the administrator confirm the details of the stock, they will supply to the market. So the supplier and the customer can get the advantage of the product. 3.1.3 FUNCTIONAL REQUIREMENTS: REQ1: Only the administrator can be able to refer the stock details. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance of the stock, the supplier should have the quality products. 4.2 SAFETY REQUIREMENTS: The stock should be maintained carefully without any damage. GANTT CHART:

USECASE DIAGRAM:

Order Cancellation Customer

Placing Order Quotation <<include>> Sales Manager

Stock Level Checking

Maintain Product Details <<Actor>> Manufacturer Maintain Purchase Details

<<Actor>> Shipper

Purchase the Product

<<Actor>> Bank Account

Return Item

Billing Process

CLASS DIAGRAM:

SEQUENCE DIAGRAM:

SEQUENCE DIAGRAM:

ACTIVITY DIAGRAM:

L O G I N

A N A L Y S I S

S T O C K N E E D E D

L I S T P R E P A R A T I O N

O L D S T O C K

E X P I R E D S T O C K Q U O T A T I O N S E L L

P U R C H A S E A N D P A Y M E N T

U P D A T E

customer

stock manager

stock maintenance system

stock

view catalog

place order to stock manager

Enter id

Ask for password

Enter password valid

invalid check for stock availability no

preorder

Alert for stock availability

yes

link details

issue bill

paybill

update details of stock

pack item

Deliver item

STATE CHART DIAGRAM:

OLD S TO C K

SELL L O G IN A N A L Y S IS STO C K NEEDED

L IS T P R E P A R A T IO N

Q U O T A T IO N

P U R C H AS E AN D P AYME N T

U P D ATE

E X P IR E D STO C K

COLLABORATION DIAGRAM:

S TO C K M AN AG E R

4 : G IV E Q U O T A T IO N 6 : D E L IV E R Y O F G O O D S C U STO MER 3: OR D ER FO R G OO D S 5 : P AYM E N T

7 : O R D E R F O R G O O D S N E E D E D A N D P A Y F O R IT

2 : A P P R O V E T H E L O G IN 9 : U P D A T A T IO N O F G O O D S D E T A I L S

8 : D E L IV E R Y O F P R O D U C T S

A D M I N IS T R A T 1 : L O G IN OR

C O M P AN Y

PACKAGE DIAGRAM:

UML COMPONENT DIAGRAM:

SMS Techn ical services

SMS Domain

SMS UI

UML DEPLOYMENT DIAGRAM:

Keyboar d

Mouse Node 1: Sto... Monitor

Printer

RESULT: Thus the UML diagrams for Stock Maintenance System was developed and verified.