Software-Integration, Schemes and Mind Maps of Hospitality and Tourism

The importance of software applications in successful enterprises and the need for software integration to meet diverse business requirements. It explains the process of software integration and the different integration styles that can be used. The document also provides a simplified explanation of how RPC communication works. It concludes by discussing the evolution of enterprise integration technologies over several decades.

Typology: Schemes and Mind Maps

2022/2023

Available from 03/16/2023

andrei-gargantiel
andrei-gargantiel 🇵🇭

1 document

1 / 5

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
INTEGRETION SOFTWARE
INTRODUCTION
Today, successful enterprises rely heavily
on underlying software applications.
To meet prevalent diverse business
requirements, enterprises must pick and
choose different software applications that
have been created with disparate
technologies and built by different vendors.
In the Beginning, There Was Nothing
Standards and protocols start popping up
after the task theyre meant to simplify has
been around for a while and no two groups
are doing it the same way. This holds true
for software, a recent example being how
mobile development became standardized,
and you can now even create a single
application that will work on all major OS's
(it wasnt too long ago when you had to use
different technologies for different models
of devices from the same company).
What is Software
The combining of subroutines, modules
or full sofprograms tware with other
software components in order to
develop an application or enhance the
functionality of an existing one.
Often requiring a lot of source code
modification, developers, as well as IT
staff, may spend a large amount of
their time performing software
integration.
Software integration provides required
steps to be conducted for integration and
checkout of informal software engineering
builds.
The software design and development
team and test engineers need to develop a
strategy for:
1. Planning
2. Design
3. Execution
4. Data collection
5. Test evaluation.
The software integration activities are
informal and flexible for software checkout
to prepare for the software and systems
integration phase of the work product.
The strategy for software integration
provides a road map that describes the
steps to be conducted as part of the
implementation of software to start
integration activities.
Sometimes senior program and project
managers need to track program and
project progress and require the following
characteristics:
Conduct effective technical reviews
Show different integration techniques
and software approaches
Software designers are required to be
involved from the start to the finish
Architectural Styles for Integration
There are several integration styles that
can be used to integrate two or more
software applications.
In the publication "Enterprise Integration
Patterns" by Gregor Hohpe, these
integration styles have been illustrated
pf3
pf4
pf5

Partial preview of the text

Download Software-Integration and more Schemes and Mind Maps Hospitality and Tourism in PDF only on Docsity!

INTEGRETION SOFTWARE

INTRODUCTION

  • Today, successful enterprises rely heavily on underlying software applications.
  • To meet prevalent diverse business requirements, enterprises must pick and choose different software applications that have been created with disparate technologies and built by different vendors.

In the Beginning, There Was Nothing

  • Standards and protocols start popping up after the task they’re meant to simplify has been around for a while and no two groups are doing it the same way. This holds true for software, a recent example being how mobile development became standardized, and you can now even create a single application that will work on all major OS's (it wasn’t too long ago when you had to use different technologies for different models of devices from the same company).

What is Software

 The combining of subroutines, modules or full sofprograms tware with other software components in order to develop an application or enhance the functionality of an existing one.

 Often requiring a lot of source code modification, developers, as well as IT staff, may spend a large amount of their time performing software integration.

  • Software integration provides required steps to be conducted for integration and checkout of informal software engineering builds.
    • The software design and development team and test engineers need to develop a strategy for:
    1. Planning
    2. Design
    3. Execution
    4. Data collection
    5. Test evaluation.
    • The software integration activities are informal and flexible for software checkout to prepare for the software and systems integration phase of the work product.
    • The strategy for software integration provides a road map that describes the steps to be conducted as part of the implementation of software to start integration activities.

Sometimes senior program and project managers need to track program and project progress and require the following characteristics:

 Conduct effective technical reviews

 Show different integration techniques and software approaches

 Software designers are required to be involved from the start to the finish

Architectural Styles for Integration

  • There are several integration styles that can be used to integrate two or more software applications.
  • In the publication "Enterprise Integration Patterns" by Gregor Hohpe, these integration styles have been illustrated

under four main categories: File Transfer, Shared Databases, Remote Procedure Invocations, and Messaging

Figure 1: Integration Styles


Integrating Systems by Remote Procedure Cals

  • RPC was developed during the 80’s and instead of integrating systems by allowing them to exchange digital documents, it allows distributed systems to integrate with each other by remotely executing procedures (or subroutines) as if it was all a single system.
  • Tracing the origin of this technology is a bit tricky, since some would say that there are theoretical implementation proposals that date back to the 70’s, but the first few practical implementations started appearing in the early 80’s.

How Does It Work?

  • You can distill RPC all the way down to a simple client server communication protocol, in which the calling code acts as the client, and the executing subroutine acts as the server.
  • An Interface Definition Language (or IDL for short) is used to define the interface, and with generators, you can grab these IDL files and generate your own client and server stubs in the language of your choice.

Simplified explanation of interaction between client and server during an PRC communication


The previous diagram provides more details on the different components involved in RPC communication. Although the details might vary from implementation to implementation, the basics of it are:

  1. The client application binds with the client stub, which is basically a “fake” instance of the remote procedure trying to be executed (same interface, but not the actual procedure).
  2. The client code executes the stub, sending it the required parameters.
  3. The client stub will marshal the parameters (which is fancy talk for “serialization”) and transmits them to the server stub.
  4. The server stub will, in turn, unmarshall the package (which again, is code for recreating the parameters from the received serialized package).
  5. The server stub will execute the server code, passing the received (and now unmarshaled) parameters.

The response from the procedure call will go through the same inverse process (marshalling, transmission over the network, unmarshalling and final reception by the client code) and land on the client.

Evolution of Technologies for Enterprise Integration

  • Over several decades, enterprise integration technologies have leveraged one or more of the integration styles that were discussed earlier.

Varieties of electronic systems are available at the disposal of the Hotel Management which may include the following

  • electronic card reader
  • computer terminal connect key system

TYPES OF KEYS FOR EFFECTIVE KEY CONTROL

  • Guest Room Keys – The hotel guest room key is normally issued to open only one room for which it was intended
  • Master Key –

 A master key is designed to open a set of several locks

 (^) These locks also have keys which are specific to each one and cannot open any of the others in the set

 Locks which have master keys have a second set of the mechanism use to open them which is identical to all of the others in the set of locks

  • Grand Master Keys – This key operates all locks in the hotel, including laundry and linen rooms
  • Emergency Key

 The emergency key opens all guestroom donors, even when they are double locked

 One procedure for emergency keys is to have them locked in a safe or safe deposit box and signed out by the individual needing one

  • Floor Supervisors Master Key – Key operates all sections on the floor / floors supervised by the particular supervisor
  • Housekeeping Staff Master Keys - Key operates all rooms serviced by particular room maid or housekeeping staff

IMPORTANT KEY CONTROL PROCEDURES

  • Security of key in transit
  • Restricted access to unauthorized people
  • Maintenance of log book
  • Established protocol for distribution of keys
  • Keys without indication of property details
  • Key audits
  • Lock rotation
  • Collecting keys from the guest
  • Dealing with suspected compromises
  • Well secured key storages

YIELD MANAGEMENT SYSTEMS

  • Yield management is a process of planning to achieve maximum room rates and most profitable guests for the hotel. Yield management system and process has some of the following important components:
  • The definition of the yield – Revenue realized as a percentage of the revenue potential is generally adopted as a measure of yield
  • Strategies adopted for healthy yield – optimal yield can be achieved through optimizing booking and rates management
  • Forecasting

 forecasting of the room sales is an important aspect of the yield management

 Accurate forecasting of transient demand will assist hoteliers in developing strategies to maximize sales to this group

 If the period following the group business is low, then advance knowledge of this information will allow time for marketing and sales to develop special promotional packages aimed at the transient and local markets