e-comma e-commerce Developer TM 03: Technical development and adaptation

Transcription

1 e-comma E-commerce developer TM 03: Technical development and adaptation

2 E-commerce developer TM 03: Technical development and adaptation Training Contents 1. Component Integration 1. The e-shop Concept and Components 2. System Solutions for Electronic Sales Basic Models 3. Components 4. Systems 2. Testing

3 Sources and further readings E-commerce developer TM 03: Technical development and adaptation CIAPE(2016), En-youth teacher, Howto create an e-business E-Commerce und M-Commerce Vortragender

4 e-comma 1 Component integration

5 The basic idea of the E-shops: phases and users Private person/ company 1.Component Integration 1.1.The e-shop Concept and Components trading intent Provision of information and searching Private person/ company Private person/ company Private person/ company Searching for trade partner Negotiations on prices an conditions Transaction execution Private person/ company Private person/ company 5

6 Phases of e-shop projects: Steps and main tasks Kick-Off-Phase Phase of analyze 1.Component Integration 1.1.The e-shop Concept and Components. Project formulation Project organisation Structure analysis Product selection Process analysis Customer analysis Actual condition demarcation Pilot project Project calculation System selection temporary to-be concept contract System design To-be - condition Duty stapler Integrations requirement System construction Pilotsystem System introduction System (Launch)

7 1.Component Integration 1.1.The e-shop Concept and Components Values of different e-shops components Operator Service Partner Hardware- Infrastructure In-House Server Housing Server Hosting Partner Shop software Individual solution basic solution Partner shop Administration Individual responsibility ASP Partner Content Management Individual responsibility Partner Resource needs high Low Strategic influence high Low

8 1.Component Integration 1.1.The e-shop Concept and Components

9 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models E-commerce Service/Partner Model/ Application service provider (ASP)-model = e-marketplace Operator Model = e-shop

10 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models OPERATOR MODEL The provider operates the system itself. Cost / effort through Purchase and operation of hardware and software interfaces WWS, CRM etc. Updating of article and order data Configuration, programming and implementation E-competence (construction and operation of the e-shop) design user guidance

11 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models Open Source shop systems Magento shopware OXID esales xt:commerce Chargeable shop systems Intershop Commerce Suite plentymarkets amazonwebstore Rakuten CMS Shop Extensions Typo3 Contao WordPress Joomla Drupal

12 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models MAGENTO is an open source CMS software created for e-commerce purposes. Magento provides two distinct platforms: Magento Open Source and Magento Commerce; the latter is available in an onpremises version or as a platform-as-a-service.

13 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models With Magento you can acton all the most important elements of an e-commerce site, from the layout to the product catalogue, to the shopping cart, to the payment and shipping procedures, justto illustrate something

14 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models The functions that differentiate it from other CMS and make it one of the most downloaded for e-commerce are: possibility of comparison between the products inserting reviews on the product cards with multiple images images with the possibility of zooming report display and order management batch of import and export of catalogue account personalization sending mail for the order to several addresses at the same time inclusion of discounts, promotions and special prices possibility of multiple online stores support for multiple currencies support for multiple languages

15 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models Operator model: Advantages and disadvantages Advantages higher data and transaction security better integration options greater independence Disadvantages distraction from the core business higher complexity slow implementation high flexibility high costs and risks

16 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models PARTNER MODEL Seller uses the system of a third party provider, e.g. Amazon Market Place E-shop is of the system fully conducted by the provider Seller maintains product data Transactions are conducted by the partner (often including payments and delivery). Partner gets provision Reasonable solution, if Product data stay the same or change rarely, Only few (own) products are offered Seller is highly dependent on provider

17 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models Advantages Disadvantages Partner model: Advantages and disadvantages distraction from the core business lower complexly and higher mobility lower flexibility high dependence fast implementation lower integration options transparent costs and lower investment risk privacy and compliance

18 1.Component Integration 1.2. System Solutions for Electronic Sales Basic Models Shop-system Market place Demandware epages hybris IBM WebSphere Commerce Intershop Jimdo Magento OXID plentymarkets PrestaShop Rakuten Shopify Shopware xt:commerce Allyouneed Amazon ebay Hitmeister Otto Rakuten Yatego

19 1.Component Integration 1.3. Components The Shop should request development in analyse phase and concretise in form of a system specification Selected elements of the specification concern: Commerce Designing online shop Search Products Shopping basket Cash register Customer registration Order Payment system ERP Marketing Performance Review General quality Content, Community, Customisation

20 1.Component Integration 1.3. Components

21 1.Component Integration 1.3. Components Construction of the category structure Filter navigation: and/or Category hierarchy (7-2-2-Rule, search engines conformity) Product information Clarity, Completeness, Security, Trust Branches specific particularities Cross Selling Information

22 1.Component Integration 1.3. Components Product text Different information needs of visitors Emphasise product advantages Compact, understandable, precise, creative, magical words, trust, up to date Google: Unique Texts, Format and Structure, Keywords Text broker (for example ) Multilingual texts Product pictures Industry / target group specific relevance Images influence the quality assessment, give security Sources: Manufacturer / Supplier, Agency / Photographer, own manufactures

23 Themes/Templates (e.g. ) Proprietary Designs Corporate Design-Guide as a basis layout design Wireframes (e.g. ) Right views Start page Category view Product detail view User registration and login Shopping cart and payment process Other views Cooperation with graphic agency / graphic artist Technical implementation of the draft 1.Component Integration 1.3. Components

24 The functions of an e-shop can be divided into Front-End Front-end feature supports direct customer contact and also in form of user interfaces for the customer. 1.Component Integration 1.3. Components Back-End Back-end-function works in the background and serves internal processing of electronic processes in e-shop.

25 1.Component Integration 1.3. Components Front-end functions / Components Back-end functions / Components Customer registration / Customer account Content Management and reaction system Online catalogue Sales support Basket function Customer management Payment system Transaction management Download function Warehouse management After sales function Statistic function

26 Web browser 1.Component Integration 1.4. Systems Presentation HTTP( -S) Application Web server SQL Data entertainment Data bank system databases Logical layers architecture Softwarelayers architecture Hardware infrastructure (Example)

27 Presentation application User interface Dialogue control business process control application range objects Webbrowser Web browser Web Application Server Webserver Application Server 1.Component Integration 1.4. Systems logical data access Data entertainment physical data access Data bank abstraction Data bank system logical layer structure Softwarelayered architecture Hardware infrastructure (Examples)

28 1.Component Integration 1.4. Systems

29 e-comma 2 Testing

30 2. Testing E-commerce application/sites are web applications or mobile application too. So, they undergo all the typical test types: Functional Testing Usability Testing Security Testing Performance Testing Database Testing Mobile Application Testing A/B testing

31 2. Testing Home page / Hero image The following are a few things to test: Is it going to auto scroll? If yes, at what interval will the image be refreshed? When the user hovers over it, is it still going to scroll to the next one? Can itbe hoveredon? Can itbe clicked on? If yes, is it taking you to the right page and right deal? Is it loading along with the rest of the page or loads last in comparison to the other elements on the page? Can the rest of the content be viewed? Does it render the same way in different browsers and different screen resolutions?

32 2. Testing Search The following are a few things to test: Search based on Product name, brand name or something more broadly, the category. Search Results have to be relevant Different sort options have to be available, based on Brand, Price, and Reviews/ratings etc. Howmany results to display per page? For multi-page results, are there options to navigate to them? Also, search happens in many places. Please take the search drilling down into multiple levels into consideration when validating this functionality.

33 2. Testing Product The following are a few things to test: Image or images of the product. Price of the product. Product specifications. Reviews. Check out options. Delivery options. Shipping information. In stock/out of stock. Multiple colour or variations options. Breadcrumb navigation for the categories (highlighted in red below). If navigation such as that is displayed, make sure every element of it is functional.

34 Shopping basket 2. Testing The following is to be tested: Add items to the cart and continue shopping. If the user adds the same item to the cart while continuing to shop, the item count in the shopping cart should get incremented. All items and their totals should be displayed in the cart. Taxes as per locationshould be applied. A user can add more items to the cart - total should reflect the same. Update the contents added to the cart - total should reflect that too. Remove items fromthe cart. Proceed to checkout. Calculate Shipping costs with different shipping options. Apply coupons. Don t check out, close the site and come back later. The site should retain the items in the cart.

35 2. Testing Payments The following is to be tested: Check different payment options. If allowing check out as Guest, simply finish the purchase and provide an option to register at the end. Returning customers Login to check out. User sign up. If storing customer Credit card or any other financial information, perform security testing around this to make sure it is secure (PCI compliance is a must). If the user is signed up for a long time, make sure the session is timed out or not. Every site has a different threshold. For some, it is 10 minutes. For some, it might be different. s/Text confirmation with the order number generated

36 2. Testing Featured products/suggested products The best way to test these parts of the application is to test the algorithm based on which these sections are populated.

37 2. Testing After sales The following is to be tested: Change the Order. Cancel the Order. Track the Order. Returns.

38 2. Testing Other tests The following should be tested as well: FAQs. Contact Us page. Login. Customer Service page etc.

39 2. Testing E-Commerce Testing is whether the visitors are converting into paying customers or not. The number of visitors that become customer is called Conversion Rate. It is also important to test whether one feature promotes better conversion as opposed to another. That is why A/B testing and Usability Engineering for E-Commerce sites are gaining prominence.