Pace-Layered

Ecological Architecture
for Digital Business
Dr. June Sung Park
Professor, KAIST
Chairman, SEMAT

Table of
Content

Architected
Model-Based
Service-Oriented
Design

Digital
Business

Pace-Layered
Architecture

Ecological
Architecture

Digital Business

SMACI is driving big changes in every

industry.

Digital
Business

Start with Customer

Connected

Car

Journey Map.

Learn/

Find/

Purchase/

Enroll/

Use/

Manage/

Renew/

Share

Select

Pay

Register

Consume

Maintain

Replace

Identify Use Cases and create Scenarios.

Learn/

Find/

Purchase/

Enroll/

Use/

Manage/

Renew/

Share

Select

Pay

Register

Consume

Maintain

Replace

Situation-aware
Navigation

Connected

Car
Ad hoc
Car Pooling

Traffic Sign
Recognition

Driving Behavior
based Lease

Remote
Telematics

Usage-based
Insurance

Self-Diagnosis

Context-aware
Safety
Car/Parking
Booking
Infotainment

Mobile Toll
Payment

Select enabling Technologies per use

case.

Situation-aware
Navigation

Connected

Car

Ad hoc
Car Pooling

Traffic Sign
Recognition

Driving Behavior
based Lease

Remote
Telematics

Usage-based
Insurance

Self-Diagnosis

Context-aware
Safety

Car/Parking
Booking

Broadcast/
Streaming
Infotainment
Mobile Toll
Payment

Design, build and orchestrate Ecosystem to realize

use cases.
Enable with APIs and Control with Identity
Auto Supply
Chain APIs
Traffic Mgmt
APIs

Connected

Car

Composite Web &

Mobile Apps

Fleet Tracking
APIs

Partner &
Payment APIs

Onboard Internal
Systems
Standards &
Regulations

APIs & External

Systems

Ecological Architecture

Ecological Architecture shows a system

of

systems, each with its own architecture.

Connected

Car

Participating systems are Orchestrated based on a Process

Model using APIs.

Digital

Govt

Digital business ecosystem requires SOA enterprise applications

that expose their APIs for internal applications,
consume APIs of public SaaS, social media and business partners,
and even sell their APIs to other firms and mobile app developers.

Presentation

Mobile
Apps
Social
Networks
Public
SaaS

Process Orchestration
IAM &
Security
Services

Business Services
(Web Services & REST Service APIs)
Enterprise Service Bus

Partners &
Customers

IoT
Sensors

Enterprise Applications and

SQL/NoSQL Databases
Virtualized Infrastructure

Analytics
Services
Metadata
Services

Not having APIs today is like not having a website in 2000s.

$7bn worth of items is on eBay through APIs.

API has 10 times more traffic than the website.

AWS Web services is currently driving more

network activity than everything Amazon does
through the traditional web sites.

Expedia generates 90% of its revenue through

APIs.

THE
BUSINESS
OF API

Evolve Application
for Digital Business.

Architecture Reference Model

Support Mobile in your architecture.

Adopt Cloud in your architecture.

SaaS

PaaS / IaaS

Incorporate Event and Context Discovery in your

architecture.
IoT Endpoint

Device

Device

Sensor

Sensor

IoT Gateway

IoT Platform

Post Event

Pub/Sub
Exchange
Subscribe to Topic

Event
Queues
Publish Event

SaaS
Context
Broker

PaaS / IaaS

Pace-Layered Architecture

IT Paradigm shifts every decade.

We need a repeatable, easy way to exploit and adapt to

emerging IT for business innovation and sustainability.

Business-IT
Alignment

We do have systematic methods for business

transformation design and business-IT

alignment.
They are EA,

BA, BPM, SOA, MDMall

based on software engineering disciplines.

EA, BA, BPM, SOA, MDM, SE, all of them pursue Sharing and

Reuse of Layered, Decomposed, Standardized

artifacts including glossary, models, and modularized executables
with interfaces.
New applications exploring and exploiting emerging IT can be built
fast if reusable core functionalities and data are readily available.

Reuse

Pace-Layered Architecture when applied to IT means

building Digital Foundation for an enterprise that contains
and provides non-variable functionalities and data through virtualized
faade layers, so that new applications can be developed fast through
its reuse.

Pace-Layered Architecture
Legacy Silos

Explorative Apps

Desktop UI
Legacy Backend
Logic &
Control
Flow
Data Access

Mobile UI
Process and Analytics
Orchestration
Business Services
New Applications Backend
Metadata Services

SQL Database

NoSQL Data Store

Architected Model-Based Service-Oriented Design

AMB SOD can be carried out using best practices and standard
notation for software engineering including BPM using BPMN 2.0,
SOMA, and OOAD and MDM using UML 2.0.
Explorative Apps

AMB
SOD

Mobile UI

UX

Process and Analytics

Orchestration

BPM

Business Services

SOA

New Applications
Backend

OOAD

Metadata Services

MDM

NoSQL Data Store

Key to success of digital business applications (or any business

application) is first to produce a blueprint for future EA, and then
generate a complete, detailed requirement specification using
competent Business

BA & BA

Analysts.
Business Architect

Business Analyst

Goal

Enterprise Success

Project Success

Role

Update EA

Generate SRS in full detail

Competency

Relationship

Domain knowledge
IT trends and emerging technologies
Process & Information analysis and design
Software engineering (including modeling languages,
methods and tools)
Project management
Enterprise success is achieved through a series of
project successes.

Use Case
Model

Process Model

Business
Analysis

I/O Info

UX Model

Process
Actor

Use Case
Actor

Persona

Process
Activity

Use Case

User Story

Process
Flow

User Journey
Map

Service Model
Information Model

Glossary

Data
Model

Service

Use Case
Scenario

User Concept
Map

Use an Integrated

Modeling Tool after mastering BA

Methodologies.

ModelBased
Devt

UX Journey Map

Process Model

Service Spec

Database Design

DDL Generation

User Concept Map

Class Diagram
Use Case

UI Wireframe

Code Generation

Use Case
Scenario

CRC

Service Interface
Diagram

Sequence Diagram

Its different to create an architecture than to apply

best known architecture styles and patterns.

Conclusion

Business architects should work closely with

software and technical architects to create them, with
business analysts leading their realization.
Because the architecting must start with business

use cases and scenarios to exploit emerging

technologies.

Its different to architect an ecology of applications

than an application.

Conclusion

We need to set up a new

architecture
competency center where mobile, cloud, big
data and IoT architects collaborate on every digital
business initiatives.

Companies need fast development of disruptive applications

to stay competitive.
The development should be sped up by utilizing a

reusable digital foundation.

Conclusion

Bimodal architecting is required, paying off

technical debt (i.e., modernizing legacy applications), and at
the same time exploring new opportunities.

SOA provides a common approach to bimodal architecting.

Business architects and business analysts

are needed to identify and specify SOA services.

Model-Based, Service-Oriented SaaS

: Business Analyst, Software Product Manager, Software Requirement Engineer, SW Developer

1~3

BPMN

24

KOSTA

4~6

DB, DW Big Data

24

KOSTA

SOA

KOSTA

SW

16

KOSTA

SW SaaS

24

KOSTA

7
8~9
10~12

: SW(KOSTA) | 070-7090-5001 | sjjung@kosta.or.kr | http://www.kosta.or.kr

june.park@kaist.ac.kr

https://www.facebook.com/JP.Institute.of.Software/

THANK YOU