DEPARTMENT OF CSE

Tholurpatti (Po), Thottiam (Tk), Trichy (Dt) – 621 215

Accredited by NAAC with B++ Grade, Approved by AICTE, New Delhi & Affiliated to Anna
University, Chennai

FACULTY LAB MANUAL

(CS8582 - OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY)

Academic Year: 2021 – 2022 Year / Semester: III / V

 TABLE OF CONTENTS
S.No. Particulars Page No.
1. Institute V/M 1
2. Department V/M/PEO;PO/PSO Statements 2
3. Lab Course Syllabus 4
4. University Prescribed Lab Experiments
I Identify a software system that needs to be developed.
Document the Software Requirements Specification (SRS) for the
II
identified system.
III Identify use cases and develop the Use Case model.
Identify the conceptual classes and develop a Domain Model and also
IV
derive a Class Diagram from that.
Using the identified scenarios, find the interaction between objects
V and represent them using UML Sequence Diagrams and Collaboration
5.
Diagrams
VI Draw relevant State Chart and Activity Diagrams for the same system.
VII Implement the system as per the detailed design
Test the software system for all the scenarios identified as per the use
VIII
case diagram
Improve the reusability and maintainability of the software system by
IX
applying appropriate design patterns.
X Implement the modified system and test it for various scenarios
SUGGESTED DOMAINS FOR MINI-PROJECT:
• Passport automation system.
• Book bank
• Exam registration
• Stock maintenance system.
• Online course reservation system
• Airline/Railway reservation system
• Software personnel management system
• Credit card processing
• e-book management system
• Recruitment system
• BPO management system
• Library management system
• Student information system
Advanced Experiments
6. I Online hotel reservation systems
II Real estate management systems
 Tholurpatti (Po), Thottiam
(Tk), Trichy (Dt) - 621 215

COLLEGE VISION & MISSION STATEMENT

VISION

"To become an Internationally renowned Institution in technical education, research and

development, by transforming the students into competent professionals with leadership skills and
ethical values."

MISSION

❖ Providing Best Resources and Infrastructure.

❖ Creating Learner centric Environment and continuous -Learning.
❖ Promoting Effective Links with Intellectuals and Industries.
❖ Enriching Employability and Entrepreneurial Skills.
❖ Adapting to Changes for Sustainable Development.
 COMPUTER SCIENCE AND ENGINEERING

VISION
To produce competent software professionals, academicians, researchers and entrepreneurs
with moral values through quality education in the field of Computer Science and Engineering.

MISSION
• Enrich the students' knowledge and computing skills through innovative teaching-learning
process with state- of- art- infrastructure facilities.
• Endeavour the students to become an entrepreneur and employable through adequate industry
institute interaction.
• Inculcating leadership skills, professional communication skills with moral and ethical values
to serve the society and focus on students' overall development.

PROGRAM EDUCATIONAL OBJECTIVES

• PEO I: Graduates shall be professionals with expertise in the fields of Software
Engineering, Networking, Data Mining and Cloud computing and shall undertake
Software Development, Teaching and Research.
• PEO II: Graduates will analyze problems, design solutions and develop programs with
sound Domain Knowledge.
• PEO III: Graduates shall have professional ethics, team spirit, life-long learning, good
oral and written communication skills and adopt corporate culture, core values and
leadership skills.

PROGRAM OUTCOMES:

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

B. E (CSE) - PROGRAM SPECIFIC OUTCOMES (PSO's)

➢ PSO1: Professional skills: Students shall understand, analyze and develop computer
applications in the field of Data Mining/Analytics, Cloud Computing, Networking etc., to
meet the requirements of industry and society.
➢ PSO2: Competency: Students shall qualify at the State, National and International level
competitive examination for employment, higher studies and research.
CS8582 OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY LT PC
0042
OBJECTIVES

• To capture the requirements specification for an intended software system

• To draw the UML diagrams for the given specification
• To map the design properly to code
• To test the software system thoroughly for all scenarios
• To improve the design by applying appropriate design patterns.

Draw standard UML diagrams using an UML modeling tool for a given case study and map design
to code and implement a 3 layered architecture. Test the developed code and validate whether the
SRS is satisfied.
1. Identify a software system that needs to be developed.
2. Document the Software Requirements Specification (SRS) for the identified system.
3. Identify use cases and develop the Use Case model.
4. Identify the conceptual classes and develop a Domain Model and also de rive a Class Diagram from
that.
5. Using the identified scenarios, find the interaction between objects and represent them using
UML Sequence and Collaboration Diagrams
6. Draw relevant State Chart and Activity Diagrams for the same system.
7. Implement the system as per the detailed design
8. Test the software system for all the scenarios identified as per the use case diagram
9. Improve the reusability and maintainability of the software system by applying appropriate design
patterns.
10. Implement the modified system and test it for various scenarios

SUGGESTED DOMAINS FOR MINI-PROJECT:

1. Passport automation system.
2. Book bank
3. Exam registration
4. Stock maintenance system.
5. Online course reservation system
6. Airline/Railway reservation system
7. Software personnel management system
8. Credit card processing
9. e-book management system
10. Recruitment system
11. BPO management system
12. Library management system
13. Student information system
TOTAL: 60 PERIODS
OUTCOMES:

Upon completion of the course, the students will be able to

• Perform OO analysis and design for a given problem specification.

• Identify and map basic software requirements in UML mapping.
• Improve the software quality using design patterns and to explain the rationale behind
• applying specific design patterns
• Test the compliance of the software with the SRS.

HARDWARE REQUIREMENTS

Standard PC

SOFTWARE REQUIREMENTS

1. Windows 7 or higher

2. ArgoUML that supports UML 1.4 and higher

3. Selenium, JUnit or Apache JMeter
Ex. No: 1 STUDENT INFORMATION SYSTEM
Date:

AIM :
To develop a project Student Information System using Arogo Uml and to implement
the software in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING :

A Student information system (SIS) is a software application for educational
establishments to manage student data. Student information systems provide capabilities f or
entering student test and other assessment scores, building student schedules, tracking student
attendance, and managing many other student-related data needs in a school, college or
university.

PROBLEM STATEMENT :
a. Effective for Administration Purpose
b. Cheap
c. Better Service

UML DIAGRAMS:
The following UML diagrams describe the process involved in the online recruitment
system
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. Activity diagram
f. Component diagram

USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, andorganize

system requirements. The use case is made up of a set of possiblesequences of interactions
between systems and users in a particular environmentand related to a particular goal. It is
represented using ellipse.Actor is any external entity that makes use of the system being
modelled. Its represented using stick figure.
For Administrator:

Admin Login

Add Student

Admin
Database
Delete Student

Update Student Records

For Student:

Student Login

Message

Attendance

Student
Databases
Profile

Result

Time Table

Fee

Library

Log Out
CLASS DIAGRAM:

A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. Its represented using a rectangle with
three compartments. Top compartment have the class name ,middle compartment the
attributes and the bottom compartment with operation.

Login Student details

+username +Name
+password +Address
+Login() +Age
+validation() +Course
+get_data() +Department
+display() +Phone no

+get_data()
+Display()

Update details
+Student details
+Result details

+Updae_info()
+get_detail()
+Display()

SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram

that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. There are two dimensions.
1. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects.
For Validity:

Admin/Student Validation Database

1 : Request for validity()

2 : Check for validity()

3 : Validate()

4 : Successful validate()

For Administrator:
Login ReqAdd Student ReqUpdate Student Database
Admin

1 : Enter Credentials for login()

2 : Check for validity()

3 : Valid user()

4 : Successful login()

5 : Enter details for adding a student()

6 : Add()

7 : Successful()

8 : Successfully added()

9 : Enter credentials for update student record()

10 : Update()

11 : Successful()

12 : Successfully Updated()
For Student:
Student Login ReqView Profile
ReqView Details Database

1 : Enter credentials for login()

2 : Check for Validity()

3 : Valid()

4 : Valid login()
5 : Request for view profile()

6 : Request()

7 : Set Details()

8 : Get the details()

9 : Request for view Details()

10 : Request()

11 : Set Details()

12 : Get the Details()

COLLABRATION DIAGRAM:

A collaboration diagram, also called a communication diagram or interaction diagram,. A

sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and the vice.

For Validity:

Database
3 : Validate()

2 : Check for validity()

Validation

1 : Request for validity()

4 : Successful validate()

Admin/Student
For Administrator:

Database

3 : Valid user()
6 : Add()
10 : Update()

7 : Successful() 2 : Check for validity()

11 : Successful()
Login

ReqAdd Student ReqUpdate Student

1 : Enter Credentials for login()

8 : Successfully added()
4 : Successful login()
12 : Successfully Updated()

9 : Enter credentials for update student record()

5 : Enter details for adding a student()

Admin
For Student:

Database

3 : Valid()
6 : Request() 2 : Check for Validity()

10 : Request()
7 : Set Details()

11 : Set Details() Login

ReqView Profile

8 : Get the details() ReqView Details

4 : Valid login()

1 : Enter credentials for login()

Object1
5 : Request for view profile()
9 : Request for view Details()

12 : Get the Details()

Student

ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the UnifiedModeling 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.
 Login

Student Registration

back to registration
If No
Yes

Select Course

Profile

Result

Fee

Library

Log Out
COMPONENT DIAGRAM:

The component diagram's main purpose is to show the structural relationships between
the components of a system. It is represented by boxed figure.Dependencies are represented
by communication association.

User

IUser

<<application>>
Management <<infrastructure>>
Persistence

Request

IRequest

DB

JDBC
DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model thephysical
deployment of artifacts on deployment targets. Deployment Diagrams show "the allocation
of artifacts to nodes according to the Deployments defined between them. It is represented by
3-dimentional box.Dependencies are represented by communication association.

Student Information System

Administrator Student Access Database

RESULT:

Thus the UML diagrams for Student Information System have been developed and
verified successfully.
Ex. No: 2 SOFTWARE REQUIREMENTS SPECIFICATION FOR
Date: STUDENT INFORMATION SYSTEM

AIM :
To develop a project Student Information System using Arogo Uml and to implement
the software in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING :

A Student information system (SIS) is a software application for educational
establishments to manage student data. Student information systems provide capabilities f or
entering student test and other assessment scores, building student schedules, tracking student
attendance, and managing many other student-related data needs in a school, college or
university.

PROBLEM STATEMENT :
a. Effective for Administration Purpose
b. Cheap
c. Better Service

UML DIAGRAMS:
The following UML diagrams describe the process involved in the online recruitment
system
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. Activity diagram
f. Component diagram
INTRODUCTION:
Student information system is developed for the exclusively for the purpose of
students and lectures. In this system students can view their results semester wise. The
purpose of this feedback questionnaire is to gather information on your learning experie nce,
as well as your response(s). When clicking the answer, you have to think of these questions as
your subjective perceptions on various aspects of the course and the teacher(s) involved in the
program. The opinion or information provided by the students is useful for the teacher(s) as
well as the University in the ongoing efforts and enhance the quality of education. The
opinion provided by the student will be kept confidential. The evolution will be calculated on
the basis of total scores from the responses from all students.
Student(s) has to mention only his register number, need not to mention his name.
Student(s) will give their opinion voice strength, teaching style, subject knowledge, and
behavior and timing sense. He has select one option from five options (excellent, very good,
good, satisfactory, not satisfactory) and also he has to mention faculty name, subject, branch,
and department. This information has to submit with the system. In admin module only
college has to register with the system. College has to add branches with the code number
and course name. College has to register faculty members with respected course and
Department and their total personal details. University or College has to add subject details in
particular branch with syllabus. Registered faculty members are appointed to the respective
branches. They have to add feedback questions to the system.
College has to register in a bulk, and then they have to segregate as groups and
allotted sections to them. Details of Promoted students to next semester will be kept on
system. They can view by student id, course name, branch name, section and year. Feedback
will be shown in charts and bars format. Then assessment details can be viewed branch,
section, course and year. It will give information about faculty members; they have to
improve their performance or vice versa will be notified.
Features:
It is useful to analyze the performance of the faculty members in engineering
college. Students can view their results, attendance by branch wise and id number. Students
will give their review about the faculty members in a questionnaire.
Lecturer appointed to the respective departments, with their experience and
qualification. Administrator will introduce the new colleges to the students and lecturers.
SYSTEM:
Designing and implementing the new links. Designing and implementing the
users.Arranging new links as subject wise. SYSTEM ANALYSIS: System analysis will be
performed to determine if it is feasible to design information based on policies and plans of
the organization and on user requirements and to eliminate the weaknesses o f the present
system. The new system should be cost effective. To expand management, improve
productivity and services. To enhance user / system interface. To improve information
quality and usability. To upgrade systems reliability, availability, flex ibility and growth
potential.
Objective of the System:
The main objective of the system is that to provide quality education with proper resources
to the students in a reasonable expenditure. Improve the quality of education and also
improve the lab facilities, teaching qualities, classroom facilities and other facilities f or the
students. Main aim is that make available results online for the students they can available for
the students.
Objectives:
1. The System is composed with convenient modules of setting and editing the
convenient modules for the students to give their opinions about the lecturers and
know about the college details.
2. Modules are designed user friendly they can reach anywhere directly without any
confusion.
3. This system is designed to save the time and reduce the paper work for taking
opinions and making assessments.
4. Administrator will introduce the new colleges to the students to increase the options
to the students while joining / selecting the colleges.
5. To improve the quality of education considering the opinions of students.
User Requirements:
➢ User has to register with the system for using all the facilities available in the
system
➢ Student User has to submit his opinion about his faculty by course, name, subject
and department / branch wise.
➢ Student can view his results semester wise, it will give the information he/she has
promoted/ demoted in the examinations.
➢ Student has to login with his id number, which is assigned by the system.
➢ College user has to provide details of total number of student, faculty members and
contact information.
➢ User can view the assessment details by way of charts and bar diagrams and
providing course name, branch name, year etc.

HARDWARE & SOFTWARE SPECIFICATIONS:

 HARDWARE REQUIREMENTS:
Processor : Intel P-IV system
Processor Speed : 250MHz to 833MHz
RAM : 512MB RAM
Hard Disk : 40GB
SOFTWARE REQUIREMENTS:
Operating System : Windows XP
Database : Sql Server
Server side technology : ASP.Net
Server side scripting : ASP
Client side scripting : HTML
Web-Server : IIS

About Student Information Systems (SIS):

Student Information System (SIS) is a web-based application software designed to

introduce a conducive and structured information exchange environment for integrating
students, parents, teachers and the administration of a school or college. Some of the other
software packages available for this purpose include Student Management System (SMS),
Student Information Management System (SIMS) and Student Records System (SRS). These
software systems enable educational institutions to supervise student-related activities such as
keeping records of tests or examinations conducted, attendance, appraisal on performance
including details of marks scored, particulars of everyday school attendance, and all other
institution-related activities; in short, they provide a complete student records system. They
are designed with diverse application potentials ranging from simple ma nagement of
students’ records at school to management of all student-related functions as well as
administrative functions of a university or a chain of educational establishments.

History:

Much of the software used in erstwhile student information system s and school
administration worked on an outdated code base and had a curious mix of presentation,
business sense, and data accessibility. It was impossible and often expensive to modify these
systems to cater to future demands.Some of the early initiative software programs such as
WebCT, SCT Campus Pipeline, Jetspeed, and Blackboard merely enabled interactions
between students and teachers for academic purposes and served only as a student
information system. The advantage of having a student management system was missing as it
was not possible to integrate any of the campus-based activities within these systems. Most
often, student data were kept strewn in multiple locations, making it difficult to construe and
project.
Educational institutions were looking for a web-based solution such as a student information
management system or an intelligent student information system with an inbuilt mechanism
to meet the requirements of student-related information management as well as to serve the
purpose of a school management system. Furthermore, they were looking forward to a
complete package on student information management system from a single vendor.

Objectives of Student Information Systems

Student information systems must meet the following objectives:

• Enable self-service for students to perform basic administrative functions and
tasks in a “one-stop” service and access environment.
• Integrate data sources and process them through a single function that supports
one-time entry of student data.
• Support the retention and recruitment of students and encourage a strong and
positive relationship with the university, alumni, donors, and other
constituencies.
• Integrate and support new learning and teaching opportunities and technologies
for students and faculty.
• Support open interfaces and integration with other campus applications and
database systems.
• Ensure data integrity, privacy, and security in an open-access environment.
• Support faculty and staff who perform both basic and complex functions through
simplified work processes and procedures.
• Enable ongoing, flexible reconfiguration of the application to extend its life cycle
and to meet the changing business processes of the university.
Features of Students Information Systems:
Admission of students to the institution :
Using an auto reply feature and a standard format, a student information system
replies all the admission-related queries of students who may want to apply. Similarly, during
the admission, the created database is used for sending admission letters or regret letters to
the prospective students. During the enrolment of students the system stores all the main
subject and optional subject details. This information is further used for automatic creation of
subject classes and assignments to teachers. The details of students who seek hostel facilities
are stored separately for allocating rooms and also providing boarding information to the
hostel wardens.

Capabilities of Student Information Systems:

The web-based student information systems have the following features:Offer an

easy-to-use interface for any normal user. Since all the applications are predefined, details
only need to be filled in the required fields of information; multiple screen inputs are avoided
for ease of working.
1) Designed to support large amounts of data and simultaneous access by a number of
users.
2) All the required details such as admission, course and syllabus, account or fee are
indexed and classified for easy access.
3) Easy-to-decipher reporting functions for individuals as well as departments, and
facilitate the generation of real-time reports and customised reports.
4) Flexible to operate in multiple ways with easy-to-change operating or processing
setups, in tune with current requirements.
5) Easy integration with the other modules that already exist; also offer ingenuity during
integration.
6) Capability to support all types of requests for approvals, and designed to generate
proper notifications for all sanctions; also support all forms of electronic signatures
for the validity of documents.
7) Easy uploading of information to the system, supporting even batch -type uploads
from various sections to keep the system up-to-date with current information; such
uploads can be made even by desktop users.
 8) User preferences allow users to permit printing of a document or to keep it in
electronic format; users also have the facility to update their system preferences,
while the system keeps a track of all such changes administered for the records.
9) The scaleable feature allows easy reconfiguring of the system permitting expansion in
data sourcing as well as introduction of more users.
10) Can store scanned images and digital photographs for use.
11) The dependable security system allows only designated users to access all the system
capabilities; it offers various levels of security to restrict access to undefined users,
and the received information from other sources is subjected to security scans.

Applications:
The availability of a computerized student information system offers a perceptivity
that provides for practical education involvement and new levels of attainment.

Conclusion:
It is always prudent to opt for a student information system that is designed using
modern system architecture to cope with changing requirements. This system should
encompass very solid information coding and distinctly outlined business applications,
separating the presentation of details and methods of support.

RESULT:
Thus the UML diagrams for Student Information System have been developed and
verified successfully.
EXPT NO: 3 EBOOK

DATE:

Problem Analysis:

The problem is to find out the book that we need with reference to the prescribed author .The books
will be categorized in to various sections . Some of the sections include Novels,Love and Romance etc.
Ebooks of various author can be found in ease.

SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION:

The statement of the system is to group the books in various categories according to user’s comfort.The
main objective is to provide all the versions of book.
PURPOSE:

The system is designed with end user requirements as main criteria. It includes front end tool to receive data
needed and to validate the entries. It has backend access to store validate data for future reference.To
analyze and design a EBOOK based on Object Oriented Analysis and Design concept.

1.2. SCOPE:

The system designed is capable of providing functional requirements based on book we chose and the
Author we wish. Non-functional requirements are clarity,text decoration ,simple language etc.

DOCUMENT CONVENTIONS:

Administrator - The person who has the full authority over the system. He can view all
registered users.
Job Seekers - the person who registers in the system in search of jobs.
Company - A company can register itself, select the required employees and provide
information about the result.

1.4. REFERENCES:
www.timesjob.com:

2 OVERALL DESCRIPTIONS:

2.1 PRODUCT PERSPECTIVE:

This project is a self-contained project for convenient recruitment process.

2.2 PRODUCT FUNCTIONS:

The front end of the project is where the visitors or job seeker’s do their

enrollment. The back end is managed by the administrator effectively

2.3 TOOLS TO BE USED

Rational Rose Enterprise Edition, AgroUML

3. SYSTEM FEATURES
3.1 APPLYING FOR JOB:

3.1.1 SYSTEM DESCRIPTION AND PRIORITY:

This feature allows the job seeker to apply for job.

3.1.2 STIMULUS AND RESPONSE SEQUENCE:

When the user types the book, a list of possible e-books has to be displayed along with other details

3.1.3 FUNCTIONAL REQUIREMENTS:

REQ1: Only registered users can search and download.

4 OTHER NON-FUNCTIONAL REQUIREMENTS:

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

4.2 SAFETY REQUIREMENTS:

The database must be maintained effective from hacking.

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

GANTT CHART:
UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:
ACTIVITY DIAGRAM:

SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:

STATE CHART DIAGRAM: (PAYMENT)

Package Diagram:

Component Diagram:
Deployment Diagram:

Result:

Thus the UML models for EBook Management System have been developed and verified
successfully.
EXPT NO: 4 ETICKETING

DATE:

PROBLEM STATEMENT:

Here the passenger who used to login, who used to view the train details and they can able to cancel the
tickets. The system administrator who used to manage the users and the security. The railway database
which is getting include by all the passenger details like view train details and cancel the ticket. In extra of
the railway database they can reserve the tickets which was enroll by the passenger.

SOFTWARE REQUIREMENT SPECIFICATION: 1.

INTRODUCTION:
This project which aims to reserve the ticket using the login form. The passenger can able to view the
train details and cancel the booked ticket if they don’t need.

1.1 PURPOSE:
The main purpose of E-Ticketing is that the travelling passenger need not go to the railway station and book
the ticket. The main advantage of the E-Ticketing is that the passenger can able to book the ticket by using
internet.

1.2. SCOPE:
The scope of the E-Ticketing is that the passengers time is saved and we can able to book the seat which
can be comfortable for us, and we can view the seats which are available when booking.

1.3. DOCUMENT CONVENTIONS:

Passenger- who can be able to login, view the train details, and cancel the tickets.
Railway database- the data which is reserved by the passenger can be included by the database. System
admin- the system admin which can manage the user and the security.

1.4. REFERENCES:
www.ticketbooking.com:

2 OVERALL DESCRIPTIONS:

2.1 PRODUCT PERSPECTIVE:

This project is a self-contained project for convenient E-TICKETING process.

2.2 PRODUCT FUNCTIONS:

The front end of the project is where the system admin or passenger do their enrollment. The back end
is managed by the railway database effectively.

2.3 TOOLS TO BE USED

Rational Rose

3. SYSTEM FEATURES

3.1 APPLYING FOR JOB:

3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature

allows the passenger to book the seats.

3.1.2 STIMULUS AND RESPONSE SEQUENCE:

When the passenger login, the seats which are available to book can be viewed to book.

4 OTHER NON-FUNCTIONAL REQUIREMENTS:

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

4.2 SAFETY REQUIREMENTS:

The database must be maintained effective from hacking.

4.3SECURITY REQUIREMENTS:
The passenger should enroll some personal details so that no cheating can be made in booking the seats.

GANTT CHART:
UML DAIGRAMS

USE CASE DIAGRAM:

Login

Train Details

Passenger
Administrator <<Uses>>

Update Report <<Extends>>

Cancellation

<<Extends>>
<<Uses>>

Seat Avail Reservation

CLASS DIAGRAM:

ACTIVITY DIAGRAM:
Train Details:

Update Report:
Seat Available:

Reservation:
Cancellation:

SEQUENCE DIAGRAM:
Sequence for Cancellation:

COLLABORATION DIAGRAM:

Login

Train Details
Update Report

Seat Available:

Reservation:

Cancellation:
STATE CHART DIAGRAM: (PAYMENT)

Package Diagram:
Component Diagram:

Deployment Diagram:

Result:

Thus the UML models for ETicketing have been developed and verified successfully.
EXPT NO: 5 BOOK BANK

DATE:

PROBLEM STATEMENT:

Book Bank is used to issue books to customers which they have to return after a
specific period of time. It is necessary that the customers register at the book bank by filling out an entry
form with proper details and submit it to the manager along with the mentioned fees. After the manager
verifies the details and deposit, he/she issues the id card and a book form.The registered customer then has
to fill out the form with the names of books and the authors and submit it back.The staff at the book bank
check the availability of the books and issue the available ones.

SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION:
This project is aimed at developing a book bank system by creating details about customers
and the available books.

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

1.2. SCOPE:
The Book Bank System is used to specify a certain procedure to the customers for quick and hassle free
registration and acquire the necessary books.

1.3. DOCUMENT CONVENTIONS:

Manager - The person who has the full authority over the system. He can view all registered
users.
Customer-The person who registers and obtains books from the Book bank.
Book Bank-The entire System comprising of the customers, manager, staff and other elements. 1.4.
REFERENCES:
www.rec.in

2 OVERALL DESCRIPTIONS:

2.1 PRODUCT PERSPECTIVE:

This project is a self-contained project for convenient book bank registration process.

2.2 PRODUCT FUNCTIONS:

The front end of the project is where the customers register and get books. The back end
is managed by the manager effectively.
2.3 TOOLS TO BE USED Rational Rose
3. SYSTEM FEATURES

3.1.1 SYSTEM DESCRIPTION AND PRIORITY:

This feature allows the customers to know the procedure to enrol l in a book bank.

3.1.2 STIMULUS AND RESPONSE SEQUENCE:

When the customer details are validated he is enquired of his book preferences and the books are issued.
3.1.3 FUNCTIONAL REQUIREMENTS:
REQ1: Only registered customers can apply for issue of books. REQ2: The
books need to be available in order to be issued.
4 OTHER NON-FUNCTIONAL REQUIREMENTS:

4.1 PERFORMANCE MANAGEMENT:

To increase the performance and free up database resources, the default features are written to cache
files on their initial load.

4.2 SAFETY REQUIREMENTS:

The database must be maintained effective from hacking.

4.3SECURITY REQUIREMENTS:
Seperate and unique ids must be provided for each and every user so that no user can access the resources
available to other users.

GANTT CHART:
UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:
ACTIVITY DIAGRAM:

SEQUENCE DIAGRAM:
Sequence for Book Return:

COLLABORATION DIAGRAM:

Borrow Book:
Return Book:

STATE CHART DIAGRAM:

Book Borrow:
Return Book:

Package Diagram:
Component Diagram:

Deployment Diagram:

Result:

Thus the UML models for Book Bank have been developed and verified successfully.
EXPT NO: 6 PASSPORT AUTOMATION SYSTEM

DATE:

Problem Statement

Passport Automation System is used in the effective dispatch of passport to all of the applicants. This system
adopts a comprehensive approach to minimize the manual work and schedule resources, time in a cogent
manner. The core of the system is to get the online registration form (with details such as name, address
etc.,) filled by the applicant whose testament is verified for its genuineness by the Passport Automation
System with respect to the already existing information in the database. This forms the first and foremost
step in the processing of passport application. After the first round of verification done by the system, the
information is in turn forwarded to the regional administrator's (Ministry of External Affairs) office. The
application is then processed manually based on the report given by the system, and any forfeiting identified
can make the applicant liable to penalty as per the law. The system also provides th e applicant the list of
available dates for appointment to 'document verification' in the administrator's office, from which they can
select one. The system forwards the necessary details to the police for its separate verification whose report
is then presented to the administrator. The administrator will be provided with an option to display the
current status of application to the applicant, which they can view in their online interface. After all the
necessary criteria has been met, the original information is added to the database and the passport is sent to
the applicant.
Software Resource Specification 1.0
Introduction
Passport Automation System is an interface between the Applicant and the Authority responsible for the
Issue of Passport. It aims at improving the efficiency in the Issue of Passport and reduce the complexities
involved in it to the maximum possible extent.
1.1 Purpose
If the entire process of 'Issue of Passport' is done in a manual manner then it would
take several months for the passport to reach the applicant. Considering the fact that the number of
applicants for passport is increasing every year, an Automated System becomes essential to meet the
demand. So this system uses several programming and database techniques to elucidate the work involved in
this process. As this is a matter of National Security, the system has been carefully verified and validated in
order to satisfy it.
1.2 Scope
• The System provides an online interface to the user where they can fill in their personal
details and submit the necessary documents (may be by scanning).
• The authority concerned with the issue of passport can use this system to reduce his
workload and process the application in a speedy manner.
• Provide a communication platform between the applicant and the administrator.
• Transfer of data between the Passport Issuing Authority and the Local Police for verification
of applicant's information.
• Users/Applicants will come to know their status of application and the date in which they
must subject themselves for manual document verification.
2.0 Overall Description
2.1 Product Perspective
The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not risking the security of
data stored in.This minimizes the time duration in which the user receives the passport.
2.4 System Functions
• Secure Registration of information by the Applicants.
• Schedule the applicants an appointment for manual verification of original documents.
• Panel for Passport Application Status Display by the Administrator.
• SMS and Mail updates to the applicants by the administrator.
• Administrator can generate reports from the information and is the only authorized personnel
to add the eligible application information to the database.

2.5 User Characteristics

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

• Police - He is the person who upon receiving intimation from the PAS, perform a personal verification of
the applicant and see if he has any criminal case against him before or at present. He has been vetoed with
the power to decline an application by suggesting it to the Administrator if he finds any discrepancy with
the applicant. He communicates via this PAS.

2.6 Constraints

• The applicants require a computer to submit their information.

• Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constant monitoring.

• The user has to be careful while submitting the inf ormation. Much care is required.

2.7 Use Case Model Description

2.8 Assumptions and Dependencies

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

GANTT CHART:
UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:
ACTIVITY DIAGRAM:

Admin:

Register:
Check Status:

SEQUENCE DIAGRAM:

Admin:

Check Status:
Register:

COLLABORATION DIAGRAM:

Admin:

Application:
Check Status:

STATE CHART DIAGRAM:

Admin:

Check Sum:
Register:

Package Diagram:
Component Diagram:

Deployment Diagram:

Result:

Thus the UML models for Passport automation system have been developed and verified
successfully.
EXPT NO: 07 Online Course Registration System

DATE:

Problem Statement
All the processes involved in the course registration system are computerized.It
must contain all the details about: Student, Course offerings, Registering a course, Availability
of courses, Eligibility for Admission. This registration system enables the admission of
candidates into the institution on the basis of their educational and social background.. The
candidate has to register their desired branch from the available courses. The registration must
include the following details:
Application No, Student information, Course selected, course Availability, Eligibility. If a student
wishes to change his/ her course, then the schedule is
updated. If course is available then the change of course is permitted and changed, else include it in
waiting list. To update a schedule, the student needs to be logged in. Then the student can select any
other course from the available list of courses.
And the schedule is submitted.
If a student wishes to cancel his/her course, the student’s current schedule is retrieved and
displayed first. Then the system prompts the user to confirm the deletion of schedule. If confirmed, the
student is removed from the course offerings.
SOFTWARE REQUIREMENT SPECIFICATION
1. INTRODUCTION:
This project is aimed at developing a Course Registration system by creating details about
customers and the available courses.
1.1 PURPOSE:
Manual maintenance of customer details is a tedious process considering the to the large number of
customers. Hence, this system is used for easy registration and maintenance of database.
1.2. SCOPE:
The Course Registration is used to specify a certain procedure to the customers for quick and hassle
free registration of courses.
1.3. DOCUMENT CONVENTIONS:
Manager - The person who has the full authority over the system. He can view all
registered users.
Customer-The person who registers and gets registered.

2 OVERALL DESCRIPTIONS:
2.1 PRODUCT PERSPECTIVE:
This project is a self-contained project for convenient online course registration process.
2.2 PRODUCT FUNCTIONS:
The front end of the project is where the customers register and online courses. The back end
is managed by the manager effectively.
2.3 TOOLS TO BE USED
Rational Rose

3. SYSTEM FEATURES
3.1.1 SYSTEM DESCRIPTION AND PRIORITY:
This feature allows the customers to know the procedure to find the courses. 3.1.2 STIMULUS
AND RESPONSE SEQUENCE:
When the customer details are validated he is enquired of his course preferences and the details about
the courses are issued.
3.1.3 FUNCTIONAL REQUIREMENTS:
REQ1: Only registered customers can apply for details of the courses. REQ2: The
courses need to be available in order to be issued.
4. OTHER NON-FUNCTIONAL REQUIREMENTS:
4.1 PERFORMANCE MANAGEMENT:
To increase the performance and free up database resources, the default features are written
to cache files on their initial load.
4.2 SAFETY REQUIREMENTS:
The database must be maintained effective from hacking.
4.3SECURITY REQUIREMENTS:
Seperate and unique ids must be provided for each and every user so that no user can access the resources
available to other users.
4.4 SYSTEM REQUIREMENTS Processor :
Pentium IV 1.7 RAM : 128 MB
Hard Disk : 40 GB
4.5 SOFTWARE REQUIREMENTS case tool :
rational rose

GANTT CHART:

UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

ACTIVITY DIAGRAM:

SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:

STATE CHART DIAGRAM:

Package Diagram:

Component Diagram:
Deployment Diagram:

Result:

Thus the UML models for online course registration system have been developed and verified
successfully.
EXPT NO: 08 Recruitment System
DATE:

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

3. SYSTEM FEATURES

3.1 APPLYING FOR JOB:

3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature

allows the job seeker to apply for job.

3.1.2 STIMULUS AND RESPONSE SEQUENCE:

When the job seeker uploads his resume, the list of jobs matching the resume will be posted.

3.1.3 FUNCTIONAL REQUIREMENTS:

REQ1: Only registered users can apply for the job.
REQ2: The Company has the right to recruit the candidates, not the system.
4 OTHER NON-FUNCTIONAL REQUIREMENTS:
4.1 PERFORMANCE MANAGEMENT:
To increase the performance and free up database resources, the default features are written to cache files on
their initial load.

4.2 SAFETY REQUIREMENTS:

The database must be maintained effective from hacking.

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

GANTT CHART:

UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

ACTIVITY DIAGRAM:

Register:
Check Status:

HR Entry:
SEQUENCE DIAGRAM:

Register:

Status:

Admin:
Collaboration Diagram:

Status:

Admin:
STATE CHART DIAGRAM:

Package Diagram:
Component Diagram:

Deployment Diagram:

Result:

Thus the UML models for Recruitment System have been developed and verified successfully.
EXPT NO: 09 SOFTWARE PERSONNEL MANAGEMENT SYSTEM

DATE:

Problem Statement
A SOFTWARE PERSONNEL MANAGEMENT SYSTEM refers to the systems and processes
at the intersection between human resource management(HRM) and information technology. It merges
HRM as a discipline and in particular its basic HR activities and processes with the information technology
field, whereas the programming of data processing systems evolved into standardized routines and packages
of enterprise resource planning(ERP) software. The linkage of its financial and human resource modules
through one database is the most important distinction to the individually and proprietary developed
predecessors, which makes this software application both rigid and flexible.
SOFTWARE REQUIREMENT SPECIFICATION
1. INTRODUCTION:
This project which aims to efficiently manage the personnel details of a software company which
includes payroll details and other important functions.
1.1 PURPOSE:
The HR function consists of tracking existing employee data which traditionally includes personal
histories, skills, capabilities, accomplishments and salary. Also, each employee can access his/her own
profile, that lets him view his salary, attendance and company related updates.
1.2. SCOPE:
The scope of the Software Personnel Management System is that it allows the HR to view the entire
employee Database conveniently and make updates. Similarly from an employee point of view, he/she can
be able to view company related information easily.
1.3. DOCUMENT CONVENTIONS:
Employees can view their personal details and other company information. They can send messages to
any other employee of the organization. The HR has more features. He can view entire employee
database, make payroll updates etc.
1.4. REFERENCES:www.infosys.com
2 OVERALL DESCRIPTIONS:
2.1 PRODUCT PERSPECTIVE:
This project is a self-contained project for convenient Software Personnel Management System.
2.2 PRODUCT FUNCTIONS:
The front end of the project is where the HR or employee can login. The back end is managed
by the organization database effectively.
2.3 TOOLS TO BE USED
Rational Rose Enterprise Edition, Argo UML
3. SYSTEM FEATURES
3.1 SYSTEM DESCRIPTION AND PRIORITY:
This feature allows the employee to view his profile.
3.2 STIMULUS AND RESPONSE SEQUENCE:
When the employee logs in, his or her personal details are displayed.
4 OTHER NON-FUNCTIONAL REQUIREMENTS:
4.1 PERFORMANCE MANAGEMENT:
To increase the performance and free up database resources, the default features are written
to cache files on their initial load.
4.2 SAFETY REQUIREMENTS:
The database must be maintained effective from hacking.
4.3SECURITY REQUIREMENTS:
The employee is given a user id and password to ensure safety of personal information.
GANTT CHART:

UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:
STATE CHART DIAGRAM:

Package Diagram:
Component Diagram:

Deployment Diagram:
RESULT:

Thus the UML diagrams for Software Personnel Management System was developed and verified.
EXPT NO: 10 STOCK MAINTENANCE SYSTEM

DATE:

Problem Statement
The Stock maintenance system which allows the administrator to display the product details, purchase
details, sales details, stock details, and the purchase the products. The customer which is used to purchase
the product. The supplier who use to supply the product. Once they enter the login details the verifier check
the details of availability and says whether the login is valid or not. Then enter the stock details, maintain
and store it.

SOFTWARE REQUIREMENT SPECIFICATION

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

GANTT CHART:

UML DAIGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
STATE CHART DIAGRAM:
Package Diagram:

Component Diagram:
Deployment Diagram:

Result:

Thus the UML models for Stock Maintenance System have been developed and verified
successfully.
EX.NO: 11 Online Hotel Reservation Systems

DATE:

Problem Statement
This Online Hotel Reservation System aims at providing the user to reserve accommodation at
hotels online. The system shall take the start and end dates from the user and check for
availability of rooms. It shall check for the number of guests and reserve the rooms for the user.
It can also modify the dates of reservation. This is a simple user interface which displays the
information about the hotel, its contact address and the amenities at the hotel. It also provides the
rates of rooms in that hotel. This tool shall enable the user to check for information regarding the
hotel and reserve rooms. It enables the user to make payments online.

INTRODUCTION:
The Reservation was not done online till now. The customers had to call up the hotel and make
bookings depending on the availability. The information was given individually to all the
customers who called for reservations. This was a difficult task.

Proposed Online Hotel Reservation System

This Online Hotel Reservation System will help the user to make reservation for hotels online.
The user can check the availability of the rooms. The tool provides an option to input start and
end dates of the booking. It also takes input such as the number of guests. Depending on the
availability of the rooms the user can book the room. The user also has an option to update the
reservation details. The user can view the room rates. He can check for different amenities
provided by the hotel. The user can also know more about the hotel and its address. Also, gallery
provides pictures of different type of accommodations. This would ease the customer to book
rooms. The tool has an option to make payments online. The Interface is simple which uses latest
web technologies. It’s well secure for payments
Online Hotel Reservation System Specifications

Modules

Hotel: This module shall have all the details regarding the hotel such as name, number of rooms,
type, address etc.

Booking: This module shall have all the details regarding the start and end dates of reservation
for different rooms.

Payment: This module holds the payment related information. It takes care of the payment for
reservation online. It verifies and validates the payments done online.
STATIC MODEL

Bill/Payment Scheduler Reservation

bills cancels

processes processes creates/modifies/deletes

Report

generates

HMS Employee HMS Room

completes processes updates
Interface

has processes
processes

Customer
Administration

Discount
ATTRIBUTES OF THE CLASSES ON THE STATIC MODEL

STATE CHARTS

STATE CHARTS

Scheduler Statechart

Retrieve Time

System Started

Time is 1:00 p.m.

Scheduler Running Billing Additional Day

Billing Complete
System Stopped

Time is 6:30 p.m.

Billing Complete
Reservations Canceled

Time is 6:00 p.m. Billing Guaranteed Reservations

Cancelling Non-guaranteed Reservations

STATE CHARTS

Bill/Payment
Statechart

Recieve & add

item

Open

Adjust Generate
Bill Bill

Generated

Record
Payment

Room state chart

Vacant

Rm No entered when customer

checks in

Five hrs. past check

in Rm. no.
entered
Customer check
out

Occupied Reserved
Room number entered when customer
check in
 CONSOLIDATED COLLABORATION DIAGRAM FOR RESERVATION & BOOKING SYSTEM
Get Pending CheckOut Data
: Hotel
: Report
Database
Pending CheckOutData returned
Get Discount

: Discount
Update / Retrieve Room Availability Info

Room Availability Info

: Room

Data returned
Av ailability
CheckRoomAv ailability (Ty pe, Dates) Update/Retriev e data
Apply Status
Discount
Set RoomAvailability

Update/Retriev e Customer Inf o Update Bill/Pay ment Data

Customer Inf o

Create/Update/Retriev e Customer Inf o Get Reserv ation Data

: Reservation : Customer
Reserv ation Data returned
Report GenerateReport Customer Inf o
Generated (PendingCheckOutRpt,
ReportParameters) Cancel Non-Guaranteed
reserv ation
Generate Bill : Scheduler Scheduler Ev ents
Charge Bill
Credit Bill
Reserv ation Inf o Bill No-Show
Bill Additional Day : <<External Timer>>
Bill Guaranteed Reserv ation Digital Clock
Create/Retriev e/Update Reserv ation, CheckIn, CheckOut (Trans Data)

<<user interface>> Make Pay ment, Credit Pay ment

: Bill/Payment
: HMSInterface
Pay ment made, Pay ment credited

Display Info
Display Inf o
CSR Input Get Room/FoodService Bill Data
Manager Input Room/FoodService Bill

<<subsystem>>
: Room/Food Services System
: Manager
: Customer
ServiceRep
 CONSOLIDATED COLLABORATION DIAGRAM FOR MANAGEMENT SERVICES SYSTEM

Get Report Data : Hotel

: Report
Database
Report Data
Update/Get Info on Room & Rate

: Room Info on Room & Rate

Employee Update/Get
Info Employee Info
Add/Modify/Delete Info on Room & Rate

Report
Generated GenerateReport (ReportType,
ReportParameters) : Administration

Add/Modify/Delete Employee Profile

Administer User Profile

Administer Info on Room & Rate

<<user interface>> : Employee

: HMSInterface

Manager Input Display Info

: Manager
 Concurrent Collaboration Diagram

<<system>>
:Hotel Management System

<<subsystem>> <<subsystem>>
:Reservation & :Room & Food
Booking Services
items added to cost

room & customer info

<<subsystem>> menu item, price

:Management
Services

reports of all subsystems' data

report pending checkout

bill data generated bill generated

HMS request
<<external output device>>
HMS data requested :Printer
<<user interface>>
:Hotel Management
System Interface
DESIGN OF RELATIONAL DESIGN DATABASE

Result:

Thus the UML models for online hotel reservation system have been developed and verified
successfully
EX.NO: 12 REAL ESTATE MANAGEMENT SYSTEMS

DATE:

Problem Statement

With the increase in the number of transactions at a branch, the total workload of the staff has
become so big that the company is employing more staff to handle the ever increasing amount of
paper work. There is also a legal requirement to produce detailed monthly, quarterly and annual
reports. Management also needs summarized statistical data in order to have access to all the data
pertinent to a decision. Inferential statistics always act as a tool to have a look at all the data of
an organization in a precise, summarized form.

Clearly, the manual system is inadequate for this type of work. The file system was originally
developed in response to the needs of the company for more efficient data access. However,
rather than establish a centralized store for a branch’s operational data, a decentralized approach
was taken, where each department stores and controls its own data.

Objectives

 Handle details for rent and sale of property from clients.

 Carry out data analysis and statistical inference.
 Allow different departments of a branch to access specific files through application
programs designed specially for them.
 Produce financial and customer reports with detailed statistical analysis
 Handle staff’s details and their different transactions with clients.
 Provide security to the company’s data at a given branch.

System Implementation

This involved the physical realization of the database and the application design. The
system was implemented with full consideration of the above noted design considerations. In
order to make the package easy to use, it was implemented using object oriented programming.
In order to facilitate easy navigation by the user through the different parts of the package, it is
menu driven, where by a user can jump to any part of the package without having to quit from
the current transaction

The new system was designed with a backup facility that requires every system user to
back up the database before exiting from the system. The system requires that a copy of the
database on the computer's disks which is made periodically and kept on magnetic table or other
removable medium.
UML Use case diagram

Class diagram
Class diagram
Activity diagram

Component diagram
State chart diagram

Result:

Thus the UML models for real estate management system have been developed and verified
successfully