SOFTWARE ENGINEERING LAB MANUAL

TASK 1: Passport Automation System

AIM: To create an automated system to perform the Passport Process

PROCEDURE: (I) 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 have been met, the original information is added to
the database and the passport is sent to the applicant.

Page 1
SOFTWARE ENGINEERING LAB MANUAL

(II) SOFTWARE REQUIREMENT SPECIFICATION:

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 reduces the complexities involved
in it to the maximum possible extent.

Page 2
SOFTWARE ENGINEERING LAB MANUAL

PURPOSE
If the entire process of 'Issue of Passport' is done in a manual manner
then it would takes 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.

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.

Page 3
SOFTWARE ENGINEERING LAB MANUAL

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS

 Administrator
Refers to the super user who is the Central Authority with the privilege to
manage the entire system. It can be any higher official in the Regional
Passport Office of Ministry of External Affairs.
 Applicant
One who wishes to obtain the Passport.
 PAS
Refers to this Passport Automation System.

 HTML
Markup Language used for creating web pages.
 J2EE
Java 2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.
 HTTP
Hyper Text Transfer Protocol.

 TCP/IP
Transmission Control Protocol/Internet Protocol is the communication
protocol used to connect hosts on the Internet.

Page 4
SOFTWARE ENGINEERING LAB MANUAL

TECHNOLOGIES TO BE USED
• HTML
• JSP
• JavaScript
• Java

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW

SRS includes two sections overall description and specific requirements

Overall Description will describe major role of the system components and
inter- connections.

Specific Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION

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.

Page 5
SOFTWARE ENGINEERING LAB MANUAL

SOFTWARE INTERFACE

• Front End Client - The applicant and Administrator online

interface is built using JSP and HTML. The Administrator’s local
interface is built using Java.
• Web Server – Apache Tomcat application server (Oracle
Corporation).
• Back End – Oracle11g database.

HARDWARE INTERFACE

The server is directly connected to the client systems. The client systems
have access to the database in the server.

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.

Page 6
SOFTWARE ENGINEERING LAB MANUAL

USER CHARACTERISTICS

 Applicant
These are the person 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 theAdministrator if
he finds any discrepancy with the applicant. Hecommunicates via this
PAS.

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.

Page 7
SOFTWARE ENGINEERING LAB MANUAL

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.

(III) USECASE DIAGRAM:

The Passport Automation system use cases are:
1. Login
2. Registration
3. Verification
4. Check status
5. Enquiry
6. Dispatch Passport

ACTORS INVOLVED:
1. Applicant
2. Passport Officer
3. Police

USE-CASE NAME: LOGIN

The applicant login to the system to obtain a passport

USE-CASE NAME: REGISTRATION

The Applicant enters his name and details for applying a Passport .The
applicant initially give his/ her details for registration.

Page 8
SOFTWARE ENGINEERING LAB MANUAL

USE-CASE NAME: VERIFICATION

The system verifies the applicant mandatory information given by him/her.

USE-CASE NAME: CHECK STATUS

The Applicant tries to check the status in which category applied. The system
displays the message to the applicant.

USE-CASE NAME: ENQUIRY

The police receive 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.

USE-CASE NAME: DISPATCH PASSPORT

The administrator check or process the application which are submitted by
applicant .Process the application means the data which are given by the
applicant is processed to create a passport for the applicant and finally
dispatches the passport to the applicant

Page 9
SOFTWARE ENGINEERING LAB MANUAL

dispatch passport

Fig.1. USECASE DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

ACTIVITY DIAGRAM:
The activity diagram represents the series of activities that are occurring
between the objects. Following is activity diagram which represents the
Software personnel management system process.

Page 10
SOFTWARE ENGINEERING LAB MANUAL

Fig.2. ACTIVITY DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

CLASS DIAGRAM:
The class diagram is referred as object modeling in the static analysis diagram.
The main task of object modeling is to graphically show what each object will
do in the problem domain. The problem domain describes the structure and
the relationships among objects.

Page 11
SOFTWARE ENGINEERING LAB MANUAL

The Passport Automation system class diagram consists of five classes

1. Login class
2. Appointment class
3. Registration class
4. Authority class
5. Verification class

1) LOGIN CLASS:

It consists of two attributes and two operations. The attributes are user
name, and password. The operations of this class are creating login ( ), sign in
( ).

2) APPOINMENT CLASS:

The attributes of this class are appointment id, applicant id, date, time,
and description. The operation of this class are get appointment ( ), get
appointment status ( ), Modify ( ), cancel ( ).

3) REGISTRATION CLASS:

The attributes are applicant id, name, dob, gender, birthplace, father
name, addr1, addr2, district, state, country, pin code, mobile, email id,
qualification. The operation are add ( ), modify( ), view( ).

Page 12
SOFTWARE ENGINEERING LAB MANUAL

4) AUTHORITY CLASS:

The attributes of this class are officered, name, designation, and

password. The operations are search( ).

5) VERIFICATION CLASS:

The attributes of this class are verification id, appointment id,

applicant id, officer id, status id, description. The operation are verify( ).

Fig.3.CLASS DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

Page 13
SOFTWARE ENGINEERING LAB MANUAL

INTERACTION DIAGRAM:
 A sequence diagram represents the sequence and interactions of a
given USE-CASE or scenario. Sequence diagrams can capture most of
the information about the system.
 Most object to object interactions and operations are considered events
and events include signals, inputs, decisions, interrupts, transitions and
actions to or from users or external devices.
 An event also is considered to be any action by an object that sends
information.
 The event line represents a message sent from one object to another,
in which the “form” object is requesting an operation be performed
by the “to” object. The “to” object performs the operation using a
method that the class contains.
 It is also represented by the order in which things occur and how the
objects in the system send message to one another.
 The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about passport
automation system are given

Page 14
SOFTWARE ENGINEERING LAB MANUAL

UI LoginClass
LoginClass RegistrationClass
RegistrationClass AppointmentClass
AppointmentClass Database
Database
: applicant

Create Login

Signin

get use name/pwd

how Registration Form

Enter applicant information

check a plicant information

save applicant information

get date and time

save date and time

show time

Fig.4.SEQUENCE DIAGRAM FOR LOGIN AND VERIFICATION

Page 15
SOFTWARE ENGINEERING LAB MANUAL

5: Check username/Pwd
12: Check username/Pwd

1: Create Login
3: Enter Username/Pwd
9: Signin 4:
14: Enter applicant information LoginCla
UI
ss

2:
8:
: applicant 13: show Registration Form 10: get username/pwd
24: shows applicant ID, Date & time
6: save username/pwd
23: 7:
11:

15: Databas
16: check applicant information e

17: save applicant information

20: save date and time

Registratio 18:
nClass 19: get date and time
21:

22: Appointme
ntClass

Fig.5.COLLABORATION DIAGRAM FOR LOGIN AND VERIFICATION

 The diagrams show the process done by the Passport Authority to the
Passport Automation system. The applicant has to enter his details.
 The details entered are verified by the Passport Authority and the
applicant is approved if the details match then the passport is dispatch,
otherwise an appropriate error message is displayed.

STATE CHART DIAGRAM:

 Every object undergoes through some state and on receiving some

event the state gets changed. This transition of the state can be
represented by the state transition diagram.

Page 16
SOFTWARE ENGINEERING LAB MANUAL

Fig.6.STATE CHART DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.

Page 17
SOFTWARE ENGINEERING LAB MANUAL

Fig.7.DEPLOYMENT DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships
among components in a system.

Fig.8.COMPONENT DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

Page 18
SOFTWARE ENGINEERING LAB MANUAL

TASK 2: BOOK BANK SYSTEM

AIM: To create a system to perform book bank operation

PROCEDURE: (I) PROBLEM STATEMENT:

A Book Bank lends books and magazines to member, who is registered

in the system. Also it handles the purchase of new titles for the Book Bank.
Popular titles are brought into multiple copies. Old books and magazines are
removed when they are out or date or poor in condition. A member can reserve
a book or magazine that is not currently available in the book bank, so that
when it is returned or purchased by the book bank, that person is notified. The
book bank can easily create, replace and delete information about the tiles,
members, loans and reservations from the system.

(II) SOFTWARE REQUIREMENTS SPECIFICATION:

INTRODUCTION

Book Bank is the interface between the students and Librarian. It aims at
improving the efficiency in the Issue of books or magazines and reduce the
complexities involved in it to the maximum possible extent.

PURPOSE
If the entire process of 'Issue of Books or Magazines' is done in a manual
manner then it would take several months for the books or magazines to reach
the applicant. Considering the fact that the number of students forBook
Bank 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. Thesystem has been
carefully verified and validated in order to satisfy it.

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 books can use this system to reduce
his workload and process the application in a speedy manner.

Page 19
SOFTWARE ENGINEERING LAB MANUAL

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS

 Librarian - Refers to the super user who is the Central

Authority who has been vested with the privilege to
manage the entire system.

 Student - One who wishes to obtain the Books or Magazines.

 HTML - Markup Language used for creating web pages.

 J2EE - Java 2 Enterprise Edition is a programming platform

and it is the part of the java platform for developing and
running distributed java applications.

 HTTP -Hyper Text Transfer Protocol

 TCP/IP - Transmission Control

Protocol/Internet Protocol is the communication
protocol used to connect hosts on the Internet.

Page 20
SOFTWARE ENGINEERING LAB MANUAL

TECHNOLOGIES TO BE USED

 Visual Basic
 Oracle 11g

TOOLS TO BE USED

 Visual Basic Tools

 Rational Rose tool (for developing UML Patterns)

OVERVIEW

SRS includes two sections overall description and specific

requirements.

Overall description will describe major role of the system

components and inter- connections.

Specific requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION:

It will describe major role of the system components and inter-

connections.

PRODUCT PERSPECTIVE

The SRS acts as an interface between the 'Students' and the 'Librarian'.
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 books or magazines.

SOFTWARE INTERFACE

 Front End Client - The Student and Librarian online

interface is built using Visual studio.
 Back End - Oracle 11 g database

Page 21
SOFTWARE ENGINEERING LAB MANUAL

HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

SYSTEM FUNCTIONS

 Secure Registration of information by the Students.

 Librarian can generate reports from the information and is

the only authorized personnel to add the eligible application
information to the database.

USER CHARACTERISTICS

 Student - They are the people who desire to obtain the

books and submit the information to the database.
 Librarian - He has the certain privileges to add the books and
to approval of the reservation of books.

CONSTRAINTS

 The Students 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 Students has to be careful while submitting the
information. Much care is required.

ASSUMPTIONS AND DEPENDENCIES

 The Student and Librarian must have basic knowledge of

computers and English Language.
 The Students may be required to scan the documents and send.

(III) USE-CASE DIAGRAM:

The book bank use cases are:
1. book_issue
Page 22
SOFTWARE ENGINEERING LAB MANUAL

2. book_return
3. book_order
4. book_entry
5. search book_details

ACTORS INVOLVED:
1. Student
2. Librarian
3. Vendor

USECASE NAME : SEARCH BOOK_DETAILS

The librarian initiates this use case when any member returns or
request the book and checking if the book is available.
Precondition: The librarian should enter all Book details.
Normal Flow: Build message for librarian who search the book.
Post Condition: Send message to respective member who reserved the book.

USECASE NAME : BOOK_ISSUE

Initiated by librarian when any member wants to borrow the desired
book. If the book is available, the book is issued.
Precondition: Member should be valid member of library.
Normal Flow: Selected book will be issued to the member.
Alternative Flow: If book is not available then reserved book use case should
be initiate.
Post Condition: Update the catalogue.

Page 23
SOFTWARE ENGINEERING LAB MANUAL

USECASE NAME : BOOK_ORDER

Initiated by librarian when the requested book is not available in the

library at that moment. The book is reserved for the future and issued to
the person when it is available.
Precondition: Initiated only when book is not available.
Normal Flow: It reserved the book if requested.
Post Condition : Mention the entry in catalogue for reservation.

USECASE NAME : BOOK_RETURN

Invoked by the librarian when a member returns the book.
Precondition: Member should be valid member of library.
Normal Flow: Librarian enters bookid and system checks for return date
of the book. Alternative Flow: System checks for return date and if it
returned late fine message will be displayed.
Post Condition: Check the status of reservation.

USECASE NAME : BOOK_ENTRY

The purchase book use-case when new books invoke it or magazines are
added to the library.

Precondition: Not available or more copies are required.

Normal Flow: Enter bookid, author information, publication
information, purchased date, prize and number of copies.
Post Condition: Update the information in catalogue.

Page 24
SOFTWARE ENGINEERING LAB MANUAL

book_order

Fig. 9. Use-Case Diagram For Book Bank System

Page 25
SOFTWARE ENGINEERING LAB MANUAL

ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the
business and operational step-by-step workflows of components in a system.
An activity diagram shows the overall flow of control. An activity is shown as
an rounded box containing the name of the operation.
This activity diagram describes the behaviour of the system.

Page 26
SOFTWARE ENGINEERING LAB MANUAL

Fig.11. Activity Diagram [ Order Book]

Page 27
SOFTWARE ENGINEERING LAB MANUAL

Fig.12. Activity Diagram [Return Book]

Page 28
SOFTWARE ENGINEERING LAB MANUAL

CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static
analysis diagram. The main task of object modeling is to graphically show
what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

The ATM system class diagram consists of four classes:

6. Student
7. Book
8. Issue
9. Return
10. Vendor
11. Details

1) STUDENT:

It consists of twelve attributes and three operations. The attributes are

enrollno, name, DOB, fathername, address, dept name, batch and book limits.
The operations of this class are addStInfo(), deleteStInfo(), modifyStInfo().

2) BOOK:

It consists of ten attributes and four operations. This class is used to

keep book information such as author, title, vendor, price, etc

3) ISSUE:

It consists of eight attributes and two operations to maintain issue

details such as, issue date, accno of issued book, name of the student
who borrowed book.

4) RETURN:

It consists of eight attributes and two operations to maintain issue

details such as, issue date, accno of issued book, name of the student
who borrowed book.

Page 29
SOFTWARE ENGINEERING LAB MANUAL

5) STUDENTS:

The attributes of this class are name, dept ,year ,bcode no The
operation is display students().

6) DETAIL:

The attributes of this class are book name, author, bcode no The
operations are delete details().

Page 30
SOFTWARE ENGINEERING LAB MANUAL

Fig.13. Class Diagram For Book Bank System

Page 31
SOFTWARE ENGINEERING LAB MANUAL

SEQUENCE DIAGRAM:

A sequence diagram represents the sequence and interactions of a

given USE-CASE or scenario. Sequence diagrams can capture most of the
information about the system. Most object to object interactions and
operations are considered events and events include signals, inputs, decisions,
interrupts, transitions and actions to or from users or external devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object to
another, in which the “form” object is requesting an operation be performed
by the “to” object. The “to” object performs the operation using a method
that the class contains.

It is also represented by the order in which things occur and how the
objects in the system send message to one another.

Page 32
SOFTWARE ENGINEERING LAB MANUAL
: student : librarian : issue : return search DB

1: request book

2: check available book

3: check available book

4: not avilable

5: not avilable

6: not available

7: request for another book

8: check availability

9: check availabilty

10: available

11: avilable

12: avilable

13: provide student details

14: enter issue data

15: update issue status

16: issue status update d

17: updated successfully

18: issue book

19: request to return book

20: enter the book details

21: update return status

22: return status updated

23: updated successfully

24: book returned

Fig. 14. Sequence Diagram For Book Issue & Return

Page 33
SOFTWARE ENGINEERING LAB MANUAL

1: request book
7: request for another book 14: enter issue data
13: provide student details
19: request to return book : issue
: librarian 17: updated successfully

6: not available

12: avilable 15: update issue statu

18: issue book

: student 24: book returned 16: issue status updated

2: check available book DB

8:check availability
23: updated successfully

20: enter the book details 5: not avilable

11: avilable
3: check available book
21: update return status
9: check availabilty

4: not avilable
22: return status updated
10: available

: return
search

Fig. 15. Collaboration Diagram For Book Issue & Return

Page 34
SOFTWARE ENGINEERING LAB MANUAL

STATE CHART DIAGRAM

It consists of state, events and activities. State diagrams are a familiar

technique to describe the behavior of a system. They describe all of the
possible states that a particular object can get into and how the object's state
changes as a result of events that reach the object

Fig. 16. State Chart Diagram

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are
deployed.

Page 35
SOFTWARE ENGINEERING LAB MANUAL

Fig.17. Deployment Diagram

Page 36
SOFTWARE ENGINEERING LAB MANUAL

TASK 3: Exam Registration System

AIM: To create a system to perform the Exam Registration system

PROCEDURE: (I) PROBLEM STATEMENT

Exam Registration system is used in the effective dispatch of registration form
to all of the students. 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, reg.no etc.,) filled by the student whose testament is verified for
its genuineness by the Exam Registration System with respect to the already
existing information in the database. This forms the first and foremost step in
the processing of exam application. After the first round of verification done
by the system, the information is in turn forwarded to the Exam Controller.
The application is then processed manually based on the report given by the
system. The system also provides the student the list of exam dates.The
controller will be provided with fees details to display the current status of
application to the student, 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 hall ticket is sent to the student.

(II) SOFTWARE REQUIREMENT SPECIFICATION:

INTRODUCTION

Exam Registration System is an interface between the Student and the Exam
Controller responsible for the Issue of Hall Ticket. It aims at improving the
efficiency in the Issue of Hall ticket and reduces the complexities involved in
it to the maximum possible extent.

PURPOSE
If the entire process of 'Issue of Hall ticket' is done in a manual manner
then it would takes several days for the hall ticket to reach the student.
Considering the fact that the number of students for hall ticket is increasing
every year, an Automated System becomes essential to meet the demand. So
this system uses several programming and database techniquesto elucidate
the work involved in this process. As this is a matter of National

Page 37
SOFTWARE ENGINEERING LAB MANUAL

Security, the system has been carefully verified and validated in order to
satisfy it.

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 controller concerned with the issue of hall ticket can use this system
to reduce his workload and process the application in a speedy manner.
 Provide a communication platform between the student and the
controller.
Students will come to know their status of application and the date in
which they must subject themselves for manual document verification.

Page 38
SOFTWARE ENGINEERING LAB MANUAL

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS
• Exam Controller - Refers to the super user who is the
Central Authority who has been vested with the privilege to
manage the entire system.
• Student - One who wishes to obtain the Hall Ticket.
• ERS - Refers to this Examination Registration System.
• HTML - Markup Language used for creating web pages.
• J2EE – Java 2 Enterprise Edition is a programming platform java
platform for developing and running distributed java applications.
• HTTP - Hyper Text Transfer Protocol.
• TCP/IP – Transmission Control Protocol/Internet Protocol
is the communication protocol used to connect hosts on the
Internet.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• JavaScript
• Java
•
TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific
requirements - Overall Description will describe major role of the
system components and inter-connections.
Specific Requirements will describe roles & functions of the actors.

Page 39
SOFTWARE ENGINEERING LAB MANUAL

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE

The ERS acts as an interface between the 'student' and the 'exam
controller'. 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 hall ticket.

SOFTWARE INTERFACE

 Front End Client - The exporter online interface is built using JSP
and HTML.
 Web Server – Apache Tomcat Server (Oracle Corporation)
 Back End - Oracle 11g database

HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

SYSTEM FUNCTIONS
• Secure Registration of information by the Students.
• SMS and Mail updates to the students by the controller.
• Controller can generate reports from the information and is the
only authorized personnel to add the eligible application information
to the database.

USER CHARACTERISTICS
• Student - They are the people who desire to obtain the hall ticket
and submit the information to the database.

Page 40
SOFTWARE ENGINEERING LAB MANUAL

• Exam controller - He has the certain privileges to add the

registration status and to approve the issue of hall ticket. He may
contain a group of persons under him to verify the documents and give
suggestion whether or not to approve the dispatch of hall ticket.

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.

ASSUMPTIONS AND DEPENDENCIES

• The Students and Exam Controller must have basic knowledge of
computers and English Language.
• The student may be required to scan the documents and send.

(III) USECASE DIAGRAM:

The Exam Registration use cases in our system are:
1. Login
2. View exam details
3. Register
4. Acknowledgement
5. Fee Processing

ACTORS INVOLVED:
1. Student
2. System DB

USE-CASE NAME: LOGIN

The student enters his username and password to login and retrieve the
information.

Page 41
SOFTWARE ENGINEERING LAB MANUAL

USE-CASE NAME: VIEW EXAM DETAILS

The student view the details about the exam schedule which contains Date,
time,etc...

USE-CASE NAME: REGISTER

The student should notify the fee details that only the student can pay the
correct amount.

USE-CASE NAME: ACKNOWLEDGEMENT

The exam fees should be paid by the student to get the hall ticket from the
exam controller.

USE-CASE NAME: FEE PROCESSING

All the details should be viewed by both the student and the controller to
verify whether all the entered details are correct.

Page 42
SOFTWARE ENGINEERING LAB MANUAL

<<include>>
Register

Fig.18. Use case Diagram For Exam Registration System

Page 43
SOFTWARE ENGINEERING LAB MANUAL

ACTIVITY DIAGRAM:

Fig.19. Activity Diagram For Exam Registration System

Page 44
SOFTWARE ENGINEERING LAB MANUAL

CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static
analysis diagram. The main task of object modeling is to graphically show
what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

The Exam Registration System class diagram consists of four two

classes of registration system.

6. Student_details
7. Exam_details
8. Register

1) STUDENT_DETAILS

It consists of six attributes and six operations. The attributes id,

password, name, age, sex, course. The operations of this class are login(),
logout(), conformation(), register(), newfeesdetails().

2) EXAM_DETAILS

It consists of four attributes and six methods. The attributes are

userid, password, examfees, fees due. The methods are login(),logout(),
feesdetails(), displayfees(), conformation(), examcontroller().

3) REGISTER
This class is used to maintain the registered student information such
as, subject registered, date of registration and etc,.

Page 45
SOFTWARE ENGINEERING LAB MANUAL

Fig.20. Class Diagram For Exam Registration System

Page 46
SOFTWARE ENGINEERING LAB MANUAL

INTERACTION DIAGRAM:

A sequence diagram represents the sequence and interactions of a

given USE-CASE or scenario. Sequence diagrams can capture most of the
information about the system. Most object to object interactions and
operations are considered events and events include signals, inputs, decisions,
interrupts, transitions and actions to or from users or external devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object to
another, in which the “form” object is requesting an operation be performed
by the “to” object. The “to” object performs the operation using a method that
the class contains.

It is also represented by the order in which things occur and how the
objects in the system send message to one another.

Page 47
SOFTWARE ENGINEERING LAB MANUAL

UI: Internet
Internet : Register
Register : Exam
Exam _details
_details
Explorer
: Student : System DB

enter(uid,pwd)

Store uid,pwd
Successfully stored

View exam details

Get exa m details

Get reg form

Fill registration form

ta

register

Store student details

return regid

Acknowledgement & iddisplay reg

Fig. 21.Sequence Diagram For Registration System

Page 48
SOFTWARE ENGINEERING LAB MANUAL

The sequence and collaboration diagram represents that the student enter the
information to get the hall ticket and the exam controller issues the hall ticket
after verifying the necessary items and this data are stored in the database.

Page 49
SOFTWARE ENGINEERING LAB MANUAL

:Exam_details

: System DB

: Student 1: enter(uid,pwd)4:Successfully stored 8:

6: View exam details
10: Get reg form
12: Fill registration form 7:Getexamdetails
16: Store student details 3: Store uid,pwd

17: return regid 2:Checkvalidation

5: 13:Checkgivendata
9:
11:
15: Verify criteria 19: Acknowledgement & display reg id

18: UI: Internet

Explorer
:Register
14: register

Fig. 21.Collaboration Diagram For Registration System

P a g e 50 | 165
SOFTWARE ENGINEERING LAB MANUAL

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are
deployed.

Fig.22. Deployment

Diagram

COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and relationships

among components in a system.

P a g e 51 | 165
SOFTWARE ENGINEERING LAB MANUAL

Fig.23.Component Diagram

P a g e 52 | 165
SOFTWARE ENGINEERING LAB MANUAL

TASK 4: Stock Maintenance

AIM: To create a system to perform the Stock maintenance

PROCEDURE: (I) PROBLEM STATEMENT

The stock maintenance system must take care of sales information of the
company and must analyze the potential of the trade. It maintains the number
of items that are added or removed. The sales person initiates this Use case.
The sales person is allowed to update information and view the database.

(II) SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
Stock maintenance is an interface between the customer and the sales
person. It aims at improving the efficiency in maintaining the stocks.
PURPOSE
The entire process of Stock maintenance is done in a manual manner
Considering the fact that the number of customers for purchase is increasing
every year, a maintenance system is essential to meet the demand. So this
system uses several programming and database techniques to elucidate the
work involved in this process.
SCOPE
• The System provides an interface to the customer where they can
fill in orders for the item needed.
• The sales person is concerned with the issue of items and can use this
system.
• Provide a communication platform between the customer and the
sales person.

P a g e 53 | 165
SOFTWARE ENGINEERING LAB MANUAL

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS
 Market Data provider: One who analyze the product and distribute
the news.
 Customer: One who takes order of product
 Sales person: One who maintains the stock details

TECHNOLOGIES TO BE USED
 Visual Studio
 VB Script

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific
requirements
Overall Description will describe major role of the system
components and inter- Connections
Specific Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
The Stock maintenance acts as an interface between the 'customer' and the
'sales person'. This system tries to make the interface as simple as possible and
at the same time not risking the work of data stored in

SYSTEM FUNCTIONS

• Secure order of information by the customer

• Schedule the customer an appointment for manual delivery of the
product.
P a g e 54 | 165
SOFTWARE ENGINEERING LAB MANUAL

USER CHARACTERISTICS

1. Customer: The person who orders for the item.

2. Validate customer: The items ordered by the customer are validated.
3. Sales Detail: Maintains the stock details after delivering the items to
the customer.

CONSTRAINTS
1. The customer should wait until the trade contractor and other to
analyze the product.
2. After the distribution of the news about the product. The
customer can take order and request of sales person to fill it.
3. Finally the sales person delivers the order.

(III) USE CASE DIAGRAM

The functionality of a system can be described in a number of different
use-cases, each of which represents a specific flow of events in a system. It is
a graph of actors, a set of use-cases enclosed in a boundary, communication,
associations between the actors and the use-cases, and generalization among
the use-cases.
The use cases used in this system are
1. Product details: Used for placing an order.
2. Purchase details: Used for tracking items that have been ordered.
3. sales details: Used for give the sales particulars about a item.
4. stock details: Used for give the stock detail in a shop.
5. Purchase the product: Used to provide bills for the customer.
P a g e 55 | 165
SOFTWARE ENGINEERING LAB MANUAL

6. supply the product: Used to give the order product to customer.

ACTORS
The actors used in this system are
1. Customer: The person who orders for the item.
2. Shopkeeper: The items ordered by the customer are validated.
3. Company: Maintains the stock details after delivering the items to
the customer.

P a g e 56 | 165
SOFTWARE ENGINEERING LAB MANUAL

product details

purchase details

shopkeeper customer
sales details

stock details

purchase the product

supply the product

company

Fig.24.Use Case Diagram

ACTIVITY DIAGRAM
It shows organization and their dependence among the set of
components. These diagrams are particularly useful in connection with
workflow and in describing behavior that has a lot of parallel processing. An
activity is a state of doing something: either a real-world process, or the
execution of a software routine.

P a g e 57 | 165
SOFTWARE ENGINEERING LAB MANUAL

login

order check
product availability

product stock
details

if available if not available

do
payment

cancle
order

get
payment

recive the
stock Fig.25. Activity Diagram

logout

CLASS DAIGRAM DESCRIPTION:

 A class diagram describes the type of objects in system and
various kinds of relationships that exists among them.
 Class diagrams and collaboration diagrams are alternate

P a g e 58 | 165
SOFTWARE ENGINEERING LAB MANUAL
representations of object models.
The Stock maintenance system class diagram consists of seven classes:

P a g e 59 | 165
SOFTWARE ENGINEERING LAB MANUAL

7. PurchaseDetails: One who takes orders for the product?

8. SalesDetails: The customer make an order for the required products.
9. Product Details: The items that are stored as stock.

Fig.26. Class Diagram

UML INTERACTION DIAGRAMS

It is the combination of sequence and collaboration diagram. It is used
to depict the flow of events in the system over a timeline. The interaction
diagram is a dynamic model which shows how the system behaves during
dynamic execution.

SEQUENCE DIAGRAM

A sequence diagram represents the sequence and interactions of a given USE-

CASE or scenario. Sequence diagrams can capture most of the information
about the system. Most object to object interactions and operations are
considered events and events include signals, inputs, decisions, interrupts,
transitions and actions to or from users or external devices.

P a g e 60 | 165
SOFTWARE ENGINEERING LAB MANUAL

An event also is considered to be any action by an object that sends information.

The event line represents a message from one object to another, in which the
“from” object is requesting an operation be performed by the “to” object. The
“to” object performs the operation using a method that the class contains.It is
also represented by the order in which things occur and how the objects in the
system send message to one another.

customer
customer shopekeeper
shopekeeper dealer
dealer database
database

check for product availability

. 6. product available

7. send for quation

8.request for delivery

11.product delivery

Fig.27. Sequence Diagram

P a g e 61 | 165
SOFTWARE ENGINEERING LAB MANUAL

COLLABORATION DIAGRAM
Collaboration diagram and sequence diagrams are alternate representations of
an interaction. A collaboration diagram is an interaction diagram that shows the
order of messages that implement an operation or a transaction. Collaboration
diagram is an interaction diagram that shows the order of messages that
implement an operation or a transaction. Collaboration diagramshows object s,
their links and their messages. They can also contain simple class instances and
class utility instances.
During, analysis indicates the semantics of the primary and secondary
interactions.Design, shows the semantics of mechanisms in the logical design
of system.

1: request for item

8: request for delivery
shopeke
custome eper
r
enter the details 11: product delivery
2:

7: send for quation update delivery details

9:
10: recording sales

sendforitem order item

3:

5: update product details

4: check foravailability
dealer databas e

6: product available
P a g e 62 | 165
SOFTWARE ENGINEERING LAB MANUAL
Fig.28. Collaboration Diagram

P a g e 63 | 165
SOFTWARE ENGINEERING LAB MANUAL

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Fig.29. Deployment
Diagram

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.

P a g e 64 | 165
SOFTWARE ENGINEERING LAB MANUAL

TASK 5: Online Course Reservation System

AIM: To create a system through which students can register to the courses
desired by them.

PROCEDURE: PROBLEM STATEMENT

The system is built to be used by students and managed by an
administrator. The student and employee have to login to the system before
any processing can be done. The student can see the courses available to
him/her and register to the course he/she wants. The administrator can
maintain the course details and view all the students who have registered to
any course.

(II) SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

Course Reservation System is an interface between the Student and the

Registrar responsible for the issue of Course. It aims at improving the
efficiency in the issue of Course and reduces the complexities involved in it to
the maximum possible extent.

PURPOSE

If the entire process of 'Issue of Course' is done in a manual manner then it

would takes several months for the course to reach the applicant. Considering
the fact that the number of applicants for course is increasing every year, an
Automated System becomes essential to meet the demand. So

P a g e 65 | 165
SOFTWARE ENGINEERING LAB MANUAL

this system uses several programming and database techniques to elucidate

the work involved in this process.

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 Registrar concerned with the issue of course can use this system
to reduce his workload and process the application in a speedy
manner.
 Provide a communication platform between the Student and the
Registrar.

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS

 Registrar
Refers to the super user with the privilege to manage the entire system.
 Applicant
One who wishes to register the Course
 OCRS
Refers to online Course Reservation System.
 HTML
Markup Language used for creating web pages.
 J2EE
Java 2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.
 HTTP

P a g e 66 | 165
SOFTWARE ENGINEERING LAB MANUAL

Hyper Text Transfer Protocol.

 TCP/IP
Transmission Control Protocol/Internet Protocol is the
communication protocol used to connect hosts on the Internet.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• Javascript
• Java

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements
Overall Description will describe major role of the system components and
inter- connections.
Specific Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE

The OCRS acts as an interface between the 'Student' and the 'Registrar'.
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 course.

P a g e 67 | 165
SOFTWARE ENGINEERING LAB MANUAL

SOFTWARE INTERFACE
• Front End Client - The Student and Registrar online interface is built
using JSP and HTML. The Administrators's local interface is built
using Java.
• Web Server – Tomcat Apache application server (Oracle
Corporation).
• Back End – Oracle 11g database.

P a g e 68 | 165
SOFTWARE ENGINEERING LAB MANUAL

HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems
have access to the database in the server.

SYSTEM FUNCTIONS
• Secure Reservation of information by the Students.
• SMS and Mail updates to the students by the Registrar
• Registrar can generate reports from the information and is the only
authorized personnel to add the eligible application information to the
database.

USER CHARACTERISTICS
• Applicant - They are the person who desires to obtain the course and
submit the information to the database.
• Administrator - He has the certain privileges to add the course
status and to approve the issue of course. He may contain a group of
persons under him to verify the documents and give suggestion
whether or not to approve the dispatch of course.

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.

P a g e 69 | 165
SOFTWARE ENGINEERING LAB MANUAL

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

(III) USE-CASE DIAGRAM:

The course registration system has the following use-cases
1. Login
2. View course details
3. Reserve for course
4. Pay fee
5. Check status

ACTORS INVOLVED:

1. Student
2. Registrar

USE-CASE NAME: LOGIN

The user enters the username and password and chooses if the user is student
or Registrar. If entered details are valid, the user’s account becomes available.
If it is invalid, an appropriate message is displayed to the user.

USE-CASE NAME: VIEW COURSE DETAILS

In this use case, a student can search all the courses available to him and
choose the best course he wants. The student can view the course duration,
faculty and department of the courses he may choose.

USE-CASE NAME: RESERVE FOR COURSE

When a student has successfully chosen a course, he can register to that course.
Upon registration, the student’s details are stored in the database.
P a g e 70 | 165
SOFTWARE ENGINEERING LAB MANUAL

USE-CASE NAME: PAY FEE

After registration to any course, the student may see the details of his current
course. He may wish to know details about fees and other information.

USE-CASE NAME: CHECK STATUS

The student tries to check the status in which category applied. The system
displays the status information to the student.

P a g e 71 | 165
SOFTWARE ENGINEERING LAB MANUAL

view course details

Registrar

<<include>>

Fig.30.Use-Case Diagram

ACTIVITY DIAGRAM:

Fig.31. Activity Diagram

Page 70
SOFTWARE ENGINEERING LAB MANUAL

CLASS DIAGRAM:
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.
The course registration system makes use of the following classes:
6. Student
7. Course Catalog
8. Reserve Course

1) STUDENT:

It consists of the details of all the students present in the database.

The attributes present in this class are student id, student name, student
qualification, student address1, student address2, student address3,
student mobile no, student emailed,, student dob, student sex. The
object of this class is created as soon as the student registers to a course.
The operations available to this class are add details (), modify details
(), del details (), reserve course().

2) COURSE CATALOG:

The course catalog class consist of course id, course name, course
duration course fee, course eligibility, total no of seat, course avail seat.
The operations are add course(), update course(), del course().

3) RESERVE COURSE:

The reserve catalog class consists of student id, course id, date, amt
paid, reg id, DD no. the operation are get course details(), check
eligibility(), confirm registration().

P a g e 71 | 165
SOFTWARE ENGINEERING LAB MANUAL

Fig.32. Class Diagram

P a g e 72 | 165
SOFTWARE ENGINEERING LAB MANUAL

INTERACTION DIAGRAM:

 A sequence diagram represents the sequence and interactions of a

given USE-CASE or scenario. Sequence diagrams can capture most
of the information about the system. Most object to object interactions
and operations are considered events and events include signals,
inputs, decisions, interrupts, transitions and actions to orfrom users or
external devices.
 An event also is considered to be any action by an object that sends
information. The event line represents a message sent from one object
to another, in which the “form” object is requesting an operation be
performed by the “to” object. The “to” object performs the operation
using a method that the class contains.
 It is also represented by the order in which things occur and how the
objects in the system send message to one another.
 The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about course
registration system are given.
 Users have to first login to the system before performing any
operation. The user has to provide the necessary details to the system
for login.

P a g e 73 | 165
: Student UI :: ::
UI ReReserservveCou
eCoursrse
e CoCou
urse
seC
Cattaalog
log

Reserve course

Eligible&Seat available

Fig.33. SEQUENCE
DIAGRAM
STATE CHART DIAGRAM:
Every object undergoes through some state and on receiving some event the
state gets changed. This transition of the state can be represented by the state
transition diagram.

Login to course registration View get list of courses Select Enter data Fill form
course course

after clicking

Pay fees Gets Submit

Confirmation form
Eligible sending form toregistrar

Gets receipt
not eligible

Reserves
seat

Fig.35. State Chart

Diagram

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.
Fig.36. Deployment Diagram
COMPONENT DIAGRAM:

Component diagrams are used to visualize the organization and

relationships among components in a system.

Fig.37.
Component
Diagram
TASK 6: E-Ticketing

AIM: To create an automated system to perform E-ticketing.

PROCEDURE: (I) PROBLEM STATEMENT

Our project is carried out to develop software for online Railway
Reservation System. This system has various options like reservation,
cancellation and to view details about available seats. Our project
mainly simulates the role of a Railway ticket booking officer, in a
computerized way.
The reservation option enables a person to reserve for a ticket at their
home itself. All he/ she has to do is to just login and enter the
required details. After this the reservation database is updated with
the person details, train name and also the source and destination place.
The cancellation option enables the passenger to cancel the tickets that
has been already booked by him/her.
The availability option prompts the person to enter train number, train
name and date of travel. After this the availability database is accessed
and available positions are produced.

(II) SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

The manual system of ticket reservation takes more time and the
number of reservations per day is limited. To increase the efficiency of
the process, we go for online ticket reservation system. This system
supports online ticket booking.

PURPOSE
If the entire process of reservation is done in a manual manner then it
would takes several months for reservation to reach the applicant.
Considering the fact that the number of passenger 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.

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 railway can use
this system to reduce his workload and process the application in a
speedy manner.
• Provide a communication platform between the passenger and
the administrator.
• Passenger will come to know their status of application and
the date in which they must subject themselves for manual document
verification.
DEFINITIONS, ACRONYMS AND THE
ABBREVIATIONS
• Passenger – The person that who wishes to obtain the railway
ticket.
• PNR – Passenger NameRecords
• HTML - Markup Language used for creating web pages.
• J2EE – Java 2 Enterprise Edition is a programming
platform java platform for developing and running
distributed java applications.
• HTTP - Hyper Text Transfer Protocol.
•TCP/IP – Transmission Control Protocol/Internet Protocol is
the communication protocol used to connect hosts on the
Internet.
TECHNOLOGIES TO BE USED
• HTML
• JSP
• Javascript
• Java

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific
requirements –
Overall Description will describe major role of the system
components and inter- connections.

Specific Requirements will describe roles & functions of the

actors.

OVERALL DESCRIPTION

PRODUCT PERSPECTIVE

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 ticket.

SOFTWARE INTERFACE
• Front End Client - The passenger and System online
interface is built using JSP and HTML. The Administrators's
local interface is built using Java.
 Web Server – Apache Tomcat Server (Oracle Corporation)
  Back End - Oracle 11g database

HARDWARE INTERFACE

The server is directly connected to the client systems. The client

systems have access to the database in the server.

SYSTEM FUNCTIONS

• Secure Registration of information by the Passengers.

• System can generate reports from the information and is the
only authorized personnel to add the eligible application
information to the database.
• Display the requested pages to the user.
• Update the database after every successful process.

USER CHARACTERISTICS
• Passenger - They are the people who desire to obtain the
ticket and submit the information to the database.

CONSTRAINTS
• The passengers 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.

ASSUMPTIONS AND DEPENDENCIES

• The Passengers must have basic knowledge of computers
and English Language.
 • The passengers may be required to scan the documents and
send.

(III) USE-CASE DIAGRAM

The online ticket reservation system uses the following use cases:
1. Request for seat availability
2. Make Reservation
3. Cancellation
4. Check status
5. Print ticket

ACTORS INVOLVED:
1) System
2) Passenger

USE-CASE NAME: REQUEST FOR SEAT

AVAILABILITY

The passenger can view the train available in the database for deciding
which train ticket he wishes to reserve. The passenger can search the
train information based on journey date, train type and reservation
type. The passenger can view the details of flights suchas, train
number, source station, destination station, arrival time, departure
time, fare and number of seats available.

USE-CASE NAME: MAKERESERVATION

The user is allowed to reserve a ticket on train as he/she requires on

the particular date and time. The user has to provide details such as
name, train number, date of travel, source station, destination station,
proof name and money transaction details.

USE-CASE NAME: PRINT TICKET

The user after booking a ticket can print a copy of the ticket reserved.
The user has to provide the details about ticket number for searching
in the database and passenger name for confirming passenger identity.

USE-CASE NAME: CANCEL TICKET

A passenger can decide to cancel a ticket after the ticket is booked. The
passenger has to provide details about ticket for searching and details
about him for confirmation of identity.

USE-CASE NAME: CHECK STATUS

The passenger can view the status of the reserved tickets. So the
passenger can confirm his/her travel.

request for seat availability

<<include>>

makeReservation

Fig.38. Use-Case Diagram For Airline Reservation

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of

stepwise activities and actions with support for choice, iteration and
concurrency. In the Unified Modeling Language, activity diagrams can
be used to describe the business and operational step-by- step
workflows of components in a system. An activity diagram shows the
overall flow of control. An activity is shown as an rounded box
containing the name of the operation.

This activity diagram describes the behaviour of the system.

• First state is login where the passenger login to the E-Ticketing
system.
• The next state is filling details the passenger are used to fill the
form.
• Then passenger used to selecting the flight.
• The passenger appears for book ticket and search details from
E-Ticketing DataBase.
 Check seat availablity based on
date/ train/reservation type

Yes
Is it valid
No data?

Show the Display the required

error page train information

Fig.39. Activity Diagram [Check Availability]

 Yes
Display the
cancellation

Select the
passenger want
to

amount

isit

enter

want
to

Fig.40. Activity Diagram [Ticket Reservation]

 request to check

Enter the PNR

number

I s valid PNR Yes

No no?
Display
I nvalid PNR the status
number

Fig.41.Activity Diagram [Check Status]

 Isitvaliduser

passenger
to

to
N

Fig.42. Activity Diagram [Ticket Cancellation]

CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the

main static analysis diagram. The main task of object modeling is to
graphically show what each object will do in the problem domain. The
problem domain describes the structure and the relationships among
objects.
.
The online ticket reservation system makes use of the following classes:

1. TICKETRESERVATION
It consists of twelve attributes and two operations. It records the
details of every ticket booked such as ticket number, passenger ID,
source and destination station and etc.

2. TRAININFO
It stores the details of all the trains such as train number, train name,
speed, source and destination stations, etc.

3. PASSENGERINFO
It consists of seven attributes and three operations. This class is used to
store passenger details such as, passenger name, age, address and etc.

4. SEATAVAILSTATUS
This class is used to update the number of seats available for a
particular train by using updateStatus() operation.
Fig.43. Class Diagram For E-Ticketing
INTERACTION DIAGRAM:

A sequence diagram represents the sequence and interactions of a

given USE- CASE or scenario. Sequence diagrams can capture most
of the information about the system. Most object to object interactions
and operations are considered events and events include signals,
inputs, decisions, interrupts, transitions and actions to orfrom users or
external devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object
to another, in which the “form” object is requesting an operation be
performed by the “to” object. The “to” object performs the operation
using a method that the class contains.
 reserveTicket : cancelTicket : : seatAvailStatus Syste
ticketReservation ticketReservation

Fig.44. Sequence Diagram

 7: Verify given details
1: Login(username,password)
5: Enter the passenger details
6: Perform money transaction
13: Print the ticket reserveTicket :

4: Display the reservation page 2: Check givendata

12: Confirm & Display the ticket
: Passenger
3: Registered user
System

14: request to cancel ticket 8: Update status

16: Select the passenger details 11:

9: Store the details

15: Display the cancellation page
19: Store the details
22: Ticket cancelled

17: Verify given details

10: Updated successfully
20: Updated successfully

18: Update status

cancelTicket :
ticketReservation
21:

Fig.45. Collaboration Diagram

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are
deployed.

Fig.46. Deployment Diagram

TASK 7: SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM: To implement a software for software personnel management system

PROCEDURE: (I) PROBLEM STATEMENT:

Software personnel management system allows employees to record

time card electronically and automatically generates pay slips based on
number of hours worked and total amount of sales. The system will run on
individual employee desktops where the employee can access and edit only
their personal details. The system will maintain information on the employee
in the company in order to calculate the payroll. The employees will also be
able to know from the system, the number of hours worked per day and total
of all hours spent on a project and total pay received year-to-date etc. Payroll
administrators keep track of all the information including adding new
employees, deleting employees, and edit information and run reports. The
system will generate records and performance report of the employees.

( II )SOFTWARE REQUIREMENT SPECIFICATION:

INTRODUCTION
The Software Personnel Management system is an interface between
Employee and the Administrator responsible for generation of payment slip.
It aims at improving the efficiency in the generation of Pay slip and reduces
the complexities involved in it to the maximum possible extent.
PURPOSE
If the entire process of Software personnel management is done in a
manual manner then it would more time for pay slip generation process.
Considering the fact that the number of employee is increasing every year, a
maintenance system is essential to meet the demand. So this system uses
several programming and database techniques to elucidate the work involved
in this process.

SCOPE
 Software system allows Administrator to manage its employee in a
better way.
 When needed, it will take just a few second to find out the background
of an employee and his/her contribution to the organization, it will also
facilitate keeping all the records of employee.
 So all the information about an employee will be available in a few
seconds, it will also make it very easy to generate statistical data or
custom data, line finding a certain set of employee.

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS

 ADMINISTRATOR
Refers to the super user who is maintaining the employee details.

 EMPLOYEE
One who works for a software company.

 SPMS
Refers to this Software personnel management system.

 HTML
Markup Language used for creating web pages.
  J2EE
Java 2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.
 HTTP
Hyper Text Transfer Protocol.

REFERENCES
IEEE Software Requirement Specification format.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• Javascript
• Java
• XML
• AJAX
TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements
Overall Description will describe major role of the system components and
inter-connections.
Specific Requirements will describe roles & functions of the actors.
 OVERALL DESCRIPTION

PRODUCT PERSPECTIVE:

The SPMS acts as an interface between the 'ADMINISTRATOR' and

the 'employee'. 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 to manage the software personnel.

SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using JSP and HTML. The
ADMINISTRATOR's local interface is built using Java.
• Web Server – Apache Tomcat application server(Oracle
Corporation).
• Back End – Oracle 11g database.

HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

SYSTEM FUNCTIONS

The payment module greatly reduces the workload of the

ADMINISTRATOR department by automating the payroll process,
allowing ADMINISTRATOR to ensure the payroll functions are
completed on time and without errors. The payroll class automatically
calculates payment amounts and various deductionssuch as income tax
before generating pay checks and employee tax reports.
 View Salary
The employee views the salary details efficiently from the SPMS. The
employees will also be able to know from the system, the number of
hours worked per day and total of all hours spent on a project and total
pay received year-to-date etc.

USER CHARACTERISTICS
 Employee
These are the person who desires to view the salary details.
 Administrator
Administrator has the certain privileges to generate pay slip for the
employee.
 Database manager
DB manager stores all the data related to Employee and Administrator.

CONSTRAINTS
 The administrator requires a system to monitor information of the
employee.
ASSUMPTIONS AND DEPENDENCIES
 The employee and Administrator must have basic knowledge of
computers and English Language.
(III) USECASE DIAGRAM:
The Software personnel management system use cases are:
1. Login
2. Job Assigned
3. View Salary
4. View Employee details
5. Generate payment slip
6. Create DB
7. Update DB
8. Delete DB
ACTORS INVOLVED:
1. Employee
2. Administrator
3. Database Manager
USE-CASE NAME: LOGIN
The Employee login to the system to view the salary details

USE-CASE NAME: JOB ASSIGNED

The employee views the job assigned to him/ her by the Administrator.

USE-CASE NAME: VIEW SALARY

The employee views the salary details efficiently from the SPMS. The
employees will also be able to know the number of hours worked per day
and total of all hours spent on a project and total pay received year-to-date etc.
.
USE-CASE NAME: VIEW EMPLOYEE DETAILS
The Administrator views the details of the employee for the payroll process

USE-CASE NAME: GENERATE PAYMENT SLIP

The Administrator generates the pay slip based on the details of the no of
hours/ no of days worked by the employee.

USE-CASE NAME: CREATE DB

The database manager creates individual database tables for the employees
USE-CASE NAME: UPDATE DB
When an employee information changes the database manager updates
individual database tables for the employees.

USE-CASE NAME: DELETE DB

When an employee relieves/terminated the database manager deletes
individual database tables for the employees.
 Delete DB

Database Manager

Fig.47. USE CASE DIAGRAM FOR SOFTWARE PERSONNEL

MANAGEMENT SYSTEM
ACTIVITY DIAGRAM:
The activity diagram notation is an action, partition, fork join and
object node. Most of the notation is self explanatory, two subtle points. Once
an action finished, there is an automatic outgoing transaction. The diagram can
show both control flow and data flow.

Fig.48. ACTIVITY DIAGRAM FOR SOFTWARE PERSONNEL

MANAGEMENT SYSTEM
 CLASS DIAGRAM:
The class diagram is referred as object modeling in the static analysis diagram.
The main task of object modeling is to graphically show what each object will
do in the problem domain. The problem domain describes the structure and
the relationships among objects.
The Software Personnel Management system class diagram consists of four
classes
1. Employee class
2. Administrator class
3. Database Manager class
4. Payment class

1. EMPLOYEE CLASS
It consists of seven attributes and two operations. The attributes are empid,
empname, emppassword, address, mobile number, date, Hours Worked. The
operations of this class are Login( ) and viewsalary( ).

2. ADMINISTRATOR CLASS
It consists of attributes Adminid, Adminname and Adminpassword. The
operations are login ( ), Generate payroll ( ), view payroll ( ) and
viewemployeedetail ( ).

3. DATABASE MANAGER CLASS

The attributes of this class are DBmanagerid, DBmanagername( ) and
DBmanagerpassword. The operation are create( ), update( ),delete( ) and
display payroll( ).
4. PAYMENT CLASS
The attributes of this class are paymentid, empid, date, Basic pay, HRA, DA,
PF, Netpay and Gross pay. The operation are calculatesalary( ) and
GenerateSlip( ).
Fig.49. CLASS DIAGRAM FOR SOFTWARE PERSONNEL MANAGEMENT
SYSTEM
 INTERACTION DIAGRAM:
 A sequence diagram represents the sequence and interactions of a
given USE-CASE or scenario. Sequence diagrams can capture most
of the information about the system.
 Most object to object interactions and operations are considered events
and events include signals, inputs, decisions, interrupts, transitions and
actions to or from users or external devices.
 An event also is considered to be any action by an object that sends
information.
 The event line represents a message sent from one object to another, in
which the “form” object is requesting an operation be performed by
the “to” object.
 The “to” object performs the operation using a method that the class
contains.
 It is also represented by the order in which things occur and how the
objects in the system send message to one another.
 The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about passport
automation system are given.
EMPLOYEE:

Fig.50.SEQUENCE DIAGRAM FOR EMPLOYEE

 UI Payment Database
: Administrator Manager
Seek Login

View Employee Details

Display Employee Detail

Generate Payslip

Display Payroll

Fig.52.SEQUENCE DIAGRAM FOR ADMINISTRATOR

 3.view employee details
7: generate payslip 1: seek login

administrator

2:
6: display employee details
12: display payroll

payment
DB manager
10: return salary

9: calculate salary

Fig.53.COLLABORATION DIAGRAM FOR EMPLOYEE

STATE TRANSITION DIAGRAM

 States of object are represented as rectangle with round corner, the
transaction between the different states.
 A transition is a relationship between two state that indicates that
when an event occur the object moves from the prior state to the
subsequent.
Fig.54.STATE TRANSITION DIAGRAM FOR SOFTWARE PERSONNEL
MANAGEMENT SYSTEM
DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed

Fig.55.DEPLOYMENT DIAGRAM FOR SOFTWARE PERSONNEL

MANAGEMENT SYSTEM

COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and relationships

among components in a system.
Fig.56.COMPONENT DIAGRAM FOR SOFTWARE PERSONNEL
MANAGEMENT SYSTEM
TASK 8: CREDIT CARD PROCESSING

AIM: To create a system to perform the credit card processing

(I) PROCEDURE: PROBLEM STATEMENT:

Credit card processing through offline involves the merchant collecting

order information (including credit card numbers), storing this in a database on
your site, and entering it using their on-site merchant credit card processing
system. Takes time to manually enter credit card information for each order.
This solution creates following cons:
· Insecure – there is a possibility that a skilled hacker could break into
the database and steal an entire list of credit card numbers, thereby damaging
the merchant’s reputation with current client.
· There is a higher risk of customer charge backs with no signature
· Higher risk of fraud for using stolen credit cards
· Many discerning online shoppers will not give their credit card to
an “untrusted” online merchant (you may want to consider being part of the
Better Business Bureau or similar organization to add credibility).
So there is a need of online and trusted credit card processing.

( II ) SOFTWARE REQUIREMENT SPECIFICATION:

INTRODUCTION
A credit card is a small plastic card issued to users as a system of
payment. It allows its holder to buy goods and services based on the holder's
promise to pay for these goods and services. The issuer of the card creates a
revolving account and grants a line of credit to the consumer (or the user)
from which the user can borrow money for payment to a merchant or as a
cash advance to the user.
 When a purchase is made the merchant swipes the card. The
information goes to a gateway processor, which either accepts or rejects
the transaction. If it is accepted, the transaction is held until the end of the
business day. The merchant then reenters the transaction via the
gateway processor, the data is logged, and the debt is transferred to the
account. The use of an ATM for cash advance is a similar process.

If you are selling to consumers, merchant services will allow you

to expand your customer base and provide a more convenient method of
payment than cash or checks. And if you are interested in selling over the
Internet, accepting credit card processing is a must. Accepting credit cards
allows funds to be transferred to your bank account in less than a week.
This can be a welcome relief for businesses that experience a tight cash
flow.

The two purchase options for Credit Card Processing facility are:
 Validation only

 Credit card processing (which secures deposits at the time of booking)

With either option, credit card accounts entered during booking are
validated to assure that the account is active and in good standing. The
credit card processing option also allows properties to process credit card
deposits.

PURPOSE
When customers complete their shopping cart, their credit card is
preauthorized and the order is entered into Sales Order. Credit Card
Processing dials out and obtains a credit card payment. Within five
minutes the customer receives an e-mail receipt.
SCOPE
 Automatically connects to your financial network for credit card
authorizations and settlements
 Integrates with Sales Order, Accounts Receivable, and e-Business
Manager
 Support for dial-up (modem) connections or secure Internet
connections through TCP/IP and SSL
 Compliant with Visa and MasterCard Electronic Commerce Indicator
(ECI) regulations.
 Multiple address verification options available.
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
• Authorization service - The issuer of the card creates a revolving
account and grants a line of credit to the consumer (or the user) from which
the user can borrow money for payment to a merchant or as a cash advance
to the user.

• User- One who wishes to uses the

credit card.

• CCP - Refers to this Credit Card

Processing.

• HTML - Markup Language used for creating web pages.

•J2EE – Java 2 Enterprise Edition is a programming platform java
platform for developing and running distributed java applications.
• HTTP - Hyper Text Transfer Protocol.
•TCP/IP – Transmission Control Protocol/Internet Protocol is the
communication protocol used to connect hosts on the Internet.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• Javascript
• Java
TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
OVERVIEW
SRS includes two sections overall description and specific
requirements –
Overall Description will describe major role of the system
components and inter- connections.
Specific Requirements will describe roles & functions of the actors.
 OVERALL DESCRIPTION
PRODUCT PERSPECTIVE

This solution involves signing up for a free Business Account. Once

this is done and the e-commerce site is properly configured, you can accept
payments from Visa, MasterCard, Amex, and Discover cards payments.

SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using JSP and HTML. The Administrators
local interface is built using Java.
• Web Server - Glassfish application server(SQL Corporation).
• Back End - SQL database.

HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

SYSTEM FUNCTIONS
1. Accept credit card numbers on the web, store them in a database,
then process them off- line
2. Credit card processing with CCP
3. Credit card processing with a third-party credit card processing
company.
USER CHARACTERISTICS
1) User/Customer - They are the people who desires to purchase the
goods using credit card.
2) Authorization Service
 Validate the credit card payments to ensure that the card number is
valid and the card has not expired
 Deposit processing to apply the deposit payment to the card
 Prepare Credit card transaction reports that show authorization
codes, amounts, and error/success messages

CONSTRAINTS
 Trusted if using a well known third-party processor
 Must suite for higher-volume sites
 Cheaper transaction rates
 Getting money transferred may be very fast
 Must provide fraud prevention measures and fraud protection
programs

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.

 ( III )USECASE DIAGRAM:

The Passport Automation system use cases are:

Creating Account: Used to create a account.
Credit card request: Used to send the request to credit card.
Bank Enquiry: Used to get the bank enquiry like pin code to verify your user
account.
Issuing card: Used to issuing the card to machine.
Purchase the item: Used to list out the purchase details in shop.
Prepare the bill: Used to issuing the bill for the purchased item.
paying bill: Used to transaction of money to paying the bill.

ACTORS INVOLVED
Customer/user: The person who order for the item.
Banker: The person to check the account details.
Retailer: The person to preparing the bills.
USE-CASE NAME: PURCHASE PRODUCT
Customer purchases items from ecommerce site then
proceeds to the site’s secure checkout area.
.

USE-CASE NAME: AUTHORIZATION REQUEST

Credit card processor collects billing information from the
customer via a secure connection.

USE-CASE NAME: AUTHORIZATION RESPONSE

Billing information is verified and the transaction is completed by the
credit card issuer.
USE-CASE NAME: PAYMENT APPROVAL
The transaction details are recorded by the credit card processor and
results are securely relayed to the merchant. Merchant’s site receives
transaction result and does appropriate actions (e.g. saves the order & shows
message).
 paying bill

Fig.57 USECASE DIAGRAM FOR PASSPORT AUTOMATION

SYSTEM
CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static
analysis diagram. The main task of object modeling is to graphically show
what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.
The Credit Card Processing system class diagram
consists of three classes. They are
1. Banker
2. Customer
3. Retailer

Fig.58.CLASS
DIAGRAM
INTERACTION DIAGRAM:

 A sequence diagram represents the sequence and interactions of a

given USE-CASE or scenario. Sequence diagrams can capture most of
the information about the system.
 Most object to object interactions and operations are considered events
and events include signals, inputs, decisions, interrupts, transitions and
actions to or from users or external devices.
 An event also is considered to be any action by an object that sends
information.
 The event line represents a message sent from one object to another,
in which the “form” object is requesting an operation be performed
by the “to” object.
 The “to” object performs the operation using a method that the class
contains.
 It is also represented by the order in which things occur and how the
objects in the system send message to one another.
 The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about passport
automation system are given.
C:Customer B:Banker

10: Swipe the card

Fig.58.SEQUENCE
DIAGRAM
 6: select shop
7: Purchase Item 9: preparing bills
8: producing item for billing
10: Swipe the card

Fig.59.COLLABORATI
ON DIAGRAM

State chart Diagram:

 States of object are represented as rectangle with round corner, the

transaction between the different states.
 A transition is a relationship between two state that indicates that
when an event occur the object moves from the prior state to the
subsequent.
 creating
account

do/requestingcreditcard

card

Fig.60. STATE CHART

DIAGRAM
DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are
deployed.

Fig.61.DEPLOYMENT DAIGRAM
COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and relationships

among components in a system.

Fig.62.COMPONENT DIAGRAM
TASK 9: E-BOOK MANAGEMENT SYSTEM

AIM: To create a system to perform E- book Management System.

(I) PROCEDURE: PROBLEM STATEMENT:

EBook process is well organized online buying and selling of books.

This system is well developed in various resources, for example Amazon site
deals more about e-booking concept. This process has various issues in the
basics of maintenance of database and updating in sites, and virus problem in
pdf books, so we have many issues in this process. The process of e-books is
fully based on online, and the process for this mainly interaction between
buyer and seller, buyer who enter the site for purchase of book will use search
engine for book to purchase, the search engine will mainly focused on the
database process, it used to search book for the buyer who mentioned the book
name, author name, edition, publication details in the site, so that the search
engine will show many books. There will be a payment option and option for
pdf file or hardcopy delivery to home, the user should decide whether he want
which one. Whether he choice hardcopy means, full detail address, driving
license no, and then he should login with his username and password, and then
payment through atm debit or credit card applicable.

(II) SOFTWARE RESOURCE SPECIFICATION:

INTRODUCTION

E-Book is the interface between the students and Librarian. It aims at

improving the efficiency in the Issue of books or magazines and reduces the
complexities involved in it to the maximum possible extent.
PURPOSE
If the entire process of 'Issue of Books or Magazines' is done in a
manual manner then it would take several months for the books or magazines
to reach the applicant. Considering the fact that the number of students for
Book Bank 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. Thesystem has been
carefully verified and validated in order to satisfy it.

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 books can use this system
to reduce his workload.

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS

 E-book manager

Refers to the super user who is the Central Authority who has
been vested with the privilege to manage the entire system.

 User
One who wishes to obtain the Books or Magazines.

 Visitor
One who visits to obtain Books or Magazines.

 Administrator

One who manages and maintain Books or Magazines.

REFERENCES
IEEE Software Requirement Specification format

TECHNOLOGIES TO BE USED
HTML - Markup Language used for creating web pages.

J2EE - Java 2 Enterprise Edition is a programming platform and it is

the part of the java platform for developing and running distributed
java applications.

HTTP -Hyper Text Transfer Protocol

TCP/IP - Transmission Control Protocol/Internet Protocol is

the communication protocol used to connect hosts on the
Internet.

TOOLS TO BE USED

Eclipse IDE (Integrated

Development Environment

Rational Rose tool (for developing

UML Patterns)
 OVERVIEW

SRS includes two sections overall description and specific

requirements.

Overall description will describe major role of the system

components and inter- connections.

Specific requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
It will describe major role of the system components and inter-
connections.

PRODUCT PERSPECTIVE

The ORS acts as an interface between the user and the 'e-book
manager'. 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 books or magazines.

SOFTWARE

INTERFACE

Front End

Client

The Student and Librarian online interface is built using JSP and HTML. The
Librarians local interface is built using Java.

Web Server

Apache Tomcat application server (Oracle Corporation).

Back End

Oracle 11g database

HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
access to the database in the server.

SYSTEM FUNCTIONS

Secure Registration of information by the Students.

Librarian can generate reports from the information and is the only
authorized personnel to add the eligible application information to the
database.
USER

CHARACTER

ISTICS User

They are the people who desire to obtain the books and submit the
information to the database.

Visitor
They are the person who visits the E-book system

Administrator

He has the certain privileges to add the books and to approval of

the reservation of books.

CONSTRAINTS

The Students 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.

ASSUMPTIONS AND DEPENDENCIES

The user and e-book manager must have basic knowledge of
computers and English Language. The user may be required to
scan the documents and send.

(III) USE-CASE DIAGRAM:

The E-book use cases in our system are:

1. Login
2. Register
3. Search book
4. Download
5. Payment
6. Publisher
7. Update

Actors involved:

1. Register User
2. Visitor
3. Administrator

1. Add: a student record. Each student should have following attributes.

-> Student id
->Name
->Address
->Phone no
2. Update:
The record would be selected
using the student id. The updates
can be made on full items only.
->name
->address
->phone no
3. Add to book item:
Each book should have following attribute
->call no
->title
->ISBN
->Author name
4. Query the book database:
The product shall let librarian query tools books detail
information by their ISBN number (or) author (or) title.
The search result would produce a list of books, which match the
search parameters.
5. Check out a book:
Librarians and member of the library can check out can be initialized
from a previous search operation where user has selected a set of books.
6. Check in a book:
Librarians and member of the library can check in a book using its call
no.
 Update

Fig.63.USE-CASE DIAGRAM
ACTIVITY DIAGRAM:
The activity diagram shows the activity of the process here first login
is done when the user is valid then the welcome page appears .Here fork is
used where two transaction line may be got search book and online reading
.search book can be used to search book and online reading can allow user to
learn online and when any of these two process is selected a join is used where
download occurs, in this download of book is done then finally cost ofbook is
paid online.

Fig.64.ACTIVITY DIAGRAM
CLASS DIAGRAM
The class diagram, also referred to as object modeling is the main static
analysis diagram. The main task of object modeling is to graphically show
what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.
The E-book Management system class diagram consists of five classes:

8. Login
9. Registered User
10. Administrator
11. Book
12. Visitor
13. download
14. Logout

1) Login: Login to the system

2) Registered User: It consists of six attributes and four operations. The

attributes are user id, name, password, email id, phone no, security
question. The operations of this class are download(),
login(),search(),register().

3) Administrator: It consists of four attributes and two operations. The

attributes are name, password, email id, admin id. The operations of
this class are update(), record().

4) Book: It consists of four attributes and two operations. The attributes

are book id, book name, author, and price. The operations of this
class are update(), add().

5) Visitor: It consists of two attributes and two operations. The attributes

are user name, email id. The operations of this class are search book(),
read book().

6) Download: It consists of two attributes and two operations. The

attributes are user id, book id, date, and amount. The operations of this
class are search download ().

7) Logout:
Logout from the system.
Fig.65. CLASS DIAGRAM
 INTERACTION DIAGRAM:

 A sequence diagram represents the sequence and interactions of a

given USE-CASE or scenario. Sequence diagrams can capture most
of the information about the system. Most object to object interactions
and operations are considered events and events include signals,
inputs, decisions, interrupts, transitions and actions to orfrom users or
external devices.
 An event also is considered to be any action by an object that sends
information. The event line represents a message sent from one object
to another, in which the “form” object is requesting an operation be
performed by the “to” object. The “to” object performs the operation
using a method that the class contains.
 It is also represented by the order in which things occur and how the
objects in the system send message to one another.
 The two sequence diagram and two collaboration diagram one for
Registered user and another for visitor are given below
Fig.66.SEQUENCE DIAGRAM FOR
REGISTERED USER
 Book
: Visitor

seek for register

Registered is granted

Search book

Check availablity of book

Display Book

Fig.67.SEQUENCE DIAGRAM FOR VISITOR

1: seek login
register user UI

2: login agreed

6: request download book

8: payment transaction submitted

7: display payment
5: 3: search book 9: downloading

4: check availabillity of book

Download

Book

Fig.68.COLLABORATION DIAGRAM FOR REGISTERED USER

 4: check availability of book

1: seek for register

3: search book
visitor Book

2: registered is granted
5: display book

Fig.69.COLLABORATION DIAGRAM FOR

VISITOR

The diagrams show first login to the system and the pin no is entered
and check the pin .Get no and validate password check the condition based
on condition book issue and return are done. Pay the online and renewed
.Finally logout from the system.

STATE CHART DIAGRAM:

The diagrams show first login to the system and view the books and
search for required book is done and then required book is downloaded and
amount paid in online
.Finally logout from the system.

Login View Searc Download Payment

h

Fig.70.STATE CHART DIAGRAM

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM
Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.

Fig.71 DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and
relationships among components in a system.

Fig.72.COMPONENT DIAGRAM
TASK 10: RECRUITMENT SYSTEM

AIM: To create an automated system to perform the Recruitment System

Process.

(I) PROCEDURE: PROBLEM STATEMENT:

The recruitment system allows the job seekers to view the job
opportunity through Advertisement and helps to apply for the job. The
organization shortlist the applicants for the interview. The shortlisted
applicants undergo through a process of Test and Interview. The HR
department selects the Applicant based on the performance in the Test and
Interview. Finally the recruited applicants are informed. 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
organization.

(II)SOFTWARE REQUIREMENT SPECIFICATION:

INTRODUCTION
Recruitment System is an interface between the Applicant and the
Organization responsible for the Recruitment. It aims at improving the
efficiency in the Recruitment process and reduces the complexities involved
in it to the maximum possible extent.

PURPOSE
If the entire process of ‘Recruitment' is done in a manual manner then
it would takes several days for the recruitment. Considering the fact that the
number of applicants for recruitment 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.

SCOPE
 The System provides an online interface to the user where they can
fill in their personal details and apply for the job.

 The Organization (HR-Department) concerned with the recruitment

process can make use of this system to reduce their workload and
process the application in a speedy manner.

 Provide a communication platform between the Applicant and the

Organization.

DEFINITIONS, ACRONYMS AND THE

ABBREVIATIONS
 Organization
Refers to the super user who is the Central Authority with the
privilege to manage the entire system. It can be any higher official in
the HR department.
 Applicant
One who wishes to apply for the job.
 RS
Refers to this Recruitment System.
 HTML
Markup Language used for creating web pages.
 J2EE
Java 2 Enterprise Edition is a programming platform java platform
for developing and running distributed java applications.
  HTTP
Hyper Text Transfer Protocol.
 TCP/IP
Transmission Control Protocol/Internet Protocol is the
communication protocol used to connect hosts on the Internet.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• JavaScript
• Java
TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)

• Rational Rose tool (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements

Overall Description will describe major role of the system components and
inter-connections.

Specific Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION

PRODUCT PERSPECTIVE
The RS acts as an interface between the ''Applicant and the
'Organization'. 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 for recruitment process.
SOFTWARE INTERFACE
• Front End Client –The Applicants and Organization online
interface is built using JSP and HTML. The Administrators’ local
interface is built using Java.
• Web Server - Glassfish application server (SQL Corporation).
• Back End - SQL database.
HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

SYSTEM FUNCTIONS
 The applicant views the jobs through Advertisement.

 Applicants apply for the job.

 Test and Interview are conducted.

 Recruited Applicants are informed.

 HR Manager can generate reports from the information and he/she is

the only authorized personnel to add the eligible application
information to the database.

USER CHARACTERISTICS
 Applicant
These are the persons who desire to apply for the job.
 Organization
These are the person with certain privileges to announce recruitment
depending upon the organization need. He/ She may contain a group
 of persons under him/her to publish advertisement and give suggestion
whether or not to approve the recruitment.
 HR
He/ She is the person who upon receiving intimation from the RS,
perform a personal verification of the applicants and see if he/she has
eligibility for the advertised job through a process of Test and
Interview.
CONSTRAINTS
 The Applicants require a computer to submit their information.

ASSUMPTIONS AND DEPENDENCIES

 The Applicants and HR must have basic knowledge of computers and
English Language.

( III )USECASE DIAGRAM:

The Recruitment system use cases are:

1. Advertisement
2. Apply for job
3. Test
4. Interview
5. Recruit Applicants
ACTORS INVOLVED:
Actors are as follows:

1. Applicant
2. Organization
3. HR
ACTORS DOCUMENTATION:
 Applicant
Applicant is an actor who applies for the job vacancy. If he/she gets
selected then HR department sends the Interview call letter.
 HR
HR is an actor who informs about the vacancy to their Organization.
HR recruits the applicants based on the required skill for the vacant
position and shortlist them. HR is also responsible for Interview
Scheduling.
 Organization
Organization is an actor who announces the Advertisement for vacancy.

USE-CASE NAME: ADVERTISEMENT

Description: This Use Case is initiated by Organization. Notifies about the
required job vacancies
Flow of Events:
1. HR informs about vacancy to Organization.
2. Organization announces the Advertisement.
Pre-Condition: Vacancy must exist.
Post-Condition: Details about the vacancy are informed.

USE CASE: APPLY FOR JOB

Description: This Use Case is initiated by Applicants. Online forms are
filled by the Applicants and submitted to the organization.
Flow of Events: 1. HR processes the filled forms.
2. HR selects the list of eligible Applicants.
Pre-Condition: Online form must exist.
Post-Condition: Forms filled are stored in an Information System for
processing. The filled forms are sent to the HR. The HR produces the list of
eligible Applicants.
USE CASE: SELECT APPLICANTS FOR INTERVIEW
Description This Use Case is initiated by HR. The lists of selected
Applicants are Informed .The Test and Interviews are conducted by the HR
of the region that has the vacancy.
Flow of Events: 1. HR schedules the interview process.
2. HR conducts test and interview for the applicant via
online system.
3. Who clear the interview process are selected.
Pre-Condition: Applicants must meet eligibility criteria.
Post-Condition: Applicants clears interview process OR doesn’t clear
interview process.

USE CASE: TEST

Description: This Use Case is initiated by the HR. A test will be conducted
by the HR
Flow of Events
 The applicants undergo the Test process.
 He/ She clear or not clear the Test.

 Pre-Condition: Applicant is selected for the Test.

 Post-Condition: Applicant clear or not clear the Test.

USE CASE: INTERVIEW

Description: This Use Case is initiated by the HR. An Interview will be
conducted by the HR
Flow of Events 1. The applicants undergo the Interview process.
2. He/ She clear or not clear the Interview.
Pre-Condition: Applicant is selected
for the Interview. Post-Condition:
Applicant clear or not clear the
Interview. USE CASE:
RECRUITED APPLICANTS

Description: This Use Case is initiated by the HR. The selected applicants are
recruited by HR.
Flow of Events 1. The applicants clear the Test.
2. The applicants clear the Interview.
Pre-Condition: Applicant is selected for the Test and Interview.
Post-Condition: Applicant clears Test and Interview.

Fig 73. USE CASE DIAGRAM FOR

RECRUITMENT SYSTEM
ACTIVITY DIAGRAM:
The activity diagram represents the series of activities that are ocurring
between the objects.Following is activity diagram which represents the
recruitment process .

Fig.74 ACTIVITY DIAGRAM FOR

RECRUITMENT SYSTEM
CLASS DIAGRAM:

The UML class diagram illustrates class interfaces and their actions.
They are used for static object modeling. The problem domain describes
the structure and the relationships among objects.

The Recruitment system class diagram consists of five classes

1. Applicant class
2. Organization class
3. HR Department class
4. Advertisement class
5. Recruitment class
APPLICANT CLASS:
It consists of eight attributes and two operations. The attributes are
Appl-id, Appl-name, Appl-DOB, Appl-Gender, Appl-Qualification, Appl-
phone, Appl-emailid, Appl-addr.The operation of this class are view jobs ( )
and Apply ( ).

ORGANIZATION CLASS:
The attributes of this class are Org-name, Org-Ph-No, and Org-Addr. The
operation of this class are HR-Dept( ), Mkt-Dept( ) and Account-Dept( ).

HR DEPARTMENT CLASS
The attributes of this class are Emp-id, Emp-name, Emp-DOB, Emp-
Gender, Emp-Phone, Emp- emailid, Emp-addr. The operation are Planning(
), Policies( ),Strategies( )
ADVERTISEMENT CLASS
The attributes of this class are Adv-No, Adv-Name and Adv-
description. The operation is display( ).

RECRUITMENT CLASS
The attributes are Rec-Designation and Rec-Totalcandiate. The operation is
recruit( ).

Fig.75 .CLASS DIAGRAM FOR RECRUITMENT SYSTEM

INTERACTION DIAGRAM:

 A sequence diagram illustrates a kind of format in which each object

interacts via message. It is generalize between two or more
specialized diagram.
 Advertisement
Advertisement Organisation
: Applicant Recruitment
Committee : HR
View Jobs

Apply for Jobs

Forward Applicants Resume

Analyse Applicants Resume

Send Intervi ew call Letter/E-mail

Attend Test

Evaluate Test

Selected /Not Selected Informed

Attend Interview

Applicant passed Test and Interview Informed

Salary Fixed /Recruited

Fig 76 SEQUENCE DIAGRAM FOR

RECRUITMENT SYSTEM
  Communication diagram illustrate that object interact on a graph or
network format. In collaboration diagram the object can be placed in
anywhere on the diagram. The collaboration comes from sequence
diagram.

 1: view jobs

appilicant advertisement

6: attend interview
2: apply for jobs
5: send interview call letter/emil
7: applicant passed test & interview informed
8: salary fixed/received
4: analyse applicant resume

3: forward applicants
organisation recuitment
commited=HR

Fig 77 COLLOBORATION DIAGRAM FOR

RECRUITMENT SYSTEM
STATE CHART DIAGRAM:

 Every object undergoes through some state and on receiving some

event the state gets changed. This transition of the state can be
represented by the state transition diagram.

Fig .78. STATE CHART DIAGRAM FOR

RECRUITMENT SYSTEM
DEPLOYMENT DIAGRAM

Deployment diagrams are used to visualize the topology of

the physical components of a system where the software
components are deployed.

Fig.79.DEPLOYMENT DIAGRAM
COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and

relationships among components in a system.

Fig.80..COMPONENT DIAGRAM