Wholesale e-commerce management system. Cuba

Summary

This work presents a proposal for a Wholesale Product Sales Management System limited to the current regulations for carrying out this activity in Cuba.

wholesale-product-sales-system

This pursues the objective of solving the problem of monetary duality and the country's own forms of payment that make it impossible to apply other existing systems.

The resulting system has improvements and additions of commercial functionalities in a friendly and easy-to-use environment; In addition, it guarantees the security and integrity required by the data that it processes, speeding up and facilitating the process of Wholesale Product Sales.

For the development of the system, the agile methodology of Scrum software construction is used and a study is made of the existing systems and the appropriate tools for its construction.

Keywords

Management Software, Electronic Commerce, Wholesale Sales.

Abstract

This investigation Project exposes a proposal for Wholesale System according to regulations in force for carrying out this activity in Cuba. This system aims to solve the dual currency problem, payment forms and other themes who make impossible to apply existing systems.

The result system improved aggregations of commercial functions in a friendly and easier environment of usage. Besides this system guarantee security and integrity required for managed data making faster and easier the process of selling products at wholesale.

For system development is used an agile method for project management: Scrum.

Keywords

E-Commerce, Wholesale System

Introduction.

Trade is an activity carried out by man since time immemorial. It alludes to the need for the purchase, sale or exchange of species, and also the exchange of services that have historically been created through markets, warehouses or commercial establishments. However, for the first time in history, this conception has changed. This is given by the emergence of the Internet that has marked a new era of interpersonal understanding, and a radical expansion of the means and scope of commerce.

Electronic commerce was born as an expression of efficiency and to be more productive; as a desire to comprehensively meet new needs, under the lens of technology, which plays an essential role in their materialization. Cuba is not exempt from conducting trade, so it enhances its entry into the international market by all means and especially through electronic commerce.

However, the country's economy has special characteristics that make it impossible to apply existing systems because they do not have the ideal ways to make payments and handle a circulating double currency, among other regulations. For this reason it can be stated that there is no computer system capable of wholesale sales that meets the characteristics of Cuban commerce. Thus, the development of a Wholesale Product Sales Management System as a tool that complies with the regulations established for Cuba would favor the development of electronic commerce, providing benefits to the country's economy.

Existing Electronic Commerce Systems

There is a wide range of platforms developed on different technologies for conducting electronic commerce. Just to mention a few, we can list Gesticom B2B, TornadoStore ™, AB-Shop 3. All of them are very user-friendly and attractive for the creation of any type of virtual store. Some of these platforms are even free and open source. However, neither of them nor the inventory systems that support them are applicable in Cuba.

Reasons that rule out the use or reuse of these systems:

• They have already ventured into the use of these systems and patches and modifications have been made to the retail sales that they carry out to adapt them to the wholesalers defined in Cuba.The processes that these model are not those applied in the country by the way in which the Contracting and the Sales Process is conceived. The way of negotiating commercial margins, credits and payment instruments are not adequate or used in Cuba.

The billing process handled by the exposed systems is not the one described for the country.

• The circulation of the double currency cannot be managed by these systems or by their respective inventories.

Taking into account that the main functions of the system must be sales and invoicing associated with the management of commercial margins and credits, there is very little to reuse of existing systems: design ideas, good programming practices, patterns…

Currently, the development of electronic commerce in the country is beginning to be promoted and the first steps are being taken in wholesale sales aimed at companies or legal entities. This gives the possibility of carrying out an exhaustive survey of requirements so that the first e-commerce platform developed capable of working with the Cuban trade model is as efficient as possible.

The idea of ​​creating a new platform is also supported by the use of a service-oriented architecture that allows greater ease of communication between systems and thus more easily achieve their integration (it must be possible to integrate the resulting system with the ERP-Cubacurrently under development). The exposed systems use a hybrid architecture between client-server and 3 layers that does not facilitate the integration process.

Development Methodology

"Scrum" is a methodology for project management, exposed by Hirotaka Takeuchi and Ikujiro Nonaka, in the article The New Product

Development Game. "The basic precept of this methodology is that the competitive market for technological products, in addition to the basic concepts of quality, cost and differentiation, also requires speed and flexibility." (Takeuchi, 1999) The Scrum characteristics that implied the decision to choose this methodology and not another are listed below:

• It is an agile development methodology. It is intended for small development teams (no more than 8 people). Few artifacts are specified eliminating unnecessary "paperwork" and spending more time on implementation. It allows the delivery of a functional product at the end of each Sprint.Gives the possibility of adjusting the functionality based on the client's business need.It allows a daily visualization of the project.It has a limited and feasible scope.It is applied in teams integrated and committed to the project and that are self-administered.No It is a methodology of analysis, not of design (although it can be adapted so that it is) but of work management. It can be applied to different quality models (such as CMMI) since these tell you what you have to do, that is,, they tell you that you have to manage the project,but they don't tell you how. That's where SCRUM comes in as a project management model.

Description of business processes.

To describe the business processes that are related to the scope of this work, it is necessary to focus attention on the problem-solving processes and the relationship of the applications of this type that are known.

This work aims to model the wholesale sales processes according to the regulations proposed in such a way as to comply with the specifications of the trade in Cuba. These particular regulations are listed below:

Hiring and the Sales Process

To carry out wholesale sales, the Commercial Area or Specialist of the Unit must compose the File of each Buyer, which will have the following documents:

• Resolution of appointment and power of the person authorized to sign Contracts License from the Central Bank of Cuba that authorizes the entity or company to operate in foreign currency, duly updated.

Minutes, Deed, Resolution, Document notarized before a Notary Public or other legal document of incorporation of the entity or company, together with its corporate purpose. Signed and minted sale contract, according to Pro forma de Contract (Annex No 4)

The Wholesale Sale Contracts will be promoted by the Sales, Production or Service Unit, adjusting the clauses of the contract pro forma (Annex 4) to the buyer with whom it is signing. Once the terms in which the contract will be carried out and the customer's purchasing interests in the territory have been specified with the Buyer, they must be sent to the Legal Counsel of the Provincial Branch for review.

The Wholesale Purchase Agreement will be signed in the name of the entity that publishes the system and will be signed by the Director of the Territorial Branch and the Commercial Director. The contracts will cover all the Wholesale Sales Units of the Territory previously agreed in the Contracts. In the Contract, the Units of the territory where the Wholesale Sales to the Buyer with whom the Contract is signed must be listed in an express annex, determining those that will be marketed in each of the Units.

In no case will wholesale sales contracts cover Wholesale Units or Areas from other territories. Once the Wholesale Contract has been signed, the Legal Counsel of the Provincial Branch certifies the copies of the Units to which the contract has scope. The Commercial Directorate of the Branch is responsible for providing the referred certified copies to the Units covered by the Contract.

In the case of new clients, the Provincial Branch will request the Client No. from the Commercial Directorate of the Headquarters as established on the Corporate Nomenclator of Clients and Suppliers. Units that do not have certified copies of the contracts or the aforementioned contracts are not updated and the Customer Code is not enabled in the system, will not be able to make sales until the documentation is updated in the Unit's file. established and enabled the Client No. in the Nomenclator.

Contracts signed with companies or state organizations for the sale of modules to their workers will have defined the Specialized Unit for wholesale retail and will not have scope to other units, territories or types of sale.

For the Sale Contracts with the Branches of the Companies

Foreign Companies based in Cuba, as well as the Free Trade Zone Operators, will be signed only by their representative, duly authorized to do so. The documents required to sign contracts with these entities with the following:

• License of the Chamber of Commerce or MINVEC, as the case may be, with which its status in the country is notified.Deed, Resolution, notarized document or other legal document of the constitution of the entity.Customer file, where the officials authorized to make purchases are listed.

The contracts with the Embassies and Consulates will be signed by the Ambassador and / or Representative. In the client's file, in addition to the related data, a copy of the card issued by MINREX for the officials authorized to make purchases and a copy of the card of the Employing Agency of the officials and workers authorized to collect merchandise will be attached.

The Contracts that are signed with the Projects or Collaboration Programs of the Ministry for Foreign Investment and Economic Collaboration must present a certified copy by the MINVEC of the budget and Terms of the Project approved with the obligations of the counterparts that must be signed by these counterparts and the MINVEC.

The Wholesale Contracts will be signed for one (1) year, date from which their validity expires. The Wholesale Contracts are not automatically extendable, they require to be supplemented and obligatorily the validity and the client's file, complying with the regulations for the latter document.

At the time of sale, the Unit will review the customer files and their validity as well as verify if the interested entity is duly registered in the customer nomenclator.

Wholesale sales to Religious Institutions, Companies and Organizations of the Central State Administration, Political, Social and Mass Organizations, Diplomatic and Consular Representations, to the Branches of

Foreign Commercial Companies, Free Trade Zone Operators, Bank Representations and Projects or Programs of the MINVEC; They will be carried out as established in this procedure in correspondence with Resolution 222/2003, authorization I-885/2007 and Instruction 2/2003 all of the Ministry of Internal Trade.

To carry out the sale to the clients mentioned in the previous section, the Unit will require, in addition to the above, the presentation of the following documents:

• For the representations of Foreign Banks:
  • Purchase request letter with the list of products to be purchased and quantity Resolution of the Central Bank of Cuba that authorizes the banking representation to operate in Cuba.
  For the Branches of Foreign Mercantile Companies and Mixed Companies:
  • Purchase request letter with the list of products to buy and the quantity.

• License issued by the Chamber of Commerce of the Republic of Cuba, to operate in the country.

• For Projects and Collaboration Programs approved by MINVEC:
  • Certified Copy by the MINVEC of the Budget of the Project or Program. o Certified copy by the MINVEC of the Terms of Reference of the approved Project with the obligations of the counterparts and their signatures and MINVEC.
  For Free Zone Operators:
  • Purchase request letter with the list of products to buy and the quantity Resolution of the Ministry for Foreign Investment that accredits you as an Operator.
  For Embassies and Consulates:
  • Purchase request letter with the list of products to be purchased and the quantity. Identification that accredits you as a member of the Diplomatic Corps, issued by the Ministry of Foreign Relations of Cuba.
  For Companies and OACE:
  • The entities will present the legal documentation established in the Wholesale Contracting system and other requirements established in this procedure without requiring other special authorizations for products that do not have special regulations. ü For Religious Institutions:The higher authority of the Religious Institution interested in the purchase will issue a signed and coined document where it reflects the needs it demands, its destinations and against what activity it is carried out. In cases where personal hygiene, hygiene and cleaning items are demanded, this must be accompanied by a sworn statement of the number of people attended at the destination entity of the products. When the request refers to electrical equipment or household appliances, industrial kitchens or bicycles with or without motor, the religious institution must submit a request for authorization to the Vice Minister of the Ministry of Internal Trade and once issued it will be processed by the Commercial Vice Presidency with the Branches and Divisions. Once the authorization of the Commercial Vice President or the Vice Minister of Internal Trade has been received,Depending on the approval and the Religious Institution requests the purchase, the Provincial Branch will consult in writing the person who attends Religion in the Provincial Committee of the territory to issue its approval of the sale. In the event that you leave totally or partially, it must be communicated in writing to the Commercial Vice Presidency. In all cases, the Unit that receives a request for purchase from Religious Institutions must process and receive written authorization to carry out the sale. The authorization and consultation documents are filed in the contract file. When a request for an offer is received from a client for the wholesale purchase of merchandise not in accordance with the usual or volumes or products that do not correspond to the activity carried out by the Company or Institution are appreciated,It will be requested in a timely manner that the request be issued or endorsed by the Head of the Company or Institution through a document that reflects the products and the quantities requested.

Trade margins, credits and payment instruments

The determination of the price will be made on the basis of calculating all the costs of the product until it is put on sale, from which the following minimum commercial margins are established:

• For the Sub-accounts of Automotive Parts and Construction Materials = Cost Price x 1.80 For the Sale of Goods = Cost Price x 1.30 For Gastronomy Productions = 10% lower than the Retail Sale Price For Services = Total Expense Cost Sheet x 1.30 Foreign Firms and Institutions, Diplomatic Corps = Cost Price x 1.40 Religious Institutions = Cost Price x 1.60 For retail wholesale (Module) = Cost Price x 1.30

(The sale prices of the merchandise sold in Units for the sale of modules will be rounded to 0 or 5 following the same procedure as in the formation of the retail price)

In the act of sale, higher prices can be applied depending on the quality of the product, its position in the market and the negotiation with the client.

When there are well-founded reasons that advise the reduction of the established margins, the Commercial Director of the Branch or Division will request the Commercial Vice President through the Hardware and Wholesale Sales Department for authorization to carry out the sale with margins lower than those established.

In the proposals must be evaluated:

1. Sales volume Inventory and product turnover Characteristics of the Purchaser to whom it is proposed to sell Proposed Commercial Margin Other quantitative and qualitative elements that support it.

Wholesale sales of merchandise to external entities will only be made through payment against delivery of the merchandise.

The collection will be made by presenting the check issued by the buyer to the seller, bank transfers received and credited to the Seller's account and by magnetic card at the time of sale, following the procedure established for this collection system.

Checks with amounts greater than 500 CUC must be certified by the Bank.

Wholesale sales will only be made to legal entities. Under no circumstances will checks or other payment instruments be received from natural persons.

For wholesale sales of productions and services, including the products that are part of these, credits of up to 30 days may be issued.

Exceptionally, for Wholesale Merchandise Sales, Commercial Credits will be issued up to 30 days after invoicing, which will be previously authorized in writing by the Commercial Vice President, at the proposal of the Director of the corresponding Branch; for which a prior analysis of the following aspects must be carried out:

• Amount of the merchandise to be sold. Recognized economic solvency of the client. If it is a regular customer, punctuality in the previous payments. Convenience of the company to carry out the proposed merchandise to be sold on credit.

Non-compliance with the payment within the period set in the Commercial Credit granted, both for wholesale sales of merchandise authorized on credit as well as for productions and services, make it impossible to carry out new sales until the payment of the debts is made.

Failure to pay the merchandise exceptionally authorized to be sold on credit automatically cancels the authorization of the Commercial Credit to the Defaulting Client and the sale may be resumed once the aging debt is settled with the payment against the delivery of the merchandise.

Customers subject to commercial credit for wholesale sales of productions and services that repeatedly fail to meet the deadlines in their payment commitments will be subject to analysis and the adoption of measures that guarantee collection on time or the suspension of commercial credit.

The accounts receivable that could be generated by non-compliance with payment will be subject to an active and systematic collection management by the unit that registers it, adopting the established measures, including presentation to the competent courts.

Billing

The Commercial Area or Specialist of the Unit will prepare a pre-invoice or sale offer to the client, setting the client's data, product data, quantities and prices as well as the validity date of the offer without creating obligations to reserve the products. When the sale to be made, it is advisable to reserve the products, you must financially ensure their realization and set the deadline for it.

At the time of sale, the Economic Area will prepare the final bill of sale according to the offer presented, giving the buyer the original duly signed and minted. The duplicate is filed in the Sales Unit and the triplicate is issued to the carrier.

Wholesale billing will be carried out in accordance with the provisions of the

Instruction No. 15/2006 of the MFP. It will be the responsibility of the Economic Head or Accountant of the Unit, to file the copy of each one of the invoices issued duly signed and minted by the authorized persons. The stamp of payment must be recorded in the invoices whose collection has been made and verified, regardless of the payment instrument used. No sales or invoices should be made without having previously verified the proof of payment. In the cases established by this procedure where commercial credits are granted, the payment date must be set on the invoice as a cross reference. In cases where the Check is used as a payment instrument, a copy of the check received from the customer must be filed with the invoice. In the cases of other payment instruments, will leave a copy of the voucher that proves the payment at the time of billing.

Description of the proposed system.

To fulfill the objective proposed at the beginning of this work and taking into account the proposed business processes, the proposed system will consist of three sites:

• HostingService (Service Server): It is the main site of the system: it contains a set of published web services that must allow all the processes outlined above to be carried out. All other sites work with the services set out in this. AdminSite (Administration Site): It is a site intended for the work of officials and that implements all the functionalities indicated for them. This site is not very attractive considering its end users. VirtualStore (Virtual Store): It is the virtual store that will be seen by customers. It has all the functionalities implemented in any online store and you adjust the necessary ones to the Cuban particularities.

User roles

The preconceived roles to act on the Wholesale Product Sales Management System are listed below:

Role Justification

User This is any person who wants to access the System and who does not need to authenticate to navigate the public pages.

User Specialization Officer: It is a person belonging to the Unit or Wholesale Sales authorized to perform various actions in the virtual store. Generalization of Administrator, Commercial, Legal and Seller.

Administrator Specialization of Official, in charge of the general administration of the system. Person in charge of the initial configuration of the system and solution of administrative problems.

Commercial Specialization of Official in charge of processing the new products received from the Inventory System and setting the sale price according to price formation rules.

Legal Specialization of Official who is in charge of "blocking" access to customers with problems of this nature, preventing them from buying in the online store.

Salesperson Officer Specialization that processes orders started by customers or creates new ones in their presence at a fixed sales counter in the physical wholesale store.

Customer User Specialization identified by a contract and representing a legal person authorized to make wholesale purchases in the store.

N-tiers service oriented architecture

A service-oriented architecture (not necessarily SOA) facilitates integration with other systems, both local and external, of other companies, opening doors for the Wholesale Electronic Commerce System; it facilitates reusability since the services can be consumed by a number of applications, or they can be combined together to form others. Combined with an n-tiers architecture it facilitates maintenance and flexibility.

Figure 2. Organization form of services and interfaces that can consume them.

The System is divided into the following layers:

• Interoperability Layer Business Layer Data Access Layer Data Layer

Figure 3. General logical view

The System communicates with users through the interface layer and with other systems through other services.

The communication of the service layer with other systems and with the graphical user interfaces will be based on SOAP messages.using the industry standard WS- *. The business layer provides a facade to customers and the rest of the services cooperate transactionally to carry out business functions.

The services use a data access layer to interact with the database. This model is flexible in terms of the type of database to use. The use of NHibernate will allow the use of any other manager only by changing the relevant settings.

Deployment

The system architecture allows vertical and horizontal scalability. The system is quite flexible in choosing a variant for deployment. The following diagrams show possible deployment configurations and the distribution of applications in those variants.

Web application and services

Figure 4. Deployment variant

Considering that some services are internal and others private, the following configuration is recommended:

Figure 5. Recommended deployment variant.

Security

System security is applied in 3 fundamental dimensions: Thin Client, Application Server and DB Server.

Figure 6. System security dimensions

The biggest security threats on the client are Cross Site Scripting (XSS) and SQL Injection. The considerations that have been made to eliminate these gaps are the following:

XSS

• Use the mehotd POST and not GET and do data validation on the server side.

SQL Injection

• The Database was created under the principle of least privilege. The flow of SQL Queries is regulated through NHibernate. Errors are filtered, exceptions thrown by the server to offer the description of the free data that describes the way in which they are structured entities.

To eliminate possible attacks on the application server, the security service is implemented in a Public Key Infrastructure (PKI) which is a combination of hardware and software, security policies and procedures that allow the execution with guarantees of cryptographic operations such as encryption, digital signature or non-repudiation of electronic transactions.

Likewise, the security provided by ASP.NET was reimplemented so that the security service methods are used and thus provide the way for Authentication, Authorization and Access Control of users. For the authentication of the services, a security “touch” is generated that expires after 15 seconds.

The data server also worked under the principle of least privilege and the manager's security rules were configured (SQL 2005 Express in this case, but configurable in any other manager determined). The application controls that the requests made to the servers come from the predefined subnet for user access in each case, making it possible to further raise the security levels of the system.

Finally, the settings are made for the work with the history and password restrictions and the invoices generated by the officials and clients are digitally signed, guaranteeing the non-repudiation of the actions they undertake. Likewise, with the use of aspect-oriented programming and Spring Framework, the generation of security logs (traces) that are registered in the Web server and in the Database is guaranteed.

Product Backlog / Product Task Stack

System or product developed requirements are listed in the Product Backlog. The Product Owner is responsible for its content, prioritization, and availability: it is never finished and is used in project planning, it is simply an initial estimate of the requirements. The Product Backlog develops in parallel as the product and the environment in which it works evolves, is dynamic; constantly manages changes to identify what the product needs to be: appropriate, competitive, and useful. As long as a product exists, the Product Backlog also exists.

Module Id Description Status

Critical Requirements

1 HostingService The System receives information from a " 100% inventory system" on the existence of products

Go	Module	Description	State
		intended for the "online sales area" (Product Code, CSTA or Family, Name, Description, Quantity, Cost, Retail Price, and the percentage of discount for applicable customers.
two	AdminSite	The System awaits an administrative process to prepare these products for presentation to customers, this process includes: Define or create the product image (s) if they exist. Assign the product to the category to which it belongs. Mark the product as ready for sale (active).	100%
3	AdminSite	User registration is done 100% administratively by some company personnel who will have a user in the System with a user administrator role. ü There are several types of users of the site: Clients, Officials. ü Within the official users are the following roles: o “Administrator” general administrative user. o "User Administrator" in charge of registering client users in the System. o "Commercial Administrator" in charge of processing the new products received from the Inventory System and setting the sale price. o "Legal Administrator" in charge of "blocking" customers with problems to prevent them from buying in the online store. o "Commercial Seller" user of the System that processes orders started by customers. ü Client users can be found in these roles:

Module Id Description Status

or "Authorized Customer" buyer identified by a contract and representing a legal person.

4 AdminSite The System must store the following 100% customer information: Company name, commercial registration number, if you are an internal customer, if you are a diplomatic customer, if you are a "one currency" customer, in case you pay by check „ term ‟specify the number of days.

5 AdminSite The System must handle a 100% mechanism , those apply to a specific customer, or to a specific product: ü Specific Customer: Certain preferred customers have a percent discount on all purchases they make while this preference is valid. This percentage is defined by a business manager. If the customer is a "preferred customer" in a purchase, this discount will be applied to the total amount of the purchase and no other discount will continue to be applied. ü Specific Product: Some products have a percent discount on their sale price. This percentage is specified by the commercial administrator. In a purchase, discounts will be applied to those products that have it as long as the current customer is not preferential, in that case only their percentage is discounted on the total amount without taking into account the discounted products.

Necessary requirements

6 VirtualStore The System must show customers the following 100% information about the approved products and organized by defined categories: image, name, sale price.

7 VirtualStore The System must show customers 100% detailed information about a specific product showing: image, sale price, name, description, quantity in stock.

Go	Module	Description	State
8	VirtualStore	The System must provide a product search engine	100%
9	VirtualStore	The System will show the user the X last visited products during their visit to the site.	100%
eleven	VirtualStore	The System must provide a "shopping cart" where you can store products until you want to buy. ü The items in the shopping cart must continue to be available on future visits to the site until you proceed to purchase or the products are removed from the System. ü The System must allow modifications to the quantity or type of products added to the shopping cart. ü In the shopping cart, the System must show the amount of each product and the total amount. ü If a product ceases to exist when updating or opening the shopping cart, it will appear highlighting its missing.	100%
12	VirtualStore	The shopping cart must allow its content to be pre-invoiced. ü The System will prepare a pre-invoice that contains the name, description, sale price and quantity of each selected product, and a summary with the total amount to be paid. ü The System will keep a history of the pre-invoices for future consultation, this information is private for the client but accessible by administrators. ü The pre-invoice will be visible to the client for a time X configurable by the administrator.	100%
13	VirtualStore	Once the pre-invoice has been made, the System must allow "reserving the merchandise". ü The System will reserve for a time X, configurable by the administrator, the merchandise requested in a certain pre-invoice. If during this time said pre-invoice has not been paid, the	100%

Go	Module	Description	State
		merchandise will not be reserved. This option is configurable by the administrator who selects whether the reservation is enabled or not. ü The System generates the "merchandise reservation note", which contains a memorandum for the client about the time in which the merchandise will be reserved and the reservation conditions.
14	VirtualStore	Once the pre-invoice is made, the System must 100% allow "to buy the merchandise". ü The System must check that the products and quantities added to the invoice are still available for the current purchase and take the pertinent measures in case they are not. ü The client must select the type of payment: Check, Letter of Credit, Bill of Exchange, Online Payment, or Cash Payment. Cash Payment can be combined with Check for the case that the customer's check is less than the invoice amount, cash payments are accepted up to $ 0.99, the system generates a payment receipt. For payment by Check or Bill of Exchange or Cash, the client will provide the relevant data. If the client pays more than the invoice amount, the System generates a letter of credit. The System saves the letters of credit and notifies the billing system. Administratively, letters of credit are canceled. To make the payment and for the System to consider the order or pre-invoice "paid" and continue the process, the client must appear at the Company's commercial premises and the official must process the order as explained later in this document. ü The System must take into account the following rules when calculating the total amount of an order: o For clients (foreign firms that do not have an account in MN) of

Module Id Description Status
a single currency: only the CUC component is charged. o For external customers who pay in a single currency: the MN amount is added to the CUC without any conversion. o For customers with a discount in CUC and collection in MN: the value of the MN is deducted from the CUC without any conversion, and is charged separately: the CUC with the discount and the full MN. o For internal customers, the base cost is charged in CUC and MN. o For diplomats the retail price is charged but subtracting the applicable percentage for some products. ü Once the invoice is generated, the System notifies the user of the days they have to collect the merchandise, this is a Company policy and does not depend on the type of products that have been purchased.
Optional Requirements
15 AdminSite The System must provide a 56% work interface for commercial personnel in the Company's commercial premises: ü The System must show details of the orders or pre-invoices and invoices. ü The System must allow an official to process an order made by a client while he is present. o The officer must select the order. o If the payment is by Bill of Exchange, Check or Cash, it must be done manually and the System must allow marking the order as paid. In the case of Cash, the System generates a payment receipt. o Once the order is processed, the System behaves the same as if it were processed online: the merchandise is reserved for
Go	Module	Description Status
		True, the products purchased are discounted from the sales area. ü The System must allow legal administrators to freeze a client. These customers cannot make purchases.
16	VirtualStore	The System will publish the form used by 65% of the Company to become a buyer.

Additional requirements

• Appearance or external interface:
  • Simple design, a simple to use and interactive interface to make it easy for the user to work with the System. Perfectly framed design for 1024 × 768 resolutions, but ready to be seen in other resolutions.
  Usability:
  • The installation of the system brings with it a greater speed in the sale of wholesale products, making the process much more efficient.
  Software:
  • The application is hosted on an IIS or Apache web server with the “aspx” module for compiling pages installed. The database server must be SQL Server 2005 or PostgreSQL, although any other can be installed by specifying it in the System configuration. All machines clients must have a browser installed, preferably Internet Explorer version 5.0 onwards, they can also be: Mozilla FireFox, Netscape and Opera

(recent versions).

• Also, Flash Player version 6.0 or higher is installed to display the banner (optional).

• Portability:
  • The application can be run on most operating systems such as Microsoft Windows 98 / Me / 2000 / XP and Linux, the latter installing the Linux versions of the software specified in these requirements.
  Hardware:
  • To work with the system efficiently, a server machine is needed that must have at least the following characteristics: Pentium IV with 768 MB of RAM, a 3.00 GHz microprocessor and a 10/100 MB / s Ethernet protocol network card. client machines: a 16-bit or higher graphics processor with a resolution of 1024 × 768 pixels or higher, a 600 MHz processor, and 64 MB or higher RAM.

They must be connected on a 10/100 MB local network or they must have a dial-up modem with a 128 Kbps connection.

Practical contributions and ways of solution.

First steps

After the system is installed, the following elements must be configured for its correct operation:

Metadata: This concept arises to store data not conceived in the entities of the designed database. For example: The system stores the number of contracts, creation date, and optionally if it is intended for a company (otherwise it is a person); if you want this contract to have a new property "X" it is defined as a contract metadata and the type of data is specified and if it is required when completing the form. In this way, when the Contract form is presented, the predefined fields for it and those added via Metadata will be painted.

Roles: Regardless of the user levels that are established for the basic operation of the system in their configuration files, these may or may not exist. For the use of the system with custom roles, this entity is created in charge of managing the system role definitions.

Categories: The system works with the families (or aggregates) provided by the inventory system or allows customization. This definition of categories is necessary when installing the system in order to later organize the products.

Coins: The system is conceived with the idea that it can be configured for the use of 1, 2 or 'n' coins. For this, the entity of the same name in charge of saving its specifications is established. These will be used for the definition of wholesale prices as explained later.

Units of Measure: The products that are sold can be treated both by their base units of measurement (from the inventory system) or by the equivalences that are defined in the system. For them the entities UM and Equivalence are created respectively.

Content: It is the definition of content in HTML format that will be displayed on the front page of the designated site. For this there is a page editor in visual WYSIWYG format.

The other elements are incorporated into the system either through the administration site or through the web services published for that purpose.

Multicurrency management and wholesale price formation

Once the 'n' currencies with which the system will work have been identified, the price formation rule (s) must be created. For this, there is a form in which the commercial administrator of the system enters his specifications, the most important being the "formula".

This formula is nothing more than a regular expression in the following format:

( w {1,} ( d {1,}) *;) *

A string of characters that must correspond to the identifier of the currency being formulated, a mathematical operator, an allocation value, and the ending of the expression specified by a semicolon (;). The case of regular expressions outside the specified format will be ignored by the evaluator. The idea is to achieve specifications like this:

CUC * 9/10; CUP;

In this case, the customers affected by the rule shown will have the result of evaluating the written function as the wholesale price, with the retail price in each of its components.

For clients that operate with a single currency or only with a part of the „n‟ configured in the system, parts of the rule are omitted or not. For example: if the system is configured to work with CUC and CUP and you want a client to pay 98% of the CUC component, the following rule should be written:

CUC * 98/100;

Once the rules are defined, the system is capable of evaluating them for authenticated customers in such a way that it is possible that a customer "X" and another "Y" are visiting a product in unison and see different prices due to the rules that apply.

With what has been described so far, it is possible for the system to formulate prices and totals according to the customers who browse its pages, but how is the payment made?

When the customer has the products he wants to buy in his “shopping cart”, he can print the content or refer to the payment form where the credit card data will be collected for each of the accounts associated with the currencies in which they are used. makes the sale. Optionally, you can define a recipient for the purchase, in which case new data will be required and the total price will be re-evaluated taking into account the distance of delivery.

Online Service

As an added value, an online service path is included in the system. To do this, in the detailed views of products, the option with this name is designed with which customers can display a chat panel and contact an official in charge of attending to these requests or other customers who browse the site. In this way, an environment for the exchange of commercial information about the products and experiences of their use between officials and clients is fostered.

To avoid misuse of this option, a dictionary of "not allowed" words must be implemented and that both the officials in charge of dealing with these requests and the legal administrators ensure the integrity of what is sent by inactivating the access of the offending clients. under penalty of commercial measures added as clauses to the contract.

Construction of the proposed solution

Principles of application design

The 7 Principles of Universal Design focus on the design that can be used universally or by all, but it must be taken into account that other aspects intervene in the design, such as cost, the culture in which it will be used, the environment; that cannot be forgotten either. These General Principles of Design are applicable and in fact are applied in architecture, engineering and, of course, Web pages and applications, among other fields of application.

1st Principle: Equivalent use

The design is useful and salable to people of various abilities.

Guidelines for Principle 1:

• Provide the same ways of use for all users: identical when possible, equivalent when it is not. Avoid segregating or stigmatizing any user. Privacy, guarantee and security features must be equally available to all users. the design is attractive to all users.

2nd Principle: Flexible use

The design accommodates a wide range of individual preferences and abilities.

Guidelines for Principle 2

• That it offers possibilities of choice in the methods of use. That it can be accessed and used with both the right and the left hand. ü That adapts to the pace or rhythm of the user.

3rd Principle: Simple and intuitive

The use of the design is easy to understand, depending on the user's current experience, knowledge, language skills or degree of concentration.

Guidelines for Principle 3

• That eliminates unnecessary complexity. That is consistent with the expectations and intuition of the user.

That accommodates a wide range of literacy and language skills.

• Dispense information consistently with its importance Provide effective prompts and response methods during and after task completion.

4th Principle: Perceptible information

The design effectively communicates the necessary information to the user, taking into account the environmental conditions or the user's sensory capabilities.

Guidelines for Principle 4

• Use different modes to redundantly present essential information (graphically, verbally, or tactilely) Provide sufficient contrast between essential information and its surroundings Expand the readability of essential information Differentiate items in ways that can be described (for example, make it easy to give directions or directions). Provide compatibility with various techniques or devices used by people with sensory limitations.

5th Principle: Tolerant of error

The design minimizes the risks and adverse consequences of unintentional or accidental actions.

Guidelines for Principle 5

• That it has the elements to minimize risks and errors: elements more used, more accessible; and hazardous elements removed, isolated or covered. Provide warnings of hazards and errors. Provide safe shutdown characteristics. Discourage unconscious actions in tasks that require vigilance.

6th Principle: That requires little physical effort

The design can be used efficiently and comfortably and with a minimum of fatigue.

Guidelines for Principle 6

• That allows the user to maintain a neutral body position, that uses the forces necessary to operate in a reasonable way, that it minimizes repetitive actions.

That minimizes continued physical effort.

7th Principle: Size and space for access and use

That it provides an appropriate size and space for access, reach, manipulation and use, taking into account the size of the body, the posture or the mobility of the user.

Guidelines for Principle 7

• Provide a clear line of sight to important items for both a seated and standing user. That the reach of any component is comfortable for any sitting or standing user. Accommodates variations in hand or grip size. To provide the space necessary for the use of technical aids or personal assistance.

The design has to be based on the mixture of the ideas, desires and needs of the user and on the materials available to the programmer, and in this case it is about users who may be experts or inexperienced in the subject; some of them unprepared in IT matters.

For this, this system uses certain general principles that guarantee usability in the designs for these applications:

• The interface should not overload the user with unnecessary complexities or distract him from his work. The user should be given a flexible environment so that he can quickly learn to use the application where options are offered in the methods of use, which facilitates the user accuracy and precision, and adapts to the user's pace or pace. The interface must be consistent. User productivity must be considered before machine productivity. If the user has to wait for the system's response for a long period of time, these losses of time can turn into financial losses for the organization. Help messages should be simple and provide answers to problems. The menus and button labels should have the process keywords. The interface should have reversible actions.

In developing the interface of this application, the above principles were taken into account as follows:

• Pleasant colors and images were used, achieving greater and adequate communication between the application and the user. The text alignments were maintained as well as the alignment of the navigable buttons, and other elements such as their lighting were taken into account.

Characteristic elements were used for the description of actions, both images and texts.

The application shows compliance with the physiological requirements with respect to the human being when receiving digital information, so that their health is not affected by improper use, for example: font size, spacing between characters, typography, contrast figure - background of the majority information, standardization of margins and distribution of information throughout the entire software.

Treatment of Exceptions

It is of vital importance to achieve the correct operation of any system to identify and control the possible errors that may occur when interacting with the software. For the correct operation of the application, these errors will be treated in such a way that the interactions with the database (insertion, deletion, modification…) are carried out correctly, to achieve this, validation mechanisms were established that verify the correctness of the data to be processed; In addition, the forms insist that the user enter the least amount of data possible, making the most of the calculable fields within the form, selection controls; such as: option buttons (RadioButton), check boxes (CheckBox), and selection lists (ListBox), among others.In this way, the user selects between predefined options, which does not leave room for error.

In the case of data entry by the user, the facilities provided by C # and ASP.NET are used for data validation; if there are errors, messages are displayed that illustrate the incorrect insertion, modification or bad manipulation of data in general with the possibilities offered by the language used, showing the user correct and explanatory information about the possible error made. All error messages are shown in highlighted messages using the facilities of AJAX technology for the implementation of the functions in charge of control and data validation in the client, and a second validation of the data sent by the user and received from the client will be implemented. the database to minimize possible errors to zero and ensure that the user interacts with a quality system.

Encoding standard

“Any fool can write code that computers understand. Good programmers write code that people understand. " Martin Fowler

The coding standard focuses on the style guides for programming in the C # language, although it can be used in many other languages ​​and environments to establish the conventions to be used.

1. Organization of files
   • Source files

Each class must be in a single file, and a file cannot contain more than one class. Although, in a file, together with its class, the related elements can be defined, eg the exceptions that it can throw.

• Directory tree and namespace

The namespace of the objects will be reflected in the source code directory tree. Thus, the Y10K.AyeAye.Switch class will have its code in Y10K / AyeAye / Switch.cs. If an abstract class contains useful code and in addition to it other classes inherit, such as specialization classes, there will be the file with a cs extension corresponding to the abstract class and, at the same level, the directory with the name of the abstract class that it will contain inheriting classes.

1. Indentation
   • Line length

The length of the line will not be kept beyond 80 characters whenever possible.

• Split lines - Whenever a line needs to be split in two, the following conventions will be used:

If there is a list of items separated by commas, it will be divided after a comma.

If it is an expression, it will be split after one of the operators. Preferably, an expression will be divided into higher levels, rather than lower levels.

The divided line will be aligned with the level within which the division has occurred.

• Indentation spacings

Given the disparity in the number of indentation spaces, tabs will be used, which can be used with many editors to be represented with different amounts of spaces and, above all, they become a click per indentation.

1. Declarations
   • Number of statements per line

By definition, the same line will never be used for more than one definition, which facilitates comments regarding the declared element.

• Initialization

Whenever possible the variables will be initialized on the same declaration line

• Declaration of classes and interfaces: To define the classes and interfaces, the following rules will be followed:

No space will be used between the name of a method and the opening parenthesis of the parameter list.

The opening brace that contains the code is written alone on the line following the definition of the prototype. Likewise, the corresponding closing brace is written alone on the last line.

1. Sentences
   • Simple statements

Each line will contain no more than one sentence, although, as explained in section 3, a sentence can be on more than one line

• Return statements

The return statement does not use parentheses.

• Basic select statement (if / if… else / if… else if… else)

The starting braces of a code block are placed at the end of the if, else, or else if statement. The closing braces are on separate lines. When an else or else if statement follows a block of code, the statement will be placed on the same line as the closing brace.

• For or foreach loop statements

In a similar way to the selection statements, the block opening brace will be placed after the definition statement of the for or foreach, and the closing brace on a separate line.

• While or do while loop statements

Identical to for, but in the case of do while, the while will be placed on the same line as the last brace.

• Multiple select statements (switch)

With regard to the keys, they will be placed as in the rest of the cases. Regarding the code and the break line, these will go with one indentation more than the corresponding case line, which will go with one indentation more than the switch line.

• Exception catch and handling statements (try / catch / finally) The handling of block keys will be as in the rest of the statements.

1. Blanks
   • Blank lines: Blank lines can be used to separate groups of lines that have a certain logical relationship. Two blank lines in a row are used to:

Separate sections of code in a file.

Separate class and interface definitions within a file.

• A blank line separates…

Methods.

Definitions of local variables within the method. Code blocks that are not directly related.

• Separations between terms

In a parameter list, spaces will be placed after commas, but never after or before parentheses. In assignments, spaces will be placed before and after the =. In expressions, spaces will be used only when strictly necessary and to separate the different expressions.

• Separations in declarations

We will try to maintain a tabulated structure for the variable declaration lines, so that reading the information is easy. In the following example you can see how to maintain this structure, but keep in mind that for spacing, you must use spaces, not tabs:

string name = "Mr. Ed ”; int myValue = 5;

Test aTest = Test.TestYou;

1. Nomenclature: It is important to keep in mind that the Hungarian notation will not be used for absolutely anything, except for the GUI encoding, where it can be used, but detailing the types in detailed suffixes (cancelButton, for example).
   • Nomenclature for classes

The name of a class must be made up of nouns. Pascal capitalization will be used. No class prefix will be used.

• Nomenclature for interfaces

They will be named with nouns or adjectives that describe the behavior. Capitalization Pascal. They are prefixed with an I, in capital letters, and the word that follows is also in capital letters.

• Nomenclature for enumerations

Pascal will be used for both value names and type names. Neither prefixes nor suffixes will be used. Singular nouns will be used.

• Nomenclature for constants and for read-only attributes Pascal will be used with nouns or abbreviations of nouns Nomenclature for normal parameters and attributes

Descriptive names will be used, highlighting the meaning before the typology of the parameter. In this case, Camel capitalization is used.

• Nomenclature for variables

Camel will be used. When trivial counters are used, names such as i, j, k, m, n,… will be used.

• Nomenclature for methods

The methods will be named with verbs, in Pascal.

• Nomenclature for properties Nouns will be used, in Pascal Nomenclature for events

Events will be suffixed with EventHandler and two parameters will be used, named sender and e. Pascal will be used. Verbs will be used in the past and present tenses to give an idea of ​​the meaning of the event.

1. Programming practices
   • Visibility

Preferably the class and instance attributes will be encoded as private, so that there will be accessor methods.

• Magic is forbidden

Numbers that can be replaced by constants will not be used. This is only so that, if the number has to be modified, it only needs to be modified in one place.

1. Comments

Only the // format will be used, the / *… * / will never be used.

When a block of lines has to be commented, as many // at the beginning of the line as necessary will be used, as if it were a # in a shell script.

Help Conception

Taking into account that all the users who will work with the application are not advanced and may have little or no experience with the application, the need arises to show them the help, which will allow them to know the operation of each of the system options, For this, several mechanisms will be implemented that allow the user to be informed and oriented at all times, hence there will be a help option in each interface with the description of each field and the options of that interface, which will allow them to know what to do. and what data to enter at any time.

Sustainability Assessment

Administrative Impact

The development of the web system does not require excessive resources, with the use of a not so advanced computer, belonging to the fifth generation of microcomputers with the most used operating systems and the use of some free distribution software, a stable version can be achieved in a few months.

Not so advanced conditions are needed to view the site: a Pentium III computer with a web browser (Internet Explorer, Mozilla Firefox, Opera), 64 MB of RAM and a connection to the NETWORK where the “HostingService” is published, which could be a LAN, Intranet or Internet. If you want to implement the application in optimal conditions, you can use state-of-the-art technologies, which would yield the following expenses (Hardware for network. Prices provided by the Copextel Corporation):

Quantity Description	Price (CUC)
one	DELL PE830 Server 3GHZ / 2MB / 800 / 512MB / 2X73GB / M / K	2,177.80
one	DELL E173FP Digital Flat Panel 17 ”Monitor	299.00
one	Wall-mounted cabinet 2 cpo 12U pta glass	239.89
one	AT-8024-10. 24 Port 10/100 Base TX, Layer 2, Manager	424.84
one	Zyxel ES-1024A Fast Ethernet Switch 24 × 10/100 Base Tx	129.04
3. 4	Patch Cord 3m	81.94
14	DEXSON Channel 60 × 40 (2m)	68.04

The creation of the system promotes new forms of distribution of products (or services) increasing business opportunities taking into account the increase in potential customers from any geographical area without limitations. Likewise, an opening and expansion towards new remote and / or unknown markets is achieved and the business hours of service are maximized from "n" hours a day to offering the service 360 ​​days a year, 24 hours a day.

The implementation of the system does not require a physical presence of personnel, thus reducing the expenses used in the maintenance and pay of these employees. It also enhances an increase in customer satisfaction by having a comfortable, fast and easy way to contact the business: They do not need to wait for the phone to be answered, to move to their store, to suggest, consult and buy from a time limitation…

For the development and implementation of the system, a series of software and work platforms are needed, some of which are freely distributed:

software	Price (USD)
Free Software Variant
Kubuntu 7.10 Gusty	Free
Monodevelop	Free
Apache Web Server	Free
PostgreeSQL Database Server 8.2.4.1	Free
Variant with Proprietary Software
Windows Xp	$ 128.00 - $ 307.53
Visual Web Developer 2005 (Express Edition)	Free
Internet Information Server	Included in the OS
SQL Server 2005 (Express Edition)	Free

Socio-Humanist Impact

The system does not harm the quality of life of society in any way, on the contrary, it constitutes a contribution to the computerization of society and a reliable and updated source of information and market, through which registered persons can make their purchases online.

The system can be accessed from anywhere with access to the Web where it is published, so its level of generalization is variable since it could be from a small local network to the Internet

The implementation of the site generates several jobs: a Computer Engineer in charge of carrying out the Administration of the services provided by the site, who will ensure its maintenance and correct operation; a Commercial Administrator and a Legal Administrator who must be graduates of specialties related to the function they perform.

To favor the acceptance of the application, a structure consisting of a pleasant user interface was designed, with smooth animations that do not prolong the loading time too much, the information that is exposed is posted by the entity that hosts the application and the prices of sales those established for this type of trade in the country.

Environmental impact

For the design of the Wholesale Product Sales Management System, no resource harmful to the environment was used and a uniform, simple user interface was conceived with pleasant contrasts, the colors used are soft and at the same time represent the entity that publishes it or the country. The excessive use of warm colors was avoided, so that the design is not exhausting and refreshes the view because the predominant color is white. The colors used are not saturated, on the contrary, light colors predominate, avoiding fatigue or damage to the eyes of the user who visits the site. The information presented is summarized and concise, with a clear font and an average size, and good navigability, this limits the time to search for information and prevents damage to the spine of users.

The interface is characterized by curved and smooth features, which conveys a sense of tranquility and peace, and due to the use of AJAX, subtle animations, smooth transitions are used, without excess information and avoids psychological stress on users.

Technological Impact

To use the application, advanced computer knowledge is not required, on the contrary, only basic knowledge of how to manipulate a web page in the browser is required; also have minimal notions about Internet browsing to be able to access the different information, sales and system configuration modules. For the administration of the site, advanced knowledge is not required either, only basic principles, mastering the different modules, and having average knowledge about client - server technology (managing a web server and a database management system).

The organization that adopts the site can be completely independent from the producer, which allows, according to its social impact, the implantation of the site in other locations without the need for the presence of the producer or creator of the site.

Among the technological factors that constitute a risk of vulnerability are the breakdown or malfunction of the server in which the application is hosted, the breakdown of the equipment of digital communication channels (network cables, switches, hubs, etc.). All this can be avoided by complying with computer security measures and applying periodic maintenance of the hardware and software that the organization has.

The application has the possibility of adapting to future changes, due to the architecture oriented to n-tiers services, which are dynamically loaded and can be updated both dynamically and manually without the application presenting failures or malfunctions in its operation.

Conclusions

As a result of the research, the following conclusions stand out:

1. A tool was developed that performs wholesale electronic commerce processes complying with the regulations established for Cuba. A review of the existing bibliography was carried out to find out the origin and evolution of electronic commerce and the degree of novelty of the results of this work. developed the design, implementation and testing of the resulting Wholesale Product Sales Management System The methodology used for the design and development of the application was efficient and is available for use in similar systems Assessed the social, economic, and economic impacts technological and environmental aspects of the development process of the Wholesale Product Sales Management System, it can be said that this product is sustainable.

recommendations

It is recommended based on the result of the investigation:

1. The implementation and use of the system in SMEs in the country to assess its deployment on a larger scale. The use of the system as support material to teach subjects such as "Electronic Commerce" and optional courses such as "Architecture and Patterns." Develop new versions venturing into the Use of other methodologies such as RUP or XP to make a comparison of the results obtained. Make the total migration of the system to platforms that guarantee its technological independence.

Bibliography

• Why ASP.NET? Esquivel, Julio Batista. 2006. 4, Madrid: sn, 2006, Vol. 1. Almeida. 2002. Bufet Almeida. Bufet Almeida Website. October 12, 2002. http://www.lssice.com/23/lssice. Alvarez, Miguel Angel. 2006. Web Development. 2006. http://www.desarrolloweb.com/php/. Aravena I, Diego, and others. 2006. Electronic Commerce. Faculty of Education and Humanities, Universidad de la Frontera. Temuco: sn, 2006. Arsys. 2007. Arsys.es. Help website: hosting resources, electronic commerce. http://www.arsys.es/ayuda/directorio/productos/hosting/comercio-electronico.htm. Associates, Anguiano &. 2006. Legal problems of electronic commerce. Spain: sn, 2006.AUKEN, J. 2007. HTTP transactions using PHP. 2007.http: //www.malditainternet.com/node/63? PHPSESSID = d7825b7a5b5ca2adea79bd0505c09db Ávila, Eduardo René Rodríguez. 2008. Electronic Commerce. Postgraduate Studies and Research Section, UPIICSA. 2008. BANKING, CDS 2006. Other banking operations: collection and payment operations. 2006. http://www1.euskadi.net/guiaconsumo/curso_bancario/preguntas.apl?apartado=26. Bitpipe. 2004. Bitpipe.com. 2004. http://www.bitpipe.com/tlist/Perl.html. BORETTO, MM 2005. Aspects of intellectual property derived from the digital environment, in private international law. 2005. http://www.eumed.net/libros/2005/mmb/index.htm. Brosa, Pedro. 2000.Business strategies and legal and tax implications. 2000. CAMPITELLI, ADRIÁN. 2003. Electronic commerce. 2003. http://www.monografias.com/trabajos12/monogrr/monogrr.shtml. CARAMÉS, HV 2006. Banks on the Internet. 2006. http://www.ciao.es/Opiniones/PayPal__289916. COMMUNICATIONS, DG 2007. Payment gateways. 2007. http://www.dimensis.com/pasarela-de-pagos.html. Corporation, Microsoft. 2005. SQL Server 2005 Product Overview. Microsoft TechNet SQL Server TechCenter. 2005. -. 2007. The Architecture Journal. 2007. Cuervo, José. 2008. The Digital Signature and Certification Entities. 2008.http: //www.informatica-juridica.com/trabajos/firma_digital.asp.DILOCONFORES. 2006. Secure Transactions, Forms of payment. 2006. http://diloconflores.com/store/comersus_index.asp. Explaining Scrum in 10 minutes. Serrano, Jorge. 2007. 4, Bogotá: sn, 2007, Vol. 1. Estenos, Raul Sanchez. 2005. 10 Reasons to use Java. Lima: sn, 2005. FERNÁNDEZ, F. 2007. Web Programming: Languages ​​used. 2007.http: //www.xeoweb.com/programacion-web.php. Gomez, Raciel. 2001. Internet Marketing. Raul Porto Santos. Lima: sn, 2001. GUARDIA, CDL 2007. The evolution of electronic commerce. 2007.http: //www.razonypalabra.org.mx/anteriores/n20/20_cguardia.html. Herrera, Johany. 2007.Techniques and tools used in requirements engineering. 2007. http://www.monografias.com/trabajos6/resof/resof2.shtml.. ITAA. 2004. Information Technology Association of America. 2004. www.itaa.org. MARAÑÓN, G. Á. 2008. Secure Electronic Transactions (SET), Means of payment. 2008. http://www.iec.csic.es/criptonomicon/comercio/set.html. MENDEZ, J. 2006. Trends in programming languages. 2006. http://www.monografias.com/trabajos/tendprog/tendprog.shtml. Microsoft. 2006. The Electronic Signature and the reliability of online transactions. 2006. http://www.microsoft.com/spain/seguridad/xp/firma/default.asp. NEWKIRK, J. 2002.Extreme programming in practice. Madrid: sn, 2002. Legal news. Legal news. 2000. http: //noticias.juridicas.com.Planeta Code. 2005. http://www.planetacodigo.com/wiki/glosario:extreme_programming. Pressman, Roger S. 2002. Software Engineering. A practical approach. 2002. REBELDE, MECD 2005. Obstacle to electronic commerce. 2005. http://www.mesaredonda.cu/informacion.asp?idInformacion=254&idSeccion=4&Logo=71. Ribas, Xavier. 2005. ELECTRONIC, LEGAL ASPECTS OF TRADE. 2005. Rodriguez, Javier Prenafeta. 2005.Hosting contracts. An overview of the main issues that should be taken into account when negotiating this type of contract “on the website of the Association for the Promotion of Information Technologies and Electronic Commerce (APT. 2005. http: // news. juridicas.com/external/nj_aptice/2002085556141710242121.html Russo, Renne. 2001. Information and communication technologies. 4, 2001, Vol. 1. Saldivar, Raul Vicente. 2007. 5 reasons not to use Spring. Mexico DF: sn, 2007. 2. Schwaber, Ken and Beedle, Mike. 2003. Agile Software Development with SCRUM. 2003. Computer Security, why and for what. 2002. November 2002, RED. Serrano, Agustín. 2006.Legal and fiscal framework in e-commerce. 2006. Simsom, Richard. 2007. Computer Security. The community of networking experts. 2007. Sparxsystems. 2005. 2005. www.sparxsystems.com. STEPHENS, M., ROSENBERG, D. 2003. Extreme programming refactored: the case against XP California: sn, 2003. Takeuchi, Hirotaka. 1999. Scrum. 1999. Varea, Ismael García. 2006. JAVA A haven for experts? 14 of 4 of 2006.

Annexes

Annex 1: View of the Virtual Store

Annex 2: View of the Administration Site

Annex 3: Basic functionalities of an electronic commerce system.

• Access restricted to users with an access code. Public and private product catalog. Printing of catalogs. Order status and follow-up. Management and situation of risks, returns and collections. Item finder. Virtual store. Stock of items by options (colors, sizes, lasts, etc.). Data and order encryption. Billing history. Order delivery. Invoice printing. Payment validation through SSL secure pages and online bank. Configurable item file. Configurable purchase form.Importing articles from other databases. Backup copy. Design templates included. Off-line maintenance. Checkout of selected products. Editing of pages in visual WYSIWYG format.

Glossary of terms

1. Wholesale Sales Areas: These are those enclaves in Retail, Production or Service Units that wholesale products or services previously approved in their wholesale assortment policy. Wholesale End Customer: Natural Person, worker of one of the Companies, Bodies or Organizations of the Central State Administration with which the Contract for the Sale of Modules has been signed and is expressly registered in the Contract. Wholesale trade: It is called wholesale or wholesale trade, the sale of nationally produced or imported goods, destined for retailers, industrial and institutional consumers and wholesalers, among others. In this store you can also carry out retail sales. Buyer: Legal Person with whom the obligations related to the Sale Act are established by means of a Contract. SME (s): Small (s) and medium (s) companies. Retail Wholesale Units(Commercialization of Modules), are Units destined to the wholesale commercialization of products foreseen in the Assortment Policy of the Unit with this type of sales destined to the Companies, Organizations and Organizations of the Central State Administration and whose delivery is carried out in detail to the end customer. This type of sales will be carried out only in Specialized Units for this type of wholesale sale. Wholesale Units: The facilities defined in a Cost Center are called Wholesale Sales Units where the wholesale marketing of the products or services approved in its Assortment Policy is carried out. Seller: Wholesale Sales Unit or Area of ​​the company authorized by this procedure to carry out the wholesale sale to the legal entities provided for in this procedure

Enterprise Resource Planning

Simple Object Access Protocol. It is a standard protocol created by Microsoft, IBM and others, it is currently under the auspices of the W3C that defines how two objects in different processes can communicate through the exchange of XML data.

Download the original file