1. 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

2. (c) 1999 by Klaus-Dieter Naujok. All right reserved. IT Progression

3. (c) 1999 by Klaus-Dieter Naujok. All right reserved. OTHER BUSINESSES FORTUNE 1000 95% 5% Using EDI EDI Capable 2% 98% Is There a Problem? Did EDI reach critical mass after 20+ years?

4. (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.

5. (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)

6. (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

7. (c) 1999 by Klaus-Dieter Naujok. All right reserved. Techniques Business & Information Modeling + + Open-edi Reference Model Distributed Object Technology =

8. (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

9. (c) 1999 by Klaus-Dieter Naujok. All right reserved. physical/ logical object modelphysical/ model virtual class library virtual application(s)application(s) current-EDI new-EDI OOAJava Messages ICSDEF OLE CORBA RMI segments dataobjects objects in-house application data in-house shareddatabases distributeddatabases technologybuffertechnologybuffer Implementations using different transport technologies

10. (c) 1999 by Klaus-Dieter Naujok. All right reserved. OO-edi and XML/EDI

11. (c) 1999 by Klaus-Dieter Naujok. All right reserved.

12. 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

13. (c) 1999 by Klaus-Dieter Naujok. All right reserved. Simplification and Harmonisation 3.Implementation & Experience 2.Simplified Design 1.Process Review

14. (c) 1999 by Klaus-Dieter Naujok. All right reserved. Development Life Cycle

15. (c) 1999 by Klaus-Dieter Naujok. All right reserved. Unified Process

16. (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

17. (c) 1999 by Klaus-Dieter Naujok. All right reserved. XML Recommendation (overall view)

18. (c) 1999 by Klaus-Dieter Naujok. All right reserved.

20. 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.

21. (c) 1999 by Klaus-Dieter Naujok. All right reserved. The next 12 months

22. (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)

23. (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)

24. (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

25. (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)

26. (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)

27. (c) 1999 by Klaus-Dieter Naujok. All right reserved. THANK YOU!

28. (c) 1999 by Klaus-Dieter Naujok. All right reserved. Questions & Comments

29. Contact Info E-mail: klaus@templar.net TMWG Web Site: www.harbinger.com/resource/klaus/tmwg