1 / 33

Pattern-Oriented Architectures for E-business Systems

Pattern-Oriented Architectures for E-business Systems. C0MP 9117 Software Architecture. 24 th August 2004. Haryanto, David (z3139532) Nyo, Yupar (z3103328) Wang, Xiaowen (z3089932). Agenda. Introduction

shea
Download Presentation

Pattern-Oriented Architectures for E-business Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pattern-Oriented Architectures for E-business Systems C0MP 9117 Software Architecture 24th August 2004 Haryanto, David (z3139532) Nyo, Yupar (z3103328) Wang, Xiaowen (z3089932)

  2. Agenda • Introduction • Pattern-Oriented Architecture in e-business domain – the need, challenges and transition. • Existing Patterns (IBM, MVC, etc). • Case Studies (FutureStep Electronics, Retailers’ Mega Exchange, Artimus). • Benefits • Future • Conclusion • References • Q & A

  3. The Beginning of Patterns [Ref 4, 7] • The use of patterns originated in the field of architecture (for buildings, towns design, etc) during late 1970. • Moved into Software Engineering field in the early 1990s as a way to describe solutions to recurring problems encountered in architectural design.

  4. Pattern-Oriented Software Architecture [Ref 4, 8] • Proven and repeatable (reusable) architectures, designs. • Address a recurring problem that arises in specific design situations. • Observed NOT invented. • Document/Capture existing, well-proven design experience and solutions. • Support the construction of software with defined properties. • Identify and specify abstractions. • Help to build and manage complex, heterogeneous software. • Patterns are a means of documenting software architectures. • Properties of POSA.

  5. Challenges/ Problems of e-business applications [Ref 11] • Going beyond traditional enterprise systems • Security • Performance • Availability • A need to integrate with existing legacy applications • Increased Complexity • No room for error • Interpretability • Time Constraint

  6. The Need for Pattern-Oriented Architecture in E-business [Ref 8] These challenges create needs for Pattern-Oriented Architecture in e-business domain, as POSA’s properties could facilitate them. • Recurring problems and similar requirements. • Higher degree of integration. Especially with existing legacy systems for payment, inventory, etc. • Quality and Complexity. • Need for speed. Crucial! If a system is delivered significantly faster, the better it is for the business, increasing competitive edge. • Reuse of patterns can help the workload, reduce the complexity and enhance the quality. It thus fastens the development.

  7. The Need for Pattern-Oriented Architecture in E-business 2 • E-business systems have to hold water from day one.[Ref 8] No room for error with systems that face into the external world. Simply cannot be tolerated. Example : Downtime, Consequence of error for an online mall. • Shortage of skills Growing Area • The need for experiences A need for knowledge base that would help architects and designers with limited skills or experiences. Patterns capture the experts’ knowledge and provide proven solutions. • Changing technology

  8. Implications and Transitions of e-business applications’ designs and architectures [Ref 9]

  9. Pattern-Oriented Architecture and ebusiness • “One of the major reasons that e-business systems fail is due to problems with the underlying technical architecture.” – McGrath, Vice President, UK Services, Princeton Softtech. [Ref 6] • Solution – Reuse the proven architecture, Pattern-Oriented Architecture

  10. Existing Patterns • IBM’s Architecture Patterns for e-business [Ref 8] • MVC (Model View Controller Pattern). [Ref 12] • Perspective Pattern – Integrate middleware with business models. From Princeton Softech, Subsidiary of Computer Horizon Corp. [Ref 6] • Dublo Pattern – To reuse elements of legacy system within multi-tier architectures. From the University of Oldenburg, Germany. [Ref 13] • BizArk – A reusable e-business architecture based on pattern-oriented technology. Encompasses main building blocks like CRM, ERP. [Ref 1] • And many more….

  11. MVC Pattern of e-business application [Ref 9]

  12. IBM’s Patterns for E-business [Ref 8]

  13. Today’s e-business solutions [Ref 9]

  14. IBM’s Patterns for E-business : Business Patterns [Ref 8]

  15. IBM’s Patterns for E-business : Integration Patterns [Ref 8]

  16. IBM’s Patterns for E-business : Composite Patterns [Ref 8]

  17. IBM’s Patterns for E-business : Application Patterns • Application patterns – conceptual layouts that describe how the application components and data within a business solution interact. • Select the application pattern that fits best, based on the key business and IT drivers. [Ref 8]

  18. IBM’s Patterns for E-business : Runtime Patterns • Runtime patterns – used to define the logical middleware structure supporting an Application pattern. • Select the best-fitting Runtime pattern based on non-functional requirements (for example, availability, performance, security and scalability). • Each Application pattern requires one or more Runtime patterns. [Ref 8]

  19. IBM’s Patterns for E-business The Foundation of the Architecture [Ref 8]

  20. Case Study I- Future Step Electronics (Customer Service System Online) • [Ref 9]

  21. Case Study I- Future Step Electronics 2 [Ref 9]

  22. Case Study I- Future Step Electronics 3 [Ref 9]

  23. Case Study II – Retailers’ Mega Exchange[Ref 8]

  24. Case Study II – Retailers’ Mega Exchange 2[Ref 8]

  25. Case Study II – Retailers’ Mega Exchange 3[Ref 8]

  26. Case Study III - ArtimusA web-based news poster (http://sourceforge.net/struts) • Implement MVC and Layer pattern [Ref 4]. • Benefit of MVC and Layer pattern. • Flexibility to add new component (Lucene search engine component). Database Presentation Layer Control Layer Business Layer Integration Layer Resource Layer(JDBC) Lucene Search Engine • [Ref 4]

  27. Benefits [Ref 7, 8] • Reusability • Greater productivity • Enable to use existing skills and proven solutions/architectures • Capture the specific knowledge of the most skilled architects within an organization. • Retain business and technology knowledge from IT staff that would otherwise disappear once a skilled member leaves the organization • Rapid implementation, faster approach. • More predictability than those produced by incremental approach.

  28. Benefits 2 • Mass customization • More cost effective • Focus on “what to build” rather than “how to build it”. • High quality e-business applications in less time. • Address non-functional properties. (E.g. Broker Architecture address interoperability. [Ref 4, pg. 407]) • Easing workload. • Achieve all these without burning out a reduced workforce.

  29. Growing Areas/Future of Patterns and e-business applications • E-business oriented pattern language – a set of patterns that allow the composition and arrangement of prefabricated patterns and components to build e-business applications. • Support and training for finding and selecting appropriate patterns. • Evaluations and improvements of POSA in e-business domain. • To further the use and development of Pattern-Oriented Architecture in e-business domain.

  30. Conclusion • No longer “build as you go”. • No longer a choice between “buy or build”. • Build, buy, rent, connect or any combination. [Ref 8] • Do more with little in tough economic conditions. Reusability. • Craftsmanship to Industrialization by learning to customize, reuse, and follow the patterns to produce similar but distinct applications. • That’s what Pattern-Oriented Architecture offers.

  31. References • A. Touir, H. Mathkour, T. Al-Naeem, BizArk : A Reusable E-business Architecture based on Pattern-Oriented Technology, Computer Systems and Applications, 2003. • D. Manolescu, A. Kunzle, Several Patterns for e-Business Applicaiton,2001. • D. Bohinc, Patterns in Software Architecture, Synergy International Limited, 2003. • F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, Pattern-Oriented Software Architecture : A System of Patterns, John Wiley and Sons, 2001. • G. Vasudeva, Patterns for e-business : Leveraging Architectural Patterns in Defining Enterprise Architecture and Solution Architecture , IBM, 2003. • R. McGrath, R. Sparks, PRINCETON SOFTECH:Princeton Softech enables fast, high quality ebusiness development, M2 Presswire, Coventry, March 15 2000, pg. 1. • T. Blankers, Combining models and patterns: delivering on the promise of increased IT productivity, Java Developer’s Journal, July 2003 v8 i7 pS1(4).

  32. References 2 • J. Adams, S. Koushik, G. Vasudeva, G. Galambos, Patterns for e-business- A Strategy for Reuse, IBM Press, August 2001. • J. Adams, S. Koushik, G. Vasudeva, G. Galambos, Patterns for e-business- An Executive Overview, IBM, August 2001. • J. Adams, Patterns for e-business in Practice, IBM, November,2001. • M. Butler, Patterns for e-business – continued evolution, IBM, Butler Direct Limited, July 2001. • P. Gopalan, IBM ebusiness : Technology, Solution and Design Overview, Chapter 2, “E- business concepts and technologies”, IBM, 2003. • W. Hasselbring, R. .Reussner, The Dublo Architecture Pattern for Smooth Migration of Business Information Systems : An Experience Report, Proceedings of the 26th International Conference on Software Engineering (ICSE ’04), 0270-5257,2004.

  33. Questions and Answers Any Question? THANK YOU.

More Related