Towards the new Millennium! Introduction to the work of the Techniques and Methodologies Working Group UN/EDIFACT Working Group Meeting Atlanta, 24 March 1999 By Klaus-Dieter Naujok UN/CEFACT/TMWG Chair
Dec 26, 2015
Towards the new Millennium!
Introduction to the work of the
Techniques and Methodologies Working Group
UN/EDIFACT Working Group Meeting
Atlanta, 24 March 1999
ByKlaus-Dieter Naujok
UN/CEFACT/TMWG Chair
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
OTHER BUSINESSESFORTUNE 1000
95%
5%
Using EDI
EDI Capable
2%
98%
Is There a Problem?
Did EDI reach critical mass after 20+ years?
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Techniques &Methodologies Work Grouping’s Mission
To research and identify techniques and methodologies which could be utilized by UN/CEFACT and its working groups to enhance the process by which its deliverables are produced and integrated.
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Membership
• Full– Austria (1)
– Australia (1)
– Canada (1)
– France (3)
– Japan (1)
– Netherlands (1)
– Norway (1)
– S.W.I.F.T. (1)
– United Kingdom (2)
– United States (3)
• Virtual– Australia (2)
– ESCAP (1)
– France (2)
– Poland (1)
– Switzerland (1)
– United States (2)
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Techniques
• Business & Information Modeling– Unified Modeling Language (UML)
• Distributed Object Technology– Common Object Request Broker (CORBA)– Dynamic Common Object Model (DCOM)– Remote Method Invocation (RMI)– extendable Metadata Interchange (XMI & XML)
• Open-EDI Reference Model
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Techniques
Business & Information Modeling
+
+
Open-edi Reference Model
Distributed Object Technology
=
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
OO-edi requires a paradigm shift
• Shift the focus on EDI standards to the business processes and the business practices behind them
• Decompose EDI business processes to the level of individual tasks that are more generic to the type of business
• Identify activities (i.e., transformations) and object classes that are likely candidates for standardization
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
physical/physical/logical objectlogical object
modelmodel
physical/physical/logical objectlogical object
modelmodelvirtualvirtual
class libraryclass libraryvirtualvirtual
class libraryclass library
application(s)application(s)application(s)application(s)
current-EDIcurrent-EDI new-EDInew-EDI OOAOOA JavaJava
MessagesMessages ICSDEFICSDEF OLE CORBAOLE CORBA RMIRMIsegmentssegments datadata objectsobjects objectsobjects
in-housein-houseapplication dataapplication data
in-housein-houseapplication dataapplication data
sharedshareddatabasesdatabases
distributeddistributeddatabasesdatabases
technologytechnologybufferbuffer
technologytechnologybufferbuffer
Implementations using different transport technologiesImplementations using different transport technologies
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
OO-edi and XML/EDI
O O -ed i
O p en -ed i
XM L /E D I
U M L
X M L
O bje ct s ,e n t it ie s , l in k s ,
pro ce s s e s
B U S IN E S SM O D E L
O bje ct s ,e n t it ie s , l in k s ,
pro ce s s e s
M ap sR e p o s i t o r y
& X M LG l o s s ar y
X M Lfo rm a t te d
o bje ct s
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
O O -edi sub-system
ScenarioM anager
Mapper
RMI
Applet
W eb Brow ser
O O -edi sub-system
ScenarioM anager
RMI
(Legacy)Application
"TheInternet"
e-Form
Com m on BusinessObject C lass
Library
Com m on BusinessObject C lass
Library
Com m on BusinessObject C lass
Library
Varieties of OO-edi Implementation
O O Stand-a lone Application(O ff-the-shelf/Shrink-w rap
solution for SM Es)
O O -edi front-end s im ilar topresent-day ED I translation
softw are
EC so lu tion for verylow vo lum e users
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Methodologies
• Development Life Cycle– Requirements
– Analysis
– Design
– Verification
– Implementation
• Unified Process– Controlled Iterative
– Component Based
– Visual Modeling (UML)
– Configurable Process
– Architecture Centric
– Requirements Management
– Use-Case Driven
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Simplification and Harmonisation
3.Implementation & Experience
2.Simplified Design
1.Process Review
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Development Life Cycle
1.Requirement
AnalysisBPAWG
2.DetailedAnalysis
EWG/ITPWG
3.Design
EWG/ITPWG
4.Verification
BPAWG &EWG/ITPWG
5.Implementation
Providers/Users
6.Maintenance
Requests
Providers/Users
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
Unified Process
• Development is an iterative process
• Manages requirements
• Visual modeling (Analysis & Design)
• Employs component-based architecture
• Verifies product’s quality
• Controls changes to the product
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
XML Recommendation (overall view)
UM L M odelRepos itory
U N / ED IF A C TD ire c t o rie s
(M e s s a g e s )
UN /T D ED
BS R
X M LF orm atted
O bjec ts
X M L/ED ID oc um entEquivalent
X M LS olutions
DTDNames
D TDU N /ED IFA C T
Ta g s
*
1
B o tto m -U p A p p ro a c hCreates X M L equivalent of eac h UN /ED IF ACT m es s ageM apping of exis ting UN /ED IF ACT m es s ages to X M L D T D s
M odel to s upportthe developm ent ofc urrent UN /ED IF ACTm es s ages
P r e p ar at i o n- M aintain T D ED- Correc tions to UN /ED IF ACT D ata Elem ent d irec tory to align w ith T D ED- expand T D ED to bec om e the c entral repos itory
T op-dow n Approac hAuto-generation of X M LD T D s bas ed on UM LClas s and S equenc e d iagram s
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
UM L M odelRepos itory
U N / ED IF A C TD ire c t o rie s
(M e s s a g e s )
UN /T D ED
BS R
X M LF orm atted
O bjec ts
X M L/ED ID oc um entEquivalent
X M LS olutions
DTDNames
D TDU N /ED IFA C T
Ta g s
*
1
B o t to m -U p A p p ro a c hCreates X M L equivalent of eac h UN /ED IF ACT m es s ageM apping of exis ting UN /ED IF ACT m es s ages to X M L D T D s
M odel to s upportthe developm ent ofc urrent UN /ED IF ACTm es s ages
P r e p ar a t i o n- M ain tain T D ED- Correc tions to UN /ED IF ACT D ata Elem ent d irec tory to align w ith T D ED- expand T D ED to bec om e the c entral repos itory
T op-dow n Approac hAuto-generation of X M LD T D s bas ed on UM LClas s and S equenc e d iagram s
Extrem lyS IM P L-ediM es s ages
Bus ines sNeed s
O th e r D o c u m e n tS ta n d a rd s
Referenc e to andc reation ofUN /ED IF ACTS ub-s ets
S im ple D es ign
M es s ageD es ign
S im pleX M LD T D s
D TDS IM A C
Ta g s
P arallel D evelopm entof X M L D T D s equating toS IM P L-edi ED IF ACTs ub-s etsReview as a P ilo t for
D T D UN /ED IF ACT tags
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
UM L M odelRepos itory
U N / ED IF A C TD ire c t o rie s
(M e s s a g e s )
UN /T D ED
BS R
X M LF orm atted
O bjec ts
X M L/ED ID oc um entEquivalen t
X M LS olutions
DTDNames
D TDU N /ED IFA C T
Ta g s
*
1
B o t to m -U p A p p ro a c hCreates X M L equivalent o f eac h UN /ED IF ACT m es s ageM apping of exis ting UN /ED IF ACT m es s ages to X M L D T D s
M odel to s upportthe developm ent ofc urren t UN /ED IF ACTm es s ages
P r e p ar at i o n- M ain tain T D ED- Correc tions to UN /ED IF ACT D ata Elem ent d irec tory to align w ith T D ED- expand T D ED to bec om e the c en tral repos itory
T op-dow n Approac hAuto-generation of X M LD T D s bas ed on UM LClas s and S equenc e d iagram s
Extrem lyS IM P L-ediM es s ages
Bus inessNeed s
O th e r D o c u m e n tS ta n d a rd s
Referenc e to andc reation ofUN /ED IF ACTS ub-s ets
S im ple D es ign
M es s ageD es ign
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
XML Recommendations
Harmonization and simplification work effort must continue to identify the core data.
UN/CEFACT should encourage W3C to develop a simple XML Repository as soon as possible to stop the proliferation of XML tag names and DTDs.
UN/CEFACT should encourage CommerceNet, the XML/EDI group, W3C, ANSI ASC X12C/TG3 and member software companies to adopt standardized tag names and DTDs for XML interchange file formats to help the SME integrate data.
Standard Web form objects need to be developed for UN Layout Key web pages. UN/CEFACT should limit its resources’ use of XML to Web forms and distributed
object messages. UN/CEFACT should NOT recast UN/EDIFACT messages into XML based on
algorithms run against EDI Directories. UN/CEFACT should encourage W3C to accelerate work on the W3C WebBroker
Note and progress it to a W3C Recommendation as soon as possible.
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
The next 12 months
TMWG DeliverablesTMWG DeliverablesOutput docucuments for UN/CEFACT WGsOutput docucuments for UN/CEFACT WGs
3/29/993/29/99
EWGValidation
Team Startup
EWGValidation
Team Startup
2/26/992/26/99
BPARequirementsSpecificationand Templatefor BPAWG
BPARequirementsSpecificationand Templatefor BPAWG
7/23/997/23/99
BPA AnalysisSpecificationsDraft for EWG
BPA AnalysisSpecificationsDraft for EWG
11/12/9911/12/99
Model DesignSpecificationand TemplateDraft for EWG
Model DesignSpecificationand TemplateDraft for EWG
11/15/9911/15/99
CBO SummitReport
CBO SummitReport
9/17/999/17/99
EWG Reviewof BPA
SpecificationsDraft
EWG Reviewof BPA
SpecificationsDraft
2/15/002/15/00
ModelVerification
SpecificationsDraft for
BPAWG/EWG
ModelVerification
SpecificationsDraft for
BPAWG/EWG
3/25/003/25/00
EWG Reviewof Model
VerificationSpecifications
EWG Reviewof Model
VerificationSpecifications
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
TMWG Time Table (Modeling)• February 1999
– Requirement Specification (Draft)
• July 1999
– Requirements Specification (Final)
– Analysis Specification (Draft)
• November 1999
– Analysis Specification (Final)
– Design Specification (Draft)
• February 2000
– Design Specification (Final)
– Verification Specification (Draft)
• July 2000
– Verification Specification (Final)
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
TMWG Time Table (+Review Periods)• February 1999
– Requirement Specification (Draft)
• March-June 1999– BPAWG Review of
Requirement Specification
• July 1999– Requirements Specification
(Final)
– Analysis Specification (Draft)
• August-October 1999– BPAWG/EWG Review of
Analysis Specification
• November 1999– Analysis Specification (Final)
– Design Specification (Draft)
• Dec 99 - January 2000– BPAWG/EWG Review of Design
Specification
• February 2000– Design Specification (Final)
– Verification Specification (Draft)
• March-June 2000– BPAWG/EWG Review of
Verification Specification
• July 2000– Verification Specification (Final)
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
SIMAC Recommendations
• Constraints and Opportunities– The current vertical UN/EDIFACT
organisational structure– Lack of focus on detailed business process
analysis e.g. through business modelling– Lack of an effective global repository of
standardised data entities
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
TMWG Time Table (+SIMPLE-edi)• February 1999
– Requirement Specification (Draft)
• March-June 1999– BPAWG Review of Requirement
Specification
• July 1999– SIMPL-edi review to determine
impact in regard to Specifications
– Requirements Specification (Final)
– Analysis Specification (Draft)
• August-October 1999– BPAWG/EWG Review of
Analysis Specification
• November 1999– Analysis Specification (Final)
– Design Specification (Draft)
• Dec 99 - January 2000– BPAWG/EWG Review of Design
Specification
• February 2000– Design Specification (Final)
– Verification Specification (Draft)
• March-June 2000– BPAWG/EWG Review of
Verification Specification
• July 2000– Verification Specification (Final)
(c) 1999 by Klaus-Dieter Naujok. All right reserved.
TMWG Time Table (+XML)• February 1999
– Requirement Specification (Draft)
• March-June 1999– BPAWG Review of Requirement
Specification
• July 1999– SIMPL-edi review to determine
impact in regard to Specifications
– Requirements Specification (Final)
– Analysis Specification (Draft)
• August-October 1999– BPAWG/EWG Review of Analysis
Specification
• November 1999– Analysis Specification (Final)
– Design Specification (Draft)
– XML Review (based on CSG actions)
• Dec 99 - January 2000– BPAWG/EWG Review of Design
Specification
• February 2000– Design Specification (Final)
– Verification Specification (Draft)
• March-June 2000– BPAWG/EWG Review of Verification
Specification
• July 2000– Verification Specification (Final)