1 / 15

e-Commerce Software

Learn about e-commerce software, architectures, presentation vs. programming, tips, crucial factors, missing elements, and core solution requirements in this detailed guide.

hogand
Download Presentation

e-Commerce Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. e-Commerce Software

  2. e-Commerce Architecture -- multi-tier software architectures • 3-tier architecture: • tier 1: webserver • tier 2: middleware • tier 3: database server • 2-tier architecture: • tier 1: webserver + middleware (servlets) • tier 2: database server • 1-tier architecture: • all rolled into one.

  3. e-Commerce Software Engineering: Presentation vs. Programming • The Presentation vs. Programming problem: • Consider this scenario: • Webpage Designer creates webpage in fancy tool. • Designer hands it over to Programmer. • Programmer inserts CGI (servlet) URLs. • Programmer write CGI code to produce some part of the page. • Designer re-designs the page. • Programmer must re-code URLs, and perhaps CGI. • Programmer and Designer drive each other crazy. • The real problem: how much of page should be program-generated vs. hand-designed?

  4. e-Commerce Software Engineering: two approaches • Program-generated approach: • Advantages: • Flexible up-to-date content, based on database. • Programming is independent. • Easy to maintain consistency with other CGI programs. • High functionality. • Disadvantages: • Difficult to change page appearance (must re-compile). • Difficult to write page appearance code, e.g., out.println ("<table> <tr> <td> <b> blah blah </b> ..."); • Presentation approach: just the reverse.

  5. e-Commerce Software Engineering: one approach • One approach to software engineering: • Designer creates template HTML, specifying which parts can be changed by Designer, independent of programming. • Designer and Programmer agree on program-generated part of page. • Programmer and Designer list events on "submit" and agree on desired program-generated output. • Programmer and Designer get out of each other's hair. • Programmer creates event chart. • Programmer programs, Designer designs. • Programmer and Designer test results, and argue.

  6. e-Commerce Software Engineering: some tips • Create a URL naming convention. • Create an event-naming convention. • Agree on template design to be used across all (or most) pages.

  7. What is e-commerce Software? • Front-end • For Visitors and Customers • Web-based by definition • Backend • For enterprise business managers • Merchandisers, Account Mangers, Customer Support, etc. • Middleware • To interface with existing systems • Customer, Inventory, Credit, Payment and Order Processing systems

  8. e-Commerce Front-end • Web Application Server • Functionality • Personalization and Profiling • Complex, Dynamic Content Presentation • Process Support • Shopping Process • Buying Process

  9. e-Commerce Backend • Content Management • Merchandizing • Catalog management • Price and on-line collateral management • Process Support • Customer Support • Anomaly management • Payment or Order processing hiccups

  10. e-Commerce Middleware • Payment Processing • Customer specific credit, purchase orders, etc. • Electronic payment including EDI and credit cards • Order Processing • Interface to proprietary, custom enterprise systems • e-enabled systems of large warehouses • e-Services that provide Order Distribution • Inventory Management • Soft and hard reserve functionality • Direct access to specific inventory

  11. The critical success factors • Backend System Management Functionality • Support for workflow and process management • Appropriate use of technology for process support • Access control in content management • Business rules in anomaly management • On-line collateral Management • Images, Audio, or Video; for virtual examination • Structured; for comparison shopping

  12. What’s missing? • Community • Polls, Message Boards, Chats, etc. • Services • Fee email, Consumer news and information, etc. • Marketing Campaign Management • Referrals, Affiliates, Banner ads, Emails, etc. • Hot features of the day • ‘Amazon innovations’ • Mobile commerce • Shopping robots

  13. What about services? • Shopping Portals • Process Re-engineering • e-Services • Branding • On-line collateral development and management • Search engine placement optimization • Efficiency improvements in web delivery

  14. Core Solution Requirements • Database • Oracle • Microsoft SQL Server • Application Servers • With integrated or separate web server • General purposes AppServers • BEA’s WebLogic, IBM’s WebSphere, Microsoft’s ASP • Specific AppServers • BroadVision, ART Technology Group, Oracle

  15. Important Technologies • Everything from the two 400 lbs gorillas • Oracle • Microsoft • DHTML • Microsoft won the browser wars in e-business • XML • Microsoft’s and IBM’s support for SOAP is promising • webMethods is proving the value in inter-application communications • Java • Server side – J2EE, JavaBeans, JSP

More Related