Organizations with many information systems should define a business process integration strategy that includes (Choose 2)

A business process integration strategy must be comprehensive, addressing both the technical and business aspects of connecting disparate systems. It must encompass the full range of applications (C), including modern commercial-off-the-shelf (COTS), custom-built, and older legacy systems that are critical to operations. Furthermore, the strategy must be driven by and aligned with the needs of its key stakeholders (B), including sponsors who provide resources, customers who receive the value, and end users who interact with the integrated processes daily.

A. ISO 9000 and ISO 9001 are standards for quality management systems; they are not an integration strategy itself, though they may influence process design.
D. Dublin Core and XML are a specific metadata standard and a data format, respectively. They are tactical implementation details or tools, not the core components of a high-level strategy.

1. Linthicum, D. S. (2003). Next Generation Application Integration: From Simple Information to Web Services. Addison-Wesley Professional. Chapter 2, "The Application Integration Strategy," emphasizes the need to account for legacy and new applications and to align the strategy with business drivers and stakeholders.

2. Hohpe, G., & Woolf, B. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley. The introduction (pp. 1-15) discusses the core problem of integrating diverse applications, including custom and packaged (commercial) systems, to meet business needs.

3. Stanford University, IT 101 - Enterprise Systems. Course materials often describe enterprise systems strategy as needing to consider the portfolio of applications (legacy, custom, COTS) and the alignment with business stakeholders to ensure project success and ROI.