In the project will work together UTN and 10 companies in the region, and will have partial funding from the Government of the Province of Santa Fe, through the Ministry of Technology.

Among the objectives, seek to implement and certify the quality of production and service processes of  the companies involved to the project and improving them continuously. Building a partnership swap of  experiences and skills enhancement about quality in production and services software processes, and increase Software Industry in the Province of Santa Fe, with demonstrable ability to develop quality products exported to other markets.

More information: http://www.frsf.utn.edu.ar/noticias/ver.php?id_noticia=1212

Internet Explorer 6

Internet Explorer 6 (IE6) was released on 27 August 2001, more than 8 years ago, and is the default browser shipped with Windows XP. The market share of this browser continues to decline, now being below 14% globally and less than 7% in Europe and USA. This version of Internet Explorer (IE) has several problems:

• Does not support PNG transparencies
• Contains errors when using float + margin / padding
• Inability to use pseudo-classes and pseudo-elements.
• Incomplete support of CSS 2.1
• Presents display errors

Developing systems or websites with IE6 compatibility means spending hours to solve displaying bugs and limit the designs so that they appear correctly in this browser. Besides the user experience is limited to the possibilities available in IE6, modern browsers (IE7, IE8, Firefox 3.5, Safari 4, Google Chrome, Opera 10, etc.) can offer a much better online experience.

It is because of this that from March 2010 IE6 won’t have support on systems and sites developed by Serfe. This means that if you want to have support for this version of Internet Explorer, you must explicitly request it.

Its objective was to develop basic skills necessary to capture, analyze, specify and validate a Product Backlog (requirements) effective preserving agile principles and practices. These where the main topics:

• Present the risks of decision-making process of the human mind and its influence on software requirements.
• Submit an effective way of identifying the scope of software project based on business analysis and project.
• Present models and effective practices for working with requirements in agile methodologies with techniques for estimating the size of the problem.
• Develop an awareness of Planning and Production Control (PCP) for the management of requirements based on concepts and practices of inventory control.

Of course that also took the opportunity to take a walk in the hills of Cordoba.

Do you have a business plan?

CRM is a tool for the management of customer relationships. It is very useful in any business, from manufacturing goods to those that provide services as it allows to plan a business strategy based on clients. This tools become essential in global markets like IT services where retain a customer is more important than winning new ones.

This tool is an open system data (front office) that gives us the opportunity to exchange information with customers. To create records which allow us to see the concept of value that the customer has with the product, to focus on the real needs processes that give rise to the application and delete processes that result in an increase in the price of the product without increasing its value. We can also anticipate new requirements and provide better after-sales services.

The use of a CRM system often fails or doesn’t give the desired results because its implementation is only limited to software installation without studying the context of the company, nor provide the necessary knowledge to its employees. A CRM system should be implemented only after studying the current relationship with customers and defining the new one that the company  wants to reach. Once we know that we will have a clearer picture of which systems we will need, which procedures will need to be standardized and on which topics will be needed to train the staff of the organization.

The CRM software was initially developed by payment and large companies. Recently, however, began to emerge such as “open source”, ie free and open source. This brings with it the following advantages: low cost and the possibility of changing them to the needs of each company.

The most important open source CRM softwares:

Sugar CRM: A powerful tool that helps companies manage customer relationships. That allows optimizing opportunities for presales, sales and after sales, improve customer service and create, implement and evaluate effective marketing campaigns. It enables easy access to available information to improve decision making. Support for multiple databases and processes that facilitate the flow of information. It can be integrated with different software for email management, spreadsheets and word processors. To be more customer friendly is separated into modules:

• Sales: Allows sharing of sales information with the rest of the staff, focus on more profitable business, increase productivity in the sales department through process standardization and monitoring the performance of employees.
• Marketing: Enables support for the creation, implementation and monitoring of marketing campaigns, as well as share information, sales opportunities with the rest of the staff, supports the identification and tracking of leads.
• Support for the client: This module ensures that customer cases are handled based on priority, status and category. This feature helps to solve customer problems and understand common drawbacks to correct and improve product quality. It also helps to measure the responsiveness of staff. The customer complaints are prioritized and assigned to a person or group in order to seek a solution to it. It also offers a self-help through FAQs with possible solutions with the use of keywords.
• Report: Create real time reports of any attribute that the CRM uses, as might be the total of customers found a solution using self-help section or efficiency of a marketing campaign. Regulates access to this information taking into account the profile of each user. Allows a user to change the format of reports.
• Collaboration: This module helps organize and monitor interdepartmental projects. It also enables a more expeditious flow of information within each department and among them too.
• Platform: This module allows administrators and developers making modifications easily. With this module managers can set the control access for different users to areas of the program and give them different privileges depending on the needs, for example providing access to the history of each customer to the marketing staff but only employees of sale will be able to modify this information. Assists programmers to standardize processes of any of the above modules and edit the look of each field to facilitate access to functions that are considered most important.

You can find more information about this tool on: http://www.sugarcrm.com/

Vtiger: CRM program to automate sales forces, support and customer service, marketing automation and inventory control. Support for multiple data bases, security manager, customizing products and services, integration with email tools (Outlook and Thunderbird). Another advantage is that it is completely separate in modules which are:

• Marketing: Manage the efforts to sell things in a company through the form of campaigns, which manage accounts, contacts, emails and leads.
• Commercial: Management and monitoring of sales from first contact with potential customer to the after sales service. You can control opportunities, orders, invoices, products and prices.
• Customer: The easiest way to maintain customer relationships after finishing a project or business, to take reports of incidents, support, etc..
• Analysis: You have ample options to generate reports and indicators at a glance charts to monitor the progress of your company and your business.
• Inventory: It is an additional features to CRM where you can do product management, suppliers, prices, purchase orders, purchase orders, quotes and invoices.

More information in: http://www.vtiger.com/

Hipergate: Open source and web-based applications completely free. Helps on a lot of information technology needs in any organization. Recognizes and indexes Office documents, also allows you to load and export data to Outlook Express. Like the previous tools also is split into modules, they are;

• Collaborative tools and group work module: to organize and keep track of meetings, reserve list and use of rooms, forums and FAQ.
• Contact management module: Managing databases of customers, suppliers and competitors, as well as managing personal databases. Distribution lists. Territorial demarcation and pipelines of sales (business opportunities).
• Project management and incident support module: Allows you to generate and store hierarchical tree of projects and monitoring tasks.
• Virtual store module: Multiple independent catalogs, unlimited hierarchy of categories of goods, stock management and billing orders.
• Content production modules: templates for communication through email and websites, including multimedia and electronic forms.
• Mass emails module: manage multiple sends email to the mailing list to receive messages statistics.
• Corporate Library: 100% disk-based virtual web-based user security roles for the files, management and indexing OLE document properties, links to favorites and ability to import / export.

More information in: http://www.hipergate.org/

Open source software customization services:

A important step of implementing a system based on a tool like consist on the modification of its features so it suits the requirements of each company. Customizing open source software is an affordable alternative, flexible, reliable, fast and secure in the development stage.

Serfe has extensive experience working on open source software to adapt them to business requirements of each company. Our staff is trained to give advice on selection, installation and software configuration. We can also assist in the development of templates, modules, components and also the integration of them with proprietary systems.

For more information visit the following link:

http://www.serfe.com/en/web-solutions/open-source-software.html

Thanks to everyone that trust us and make this possible.  It would be no fun without you.

Work team - October 2009

Asado in celebration of 6 years of Serfe.com

Kinds Regards

Serfe.com team

Directory structure

Joomla has a directory structure divided into 2 big groups. Administrator, where are all the files needed for the backend to work and the various directories that are located in the root directory.

The directories of interest are the components, both within the administrator directory, as in the root directory, since here is where the files for each component are, which in turn are in sub-directories as follows, com_componentName, example com_users.

If we want to see the files corresponding to the users component, must look at

• Administrator/components/com_users (backend)
• Components/com_users (frontend)

Another important is the includes directory, since within it we find files that have classes that are going to be used in the component, for example to connect the database (database.php), to manage user data, paging, etc (joomla.php).

The components are stored in the database, more precisely in the jos_components table.

Files that make up a component

A component to be installed must be compressed in a zip file, with the following format com_ComponentName.zip example com_users.zip.

This file must have at least 8 files that are going to be described in brief:

• admin.componentName.php (backend)
• admin. componentName.html.php (backend)
• toolbar. componentName.php (backend)
• toolbar. componentName.html.php (backend)
• componentName.xml (backend)
• componentName.class.php (opcional)
• componentName.php (frontend)
• componentName.html.php (frontend

The following describes each file.

componentName.xml (Backend)

This file is the one that installs the component.

Basic structure of the file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

<?xml version="1.0" ?>
 <mosinstall type="component">
 <name>Presentation</name>
 <creationDate>01/10/2008</creationDate>
 <author>Serfe</author>
 <copyright>This component in released under the GNU/GPL License</copyright>
 <authorEmail>info@serfe.com</authorEmail>
 <authorUrl>www.serfe.com</authorUrl>
 <version>1.0.0</version>
 <files>
 <filename>example.php</filename>
 <filename>example.html.php</filename>
 <filename>example.class.php</filename>
 </files>
 <install>
 <queries>
 <query>CREATE TABLE `#__example` (
 id INT NOT NULL AUTO_INCREMENT,
 title VARCHAR(100) NOT NULL,
 content TEXT NOT NULL,
 published TINYINT(1) NOT NULL,
 date DATETIME NOT NULL,
 PRIMARY KEY (`id`)
 )
 </query>
 </queries>
 </install>
 <uninstall>
 <queries>
 <query>
 DROP TABLE IF EXISTS `#__example`;
 </query>
 </queries>
 </uninstall>
 <administration>
 <menu>Example</menu>
 <submenu>
 <menu act="all">List</menu>
 </submenu>
 <files>
 <filename>admin.example.php</filename>
 <filename>admin.example.html.php</filename>
 <filename>toolbar.example.php</filename>
 <filename>toolbar.example.html.php</filename>
 </files>
 </administration>
 </mosinstall>

admin. componentName.php (Backend):

It is the first file to be executed when loading the component in the backend, and is responsible for controlling what action is going to be performed, according to act and task parameters.

The act parameter identifies which backend’s menu item was selected.

The task parameter tells us which action is going to be executed, such as save, delete, etc.

For example:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

<?php
 defined('_VALID_MOS') or die('Direct Access to this location is not allowed.');
 //The direct access to the file is not allowed.
 
require_once( $mainframe->getPath( 'admin_html' ) );
 require_once( $mainframe->getPath( 'class' ) );
 //Performs the includes of the needed files.
 
$id = mosGetParam( $_REQUEST, 'cid', array(0) );
 //Capture the variable passed by REQUEST.
 
switch($act)
 {
 default
 switch($task)
 {
 default:
 list($option);
 break;
 case "save":
 save($option);
 break;
 }
 break;
 }
 break;
 
//Function that lists the records from a table in the database.
 function list($option)
 {
 global $database, $mainframe;
 $limit = $mainframe->getUserStateFromRequest( "viewlistlimit", 'limit', 10 );
 //Get the variable limit that is used for paging
 $limitstart = $mainframe->getUserStateFromRequest( "view{$option}limitstart", 'limitstart', 0 );
 //Get the variable limitstart that specifies from which record to begin displaying.
 
$query = "SELECT COUNT(id) FROM #__example";
 $database->setQuery($query);
 $total = $database->loadResult();
 //Executes the query and returns the result in a variable, this function is used when the consult returns a single result.
 require_once("includes/pageNavigation.php");
 //Includes the file cointaning the class for the paging.
 $pageNav = new mosPageNav( $total, $limitstart, $limit );
 //Instantiate the page class.
 $query  = "SELECT * FROM #__example";
 $query .= " LIMIT ".$limitstart.", ".$limit;
 $database->setQuery($query);
 $rows = $database->loadObjectList();
 //Executes the query returning the result into an objects array.
 HTML_Example::list($option, $rows, $pageNav);
 //Call the method that will generate the HTML from the list, and it gets as parameters the option the actual component will have, the array with the records, and the object with the paging.
 }
 
//Function that saves a record in the database.
 function save($option) {
 global $database;
 
$row = new presentacionTable($database);
 //Instance the class that to be created in the file componentName.class.php
 $row->bind($_POST));
 //If the form's input names match with the names in the database table's fields, this method takes care to relate each form field with its respective column in the table.
 $row->date = date("Y-m-d H:i");
 // Seats a particular field.
 $row -> store();
 // Saves the values in the database.
 mosRedirect("index2.php?option=".$option, "Example saved!");
 // The page is redirected to a specific address, the second parameter is the message to display.
 }
 ?>

This file implements 2 actions: list and save.

The first lines includes the needed files, then receive the variables that come in for REQUEST. Next, we determine which action to execute according to the value of the act and task variables.

Then, we implement each of the necessary functions to perform the required tasks.

admin. componentName.html.php (Backend):

This file defines the class that will contain the different methods responsible for generating the HTML.

The basic structure of the file is:

1
2
3
4
5
6
7

<?php
defined('_VALID_MOS') or die('Direct Access to this location is not allowed.');
class HTML_Example
{
 // Methods that generate the HTML to displayed.
}
?>

toolbar. componentName.php (Backend):

This file controls which menu to display according to the received act and task parameters. The basic structure of the file is:

1
2
3
4
5
6
7
8
9
10
11
12
13

<?
defined( '_VALID_MOS' ) or die( 'Direct Access to this location is not allowed.' );
 
require_once( $mainframe->getPath( 'toolbar_html' ) );
// Performs an include of the file named toolbar.componentName.html.php which has the HTML for the menu to display.
 
switch ( $task ) {
 default:
 menuExample::DEFAULT_MENU();
 // Load the default menu from the class menuExample.
 break;
 }
?>

toolbar. componentName.html.php (Backend):

This file generates the menu to display. The basic structure of the file is:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

<?php
 defined( '_VALID_MOS' ) or die( 'Direct Access to this location is not allowed.' );
 //Define the class that will have the menu.
 class menuExample
 {
 function DEFAULT_MENU()
 {
 mosMenuBar::startTable();
 mosMenuBar::publish('publish');
 mosMenuBar::unpublish('unpublish');
 mosMenuBar::divider();
 mosMenuBar::addNew('new');
 mosMenuBar::editList('edit', 'Edit');
 mosMenuBar::deleteList( ' ', 'delete', 'Remove' );
 mosMenuBar::endTable();
 }
 }
 ?>

componentName.class.php (opcional):

This file is used to create a class that will make it easier for us to save, edit and delete a record from the table using the methods inherited from the class mosDBTable.

In the example provided in the file admin.componentName.php we have used a class of this king, more specifically when using the methods bind(), store().

This class also allows us to load a record simply by using the load() method, which receives as parameters the record id.

Basic structure of the file:

1
2
3
4
5
6
7
8
9
10
11
12
13

<?
 defined( '_VALID_MOS' ) or die( 'Direct Access to this location is not allowed.' );
 class classNameTable extends mosDBTable {
 // Each variable is defined according to the number of fields in the table that is referenced in the database.
 var $id = null;
 var $fieldName1 = null;
 var $ fieldName 2 = null;
 function classNameTable (&$db){
 $this->mosDBTable('#__tableName', 'id', $db);
 //This method receives 3 parameters: table name, field with the primary key, database connector.
 }
 }
 ?>

componentName.php and componentName.html.php (Frontend):

These 2 files are used to perform actions in the frontend component. The file componentName.php has the same structure as the admin.componentName.php file. The file componentName.html.php has the same structure as the file named admin.componentName.html.php

What is Joomla?

Joomla is an open source Content Management System (CMS) built with PHP under a GPL license. This o Content Management System can be used to create a website with dynamic content, using a MySQL database.

Features:

• Websites organization.
• Publication of contents.
• Scalability and implementation of new functionalities.
• User’s management.
• Websites design.
• Navigation and menu.
• Image manager.
• Modifiable modules order.
• Polls.
• Advertising.
• Statistics of visits.
• And more…

Which websites can be created with Joomla?

With Joomla we can create news websites, corporate sites, community portals, and we can also create with Joomla systems operating on closed networks (Intranets) to manage internal information (communications, users, etc) from companies or business firms.

Who can use Joomla?

Anyone who wants to have a website can use Joomla.

To build sites on Joomla you must have knowledge about web design and programming, but to manage websites developed on Joomla you just need a minimal training on the programs use.

Joomla’s administrative interface is so simple and friendly, that anyone can manage their own web contents without the need to have technical knowledge, without knowing HTML, and without appeal to a WebMaster every time you have something to update in a website.

All technical aspects of the system are hidden from the common user, and have been resolved by the developers of Joomla, making things simple for administrators and content editors to dispense almost entirely of a specialized technical training.

How is Joomla composed?

Component:

The “Components” are content elements or Joomla’s applications that are usually shown in the center of the main content area of a template. The components are core elements of Joomla’s functionality.

Modules:

The “Modules” extend the possibilities of Joomla by providing the software new functionalities. Modules are small content items that can be displayed in any place that your template permits. The modules that Joomla typically includes are: Main Menu, Top Menu, Template Chooser, Polls, Hit Counter, etc.

Mambot:

The “Mambot” or “Plugins”are small task-oriented functions that intercept content before it is displayed and manipulates it somehow. Joomla provides several mambots/plugins in the distribution of the core. Between Mambots examples we can find WYSIWYG editors.

Versions

The first version of Joomla! (Joomla! 1.0.0) was published on 16 September 2005 and it was an enhanced evolution of Mambo 4.5.2.3 combined with changes in security and anti-bugs. The latest release is called Joomla! 1.5 stable, with its code completely rewritten and build under PHP 5.

How is Joomla divided?

Backend:

The “Joomla Administrator” (Back-end) is the administrative control panel from which the Manager, Administrator or Super Administrator administers the site and its contents.

Frontend:

“The Site” (Front-end) is the website that your visitors or registered users see, and it contains all the information managed from the Administrator.

A web service is an application that exposes or publish its functionalities or methods through an interface. It works in client-server mode, other applications talk to the web service using messages in a standardized format. Essentially, the communication is the same as a web server returning requested data by a browser such as an HTML page, the only difference is that instead of serving up HTML in response to HTTP requests, it serves up SOAP (XML) responses to SOAP requests.

Four elements make a web service:

• XML

Standard format for exchange data primarily designed to the web. Its principal advantage is that a developer can define his own tags, this fix the way the data are read and validated by the client applications. XML schemas must be public so any change made in the application doesn’t affect communication. An xml file begins with this header:

<?xml version="1.0" encoding="UTF-8"?><span id="more-134"></span>

• SOAP

Acronym of Simple Object Access Protocol. Is a communication protocol between applications through messages, where web service objects will be instantiated and their methods will be requested. It was conceived to maintain independence of platform and language implementation, two applications created in different programming languages running on different operative systems, can request data and exchange information without know nothing about each other. SOAP is based on XML, that means that messages of applications are XML files with a predefined schema: SOAP messages must be contained in an envelope associated with a namespace by

<?xml version="1.0"?>
 <soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope"
   Soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">
   <soap:Header>
   ...
   </soap:Header>
   <soap:Body>
   ...
     <soap:Fault>
     ...
     </soap:Fault>
   </soap:Body>
 </soap:Envelope>

SOAP messages must be contained in an envelope associated with a namespace by

xmlns:soap = "http://www.w3.org/2001/12/soap-envelope"

In this case the predefined standard is used:

http://www.w3.org/2001/12/soap-envelope

With encodingStyle, all the complex and simple data types used in the document are defined (any complex type formed with simple type elements can be defined and used). Header includes specific information about the message, like autetication. The message itself is inside the body.

• WSDL

Web Service Description Language is a standard based on XML that describes access to the web service. It indicates wich are the interfaces, operations, messages and data type needed. This is a brief example, to see the file in more detail see:  http://soap.amazon.com/schemas3/AmazonWebServices.wsdl

<wsdl:definitions targetNamespace="http://soap.amazon.com" name="AmazonSearch">
  <wsdl:types>
    <xsd:schema targetNamespace="http://soap.amazon.com">
      <xsd:complexType name="ProductLineArray">
        <xsd:complexContent>
          <xsd:restriction base="soapenc:Array">
            <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="typens:ProductLine[]"/>
          </xsd:restriction>
        </xsd:complexContent>
      </xsd:complexType>
      ....
      <xsd:complexType name="CustomerReview">
        <xsd:all>
          <xsd:element name="Rating" type="xsd:string" minOccurs="0"/>
          <xsd:element name="Date" type="xsd:string" minOccurs="0"/>
          <xsd:element name="Summary" type="xsd:string" minOccurs="0"/>
          <xsd:element name="Comment" type="xsd:string" minOccurs="0"/>
        </xsd:all>
      </xsd:complexType>
      ....
    </xsd:schema>
  </wsdl:types>
  <message name="KeywordSearchRequest">
    <!-- Messages for Amazon Web APIs -->
    <part name="KeywordSearchRequest" type="typens:KeywordRequest"/>
  </message>
  <message name="KeywordSearchResponse">
    <part name="return" type="typens:ProductInfo"/>
  </message>
  <portType name="AmazonSearchPort">
  <!-- Port for Amazon Web APIs -->
    <operation name="KeywordSearchRequest">
      <input message="typens:KeywordSearchRequest"/>
      <output message="typens:KeywordSearchResponse"/>
    </operation>
    <operation name="TextStreamSearchRequest">
      <input message="typens:TextStreamSearchRequest"/>
      <output message="typens:TextStreamSearchResponse"/>
    </operation>
  </portType>
  <binding name="AmazonSearchBinding" type="typens:AmazonSearchPort">
  <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
  <operation name="KeywordSearchRequest">
    <soap:operation soapAction="http://soap.amazon.com"/>
     <input>
       <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://soap.amazon.com"/>
     </input>
     <output>
       <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://soap.amazon.com"/>
     </output>
  </operation>
  ....
  <service name="AmazonSearchService">
  <!-- Endpoint for Amazon Web APIs -->
    <port name="AmazonSearchPort" binding="typens:AmazonSearchBinding">
      <soap:address location="http://soap.amazon.com/onca/soap3"/>
    </port>
  </service>
</wsdl:definitions>

• UDDI

Universal Discovery Description and Integration is a standard that describes the nature of a service, its capacities, location and requeriments in such a way that it can be categorized in web sites offering web service directory. UDDI uses WSDL to describe web service interfaces.

Some of the more common directories are:

http://soapclient.com/uddisearch.html

http://uddi.org/find.html

Applicability

The most used protocol used by web services is HTTP, not because web services can’t be mounted on other protocols such as FTP or SMTP, but because in an environment such as Internet firewalls block many times the access to other protocols.

Implementation

PHP has a few options for SOAP: a PEAR package, an independent and very popular library called NuSOAP and a PHP 5 extension. The last option will be used in this example. First of all native support must be enabled in the web server, in this example Apache is used. Find this lines in the PHP configuration file an uncomment them.

[soap]
; Enables or disables WSDL caching feature.
soap.wsdl_cache_enabled=1
; Sets the directory name where SOAP extension will put cache files.
soap.wsdl_cache_dir="/tmp"
; (time to live) Sets the number of second while cached file will be used
; instead of original one.
soap.wsdl_cache_ttl=86400

If we create a php script with phpinfo() function we will see something like this:

soap

Soap Client enabled

Soap Server enabled

Once this is done, the rest of the process is very simple

<?php
 $wsdl_url = "http://soap.amazon.com/schemas3/AmazonWebServices.wsdl";
 $client = new SoapClient($wsdl_url);
 var_dump($client-;__getFunctions());
?>

In this script we see a class instantiation and a parameter passing to use an amazon web service. The last line of code will shows us wich methods are exposed and what data types use.

The output is:

<pre lang="php" line="1" escaped="true">array(26) {
 [0]=> string(70) "ProductInfo KeywordSearchRequest(KeywordRequest $KeywordSearchRequest)"
 [1]=> string(79) "ProductInfo TextStreamSearchRequest(TextStreamRequest $TextStreamSearchRequest)"
 [2]=> string(64) "ProductInfo PowerSearchRequest(PowerRequest $PowerSearchRequest)"
 [3]=> string(79) "ProductInfo BrowseNodeSearchRequest(BrowseNodeRequest $BrowseNodeSearchRequest)"
 [4]=> string(61) "ProductInfo AsinSearchRequest(AsinRequest $AsinSearchRequest)"
 [5]=> string(75) "ProductLineArray BlendedSearchRequest(BlendedRequest $BlendedSearchRequest)"
 [6]=> string(58) "ProductInfo UpcSearchRequest(UpcRequest $UpcSearchRequest)"
 [7]=> string(58) "ProductInfo SkuSearchRequest(SkuRequest $SkuSearchRequest)"
 [8]=> string(67) "ProductInfo AuthorSearchRequest(AuthorRequest $AuthorSearchRequest)"
 [9]=> string(67) "ProductInfo ArtistSearchRequest(ArtistRequest $ArtistSearchRequest)"
 [10]=> string(64) "ProductInfo ActorSearchRequest(ActorRequest $ActorSearchRequest)"
 [11]=> string(85) "ProductInfo ManufacturerSearchRequest(ManufacturerRequest $ManufacturerSearchRequest)"
 [12]=> string(73) "ProductInfo DirectorSearchRequest(DirectorRequest $DirectorSearchRequest)"
 [13]=> string(83) "ListingProductDetails ExchangeSearchRequest(ExchangeRequest $ExchangeSearchRequest)"
 [14]=> string(76) "ProductInfo ListManiaSearchRequest(ListManiaRequest $ListManiaSearchRequest)"
 [15]=> string(73) "ProductInfo WishlistSearchRequest(WishlistRequest $WishlistSearchRequest)"
 [16]=> string(90) "SellerProfile SellerProfileSearchRequest(SellerProfileRequest $SellerProfileSearchRequest)"
 [17]=> string(68) "SellerSearch SellerSearchRequest(SellerRequest $SellerSearchRequest)"
 [18]=> string(88) "MarketplaceSearch MarketplaceSearchRequest(MarketplaceRequest $MarketplaceSearchRequest)"
 [19]=> string(79) "ProductInfo SimilaritySearchRequest(SimilarityRequest $SimilaritySearchRequest)"
 [20]=> string(83) "ShoppingCart GetShoppingCartRequest(GetShoppingCartRequest $GetShoppingCartRequest)"
 [21]=> string(89) "ShoppingCart ClearShoppingCartRequest(ClearShoppingCartRequest $ClearShoppingCartRequest)"
 [22]=> string(98) "ShoppingCart AddShoppingCartItemsRequest(AddShoppingCartItemsRequest $AddShoppingCartItemsRequest)"
 [23]=> string(107) "ShoppingCart RemoveShoppingCartItemsRequest(RemoveShoppingCartItemsRequest $RemoveShoppingCartItemsRequest)"
 [24]=> string(107) "ShoppingCart ModifyShoppingCartItemsRequest(ModifyShoppingCartItemsRequest $ModifyShoppingCartItemsRequest)"
 [25]=> string(118) "GetTransactionDetailsResponse GetTransactionDetailsRequest(GetTransactionDetailsRequest $GetTransactionDetailsRequest)"
 }

As you can see these are the methods exposed by the amazon web service.

Resources:

http://www.w3schools.com/webservices/

http://www.sitepoint.com/article/own-web-service-php-xml-rpc/

http://www.builderau.com.au/program/php/soa/Powerful-Web-Services-with-PHP-and-SOAP/0,339028448,339288552,00.htm

http://ar2.php.net/manual/en/book.soap.php

http://devzone.zend.com/article/689

Subversion is a software Version Control System that seeks to replace the popular CVS, which has several shortcomings. It is open source and is also known as svn (because this is the name of the command-line tool).

The use of Web applications is growing day by day as well as its size. This is why a project of this topic need a team of several developers with different skills in order to finish the product on time. This is why we use this tool. All files related to the project are stored in the repository which is located on a remote server. Any member of the team could make changes and send to the repository, which can then be downloaded by other members of the team.

These are some of the benefits of using this tool:

1. Management:
   1. Resources Management
   2. Packages Management
   3. Prices and Availabilities Management
   4. Clients Managements
   5. Agents Managements
   6. Configuration Managements
2. Services that would be offered to visitors:
   1. Resources Catalog and Packages
   2. Online Booking

1 Resources Management:

The system will allow the management of resources, allowing to Create, Read, Update y Delete (CRUD) them. The system must store relevant information about it including: title, description and images.

Also should allow to classify the resources in a flexible manner in order to be suitable for any business allowing the proper adaptation of the tool to any environment. A resource would be associated to a bookable category which will be associated with one or more than one category. At the same time, a category can be classified in other parents categories. For example, for a resource of a hotel called “101 room” could be associated to a bookable category called “Double Room”, which may be associated with the following categories “Caesar Hotel” to define that it belong to this hotel. At the same, this hotel may be associated with “Santa Fe” to identify to which city belongs. The category “Caesar Hotel” may be a children of another category called “Emperors Chain” to identify which chain owns the hotel while “Santa Fe” is the children of “Argentina” to determine to which country it belongs. As you can see this is very flexible and could be adapted to any business.

A bookable category may be associated to one or more addons. These addons can be purchased at the same time of the booking. For example, by booking a “Double Room” we would be able to add to our order a “Dinner Menu”. It is possible that the addons impact on the price of the reservation.

Picture 1: Entities associated with resources

Bookable categories and categories would also have associated properties that represents its characteristics. Having this information in a separate entity will allow to perform searches of resources and categories which have these characteristics in common. As an example, the resource “Double Room” could have assigned properties “Jacuzzi”, “Private Bath”, “Air Conditioning”. Then if you’re interested in making a reservation for a room with Jacuzzi you could make a filtering to obtain a list of all the rooms that have those features and then choose between them.

2 Packages Management:

The system would have CRUD of packages. These packages consist of a set of resources and addons and let us create special offers. For example in one package “Weekend in Santa Fe” we could add 2 nights of “Double Room” with an addon “Santa Fe City Tour” and offer it at a price of $500.

The packages may also have associated properties that detail their characteristics. As well as images which are used to show it to potential customers.

Picture 2: Entities associated with packages

3 Prices and Availabilities Management:

The system should allow setting the price of bookable categories and packages as well as their availability. The system must consider the possibility of setting different prices according to seasons. In the same way must allow to apply different discount depending on the month of the year, day of the month, day of week or hour of day. Also offer discount on longer period reservations. The system also would let the administrator to set the availability of the resource in order to prohibit its booking in periods that its not available.

Picture 3: Entities associated with prices and availabilities

4 Client Management:

The system should have features that allow CRUD of customers as well as the create order for a client, this would be useful for an operator to take telephone bookings from customers. It also may allows to manage the orders placed by customers, allowing the follow-up throughout the sales process.

Picture 4: Entities associated with clients and orders

5 Agents Management:

The agents are the users who use the system to manage resources, bookable categories, categories, packages and customers. The system needs to allow to current administrator or agents with sufficient permission to perform CRUD of agents. It will also enable the management of permissions which are then allocated to agents. This will limit the access of agents to the functionality of the system, allowing to perform only those task permitted based on their profile within the company.

Picture 5: Entities associated with agents

6 Configuratin Management:

The system administrator can modify the settings of the software. In this way would be able to set the rates of currencies, payment methods, taxes, among other parameters used.

7 Resource Catalog and Packages:

The system should displays all the information detailed before to visitors. The catalogue shall provide sufficient information in an orderly fashion and ensuring an enjoyable experience for the potential customer.

Should allow to perform searches on resources by identifying the desired characteristics, period where the visitor in interested on making the booking as well as its price. Visitors may also browse the entire catalog by visiting the various resource, packages and categories, reviewing the characteristics of each.

8 Online Booking:

When the potential customer finds a good or service in which is interested on making a booking then the system must also provide a simple process to make it. The visitor should have no problems in signing up as a client, set the start and end date of the reservation as well as all the special features of it. The system also must have an easy payment procedure.