This is the colloquium version of my master thesis project about enterprise architecture of pluggable e-commerce service platform. In this research, I created an e-commerce platform by integrating various web services using Service Oriented Architecture (SOA) and REST API (Application Programming Interface), run on top of a cloud-based integration platform namely Mulesoft

1. DESIGN AND INSTANTIATION OF
REFERENCE ARCHITECTURE FOR
PLUGGABLE SERVICE PLATFORM
IN E-COMMERCE
MOHAMMAD ANGGASTA PARAMARTHA - S1341243
MASTER INDUSTRIAL ENGINEERING & MANAGEMENT

2. Traditional approach
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
2
INTRODUCTION
BACKGROUND & MOTIVATION
E-
commerce
Platform
Function
1
Function
2
Function
3E-
commerce
Platform
Function
1
Function
2
Function
3
Flexible & Lightweight Platform
- Impact to agility
- Limited options for retailers - Pluggable Platform
- Integration

3.  Needs to integrate diverse applications of
business partners
 Emergence of new technologies (Cloud, SaaS,
Mobile, Social Media)
 Lack of suitable E-commerce platform
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
3
RESEARCH PROBLEMS

4. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
4
RESEARCH QUESTION
MAIN RESEARCH QUESTION
What reference architecture can best serve as
the foundation for a
pluggable e-commerce platform
which supports
seamless integration and coordination
of e-commerce supply chain partners’
application and services?

5. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
5
RESEARCH QUESTION
SUB RESEARCH QUESTIONS
 RQ 1: What is the current e-commerce platform
solutions landscape?
 RQ 2: How is the current integration platform
solutions landscape?
 RQ 3: How to design the reference architecture of
pluggable E-commerce platform which support
seamless integration and coordination?
 RQ 4: How to implement and evaluate the
reference architecture?

6. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
6
RESEARCH METHODOLOGY
 Design Science Research Methodology (DSRM)
(Peffers et. al. , 2007)
RQ1
RQ2
RQ3
RQ4

7.  Common components: compilation of
common e-commerce platform functionalities
 Gaps & issues:
 Webshop-specific
connectors
 Point-to-point
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
7
E-COMMERCE WEB SHOP STATE-OF-THE-ART
KEY FINDINGS

8.  Web Services
 Service Oriented Architecture & SOAP Web Services
 RESTful Services & REST API
 Cloud Computing
 Cloud-based Integration platform
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
8
B2B INTEGRATION TECHNOLOGIES
LATEST DEVELOPMENT

9.  Common components:
 SOA Governance and API Management
 Process management
 Gaps:
 Lack of BPM engine
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
9
CLOUD-BASED INTEGRATION PLATFORM
KEY FINDINGS

10.  Enterprise Architecture
 Architecture Framework : TOGAF
 Architecture Modeling Language : Archimate
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
10
REFERENCE ARCHITECTURE
KEY CONCEPTS

11. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
11
ARCHIMATE

12. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
12
THE COMPLETE REFERENCE ARCHITECTURE

13. 27/9/14 13
ONLINE RETAILER
Common e-commerce
platform functionalities
from the state-of-the-art
analysis

14. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
14
SERVICE PROVIDER

15. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
15
PLATFORM PROVIDER
SOA Governance & API Management Process Management

16. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
16
PLATFORM PROVIDER
 Collaborative Data Management
 Canonical data model
 Schema mapper & matching
 Identity and Access Management

17. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
17
CASE SELECTION
ARCHITECTURE INSTANTIATION AS PROTOTYPE
 Return Registration Process
 Efficient return handling can increase customer
satisfaction and lead to major cost saving
 Not provided in most of e-commerce platform &
ERP (van Hillegersberg et. al. , 2001)
 Not present in existing online retailer process
models

18. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
18
PROTOTYPE DEVELOPMENT
 Model Driven Architecture (MDA)
 Computation Independent Model (CIM)
 Platform Independent Model (PIM)
 Platform Specific Model (PSM)

19. 27/9/14 19
CIM & BUSINESS PROCESS DIAGRAM
RETURN REGISTRATION PROCESS

20. 27/9/14 20
PIM& RETURN HANDLING ARCHITECTURE

21. 27/9/14 21
PSM & MULESOFT INTEGRATION FLOW

22. PROTOTYPE DEMONSTRATION
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
22
 Catelog Front-end Webshop (1)

23. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
23
DESIGN VALIDATION
 System agility aspects (Lankhorst, 2012)
 The ease of making changes to a system: adaptability
 The ease of rapidly deploying changes: manageability
 The ease of minimizing and dealing with effects of
changes: resilience
 The ease of integrating a system with its
environment: interoperability
 The ease of decoupling a system from its
environment: reusability

24. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
24
DESIGN VALIDATION
Replace some of the existing services with new
set of services
Type of services Existing New
Mailing Google Mail Yahoo Mail
Shippping Postmaster Shipcloud

25. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
25
DESIGN VALIDATION
RESULTS
 Only few parameters need to be changed
 ESB architecture design, one endpoint for each
service
 Schema mapping as the key to replace services
 Manual service configuration during design-time
 Deploying changes to Cloudhub takes few minutes
 Hard to define the right granularity

26. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
26
CONCLUSION
CONTRIBUTIONS
 Contributions to theory
 Add to the literatures of e-commerce, integration
platform and enterprise architecture
 Fill the gap in pluggable platform topic research
line
 State-of-the-art analysis
 Contributions to practice
 The architecture as the basis for real products
 Fully functional prototype

27. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
27
CONCLUSION
LIMITATION & FUTURE RESEARCH
Limitations Future Research
Qualitative, subjective
assessment to the platform
design
Try to find suitable metrics for
assessment with external
experts
Simplified use-case Broader & more complex use-
case, or more than one case
Implement security
mechanism
Partial evaluation on some
architecture components
Detailed service classification
with respect to pluggability

28. THANK YOU
DISCUSSION TIME
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
28
 conclusion
 contributions

29. RESERVED SLIDES
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
29
 conclusion
 contributions

30.  Content & Product Information Management
 Website Storefront Management
 Customer Account Management and Customer Service
 Marketing, Promotion and Conversion
 Analytic and Reporting
 Data Repository & Search
 Rich Web and Client Presentation
 Stable Core Web Framework
 Shopping Cart and Payment (Transaction Processing)
 Order Management & Fulfilment System
 Shipping, logistic/distribution, and warehousing
 Back-office Integration
 Social Media Integration
 (Multi) Channel Management
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
30
FEATURES OF E-COMMERCE WEB SHOP
PLATFORM

31. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
31
E-COMMERCE PLATFORM STATE-OF-THE-ART
KEY TAKEAWAYS

32.  Web Services
 Universal Description Discovery and Integration (UDDI):
service discoverability mechanism
 Web Service Description Language (WSDL):
A formal document explaining service contracts, service
interface
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
32
DEVELOPMENT HISTORY OF INTEGRATION
TECHNOLOGIES
WEB SERVICES

33. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
34
DEVELOPMENT HISTORY OF INTEGRATION
TECHNOLOGIES
SOA STACK

34.  SOAP
 REST
27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
35
DEVELOPMENT HISTORY OF INTEGRATION
TECHNOLOGIES
SOAP AND RESTFUL SERVICES COMPARISON

35. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
36
STATE-OF-THE-ART ANALYSIS

36. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
37
STATE-OF-THE-ART OF CLOUD-BASED
SERVICE INTEGRATION PLATFORMS

37. 27/9/14 39
MULESOFT STUDIO MAIN WORKFLOW
Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce

38. 27/9/14 40
APPROVED REQUEST
Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce

39. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
41
APPROVED REQUEST
OBTAIN CUSTOMER DETAILS

40. 27/9/14 42
DATA MAPPER
Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce

41. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
43
GENERATE RMA LABEL

42. 44
POSTMASTER LABEL

43. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
45
APPROVED REQUESTGENERATE RMA (RETURN MERCHANDISE AUTHORIZATION)
LABEL

44. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
46
REJECTED REQUEST
MAIN FLOW

45. Compone
nt
Postmaster Shipcloud
JSON
Payload
{
"to":
{ "company": "Catelog",
"contact": "Mohammad Anggasta”
"line1":”Emmastraat 210",
"city": "Enschede”,
"state": "Null",
"zip_code": "7513BH",
"phone_no": "123456789" },
"package":
{ "weight": 1.5,
"length": 10,
"width": 6,
"height": 8 }
}
"carrier": "Fedex",
"service": "2DAY",
{
"to":
{ "company":"Catelog",
"first_name":"Mohammad",
"last_name":"Anggasta",
"street":"Emmastraat",
"street_no":"210",
"country":"NL",
"city":"Enschede”,
"zip_code":"7513BH" },
"package":
{ "weight":1.5,
"length":20,
"width":20,
"height":20 },
"carrier":"DHL",
"service":"standard",
CHANGES FROM POSTMASTER TO SHIPCLOUD

46. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
48
DESIGN VALIDATION
CHANGES FROM GMAIL TO YAHOO MAIL
Parameters Gmail Yahoo Mail
Host smtp.gmail.com smtp.mail.yahoo.com
Port 25 465
Password
Application-specific password
(two-step authentication)
Original account password

47. 49
SHIPCLOUD LABEL

48. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
50
PROTOTYPE DEVELOPMENT
DISCUSSION
 General Remarks
 Collaborative Services and Process Framework
 Collaborative Data Management
 Service Classification
 Mulesoft flow, Message Structure, and Data
Transformation

49. 27/9/14Design and Instantiation of Reference Architecture of Pluggable
Service Platform in E-Commerce
51
OAUTH
DISCUSSION
 Tokens can get really big
 Your apps/APIs gets more complicated
 Whoever grant these permissions will have a
hard time managing all this.