Academia.edu no longer supports Internet Explorer.

To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.

Log In
Sign Up

Figure from:An XML implementation process model for enterprise applications

See full PDF downloadDownload figure

Fig. 3. The implementation process. 3.2. Initial planning first, most common ones among enterprise applica- tions second, and the remaining ones used by the enterprise applications last. The rationale is to follow the most adopted classes and names as much as possible, which will ensure the least conflicts among different inter-/intra-organizational applications. — Figure 3 The implementation process. 3.2. Initial planning first, most common ones among enterprise applica- tions second, and the remaining ones used by the enterprise applications last. The rationale is to follow the most adopted classes and names as much as possible, which will ensure the least conflicts among different inter-/intra-organizational applications.

Related Figures (10)

Fig. 1. RosettaNet clusters, segments, and PIPs.

Fig. 2. The quote and order entry process by PIPs in segment 3.

Fig. 4. The intra-organizational MES system data exchange process.

Fig. 5. The B2B MES system data exchange process. The system implementation in the XML integration domain refers to the design of DTD specifications and

Fig. 6. The framework of enterprise internal system.

Fig. 7. The framework of B2B system. Y.-H. Tao et al./Computers in Industry 55 (2004) 181-196

The work order data Among the seven steps of the proposed process model, system implementation is the core and the most unique step in the XML integrating process model. In this section a simple example, the work order sent from MIRL-WIP to IBM MQquery, is first presented to demonstrate the complete process in Section 4.1. Then a RosettaNet WIP component is added in Section 4.2, for an easy comparison to the first simple example, and shows how the process may change from the begin- ning due to the large DTD size of the RosettaNet WIP. The XML document can be constructed according to the DTD specification from Section 4.1.3. Table 3 is

Fig. 8. The hierarchical tree.

The element changes in Table 1 Table 4

Table 3 RosettaNet, we used the RosettaNet business dic- tionary version of October 2002 and the PIP version of August 2002 to discuss the design changes through some scenarios as shown below. Since, the step-by-step process is the same as that in Section 4.1 and only the delivery information changes, the following discussion only shows the changed infor- mation specification. steps remain unchanged in this external data exchange scenario.

About
Press
Papers
Topics
We're Hiring!
Help Center

Find new research papers in:
Physics
Chemistry
Biology
Health Sciences
Ecology
Earth Sciences
Cognitive Science
Mathematics
Computer Science

Terms
Privacy
Copyright
Academia ©2025