Job Oppurtunities in Hotel Management.

The ManagersHotel managers are responsible for the efficient and profitable operation of their establishments. The General Manager controls the finances, establishment norms to be followed by the staff while providing their services to the guests, housekeeping, food quality, decor and interiors. Assistant Managers supervise the day-to-day operations of their departments. Large hotels have Resident Managers to resolve problems round the clock. The Department Managers work under the supervision and guidance of the top management.The Front Office The first people to welcome guests in a hotel are the personnel in the front office. The Front Office Manager supervises the work of the receptionists, information clerk, reservation clerk and other service personnel like bell captain, bell boy and doorman. The Bell Boy assists the guests with the baggage to check in to the room. The Bell Captain supervises the work of bell boys. The Information Clerk delivers the telephone messages to the guests through the Bell Captain.F&B (Food and Beverage)This department includes:
Culinary Unit
Steward Department
Food Service Department Restaurant and Food Service Managers are responsible for stocks of tableware, linens, paper, supplies furniture, and fixtures cleaning. They arrange for equipment maintenance and repairs. They also have to maintain records of hours and wages of employees, payrolls, and taxes, etc. Banquet Managers are in-charge of catering assignments.HousekeepingA hotel requires maintenance on a very large scale. Hotels have a house keeping department to look after cleanliness in rooms, lounges, lobby, restaurant, dining halls, parks etc. This department functions under the supervision of the Executive Housekeeper.Executive Housekeepers are responsible for ensuring that guest rooms, meeting and banquet rooms and public areas are clean, orderly and well maintained. They train, schedule and supervise the work of housekeepers, inspect rooms and order for the necessary supplies. Housekeeping is a round the clock job .This department works in shifts.Marketing DepartmentToday marketing of services is a major aspect of hotel management. Sales and marketing division works to identify the needs of prospective customers, develop stay packages to suit their needs and sell the services, which have been developed.

Hotel Management System methodology.

Methodology

The method being used in developing the system is the system Development Life Cycle (SDLC) The SDLC process includes project identification and selection, project initiation and planning, analysis, design, implementation and maintenance.

PROJECT IDENTIFICATION AND SELECTION

PROJECT INITIATION AND PLANNING

.

ANALYSIS

PHYSICAL DESIGN

MAINTENANCE

IMPLEMENTATION

LOGICAL DESIGN

Figure 2.4: Waterfall Model (SDLC)

System Development Life Cycle (SDLC)

The system Development Life Cycle(SDLC) is a traditional methodology used to develop, maintain and replace or enhance information system. The main reason SDLC model is chosen because in SDLC it is possible to complete some activities in one phase in parallel with some activities of another phase. The life cycle can also be interactive that is phase are repeated as required until an acceptable system is found.

1.4.1.1 Phase 1: Project identification and selection

In this phase the project information system needs are identified and analyzed such as identified the title of the project that is Web Based XpathAnalyzer, scope and objective of the Web Based XpathAnalyzer.

1.4.1.2 Phase 2: Project initiation and planning

During this phase the Gantt chart has been developed as a time line to determining the task involve in developing the Web Based XpathAnalyzer.

1.4.1.3 Phase 3: Analysis

In the phase, the exiting system is studies by collecting the information through the Internet and analyzed the information to get alternatives for the used of proposed system. Determine what the Web Based XpathAnalyzer should do.

1.4.1.4 Phase 4: Design

Logical design is the fourth phase in SDLC methodology. The functional features chosen for the proposed system in Analysis phase are described. Part of the logical design of the information system is to devise the user interface. The interface plays an important role to connect the user with the system and is thus extremely important.

Hotel Management System Testing.

Testing

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also.

Psychology of Testing

The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. Hence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesn’t work. Testing is the process of executing a program with the intent of finding errors.

Testing Objectives

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say,

Ø Testing is a process of executing a program with the intent of finding an error.

Ø A successful test is one that uncovers an as yet undiscovered error.

Ø A good test case is one that has a high probability of finding error, if it exists.

Ø The tests are inadequate to detect possibly present errors.

Ø The software more or less confirms to the quality and reliable standards.

Levels of Testing

In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are as shown below…

Acceptance Testing

System Testing

Integration Testing

Unit Testing

Client Needs

Requirements

Design

Code

System Testing

The philosophy behind testing is to find errors. Test cases are devised with this in mind. A strategy employed for system testing is code testing.

Code Testing:

This strategy examines the logic of the program. To follow this method we developed some test data that resulted in executing every instruction in the program and module i.e. every path is tested. Systems are not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed or that matter is performed or for that matter is performed on all systems.

Types Of Testing

Ø Unit Testing

Ø Link Testing

Unit Testing

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. All modules must be successful in the unit test before the start of the integration testing begins.

In this project each service can be thought of a module. There are so many modules like Login, HWAdmin, MasterAdmin, Normal User, and PManager. Giving different sets of inputs has tested each module. When developing the module as well as finishing the development so that each module works without any error. The inputs are validated when accepting from the user.

In this application developer tests the programs up as system. Software units in a system are the modules and routines that are assembled and integrated to form a specific function. Unit testing is first done on modules, independent of one another to locate errors. This enables to detect errors. Through this errors resulting from interaction between modules initially avoided.

Link Testing

Link testing does not test software but rather the integration of each module in system. The primary concern is the compatibility of each module. The Programmer tests where modules are designed with different parameters, length, type etc.

Integration Testing

After the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

In this project integrating all the modules forms the main system. When integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration.

System Testing

Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see if software meets its requirements.

Here entire ‘ATM’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.

Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on external behavior of the system; the internal logic of program is not emphasized.

In this project ‘Network Management Of Database System’ I have collected some data and tested whether project is working correctly or not.

Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. The testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.

White Box Testing

This is a unit testing method where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. I tested step wise every piece of code, taking care that every statement in the code is executed at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data, which is used to check all possible combinations of execution paths through the code at every module level.

Black Box Testing

This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules.

Criteria Satisfied by Test Cases

Test cases that reduced by a count that is greater than one, the number of additional test cases that much be designed to achieve reasonable testing.

Test cases that tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.

ABOUT HIBERNATE 3.0

ABOUT HIBERNATE 3.0

Hibernate 3.0, the latest Open Source persistence technology at the heart of J2EE EJB 3.0 is available for download from Hibernet.org.The Hibernate 3.0 core is 68,549 lines of Java code together with 27,948 lines of unit tests, all freely available under the LGPL, and has been in development for well over a year. Hibernate maps the Java classes to the database tables. It also provides the data query and retrieval facilities that significantly reduces the development time. Hibernate is not the best solutions for data centric applications that only uses the stored-procedures to implement the business logic in database. It is most useful with object-oriented domain modes and business logic in the Java-based middle-tier. Hibernate allows transparent persistence that enables the applications to switch any database. Hibernate can be used in Java Swing applications, Java Servlet-based applications, or J2EE applications using EJB session beans.

Features of Hibernate

· Hibernate 3.0 provides three full-featured query facilities: Hibernate Query Language, the newly enhanced Hibernate Criteria Query API, and enhanced support for queries expressed in the native SQL dialect of the database.

· Filters for working with temporal (historical), regional or permissioned data.

· Enhanced Criteria query API: with full support for projection/aggregation and subselects.

· Runtime performance monitoring: via JMX or local Java API, including a second-level cache browser.

· Eclipse support, including a suite of Eclipse plug-ins for working with Hibernate 3.0, including mapping editor, interactive query prototyping, schema reverse engineering tool.

· Hibernate is Free under LGPL: Hibernate can be used to develop/package and distribute the applications for free.

· Hibernate is Scalable: Hibernate is very performant and due to its dual-layer architecture can be used in the clustered environments.

· Less Development Time: Hibernate reduces the development timings as it supports inheritance, polymorphism, composition and the Java Collection framework.

· Automatic Key Generation: Hibernate supports the automatic generation of primary key for your.

· JDK 1.5 Enhancements: The new JDK has been released as a preview earlier this year and we expect a slow migration to the new 1.5 platform throughout 2004. While Hibernate3 still runs perfectly with JDK 1.2, Hibernate3 will make use of some new JDK features. JSR 175 annotations, for example, are a perfect fit for Hibernate metadata and we will embrace them aggressively. We will also support Java generics, which basically boils down to allowing type safe collections.

· EJB3-style persistence operations: EJB3 defines the create() and merge() operations, which are slightly different to Hibernate's saveOrUpdate() and saveOrUpdateCopy() operations. Hibernate3 will support all four operations as methods of the Session interface.

· Hibernate XML binding enables data to be represented as XML and POJOs interchangeably.

· The EJB3 draft specification support for POJO persistence and annotations.