CompTIA EIDX Implementation Options

An electronic commerce implementation involves a choice of content standard, a choice of business process, and a choice of how information will be conveyed - implementation options. These can be combined in many ways. This section discusses the choices of transport and routing standards. These are used to move the payload - the actual data files - and ensuring the content privacy, authentication, integrity and non-repudiation.

• The Technical Basics of eBusiness Implementations
• Basic Implementation Options - User View
• Information Exchange Timing Options
• Mixing and Matching Options
• Barriers to Electronic Commerce
• Cost Factors to Consider for Implementation Options
• EC Technology Matrix
• Basic System Architecture Components (IT View)
• eBusiness Gateways
• Value Added Networks

• Traditional Electronic Data Interchange (EDI) via a VAN
  • Traditional EDI UML Activity Diagram Example
  
  
• Client (PC/Mac) EDI application with a VAN
  • Client EDI UML Activity Diagram Example
  
  
• Integrated B2B via the Internet - Point-to-Point (no VAN or Hub)
  • Standards Agnostic (Generic B2B)
    • Standards Agnostic UML Activity Diagram Example
  • EDIINT - Legacy EDI (ASC X12 and EDIFACT) over the Internet
    • EDIINT UML Activity Diagram Example
    • EDIFICE White Paper: Internet EDI Implementation Guideline
  • RosettaNet XML using RNIF
    • RosettaNet XML Inventory Example
  • OAGIS XML
  • Other XML
  
  
• Integrated B2B via 3rd Party (Modern VANs/Hubs)
  
  • Standards Agnostic" (Generic B2B)
    • Standards Agnostic UML Activity Diagram Example
  • Legacy EDI formats - ASC X12 and EDIFACT
  • RosettaNet XML
  • OAGIS XML
  • Other XML
  
  
• Web Applications
  • Buyer's Web Application (using Web Forms) - with or without back-end integration on seller side
  • Buyer manages own web application in its own extranet, buyer's data is mastered in back-end application, back-end application is slave
    • UML Activity Diagram Example
  • Buyer manages own web application in its own extranet, buyer's data is mastered in web application, back-end is slave
  • Third-party web application used, with buyer-specific forms/templates, buyer's data is mastered in back-end application, back-end application is slave
  • Third-party web application used, with buyer-specific forms/templates, buyer's data is mastered in web application, back-end is slave
  • Seller's Web Application (using Web Forms), with or without back-end integration on buyer side
  • Seller manages own web application in its own extranet, seller's data is mastered in back-end, web application is slave
    • Standards Agnostic UML Activity Diagram Example
  • Seller manages own web application in its own extranet, seller's data is mastered in web application, back-end is slave
  • Third-party web application used, with seller-specific forms/templates, seller's data is mastered in back-end application, back-end application is slave
  • Third-party web application used, with seller-specific forms/templates, seller's data is mastered in web application, back-end is slave
  
  Emerging Technologies

  These technologies are emerging and/or may be variations on other technologies; models for some of these technologies are still being piloted. EIDX will be adding documentation and models for these technologies as they become better understood.

• Collaborative (Shared) Applications
  • Trading Communities - Exchanges, Hubs, etc.
  • Collaborative (shared) web application, with or without back-end integration
  
  
• Web Services
  
• eCommerce Technology Standards - Internet Commerce Model