Jump to content

Business-oriented architecture

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 68.84.46.40 (talk) at 03:44, 10 April 2013 (Business models). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Business Oriented Architecture is the combination of business process management (BPM), interoperable applications and functions, service-oriented architecture (SOA), and high performance network-based distributed computing.[1][2][3][4][5] It exposes, connects, and leverages enterprise assets.[1][6][7][8]

Business models

BOA is an Enterprise Architecture approach that focuses on the designing business models that are aligned to an organization's strategy.

The current theory of BOA allows a company to design and integrate critical business architecture components, such as capabilities, processes, customers, employees, channels, and products with IT application, data, and technology architectures.

Strategic management

BOA is driven by business goals, business objectives, customer expectations, and definitions of business challenges.[7][9] BOA systems let clients “design, deploy, and operate entire business workflows or operating models” by integrating several technologies and functions.[4][5][9]

Management

BOA is focused on managing and integrating critical business processes. It includes:

  • objectives & strategy
  • assessment
  • solution modeling
  • solution analysis
  • implementation
  • analysis and optimization[6][9]

When considered as a mix of multiple disciplines--including BPM, BI, and SOA--business oriented architecture involves the IT-facing components of SOA (directory services, data services, application services, security services, partner services), the business-facing, process-improvement components of BPM (business event monitoring, human activity management, process choreography, simulation, and optimization), and analytical disciplines (BI, predictive, and rules) for end-to-end application and operating models.[2][5][10]

Benefits

  • Successful BOA leads to faster, cheaper, and more effective process improvement, application development and deployment, and increased integration of the enterprise.[1][9][11]
  • New BOA structures integrate legacy applications and assets in a single interoperable framework for increased leverage, reuse, and longevity of assets.[5][10]
  • Unified Interoperability models integrate assets and solutions across a network for the creation of virtualized operating models and solutions.[5][10]

References

  1. ^ a b c Gilbert, Phil. "A Business Oriented Architecture Combining BPM and SOA for Competitive Advantage". BPTrends. Retrieved 25 March 2013.
  2. ^ a b "New TABB Research on Data Agility Highlights the Pneuron Platform as a New Innovation in Financial Services Competitiveness and Transparency". EON. Retrieved 25 March 2013.
  3. ^ Moe, John. "Business Oriented Architecture and SOA". ModernAnalyst.com. Retrieved 25 March 2013.
  4. ^ a b Moss, Simon. "Pneuron: A Business Orientated Architecture and ETL". Pneuron. Retrieved 25 March 2013.
  5. ^ a b c d e Moran, Andrew. "Industry making the transition to Business Oriented Architecture". Digital Journal. Retrieved 25 March 2013.
  6. ^ a b "Business Oriented Architecture". Sath. Retrieved 25 March 2013.
  7. ^ a b Speer, Pat. "Is BOA the New SOA?". Information Management. Retrieved 25 March 2013.
  8. ^ Bordogna, Raymond. "Business-Oriented Enterprise Architecture". LiquidHub. Retrieved 25 March 2013.
  9. ^ a b c d Cite error: The named reference TABB was invoked but never defined (see the help page).
  10. ^ a b c Cite error: The named reference TE was invoked but never defined (see the help page).
  11. ^ "TABB Forum: Will Technology Kill the Banking Business? (video)". SproutVideo.com. Retrieved 25 March 2013.

See Also