0% found this document useful (0 votes)
42 views

S.E Lab Manual Cse-B

Uploaded by

Satish Babu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views

S.E Lab Manual Cse-B

Uploaded by

Satish Babu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 181

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

(AI&ML)
SOFTWARE ENGINEERING LAB
MANUAL
(J22- CS308PC)

B.TECH CSE (AI&ML)


(II YEAR – I SEM)
(2023-24)

JYOTHISMATHI INSTITUTE OF TECHNOLOGY & SCIENCE


(Autonomous Institution – UGC, Govt. of India)
Recognized under 2(f) and 12 (B) of UGC ACT 1956
(Affiliated to JNTUH, Hyderabad, Approved by AICTE - Accredited by NBA &
NAAC – ‘A’ Grade - ISO 9001:2015 Certified)
Nustulapur , Ramakrishna Colony, LMD – 505481, Telangana State, India
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Vision
To acknowledge quality education and instill high patterns of discipline making the
students technologically superior and ethically strong which involves the
improvement in the quality of life in human race.

Mission
 To achieve and impart holistic technical education using the best of infrastructure,
outstanding technical and teaching expertise to establish the students in to competent
and confident engineers.
 Evolving the center of excellence through creative and innovative teaching learning
practices for promoting academic achievement to produce internationally accepted
competitive and world class professionals.

PROGRAMME EDUCATIONAL OBJECTIVES (PEOs)

PEO1 – ANALYTICAL SKILLS


 To facilitate the graduates with the ability to visualize, gather information, articulate, analyze,
solve complex problems, and make decisions. These are essential to address the challenges of
complex and computation intensive problems increasing their productivity.

PEO2 – TECHNICAL SKILLS


 To facilitate the graduates with the technical skills that prepare them for immediate
employment and pursue certification providing a deeper understanding of the technology in
advanced areas of computer science and related fields, thus encouraging to pursue higher
education and research based on their interest.

PEO3 – SOFT SKILLS


 To facilitate the graduates with the soft skills that include fulfilling the mission, setting goals,
showing self-confidence by communicating effectively, having a positive attitude, get
involved in team-work, being a leader, managing their career and their life.

PEO4 – PROFESSIONAL ETHICS


 To facilitate the graduates with the knowledge of professional and ethical responsibilities by
paying attention to grooming, being conservative with style, following dress codes, safety
codes, and adapting themselves to technological advancements.
PROGRAM SPECIFIC OUTCOMES (PSOs)

After the completion of the course, B. Tech Computer Science and Engineering, the graduates
will have the following Program Specific Outcomes:

1. Fundamentals and critical knowledge of the Computer System:- Able to Understand


the working principles of the computer System and its components , Apply the knowledge to
build, asses, and analyze the software and hardware aspects of it .

2. The comprehensive and Applicative knowledge of Software Development:


Comprehensive skills of Programming Languages, Software process models, methodologies,
and able to plan, develop, test, analyze, and manage the software and hardware intensive
systems in heterogeneous platforms individually or working in teams.

3. Applications of Computing Domain & Research: Able to use the professional,


managerial, interdisciplinary skill set, and domain specific tools in development processes,
identify the research gaps, and provide innovative solutions to them.
PROGRAM OUTCOMES (POs)
Engineering Graduates should possess the following:

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering


fundamentals, and an engineering specialization to the solution of complex engineering
problems.

2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.

3. Design / development of solutions: Design solutions for complex engineering problems


and design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.

4. Conduct investigations of complex problems: Use research-based knowledge and


research methods including design of experiments, analysis and interpretation of data, and
synthesis of the information to provide valid conclusions.

5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modeling to complex engineering
activities with an understanding of the limitations.

6. The engineer and society: Apply reasoning informed by the contextual knowledge to
assess societal, health, safety, legal and cultural issues and the consequent responsibilities
relevant to the professional engineering practice.

7. Environment and sustainability: Understand the impact of the professional engineering


solutions in societal and environmental contexts, and demonstrate the knowledge of, and need
for sustainable development.

8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.

9. Individual and team work: Function effectively as an individual, and as a member or


leader in diverse teams, and in multidisciplinary settings.

10. Communication: Communicate effectively on complex engineering activities with the


engineering community and with society at large, such as, being able to comprehend and
write effective reports and design documentation, make effective presentations, and give and
receive clear instructions.

11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a member and
leader in a team, to manage projects and in multi disciplinary environments.

12 .Life- long learning: Recognize the need for,and have the preparation and ability to
engage in independent and life-long learning in the broadest context of technological change
JYOTHISMATHI INSTITUTE OF TECHNOLOGY AND SCIENCE

GENERAL LABORATORY INSTRUCTIONS

1. Students are advised to come to the laboratory at least 5 minutes before (to the
starting time), those who come after 5 minutes will not be allowed into the lab.
2. Plan your task properly much before to the commencement, come prepared to the
lab with the synopsis / program / experiment details.
3. Student should enter into the laboratory with:
a. Laboratory observation notes with all the details (Problem statement, Aim,
Algorithm, Procedure, Program, Expected Output, etc.,) filled in for the lab
session.
b. Laboratory Record updated up to the last session experiments and other
utensils (if any) needed in the lab.
c. Proper Dress code and Identity card.
4. Sign in the laboratory login register, write the TIME-IN, and occupy the computer
system allotted to you by the faculty.
5. Execute your task in the laboratory, and record the results / output in the lab
observation note book, and get certified by the concerned faculty.
6. All the students should be polite and cooperative with the laboratory staff, must
maintain the discipline and decency in the laboratory.
7. Computer labs are established with sophisticated and high end branded systems,
which should be utilized properly.
8. Students / Faculty must keep their mobile phones in SWITCHED OFF mode during
the lab sessions. Misuse of the equipment, misbehaviors with the staff and systems
etc., will attract severe punishment.
9. Students must take the permission of the faculty in case of any urgency to go out;
10. Students should LOG OFF/ SHUT DOWN the computer system before he/she
leaves the lab after completing the task (experiment) in all aspects. He/she must
ensure the system / seat is kept properly.

HEAD OF THE DEPARTMENT PRINCIPAL


JYOTHISMATHI INSTITUTE OF TECHNOLOGY AND SCIENCE
II Year B.Tech. CSE(AI&ML)-I SEM

L/T/P/
C0/0/2/
1
(J-22 CS308PC) SOFTWARE ENGINEERING

LAB List of Experiments

Prerequisites
1. A course on “Programming for Problem Solving”

Co-requisite
1. A Course on “Software Engineering”

Do the following 8 exercises for any two projects given in the list to sample
projects or any other projects:

1) Development of problem statement.

2) Preparation of Software Requirement Specification Document ,Design


Documents and Testing Phase related documents.
3) Preparation of Software Configuration Management and Risk Management
related documents.
4) Study and us age of any Design phase CASE tool.

5) Performing the Design by using any Design phase CASE tools.

6) Develop test cases for unit testing and integration testing.


7) Develop test cases for various white box and black box testing Techniques.
Sample Projects:

1. Passport automation System

2. Book Bank

3. Online Exam Registration

4. Stock Maintenance System

5. Online course reservation system

6. E-ticketing

7. Software Personnel Management System

8. Credit Card Processing


9. E-book management System.

10. Recruitment system

TEXT BOOKS:

1. Software Engineering, A practitioner’s Approach-

RogerS.Pressman,6thedition, Mc GrawHill International Edition.

2. SoftwareEngineering-Sommerville,7thedition, Pearson Education.


3. The unified modeling language user guide Grady Booch,
James Rambaugh, IvarJacobson,Pearson Education.
INDEX

Signature
Date of of Faculty
S. No. Name of Experiment Page No. Remarks
Experiment with Date

1
1 Passport Automation System

19
2 Book Bank

38
3 Online Exam Registration

53
4 Stock Maintenance System

Online Course Reservation 64


5 System

78
6 E Ticketing

Software Personnel 96
7 Management System

115
8 Credit Card Processing

131
9 EBook Management System

149
10 Recruitment System
SE LAB A.Y:2023-24

TASK1: 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 (data) is added to the database.

DEPT.OF CSE Page1


SE LAB A.Y:2023-24

(II) SOFTWAREREQUIREMENTSPECIFICATION:

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.

DEPT.OF CSE Page2


SE LAB A.Y:2023-24

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 fil in their
personal details and submits then 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 form annual document verification.

DEPT OF CSE Page3


SE LAB A.Y:2023-24

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.

DEPT OF CSE Page4


SE LAB A.Y:2023-24

TECHNOLOGIESTO BEUSED
• HTML
• JSP
• JavaScript
• Java

TOOLSTOBEUSED
• Eclipse IDÉ(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.

OVERALLDESCRIPTION
PRODUCTPERSPECTIVE

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.

DEPT OF CSE Page5


SE LAB A.Y:2023-24

SOFTWAREINTERFACE

• 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 –Oracle11gdatabase.

HARDWAREINTERFACE

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


systems have access to the database in the server.

SYSTEMFUNCTIONS
 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.

DEPT OF CSE Page6


SE LAB A.Y:2023-24

USERCHARACTERISTICS

 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 the Administrator if he finds any discrepancy with the
applicant. He communicates 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.

DEPT OF CSE Page7


SE LAB A.Y:2023-24

ASSUMPTIONSANDDEPENDENCIES
 The Applicant sand Administrator must have basic
knowledge of computers and English Language.

 The applicants may be required to scan the documents and send.

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

ACTORSINVOLVED:
1. Applicant
2. Passport Officer
3. Police

USE-CASENAME: LOGIN
The applicant log into the system to obtain a passport

USE-CASENAME: REGISTRATION
The Applicant enters his name and details for applying a Passport. The
applicant initially give his/ her details for registration.

DEPT OF CSE Page8


SE LAB A.Y:2023-24

USE-CASENAME: VERIFICATION
The system verifies the applicant mandatory information given by him/her.

USE-CASENAME: CHECKS TATUS


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

USE-CASENAME: 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
bysuggestingittotheAdministratorifhefindsanydiscrepancywiththeapplica
nt.Hecommunicates via this PAS.

USE-CASENAME: DISPATCHPASSPORT
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

DEPT OF CSE Page9


SE LAB A.Y:2023-24

logi

applic

registra
passport

verificat

check

enqu
poli

dispatchpassport

Fig.1.USECASEDIAGRAMFORPASSPORTAUTOMATIONSYSTEM

ACTIVITYDIAGRAM:
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.

DEPT OF CSE Page10


SE LAB A.Y:2023-24

Fig.2.ACTIVITY DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

CLASSDIAGRAM:
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.

DEPT OF CSE Page11


SE LAB A.Y:2023-24

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) LOGINCLASS:

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) APPOINMENTCLASS:

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) REGISTRATIONCLASS:

The attributes are applicant id, name, dob, gender, birthplace,


fathername,addr1,addr2,district,state,country,pincode,mobile,emailid,qualification.The
operation areadd( ), modify( ),view().

DEPT OF CSE Page12


SE LAB A.Y:2023-24

4) AUTHORITYCLASS:
The attributes of this class are officered, name, designation, and password. The
operations are search ( ).

5) VERIFICATIONCLASS:

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

DEPT OF CSE Page13


SE LAB A.Y:2023-24

INTERACTIONDIAGRAM:
 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
event s 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.

DEPT OF CSE Page14


SE LAB A.Y:2023-24

UI LoginClass
LoginClass RegistrationClass
RegistrationClass AppointmentClass
AppointmentClass Database
Database
:applicant

CreateLogin

EnterUsername/Pwd

Checkusername/Pwd

saveusername/pwd

Signin

getuse rname/pwd

Checkusername/Pwd

s howRegistrationForm

Enterapplicantinformati on

checka plicantinformation

saveapplica ntinformation

getdateandtime

savedateandtime

showsapplicantID,Date& time

Fig.4.SEQUENCE DIAGRAM FOR LOGIN AND VERIFICATION

DEPT OF CSE Page15


SE LAB A.Y:2023-24

5:Checkusername/Pwd
12:Checkusername/Pwd

1:CreateLogin
3:EnterUsername/Pwd
9:Signin 4:
14:Enterapplicantinformation LoginCla
UI
ss

2:
8:
:applicant 13:showRegistrationForm 10:getusername/pwd
24:showsapplicantID,Date&time
6:sav euse
rname/pwd
23: 7:
11:
15:
16:checkapplicantinformation
Databas
17:saveapplicantinformation e

20:savedateandtime
Registratio 18:
nClass 19: getdateandtime
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 this to enter his
details.
 The details entered are verified by the Passport Authority and
theapplicantisapprovedifthedetailsmatchthenthepassportisdispatc
h, otherwise an appropriate error message is displayed.

STATECHARTDIAGRAM:

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

DEPT OF CSE Page16


SE LAB
A.Y:2023-24

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.

DEPT OF CSE Page17


SE LAB
A.Y:2023-24

Fig.7.DEPLOYMENT DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

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

Fig.8.COMPONENT DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

DEPT OF CSE Page18


SE LAB
A.Y:2023-24

TASK2: 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) SOFTWAREREQUIREMENTSSPECIFICATION:

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 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. The system has been carefully verified and validated in order to satisfy it.

DEPT OF CSE Page19


SE LAB
A.Y:2023-24

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

DEPT OF CSE Page20


SE LAB
A.Y:2023-24

TECHNOLOGIESTO BEUSED

Visual Basic
Oracle11g

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

OVERALLDESCRIPTION:

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

PRODUCTPERSPECTIVE

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
DEPT OF CSE Page 21
SE LAB
A.Y:2023-24
of data stored in. This minimizes the time duration in which the user receives the books
or magazines.

SOFTWAREINTERFACE

Front End Client - The Student and Librarian online interface is built using
Visual studio.
BackEnd-Oracle11gdatabase

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

SYSTEMFUNCTIONS

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

DEPT OF CSE Page 22


SE LAB
A.Y:2023-24

ASSUMPTIONSANDDEPENDENCIES

 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

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


DEPT OF CSE Page 23
SE LAB
A.Y:2023-24

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.

USECASENAME: 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.

USECASENAME: 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.

DEPT OF CSE Page 24


SE LAB
A.Y:2023-24

USECASENAME: 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 booki
d, author information, publication information, purchased date, prize and number of
copies.
Post Condition: Update the information in catalogue.

DEPT OF CSE Page 25


SE LAB
A.Y:2023-24

book_issu

studen
libraria

book_retu

book_ent

vend
search

book_order

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

DEPT OF CSE Page 26


SE LAB
A.Y:2023-24

ACTIVITYDIAGRAM:

Activity diagrams are graphical representations of workflows of step wise 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 behavior of the system.

DEPT OF CSE Page 27


SE LAB
A.Y:2023-24

DEPT OF CSE Page 28


SE LAB
A.Y:2023-24

collectsquotationfr
omvendors

no

ifsatisfiedwith
norms?

yes

placeorder

discount&modeofp
aymentfinalised

takesdelivery

billamtpaid

Fig.11. Activity Diagram[OrderBook]


DEPT OF CSE Page 29
SE LAB
A.Y:2023-24

showsidandli
brarycard

librarianm
akesentry

onorbeforer
eturndate? no

paysfine

yes

librarianapprovest
ransaction

DEPT OF CSE Page 30


SE LAB
A.Y:2023-24
Fig.12.Activity Diagram[ReturnBook]

DEPT OF CSE Page 31


SE LAB
A.Y:2023-24

CLASSDIAGRAM:

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:


1. Student
2. Book
3. Issue
4. Return
5. Vendor
6. Details

1) STUDENT:

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


enrolling no, name, DOB, father name, address, dept name, batch and book limits.
The operations of this class are addStInfo(), deleteStInfo(), modify StInfo().

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

DEPT OF CSE Page 32


SE LAB
A.Y:2023-24
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

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 ().

DEPT OF CSE Page 33


SE LAB
A.Y:2023-24

Fig.13.ClassDiagramForBook Bank System

DEPT OF CSE Page 34


SE LAB
A.Y:2023-24

SEQUENCEDIAGRAM:

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
performedbythe“to”object.The“to”objectperformstheoperationusingamethodthatthe
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.

DEPT OF CSE Page 35


SE LAB
A.Y:2023-24

:student :librarian :issue ::return


return search DB

1:requestbook

2:checkavailablebook

3:checkavailablebook

4:notavilable

5:notavilable

6:notavailable

7:requestforanotherbook

8:checkavailability

9:checkavailabilty

10:available

11:avilable

12:avilable

13:providestudentdetails

14:enterissuedata

15:updateissuestatus

16:issuestatusupdated

17:updatedsuccessfully

18:issuebook

19:requesttoreturnbook

20:enterthebookdetails

21:updatereturnstatus

22:returnstatusupdated

23:updatedsuccessfully

24: bookreturned

Fig.14.SequenceDiagram For Book Issue &Return

DEPT OF CSE Page36


SE LAB
A.Y:2023-24

1:requestbook
7: request for another 14:enterissuedata
book13: provide student
details19:requesttoreturnb :issue
ook :librarian 17:updatedsuccessfully

6:not available
12:avilable 15:updateissuestatu
18:issuebook
:student 24:bookreturned 16:issuestatusupdated

2: check available DB
book8:checkavailabil
23:updatedsuccessfully
ity
20:enterthebookdetails
5: notavilable
11:avilable 3:checkavailablebook
21:updatereturnstatus
9:checkavailabilty

4:notavilable
22:return statusupdated
10:available

:return
search

Fig.15.CollaborationDiagram For BookIssue &Return

DEPT OF CSE Page37


SE LAB
A.Y:2023-24

STATECHART 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

start bookissue bookreturn

vendor suppliesbook studentreturnsbooktolibrary[pa


studenttakesbookfr
tothelibrary ysfineifneeded]
omlibrary

Fig.16.State Chart Diagram

DEPLOYMENTDIAGRAMAND COMPONENTDIAGRAM

Deployment diagrams are used to visualize the topology


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

DEPT OF CSE Page 38


SE LAB
A.Y:2023-24

Fig.17. Deployment Diagram

DEPT OF CSE Page 39


SE LAB
A.Y:2023-24

TASK3: Exam Registration System

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

PROCEDURE :(I)PROBLEMSTATEMENT
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 he 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 there port 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.

SOFTWAREREQUIREMENTSPECIFICATION:
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

DEPT OF CSE Page 40


SE LAB
A.Y:2023-24
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 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 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 form annual document verification.

DEPT OF CSE Page 41


SE LAB
A.Y:2023-24

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 Tex t Transfer Protocol.
• TCP/IP–Transmission Control Protocol/Internet Protocol is the
communication protocol used to connect hosts on the Internet.

TECHNOLOGIESTOBEUSED
• HTML
• JSP
• JavaScript
• Java

TOOLSTOBEUSED
• Eclipse IDE(Integrated Development Environment)
• Rational Rose tool(for developing UMLPatterns)

OVERVIEW

SRS includes two sections overall description and specific requirements –

DEPT OF CSE Page42


SE LAB
A.Y:2023-24
Overall Description will describe major role of the system components and
inter-connections.
Specific Requirements will describe roles & function soft he actors.

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 -Oracle11gdatabase

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

SYSTEMFUNCTIONS
• 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.

DEPT OF CSE Page43


SE LAB
A.Y:2023-24

USERCHARACTERISTICS

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

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

(II) USECASEDIAGRAM:
The Exam Registration use cases in our system are:
1. Lo gin
2. View exam details
3. Register
4. Acknowledgement
5. Fee Processing

ACTORSINVOLVED:
1. Student
2. System DB
DEPT OF CSE Page44
SE LAB
A.Y:2023-24

USE-CASENAME:LOGIN
The student enters his username and password to login and retrieve the information.

USE-CASENAME: VIEW EXAMDETAILS


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

USE-CASENAME: REGISTER
The student should notify the fee details that only the student can pay the correct
amount.

USE-CASENAME: ACKNOWLEDGEMENT
The exam fees should be paid by the student to get the hall ticket from the exam
controller.

USE-CASENAME: FEE PROCESSING


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

DEPT OF CSE Page45


SE LAB
A.Y:2023-24

Logi

Viewexam
Studen System
<<include>>
Register

Fig.18.UsecaseDiagramForExam Registration System

DEPT OF CSE Page46


SE LAB
A.Y:2023-24

ACTIVITYDIAGRAM:

Fig.19.Activity Diagram For Exam Registration System

DEPT OF CSE Page47


SE LAB
A.Y:2023-24

CLASSDIAGRAM:

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 r

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(), new fees details().

2) EXAM_DETAILS

It consists of four attributes and six methods. The attributes are userid,
password, exam fees, fees due. The methods are login(), logout(), fees details(), display
fees(), conformation(), exam controller().

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

DEPT OF CSE Page48


SE LAB
A.Y:2023-24

Fig.20.ClassDiagram For Exam Registration System

DEPT OF CSE Page49


SE LAB
A.Y:2023-24

INTERACTIONDIAGRAM:

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 operation 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 in


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

DEPT OF CSE Page50


SE LAB
A.Y:2023-24
UI:Internet :Register :Exam_details
Explorer

UI: :Register :Exam_details


InternetE
:Student xplorer :SystemDB

enter(uid,pwd)

athio n
eckvalidC

Storeuid,pwd
Successfullystored

Viewexamdetails
Getexa mdetails

Getregform

Fillregistrationform

eckgivenCdha ta

register

rifycriterViae

Storestudentdetails
returnregid

Acknowledgement&iddisplayreg

Fig.21.SequenceDiagramForRegistrationSystem

DEPT OF CSE Page51


SE LAB
A.Y:2023-24

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.

DEPT OF CSE Page49


SE LAB
A.Y:2023-24

:Exam_details

:SystemDB

:Student 1:enter(uid,pwd)4:Successfullystored 8:
6:Viewexamdetails
10:Getregform
12:Fillregistrationform 7:Getexamdetails3
16:Store studentdetails :Storeuid,pwd
17: returnregid 2:Checkvalidation
5:
13:Checkgiven
data
9:
11:
15:Verifycriteria 19:Acknowledgement&displayreg id

18: UI:Internet
Explorer
:Register
14:register

Fig.21.CollaborationDiagramForRegistrationSystem

DEPT OF CSE Page50


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAMAND COMPONENTDIAGRAM

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

COMPONENTDIAGRAM

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

DEPT OF CSE Page51


SE LAB
A.Y:2023-24

Fig.23.Component Diagram

DEPT OF CSE Page52


SE LAB
A.Y:2023-24

TASK4: Stock Maintenance

AIM: To create a system to perform the Stock maintenance

PROCEDURE :(I)PROBLEMSTATEMENT

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) SOFTWAREREQUIREMENTSPECIFICATION
INTRODUCTION
Stock maintenance is an interface between the customer and the salesperson. 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.

DEPT OF CSE Page53


SE LAB
A.Y:2023-24

DEFINITIONS,ACRONYMS
ANDTHEABBREVIATIONS
 Market Data provider: One who analyze the product and distribute the news.
 Customer: One who takes order of product
 Salesperson: One who maintains the stock details

TECHNOLOGIESTOBEUSED
 Visual Studio
 VBScript

TOOLSTOBEUSED
• 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.

OVERALLDESCRIPTION
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

SYSTEMFUNCTIONS
Secure order of information by the customer
• Schedule the customer an appointment form annual delivery of the product.

DEPT OF CSE Page54


SE LAB
A.Y:2023-24

USERCHARACTERISTICS

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) USECASE 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. Purchased details: Used for tracking items that have been ordered.
3. Sales details: Used forgive the sales particulars about a item.
4. Stock details: Used forgive the stock detail in a shop.
5. Purchase the product : Used to provide bills for the customer.
DEPT OF CSE Page55
SE LAB
A.Y:2023-24

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. Shop keeper: The items ordered by the customer are validated.
3. Company: Maintains the stock details after delivering the items to the
customer.

DEPT OF CSE Page56


SE LAB
A.Y:2023-24

productdetails

purchasedetails

shopkeeper
custom
er
salesdetails

stockdetails

purchasetheproductsupplythe

product
company

Fig.24.UseCaseDiagram

ACTIVITYDIAGRAM
Itshowsorganizationandtheirdependenceamongthesetofcomponents.Thesediagra
msareparticularlyusefulinconnectionwithworkflow 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.

DEPT OF CSE Page57


SE LAB
A.Y:2023-24

login

order check availability


product

product stock
details

if available ifnotavailable
dopay
ment

c
a
n
c
l
e

o
r
d
e
r

get
payment

recive the
stock Fig.25.ActivityDiagram

logout

DEPT OF CSE Page58


SE LAB
A.Y:2023-24
CLASS DAIGRAM DESCRIPTION:
 A class diagram describes the type of objects in system and various
kinds of relationships that exists among them.
 Classdiagramsandcollaborationdiagramsarealternaterepresentationsof
object models.
The Stock maintenance system class diagram consists of seven classes:

DEPT OF CSE Page59


SE LAB
A.Y:2023-24

7. Purchase Details: One who takes orders for the product?


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

Fig.26.ClassDiagram

UMLINTERACTIONDIAGRAMS
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 show the system behaves during dynamic execution.

SEQUENCEDIAGRAM

A sequence diagram represents the sequence and interactions of a givenUSE-


CASEorscenario.Sequencediagramscancapturemostoftheinformationaboutthesystem.Mos
tobjecttoobjectinteractionsandoperationsareconsideredeventsandeventsincludesignals,
inputs, decisions, interrupts, transitions and actions to perform users to devices.

DEPT OF CSE Page60


SE LAB
A.Y:2023-24

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 shopekeeper dealer database

customer shopekeeper dealer database


1. requestforitem

2. enterthedetails

3. sendfor item

4. check forproduct availability

5. updateproductdetails

.6. product available

7.sendforquation

8.requestfordelivery

9.orderitem

10. updatedeliverydetails

11.productdelivery

Fig.27.SequenceDiagram
DEPT OF CSE Page61
SE LAB
A.Y:2023-24

COLLABORATIONDIAGRAM
Collaboration diagram and sequence diagrams are alternate representations of an
interaction. A collaboration diagram is an interaction diagrams 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 diagram shows 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
Shop ke
custome eper
r
enter the details 11:product delivery
2:

7:send for quation update delivery details9:


10:
Recording sales

Sendfor item order


item3:

5:update product details

4:check for availability


dealer data base

6:product available
Fig.28.CollaborationDiagram

DEPT OF CSE Page62


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAMAND COMPONENTDIAGRAM

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.

DEPT OF CSE Page63


SE LAB
A.Y:2023-24

TASK5: 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 the course
he/she wants. The administrator can maintain the course details and view all the
students who have registered to any course.

(II) SOFTWAREREQUIREMENTSPECIFICATION

INTRODUCTION

Course Reservation System is an interface between the Student and


theRegistrarresponsiblefortheissueofCourse.Itaimsatimprovingtheefficiency 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


itwouldtakesseveralmonthsforthecoursetoreachtheapplicant.Considering the fact that
the number of applicants for course is increasing every year, an Automated System
becomes essential to meet the demand. So

DEPT OF CSE Page64


SE LAB
A.Y:2023-24

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
or developing and running distributed java applications.
 HTTP

DEPT OF CSE Page65


SE LAB
A.Y:2023-24

Hyper Text Transfer Protocol.


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

TECHNOLOGIESTOBEUSED
• HTML
• JSP
• Java script
• Java

TOOLSTOBEUSED
• 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.

OVERALLDESCRIPTION

PRODUCTPERSPECTIVE

The OCR S acts as an interface between the Student and the 'Registrar'.
This system tries to make the interface as simple as possible and a the same time not
risking the security of Data stored in. This minimizes the time duration in which the user
receives the course.

DEPT OF CSE Page66


SE LAB
A.Y:2023-24

SOFTWAREINTERFACE
• Front End Client - The Student and Registrar online interface is built using JSP and
HTML. The Administrator’s local interface Is built using Java.
• Web Server – Tomcat Apache application server (Oracle Corporation).
• Back End –Oracle11gdatabase.

HARDWAREINTERFACE
The server is directly connected to the client systems. The client systems have access to
the data base in the server.

SYSTEMFUNCTIONS
• 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.

USERCHARACTERISTICS

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

DEPT OF CSE Page67


SE LAB
A.Y:2023-24
CONSTRAINTS
• The applicants require a computer to submit the ir information.
• Although the security is given high importance, there is always en 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.

ASSUMPTIONSANDDEPENDENCIES
• 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) U
SE-CASEDIAGRAM:
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

ACTORSINVOLVED:

1. Student
2. Registrar

USE-CASENAME: 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.

DEPT OF CSE Page68


SE LAB
A.Y:2023-24

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-CASENAME: 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 data base.

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-CASENAME: CHECK STATUS


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

DEPT OF CSE Page69


SE LAB
A.Y:2023-24

View course details

Registrar

Student
login

<<include>>
payfee
Reserve for
coursecourse

checkstatus

Fig.30.Use-CaseDiagram
SE LAB
A.Y:2023-24

ACTIVITYDIAGRAM:

Fig.31.ActivityDiagram

View Displa

Selects

Fills

Sendfor

Eligibilit Retrieve

Registers

DEPT OF CSE Page70


SE LAB
A.Y:2023-24

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, studentaddress2, 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) COURSECATALOG:

The course catalog class consist of course id, course name, course duration course fee,
course eligibility, total no of seat, course avai 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().

DEPT OF CSE Page71


SE LAB
A.Y:2023-24

Fig.32.ClassDiagram

DEPT OF CSE Page72


SE LAB
A.Y:2023-24

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

DEPT OF CSE Page73


SE LAB
A.Y:2023-24

UI ::ReReserservveCou
eCoursrse ::Co
Cou
urse
seC
Cattaalog
lo
UI e g
:Student

Login(username,
ppwd)
CheckData

Viewcoursedetails

getCoursedetails

ReservecourseViewr

eservationform

Fillsupthereservationform

confirmReservation

getCourseDetails

ckeckEligibilityCriteria

Eligible&Seatavailable

Registersforthecourse

Fig.33. SEQUENCE DIAGRAM

DEPT OF CSE Page 74


SE LAB
A.Y:2023-24
STATECHARTDIAGRAM:
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.

Logintocourseregistration Viewc getlistofcourses Select Enterdata Fillform


ourse course

afterclicking

Payfees Gets Submit


Confirmation form
Eligible sending formtoregistrar

Getsreceipt
noteligible

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.

DEPT OF CSE Page 75


SE LAB
A.Y:2023-24

Fig.36.DeploymentDiagram

DEPT OF CSE Page 76


SE LAB
A.Y:2023-24
COMPONENTDIAGRAM:

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

Fig. 37. Component Diagram

DEPT OF CSE Page 77


SE LAB
A.Y:2023-24
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 Rail way 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
theirhomeitself.Allhe/shehastodoistojustloginandentertherequireddetails.Afterthisthe
reservationdatabaseisupdatedwiththe 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) SOFTWAREREQUIREMENTSPECIFICATIONIINTRODUC

TION

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.

DEPT OF CSE Page 78


SE LAB
A.Y:2023-24

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 Name Records

• HTML –Markup Language used for creating web pages.

DEPT OF CSE Page 79


SE LAB
A.Y:2023-24
J2EE–Java2EnterpriseEditionisaprogrammingplatform 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.

TECHNOLOGIESTO BEUSED

• HTML
• JSP
• Java script
• Java

TOOLSTOBEUSED

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

DEPT OF CSE Page 80


SE LAB
A.Y:2023-24

OVERALL DESCRIPTION
PRODUCTPERSPECTIVE
This system tries to make the interface as simple as possible and at the same time not
asking the security of data stored in. This minimizes the time duration in which the user
receives the ticket.

SOFTWAREINTERFACE

• Front End Client - The passenger and System


onlineinterfaceisbuiltusingJSPandHTML.TheAdministrators'slocalinterfaceis built using
Java.

 Web Server–Apache Tom cat Server (Oracle Corporation)


 Back End -Oracle11gdatabase

HARDWARE INTERFACE

The server is directly connected to the client systems. The client system have access to
the data base in the server.

SYSTEM FUNCTIONS

• Secure Registration on fin formation by the Passengers.

DEPT OF CSE Page 81


SE LAB
A.Y:2023-24
• 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.

USERCHARACTERISTICS
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-CASEDIAGRAM
The online ticket reservation system uses the following gusecases:
1. Request forseat availability
2. Make Reservation
3. Cancellation
4. Check status
5. Print ticket
DEPT OF CSE Page 82
SE LAB
A.Y:2023-24

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 such as, train number, source station, destination station, arrival time, departure
time, fare and number of seats available.

USE-CASENAME: MAKE RESERVATION

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-CASENAME: 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-CASENAME: CANCEL TICKET

DEPT OF CSE Page 83


SE LAB
A.Y:2023-24
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-CASENAME: 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>>

printreport
makeReservation
Passenger System

cancellation

checkstatus

Fig.38.Use-Case Diagram For Airline Reservation

DEPT OF CSE Page 84


SE LAB
A.Y:2023-24

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of step wise 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 behavior 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 Data Base.

DEPT OF CSE Page 85


SE LAB
A.Y:2023-24

Checkseatavailablitybasedond
ate/train/reservationtype

Yes
Is it
No validdata
?
Show Displaytherequiredt
theerrorp raininformation
age

Fig.39.Activity Diagram[Check Availability]

DEPT OF CSE Page 86


SE LAB
A.Y:2023-24

Login(usernam
e
,password)

Ye
Checkthe

Isitvalid N
Yes
Displaythe
cancellation Show
errormessagetoe
nter
Selectthe
passenger want
to
Perform Ye
amount

N
isitv
alid
Yes
Store& Askto
updatethe enter

Show
theConfirm wa
atio ntto
N

Print
the N

DEPT OF CSE Page 87


SE LAB
A.Y:2023-24

requesttocheckp
nrstatus

EnterthePNR
number

IsvalidPNRYesn
No o?
Displayt
I nvalid hestatus
PNRnum
ber

Fig.41.Activity Diagram[Check Status]

DEPT OF CSE Page 88


SE LAB
A.Y:2023-24

Login(usernam
e

Checkthedata Ye
with

Isitvaliduser
Yes
Display
thecancellationpage Showerrormess
agetoenter

Select
thepasseng want
er to

Ye

N
is
itvali
d
Store& Askto
updatethe enter

Show want
theConfirm to
N
atio

DEPT OF CSE Page 89


SE LAB
A.Y:2023-24

CLASSDIAGRAM:

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 relationship same 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 update Status()operation.

DEPT OF CSE Page 90


SE LAB
A.Y:2023-24

Fig.43.ClassDiagramForE-Ticketing

DEPT OF CSE Page 91


SE LAB
A.Y:2023-24

INTERACTIONDIAGRAM:

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.

DEPT OF CSE Page 92


SE LAB
A.Y:2023-24

reserveTicket cancelTicket:tic :seatAvailStatus Syste


:ticketReservatio ketReservation
n
:Passenger

reserveTicket:tic cancelTicket:tic : System


ketReservation ketReservation seatAvailStatus

Login(username,password

Check
givendata

Display the

reservationpage Enter

the

passengerdetailsPerform

money
Update
transaction
Store
thedeta
ils

Confirm&DisplaytheticketP

rinttheticket

requesttocancelticket

Display

thecancellationpageSelec

tthepassenger Verifygivendetails

Update

Store
thedeta
ils

Ticket

Fig.44.SequenceDiagram

DEPT OF CSE Page 93


SE LAB
A.Y:2023-24

7:Verifygiven details
1:
Login(username,password)5:Ent
erthepassengerdetails6:Perform
moneytransaction13:Printthetic reserveTicket
ket :ticketReservation

4: Display the reservation 2:Checkgivendata3:


page12:Confirm&Display theticket
:Passenger
Registered user
System

14:request tocancelticket 8:Updatestatus


16:Selectthepassenger details 11:

9: Store the
15:Displaythecancellationpage22:Ti
details19:Storethedet
cketcancelled ails

17:Verifygivendetails
10:Updatedsuccessfully
20:Updatedsuccessfully

18:Updatestatus :seatAvailStatus
cancelTicket
:ticketReservation
21:

Fig.45.CollaborationDiagram

DEPT OF CSE Page 94


SE LAB
A.Y:2023-24
DEPLOYMENTDIAGRAMAND COMPONENTDIAGRAM

Deployment diagrams are used to visualize the topology of the physical


components of a system where the software components are deployed.

Fig.46.DeploymentDiagram

DEPT OF CSE Page 95


SE LAB
A.Y:2023-24
TASK7: SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM: To implement software for software personnel management system

PROCEDURE: (I) PROBLEMSTATEMENT:

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.
Payrolladministratorskeeptrackofalltheinformationincludingaddingnewemployees,
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

DEPT OF CSE Page 96


SE LAB
A.Y:2023-24
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,
ACRONYMSANDTHEABBREVIATI
ONS

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

DEPT.OF CSE Page 97


SE LAB
A.Y:2023-24

 J2EE

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

TECHNOLOGIESTO BEUSED
• HTML
• JSP
• Java script
• Java
• XML
• AJAX

TOOLSTOBEUSED
• 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.

DEPT.OF CSE Page 98


SE LAB
A.Y:2023-24

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.

SOFTWAREINTERFACE

• Front End Client –The applicant and Administrator online interface is built
using JSP and HTML. The ADMINISTRATOR's local interfaces built using
Java.
• Web Server–A pacheTomcatapplicationserver (Oracle Corporation).

• Back End –Oracle11gdatabase.

HARDWAREINTERFACE

The server is directly connected to the client systems. The client systems have
access to the database in the server.
SYSTEMFUNCTIONS
The payment module greatly reduces the workload of the ADMINISTRATOR
department by automating the payroll process, allowing ADMINISTRATOR to ensure
the pay roll functions are completed on time and without errors. The pay roll class
automatically calculates payment amounts and various deductions such as income tax
before generating pay checks and employee tax reports.

DEPT.OF CSE Page 99


SE LAB
A.Y:2023-24

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.

 Data base manager

DB manager stores all the data related to Employee and Administrator.

CONSTRAINTS

 The administrator requires a system to monitor information of the employee.

ASSUMPTIONSANDDEPENDENCIES
 The employee and Administrator must have basic knowledge of computers and
English Language.
(III) USECASEDIAGRAM:

The Software personnel management system use cases are:

1. Login

2. Job Assigned

3. View Salary

DEPT.OF CSE Page 100


SE LAB
A.Y:2023-24

4. View Employee details

5. Generate payment slip

6. Create DB

7. Update DB

8. Delete DB

ACTORSINVOLVED:
1. Employee
2. Administrator
3. Data base Manager
USE-CASENAME: LOGIN
The Employee log into the system to view the salary details

USE-CASENAME: JOB ASSIGNED


The employee views the job assigned to him/ herby the Administrator.

USE-CASENAME: VIEWSALARY
TheemployeeviewsthesalarydetailsefficientlyfromtheSPMS.Theemployeeswillalsobeabl
etoknowthenumberofhoursworkedperdayand total of all hours spent on a project and
total pay received year-to-date etc.
.

USE-CASENAME: VIEWEMPLOYEEDETAILS
The Administrator views the details of the employee for the pay roll process

USE-CASENAME: GENERATEPAYMENTSLIP
The Administrator generates the pay slip based on the details of the no of hours/no of
days worked by the employee.

DEPT.OF CSE Page 101


SE LAB
A.Y:2023-24

USE-CASENAME: CREATE DB
The data base manager creates individual data base tables for the employees

USE-CASENAME: UPDATEDB
When employee information changes the data base manager updates individual data
base tables for the employees.

USE-CASENAME: DELETEDB
When an employee relieves/terminated the data base manager deletes individual data
base tables for the employees.

Login

JobAssigned

Administrator

Employee ViewSalary

ViewEmployeedetails

DEPT.OF CSE Page 102


SE LAB
A.Y:2023-24

GeneratePaymentSlip

CreateDB

UpdateDB

DeleteDB

DatabaseManager

Fig.47. USECASE DIAGRAM FOR SOFTWARE


PERSONNEL MANAGEMENT SYSTEM

DEPT.OF CSE Page 103


SE LAB
A.Y:2023-24

ACTIVITYDIAGRAM:
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
dataflow.

Employe Administrat

Logi

Logi
view
employe

Do

Generat
e

View
Salary
ViewPayro

Logou

Fig.48.ACTIVITY DIAGRAM FOR SOFTWARE


PERSONNEL MANAGEMENT
SYSTEM

DEPT.OF CSE Page 104


SE LAB
A.Y:2023-24

CLASSDIAGRAM:
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. Data base Manager class
4. Payment class

1. EMPLOYEECLASS
It consists of seven attributes and two operations. The attributes are EMP id, EMP
name, EMP password, address, mobile number, date, Hours Worked. The operations of
this class are Login () and view salary ( ).

2. ADMINISTRATORCLASS
It consists of attributes Admin id, Admin name and Admin password. The operations
are login (), Generate pay roll (), view payroll () and view employee detail ( ).

3. DATABASEMANAGERCLASS
The attributes of this class are DB manager id, DB manager name () and DB manager
password. The operation are create ( ), update ( ), delete ( ) and display pay roll ( ).

DEPT.OF CSE Page 105


SE LAB
A.Y:2023-24

4. PAYMENTCLASS
The attributes of this class are payment id, EMP id, date, Basic pay, HRA, DA, PF, Net
pay and Gross pay. The operation are calculate salary () and Generate Slip ().

DEPT.OF CSE Page 106


SE LAB
A.Y:2023-24

Fig.49.CLASS DIAGRAM FOR SOFTWARE PERSONNEL


MANAGEMENT SYSTEM

DEPT.OF CSE Page 107


SE LAB
A.Y:2023-24
INTERACTIONDIAGRAM:
 A sequence diagram represents the sequence and interactions of a given USE-
CASE or scenario .Sequence diagram scan capture most of the information
about the system.
 Mostobjecttoobjectinteractionsandoperationsareconsideredeventsandeventsincl
udesignals, 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.

DEPT.OF CSE Page 108


SE LAB
A.Y:2023-24

EMPLOYEE:

Fig.50.SEQUENCEDIAGRAMFOREMPLOYEE

DEPT.OF CSE Page 109


SE LAB
A.Y:2023-24

UI Payment Database
:Administrator
Manager
SeekLogin

ViewEmployeeDetails

DisplayEmployeeDetail

GeneratePayslip

CalculateSalary

returnsalary

DisplayPayroll

Fig.52.SEQUENCE DIAGRAM FOR ADMINISTRATOR

DEPT.OF CSE Page 110


SE LAB
A.Y:2023-24

3.viewemployeedetails
7:generatepayslip1:seeklogin

administrator UI

2:
6:displayemployeedetai
ls12:display payroll
5:
11:
4:
8:

payment
DBmanager
10:returnsalary
9:calculatesalary

Fig.53.COLLABORATION DIAGRAM FOR EMPLOYEE

STATETRANSITIONDIAGRAM
 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.

DEPT.OF CSE Page 111


SE LAB
A.Y:2023-24

Login ViewEmployee Generate calculate


Detail Payroll Salary

Display
Payroll

Fig.54. STATE TRANSITION DIAGRAM FOR SOFTWARE


PERSONNEL MANAGEMENT SYSTEM

DEPT.OF CSE Page 112


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAMANDCOMPONENTDIAGRAM
Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components
are deployed

Fig.55.DEPLOYMENTDIAGRAMFORSOFTWAREPERSONN
ELMANAGEMENTSYSTEM

COMPONENTDIAGRAM

Component diagrams are used to visualize the organization and


relationships among components in a system.

DEPT.OF CSE Page 113


SE LAB
A.Y:2023-24

Fig.56.COMPONENT DIAGRAM FOR SOFTWARE


PERSONNEL MANAGEMENT SYSTEM

DEPT.OF CSE Page 114


SE LAB
A.Y:2023-24

TASK8: 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, there by 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 “un
trusted” 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)

DEPT.OF CSE Page 115


SE LAB
A.Y:2023-24

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
ofthebusinessday.Themerchantthenreentersthetransactionviathegateway 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.

DEPT.OF CSE Page 116


SE LAB
A.Y:2023-24

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 Master Card Electronic Commerce Indicator (ECI)
regulations.
Multiple address verification options available.

DEPT .OF CSE Page 117


SE LAB
A.Y:2023-24

DEFINITIONS, ACRONYMSANDTHEABBREVIATIONS
• Authorization service - The issuer of the card creates a revolving account
and grants a line of credit to the consumer (or the user) from
whichtheusercanborrowmoneyforpaymenttoamerchantorasacashadvanceto 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.

TECHNOLOGIESTO BE USED
• HTML
• JSP
• Java script
• Java
TOOLSTOBEUSED
• 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.

DEPT.OF CSE Page 118


SE LAB
A.Y:2023-24

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, Master Card, Amex, and Discover cards payments.

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

HARDWAREINTERFACE
The server is directly connected to the client systems .The client systems have
access to the data base in the server.

SYSTEMFUNCTIONS
1. Accept credit card numbers on the web, store the mine data base, then process
them off-line
2. Credit card processing with CCP
3. Credit card processing with a third-party credit card processing company.

DEPT OF CSE Page 119


SE LAB
A.Y:2023-24

USER CHARACTERISTICS
1) User/Customer-They are the people who desire to purchase the goods using
credit card.
2) Authorization Service
 Validatethecreditcardpaymentstoensurethatthecardnumberisvalidand the card
has not expired
 Deposit processing to apply the deposit payment to the card
 PrepareCreditcardtransactionreportsthatshowauthorizationcodes,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

ASSUMPTIONSANDDEPENDENCIES
 The Applicants and Administrator must have basic knowledge of computers
and English Language.

 The applicants may be required to scan the documents and send.

DEPT.OF CSE Page 120


SE LAB
A.Y:2023-24

(III)USECASEDIAGRAM:
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.

ACTORSINVOLVED
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-CASENAME: PURCHASE PRODUCT
Customer purchases items from ecommerce site then proceeds to the site’s
secure checkout area.
.

USE-CASENAME: AUTHORIZATION REQUEST


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

USE-CASENAME: AUTHORIZATION RESPONSE


Billing information is verified and the transaction is completed by the credit
card issuer.

DEPT.OF CSE Page 121


SE LAB
A.Y:2023-24

USE-CASENAME: PAYMENT APPROVAL


The transaction details are recorded by the credit card processor
andresultsaresecurelyrelayedtothemerchant.Merchant’ssitereceivestransactionresultand
doesappropriate actions (e.g. saves the order & shows message).

DEPT.OF CSE Page 122


SE LAB
A.Y:2023-24

creatingaccount

creditcardrequest

bankenquiry

banker
issuingcard
customer

purchasetheitem

preparethebill

retailer

payingbill

Fig.57 USE CASE DIAGRAM FOR PASSPORT


AUTOMATION SYSTEM

DEPT.OF CSE Page 123


SE LAB
A.Y:2023-24

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

DEPT.OF CSE Page 124


SE LAB
A.Y:2023-24

INTERACTIONDIAGRAM:

 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.
 Mostobjecttoobjectinteractionsandoperationsareconsideredeventsandeventsinclu
designals,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 object sin
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.

DEPT.OF CSE Page 125


SE LAB
A.Y:2023-24

B:Banker C:Customer

B:Banker

1: Select Bank

2:CreatingAccount

3:RequestingCard

4: Enquiry

5:IssuindCard

R:Retailer

6:selectshop

7: PurchaseItem

8:producingitemforbilling

9:preparingbills

10:Swipethecard

11:validatecard

12:Payingthebills

13:returningamount

14:checkingaccountdetails

Fig.58.SEQUENCE DIAGRAM

DEPT.OF CSE Page 126


SE LAB
A.Y:2023-24

6:select shop
7:PurchaseItem 9:preparingbills
8: producing item for
billing10:Swipethecard
C:Custo R:Retail
mer er

12:Payingthebills
5:IssuindCard

1:Select Bank
2:CreatingAccount
3:RequestingCard
13:returningamount
14:checkingaccountdetails

4:Enquiry

11:validatecard

B:Banke
r

Fig.59. COLLABORATION 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.

DEPT.OF CSE Page 127


SE LAB
A.Y:2023-24

Start

[new
creating
custome
account

Exiting
RequestTo

[CustomerEnquiry

requestingforcredit Bank enquiryfrom

do/requestingcreditcard do/bank

[SatisfiedCustomer

issuing
abor
card

End

Fig.60. STATE CHARTDIAGRAM

DDEPT.OF CSE Page 128


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAMAND COMPONENTDIAGRAM

Deployment diagrams are used to visualize the topology of the physical


components of a system where the software components are deployed.

Fig.6.1.DEPLOYMENTDAIGRAM

DEPT.OF CSE Page 129


SE LAB
A.Y:2023-24

Component diagrams are used to visualize the organization and


relationships among components in a system.

Fig.62.COMPONENT DIAGRAM

DEPT .OF CSE Page 130


SE LAB
A.Y:2023-24

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

DEPT.OF CSE Page 131


SE LAB
A.Y:2023-24
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. 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 books can use this system to reduce his
workload.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

 E-bookmanager

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.

DEPT.OF CSE Page 132


SE LAB
A.Y:2023-24

 Administrator
One who manages and maintain Books or Magazines.

IEEE Software Requirement Specification format

TECHNOLOGIESTO BEUSED

HTML-Markup Language used for creating web pages.

J2EE-Java2Enterprise 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)

DEPT.OF CSE Page 133


SE LAB
A.Y:2023-24

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 &function soft he actors.

OVERALLDESCRIPTION

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

PRODUCTPERSPECTIVE

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.

SOFTWAREINTERFACE
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).

DEPT.OF CSE Page 134


SE LAB
A.Y:2023-24

Back End

Oracle11gdatabase

HARDWAREINTERFACE

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

DEPT.OF CSE Page 135


SE LAB
A.Y:2023-24

intrusion in the web world which requires constant monitoring.

The user has to be careful while submitting the information. Much


carries required.

ASSUMPTIONSANDDEPENDENCIES

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-CASEDIAGRAM:

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

DEPT.OF CSE Page 136


SE LAB
A.Y:2023-24

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

->Student id

->Name

->Address

->Phoneno

2. Update:

The record would be selected using the studentid. The updates can be made on full
items only.
->name

->address

->phoneno

3. Add to book item:

Each book should have following attribute

->callno

->title

->ISBN

->Authorname

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.

DEPT.OF CSE Page 137


SE LAB
A.Y:2023-24

5. Checkout 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.

DEPT.OF CSE Page 138


SE LAB
A.Y:2023-24

Register

Visitor

Login

Administrator

SearchBook

Download

RegisterUser
Payment

Publisher

Update

Fig.63.USE-CASE DIAGRAM

DEPT.OF CSE Page 139


SE LAB
A.Y:2023-24

ACTIVITYDIAGRAM:
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 of book is paid online.

Welcome

Search Online

Fig.64. ACTIVITY DIAGRAM

DEPT.OF CSE Page 140


SE LAB
A.Y:2023-24

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:

1 .Login
2. Registered User
3. Administrator
4. Book
5. Visitor
6. Download
7. 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 operation s 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().

DEPT.OF CSE Page 141


SE LAB
A.Y:2023-24

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.

DEPT.OF CSE Page 142


SE LAB
A.Y:2023-24

Fig.65. CLASS DIAGRAM

DEPT.OF CSE Page 143


SE LAB
A.Y:2023-24

INTERACTION DIAGRAM:

 A sequence diagram represents the sequence and interactions of a given


USECASE or scenario. Sequence diagram scan capture most of the
information about the system. Most object to object interactions and
operations are considered events and events
includesignals,inputs,decisions,interrupts,transitionsandactionstoorfromusers
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.

DEPT.OF CSE Page 144


SE LAB
A.Y:2023-24

Fig.66. SEQUENCE DIAGRAM FOR REGISTERED


USER

DEPT.OF CSE Page 145


SE LAB
A.Y:2023-24

Book
:Visitor

seekfor register

Registeredisgranted

Searchbook

Checkavailablityof book

DisplayBook

Fig.67.SEQUENCEDIAGRAMFORVISITOR

1:seeklogin
registeruser UI

2:loginagreed

6:requestdownloadbook
8:paymenttransactionsubmitted

7:displaypayment
3: searchbook
5:
9:downloading

4:checkavailabillityofbook
Download

Book

Fig.68.COLLABORATIONDIAGRAMFORREGISTEREDUSER

DEPT.OF CSE Page 146


SE LAB
A.Y:2023-24

4:checkavailabilityofbook

1:seekforregist
er3:
searchbook
visitor Book

2:registeredisgrante
d5:displaybook

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 valid at e password check the condition based on condition book issue and
return is done. Pay the online and renewed finally logout from the system.

STATECHARTDIAGRAM:
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

DEPT.OF CSE Page 147


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAMANDCOMPONENTDIAGRAM
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.

Fig.71DEPLOYMENTDIAGRAM

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

DEPT.OF CSE Page 148


SE LAB
A.Y:2023-24

TASK10: RECRUITMENT SYSTEM

AIM: To create an automated system to perform the Recruitment


System Process.

(I) PROCEDURE: PROBLEM STATEMENT:


The recruitment system allows the job seeker overview the job opportunity
through Advertisement and helps to apply for the job. The organization short lists 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)SOFTWAREREQUIREMENTSPECIFICATION:

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 become
essential to meet the demand. So this system use several

DEPT.OF CSE Page 149


SE LAB
A.Y:2023-24
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 their recruitment process


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

 ProvideacommunicationplatformbetweentheApplicantandtheOrganization.

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
Java2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.

DEPT.OF CSE Page 150


SE LAB
A.Y:2023-24

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

TECHNOLOGIESTO BEUSED
• HTML
• JSP
• JavaScript
• Java
TOOLSTOBEUSED
• 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 SRS 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.

DEPT.OF CSE Page 151


SE LAB
A.Y:2023-24

This minimizes the time duration for recruitment process.

SOFTWAREINTERFACE
• 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- Glass fish application server (SQL Corporation).
• Back End –SQL database.
HARDWARE INTERFACE
These are 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.

USERCHARACTERISTICS
 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

DEPT.OF CSE Page 152


SE LAB
A.Y:2023-24

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.

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

(III)USECASEDIAGRAM:
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

DEPT.OF CSE Page 153


SE LAB
A.Y:2023-24

ACTORSDOCUMENTATION:
 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 short list
them. HR is also responsible for Interview Scheduling.
 Organization
Organization is an actor who announces the Advertisement for vacancy.

USE-CASENAME: 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.

USECASE: APPLY FORJOB

Description: This Use Case is initiated by Applicants. Online forms are filled by the
Applicants and submitted to the organization.
FlowofEvents: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.

DEPT.OF CSE Page 154


SE LAB
A.Y:2023-24

USECASE: 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.
FlowofEvents: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.

USECASE: 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.

USECASE: 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.

DEPT.OF CSE Page 155


SE LAB
A.Y:2023-24
Pre-Condition: Applicant is selected for the Interview.

Post-Condition: Applicant clear or not clear the Interview.


USE CASE:
RECRUITEDAPPLICANTS

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.

Fig73. USECASE DIAGRAM FOR RECRUITMENT


SYSTEM

DEPT.OF CSE Page 156


SE LAB
A.Y:2023-24
ACTIVITYDIAGRAM :
The activity diagram represents the series of activities that are occurring between the
objects. Following is activity diagram which represents there recruitment process .

ApplicantKnowstheor
ganisationjobs

Advertisement OtherSources

Applicantapplyforor
ganisationJobs

SelectedApplicantc
alled forInterview

Test Interview

FixSalary

Recruited&NotRecruitedAp
plicantsInformed

Fig.74 ACTIVITY DIAGRAM FOR RECRUITMENT


SYSTEM

DEPT.OF CSE Page 157


SE LAB
A.Y:2023-24
CLASSDIAGRAM:

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
APPLICANTCLASS:
It consists of eight attributes and two operations. The attributes areAppl-
id,Appl-name,Appl-DOB,Appl-Gender,Appl-Qualification,Appl-phone, Appl-email id,
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-email id, Emp-addr. The operation are Planning( ), Policies (
),Strategies()

DEPT.OF CSE Page 158


SE LAB
A.Y:2023-24

The attributes of this class are Adv-No, Adv-Name and Adv-description. The operation
is display ( ).

RECRUITMENTCLASS
The attributes are Rec-Designation and Rec-Total candiate.The operation is recruit( ).

Fig.75.CLASS DIAGRAM FOR RECRUITMENT SYSTEM

DEPT.OF CSE Page 159


SE LAB
A.Y:2023-24

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


via message. It is generalize between two or more specialized diagram.

DEPT.OF CSE Page 160


SE LAB
A.Y:2023-24

Advertisement
Advertisement Organisation
:Applicant RecruitmentCo
mmittee:HR
ViewJobs

ApplyforJobs

ForwardApplicants
Resumee

AnalyseApplicantsResum

SendIntervi ewcallLetter/E-mail

AttendTest

EvaluateTest

Selected/NotSelectedInformed

AttendInterview

ApplicantpassedTestand InterviewInformed

Salary Fixed/Recruited

Fig76 SEQUENCE DIAGRAM FOR RECRUITMENT


SYSTEM

DEPT.OF CSE Page 161


SE LAB
A.Y:2023-24
 Communication diagram illustrate that object interact on a graph or network
format. In collaboration diagram the object can be placed in any where on the
diagram. The collaboration comes from sequence diagram.

 1:viewjobs

appilicant advertisement

6:attendinterview
2:applyforjobs
5:sendinterviewcallletter/emil
7:applicantpassedtest& interviewinformed
8:salaryfixed/received
4:analyseapplicantresume

3:forwardapplicants
organisation recuitmentcommit
ed=HR

Fig77 COLLOBORATION DIAGRAM FOR RECRUITMENT


SYSTEM

DEPT.OF CSE Page 162


SE LAB
A.Y:2023-24

STATECHARTDIAGRAM:

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

ViewJobs ApplyJob Select Test


forIntervi
ew

Interview

Salary

Recruit

Fig.78.STATE CHART DIAGRAM FOR RECRUITMENT


SYSTEM

DEPT.OF CSE Page 163


SE LAB
A.Y:2023-24

DEPLOYMENTDIAGRAM

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

DEPT.OF CSE Page 164


SE LAB A.Y :2023-24

COMPONENTDIAGRAM

Component diagrams are used to visualize the organization


and relationships among components in a system.

Fig.80..COMPONENT DIAGRAM

DEPT.OF CSE Page 165


SE LAB A.Y :2023-24

DEPT.OF CSE Page 166


SE LAB A.Y :2023-24

DEPT.OF CSE Page 167


SE LAB A.Y :2023-24

DEPT.OF CSE Page 168


SE LAB A.Y :2023-24

SIGNATURE OF FACULTY

DEPT.OF CSE Page 169

You might also like