Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Magento implementation - case study

170,150

Published on

Case study of Magento implementation + Microsoft BizTalk. Complex case study.

Case study of Magento implementation + Microsoft BizTalk. Complex case study.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
170,150
On Slideshare
0
From Embeds
0
Number of Embeds
53
Actions
Shares
0
Downloads
23
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Case Study Magento Implementation
  • 2. TIM SA •  TIM SA is the biggest Polish distributor of techelectro materials. •  The company offers ca. 9 000 products on demand. •  The company has 25 years of experience on the market. •  It employs 300 people in its 30 divisions in Poland. •  Logistics Center, which ensures smooth delivery flow – directly to the customers, is localized in Siechnice (near Wroclaw). •  Central Magazine is fully automated. Special assembly lines are designed to cut and package cables and electric equipment.
  • 3. New Sales Channel The multichannel character of sale is crucial for us – says Krzysztof Folta, CEO in TIM SA. European eCommerce market in 2011 constituted ca. 8% of the total retailcommerce value. The highest levels were noted in Great Britain and Germany (ca. 9% and 12%). In Poland, it was 3%, in Italy - 1%. So there is a large potential and in case it develops, I hope that TIM could have a noticeable share in this growth – adds Krzysztof Folta. •  Integration of the project with the company’s logistic systems •  Creating a self-service platform as a new sales channel •  Optimization of the new channel in order to meet the demands of small companies from B2B sector, as well as the expectations of B2C sector customers
  • 4. Realization Requirement analysis and analysis of business needs Designing interaction • designing • research • optimization Technical analysis and establishing integration Graphic design Implementation Tests and start Measurement and optimization
  • 5. Interactive Prototypes •  Interactive prototypes enable the demonstration of how the applications will work. •  Designer’s ideas are verified against expectations of a given client. •  Conceptual work on models enables cheap and fast verification of the ideas. •  A number of changes during the successive phases of a project gradually diminishes.
  • 6. User Tests •  We conducted tests to see how the potential client operated an interactive prototype. •  Tests were made in the client’s headquarters. •  We examined people differing in the level of computer/Internet knowledge, coming from a couple of regions of Poland. •  During the tests users were performing tasks based on defined scenarios and using interactive prototypes. •  Those tests showed us what range of problems and what kind of interactions real people had with our site. •  One of the scenarios/tasks: 1.  Task Task for electric shops and warehouses Imagine that you need 345 m of electric cable for sale. Try to buy it on the page.   Task for traffic management Imagine that you need 345 m of electric cable to supply a building. Try to buy it on the page.  
  • 7. Calculator Optimization The first version received from the client After first simplifications Optimizations after usability examinations
  • 8. Integration Microsoft BizTalk Server
  • 9. Microsoft BizTalk Server •  The application communicates with the warehouse system thanks to the data bus of BizTalk Server. •  It enables an online access to the warehouse stock.
  • 10. Integration •  Elaboration of project integration •  Prepared in cooperation with IT department, contains the detailed description of mechanisms of the synchronization, security systems and data formats. •  Two-way data exchange Warehouse stock, product features, orders. •  Early start and tests Testing the mechanism at an early stage of implementation allows for capture and removal of all the mistakes in order to make sure that they will not influence the functioning of an application.
  • 11. Graphics Graphic Design
  • 12. Graphic Design •  Graphic design was created based on the delivered visual identification and according to the arrangement of the elements of interactive prototypes. •  One consistent graphic line was developed. •  After look&feel approval, graphic plans were prepared for the next subpages. •  Graphic work took 1 month.
  • 13. Implementation Magento
  • 14. Magento •  Magento is one of the most popular eCommerce platforms. •  Magento has 3 versions: –  Magento Community (with open source licence); Magento’s administrator panel –  Magento Professional; –  Magento Enterprise. •  The commercial versions of Magento are characterized by producer guarantee and the compliance with corporate standards of security and data exchange. Elastic choice of the product features, which is essential for the customer
  • 15. Advantages and Disadvantages of Magento •  Configuration-over-conventions – highly complicated configuration, because of a long XML file (with a compiler of XML to PHP file type), lack of cohesive nomenclature •  Very elastic but complicated code – steep learning curve for new developers •  „Slow acting” – because of multiple classes and PHP files; however, it is possible to optimize it by well-managed hosting and configuration of the server APC, Memcached etc. •  Expanded EAV data model and a high degree of the standarization of the database – elastic and easy to manage, but relatively slow (views, management on the code level)
  • 16. Quality of the Implemetation •  All changes in the application are under version control (SVN), new versions are created in branches, stable version is always available. •  Separate development, test and production environments are kept. •  Changes are implemented only through a ticket system. •  Transaction and automatic deployment on production servers is matched with the possibility to remove the changes. •  Automatic tests (check-ups, http, functional) are conducted after each deployment. Development Testing Production
  • 17. Implementation Start and Tests
  • 18. To Provide the Quality •  Designing according to the User-Centered Design •  The internal quality control on each level of the project – checklists and tests •  System management of requirements, changes and system applications •  All service applications and project establishments are made within the system. •  A client has online access to all applications. •  We use Redmine task management system.
  • 19. Contact http://divanteltd.com

×