Aligning Business and System
Functionality
Colette Rolland
Université Paris1 Panthéon Sorbonne
http://crinfo.univ-paris1.fr
Outline
 The Conceptual Mismatch
 The MAP representation system
 The matching Process
 Conclusion
The Conceptual Mismatch
Avoiding the « conceptual
mistmatch » (Arsajanasi01)
Organisation
Purpose
System Product
Functionality
Mitigating the Mismatch
Business model
ERP Requirements
High level expression
Goal - strategy driven
High level expression
Goal - strategy driven
Global
Global
Abstracting
ERP Functionality
Descriptions
Low level description
Function driven
Local
A Requirements Driven
matching
ERP customisation process
Abstraction
Step
ERP
System
ERP
Iteration
Matching
Reqts
Matching
Step
Organisation
Reqts
Iteration
Reqts
Modelling with Map
Map as a set of interconnected
sections <Ii, Ij, Sij> with
A map is a process model in which
is featuredand multipath
a multithread
a non-deterministic ordering of intentions
and strategies
topology
sij2
Ii
si
sij1
sk
Ij
sji
sjk
ski
Start
Intention
a goal to be achieved
Stop
Ik
ss
Strategy
a mean or a manner to achieve
an intention
Section
a triplet <Intention Ii, Intention
Ij, Strategy Sij> that constitutes
the basic block of a map
Modelling with Map
The SAP Material Management map
Inventory
balance
strategy
Start
By planning
By
Reminder
Manually
Purchase
Material
Bill for
expenses
strategy
Quality
inspection
strategy
Reservation
strategy
Monitor
Stock
Valuation
strategy
Out-In
strategy
In-In strategy
Financial
control
strategy
Stop
SAP-MM map:
Business view / System view
By reorder point
planning
C2
Start
C1
Manually
C4
Purchase
material
By reminder
By forecast
based
planning
C3
C6
By billReference
for
Periodic
expenses
Sampling
C2
strategy
Component Name Continuous
Purchase Material
on reorder
By based
inventory
C7points
By C11
balance
Component
Interface
reservation
strategy
strategy<(Start, Purchase material,
C8 Byby reorder
Manage
course
Monitorpoint
stockplanning)>
valuation
registration
C5
Component strategy
Body
C9
By ‘out-in’ strategy C10
By quality
Automatically
generate purchase
By -‘in-in’
inspection
requisition order
when the stock
strategy
of a given material attains the
reorder point
-Transform
C12
By purchase requisition
into financial
purchase order
Stop
control
SAP-MM map:
Business view / System view
By reorder point
planning
Start
C6
By bill for
Periodic
Reference
expenses
Sampling
C1
C2
C1
strategy
C3
Component
Name Continuous
By
forecast
Manually
By inventory
based
Purchase Material
manually
C7
By C11
planning
Componentbalance
Interface
reservation
strategy
strategy<(Start, Purchase material,
Purchase
C8 Bymanually)>
C4
Manage
course
Monitor stock
material
valuation
registration
Component Body
C5
strategy
C9
By reminder
- Collect information about
By ‘out-in’ strategy C10
By quality
material, vendor,
price…
By ‘in-in’
- Manually inspection
define a purchase
strategy
requisition order
- Check information
C12
By
correctness
financial
- Create
a purchase order
Stop
control
Map Meta Model and Formal
Definition
Map
Path
Refined by
OR
source
XOR
Section
Link
target
sequence
Target
Intention
Source
Intention
Strategy
Start
Intention
Stop
Modelling with Map
Purchase
material
Map refinement
C5
Monitor stock
By ‘out-in’ strategy
Start
Rejection strategy
ReconReconciliation
C5.4
ciliation
of under/over
Okay
of unit
Stop
delivery
C5.2
strategy
difference
Reconciliati
C5.0
C5.7
C5.1
on by
Completeness
C5.5
Accept
PO
strategy
Out-in direct
delivery
recovery
consumption strategy
Enter goods
In stock
Out-in storage C5.6
based strategy
C5.3
Modelling with Map
Refined map: Business / System views
Rejection strategy Reference
Start
Okay
strategy
C5.3
Reconciliation
Component Name
of under/over
C5.4
delivery Accepting delivery
Stop
Component Interface
C5.0
C5.7 by okay
<(Start, Accept delivery,
Completeness
strategy)>
Accept
strategy
Component
Body
C5.5
delivery
Out-in direct
consumption
strategy check the
- Automatically
Enter goods
compliance of the delivered
C5.6
In stock
goods
with
the
purchase
order
Out-in storage
-Generate goods receipts
based strategy
Reconciliation
of unit
difference
C5.1
C5.3
Reconciliation by
C5.2
PO recovery
The Matching Process
The Matchmaking Process Modeled as a Map
Start
Abstraction
ERP driven
Construct As-Wished driven
As-Is,
As-Is driven
As-Wished
ERP maps
Feed-back
Construct
Matched
Map
As-Wished
driven
verification
Stop
Applying the Matching
Process
ERP customisation process
Aligning business requirements
with ERP functionality at SNCF
Economic
performance
Customer
Satisfaction
Business
Process
Supply Chain
Manufacturing
Aligning
Distribution
eCenter
Financials
Workforce
Analytics
eProcurement
Resources
Optimization
Finances
eStore
HRMS
EPM
CRM
The Matching Process
Introducing similarity measures
As-Wished
Map
Map
Map
To-Be
As-Is
Similarities
Analysis
Map
Map
Map
Map
Map
Map
Might-Be
Map
Matched
Map
Map
The Matching Process
Similarity Typology: different types of similarities between 2 maps
Intention
Strategy
Similarity
Section
Map
Intrinsic
Synonymy
Hyperonymy/
Hyponymy
Dice / Jaccard / Cosine
S Dm ( A, B) 
A
Relational
Compositional
Sim(A,B)= 1 if A and B are identical or synonyms
1- if A is hyponym of B
 if A is hyperonym of B
0 else
MAX Sim ( Mots A , MotsB )
  ]0,1[
B
Modified Coefficients
2 
Structural
Mots A   MotsB 
Applying the Matching
Process
Global deployment of IS

Uniform installation of an information system
to support financial activities at DIAC
As-Wished
BERCI
As-Is
SIRCI
Matches
Covers
FUSE
Might-Be
LOGEsp
Reuses
The Matching Process
Introducing Gaps
As-Wished
Map
To-Be
As-Is
Gaps
Gaps
Map
Analysis
Matched
Map
Map
Might-Be
The Matching Process
Gap Typology
Gap Category
Naming
Gap types
Rename
strategy
Rename intention( verb,
Give/
target, parameter)
Remove intention (parameter)
Modify intention( verb, target, parameter)
On Element
Give/Remove/Modify section (pre, post condition,
business rule)
Retype intention into strategy
Add/remove intention, strategy, section
Structural
Change section (source, target)
Merge/Split, intention, strategy, section
The Matching Process
Introducing Gaps

Top down approach : from business
gaps to software gaps
Intentional
view
LOGESP
Gaps

Intentional
view
FUSE
Maps
Intentional
Operational
Operational
view
LOGESP
Gaps

Operational
view
FUSE
Conceptual
OO specs
Conclusion
 Map provides a representation of the functionality in an
easy to understand language
 Map provides a basis for expressing two combined
view points about SF and BM
 Map helps in customising the ERP offer in high level terms
 Multiply experiences & validate approach
 Develop a methodological support tool