Training Webinar: Fitting OutSystems applications into Enterprise Architecture
•
4 likes•3,951 views
Want to become an expert architect in 60 minutes? We're having a quick hands-on session to show how to design evergreen applications that will grow with your company strategy - from initial design to keeping the blueprint of your applications healthy as you need to adapt to new business demands In this session you will learn: - The 4 Layer Canvas concepts - the OutSystems architecture framework - How to use the the Canvas to design a new solution - How to use Discovery (tool available in the Forge) to keep track of your architecture and extract useful recommendations to fix architecture issues Free Online training: https://www.outsystems.com/learn/courses/ Follow us on Twitter http://www.twitter.com/OutSystemsDev Like us on Facebook http://www.Facebook.com/OutSystemsDev
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to Training Webinar: Fitting OutSystems applications into Enterprise Architecture
Similar to Training Webinar: Fitting OutSystems applications into Enterprise Architecture (20)
More from OutSystems
More from OutSystems (20)
Recently uploaded
Recently uploaded (20)
Training Webinar: Fitting OutSystems applications into Enterprise Architecture
- 1. Fitting OutSystems applications into Enterprise Architecture Architecture Webinar Francisco Menezes 1 Webinar / September 1st 2016
- 2. Replace This image in master About me OutSystems Experts Architect Francisco Menezes francisco.menezes@outsystems.com 2
- 3. 3 Learn how to build a Flexible and Cost-effective Solution Architecture aligned with Business concepts G al
- 4. Orchestration Modules End User Modules Core Business Modules Library Modules Reusable Services No Services The 4 layers canvas (4LC) UI and processes That provide functionality to end users Access Portals Cross-application processes and dashboards Business services Services around business concepts Non functional requirements services to connect to external systems or to extend your framework 4
- 5. Speeds up architecture design with a systematic approach Why use the Canvas? Common understanding between all Business users and Developers Easy to validate supported by a tool 5
- 7. Services architecture CRM ERP CMS OutSystems Services External API Core Services Integration Services Customer_CSContract_CS Sales_API Order_CS Product_CS Corporate DB External Consumer Catalog_API Customer_IS Order_IS OutSystems Consumer Product_IS 7
- 8. Service patterns Customer_CS Customer_IS ERP External Core Service (ECS) ECS with local replica ECS with isolated synchronization logic Customer_CS Customer_IS ERP Customer_CS Customer_IS ERP Customer _Sync Customer_CS ERP2 SaaSERP1 ERP1_IS ERP2_IS SaaS_IS Customer_Sync Transparency service 8
- 9. Architecture design process Keep iterating 3 steps to refine the architecture using the canvas
- 10. Keep iterating 3 steps to refine the architecture using the canvas, as new concepts and more details are disclosed Architecture design in 3 steps 10
- 11. business concepts and integration needs Integration technology User Stories and Roles Points:13 Must Have Information Architecture UX expectations 1. Disclose Architecture design in 3 steps 11
- 12. concepts on the canvas 1. Disclose 2. Organize Architecture design in 3 steps Access Portals Site Call Center Backoffice User Processes Customer management Claim handling Analytics Business Concepts Customer Claim Contract Product Integration & NFRs ERP CRM Audit ACL 12
- 13. 1. Disclose 2. Organize 3. Assemble Matching recommended patterns Architecture design in 3 steps Customer_CS Customer_IS ERP Customer _Sync Portal App1 App2 Theme 13
- 14. Architecture design process Let’s follow an example
- 15. Orchestration Modules End User Modules Core Business Modules Library Modules Product Store Supplier Recall plan ERP Connector User process Business concepts Integration needs Product Family Stock Recall Process Steps 1 2 - Disclose and Organize concepts 15
- 16. Orchestration Modules End User Modules Core Business Modules Library Modules Product Store Supplier Recall plan ERP Connector Steps 1 2 - Disclose and Organize concepts Recall Process Product Family Stock Supplier Audit Supplier report Supplier audit Supplier audit plan Internal Theme Supplier Theme Internal portal Supplier portal Access Portals Domain Themes 16
- 17. Orchestration Modules End User Modules Core Business Modules Library Modules ERP Connector Step 3 - Assemble Recall Process Supplier Audit Internal Theme Supplier Theme Internal portal Supplier portal Process support concepts Product Product Family Unbreakable concepts Supplier StoreStock Location Base core concepts Recall plan Supplier audit Supplier report Supplier audit plan 17
- 18. Orchestration Modules End User Modules Core Business Modules Library Modules Final architecture Product Services Supplier Services Store Services Stock Services Supplier Audit Services Recall Services Recall Process Supplier Audit Internal portal Supplier portal Supplier IS Internal Theme Supplier Theme Abstracts external systems 18
- 19. Orchestration Modules End User Modules Core Business Modules Library Modules Product Services Supplier Services Store Services Stock Services Supplier Audit Services Recall Services Recall Process Supplier Audit Internal portal Supplier portal Supplier IS Internal Theme Supplier Theme Granularity Low Medium High + Building blocks Reusability Low Medium High + Savings Abstraction Low Medium High + Information hiding Mash up High Medium Low + Composition Autonomy + Control The benefits 19
- 20. How to validate the Architecture Basic rules to check if the architecture is Sound
- 21. Orchestration Modules End-user Modules Library Modules Core Modules Validation rules Every one became dependent on this cluster of modules No Upward references 21
- 22. Orchestration Modules End-user Modules Library Modules Core Modules Validation rules No Upward references No side references among orchestration or end-user modules EU1 EU2 EU1 unnecessarily inherits this cluster 22
- 23. Orchestration Modules End-user Modules Library Modules Core Modules Validation rules No Upward references • No Front-end screens • Read-only entities • No Business logic • No core entities cycles No No side references among orchestration or end-user modules 23
- 24. Validate your architecture with Discovery Get a comprehensive explanation about layers and violations Place each module in a layer 24
- 27. 4 Rules for composing LifeTime applications That will: - Minimize impacts between applications - Simplify deployments - Cope with different paces
- 28. Concepts Orchestration applications End-user applications Core applications Library applications Application Set of modules defined in Service Studio that constitutes a minimal deployment unit for LifeTime Application layer Topmost layer of the modules inside the application 28
- 29. Rule #1 Correctly layer your modules No upward references No references among orchestrations or among end-users Cycles No 29
- 30. Application composition Rule #2 Layer your applications End-user Application 1 End-user #1 Core A Library A Core B Library B End-user Application 2 End-user #2 Core C Library C Core D Library D Layered module architecture End-user #1 Core A Core B Library A Library B 1st project End-user #2 Core C Library C Core D Library D 2nd project 3rd project WRONG 30
- 31. Application composition Rule #2 Layer your applications End-user Application 1 End-user #1 Core A Library A Core Application Core B Library B Core C Library C End-user Application 2 End-user #2 Core D Library D Layered module architecture End-user #1 Core A Core B Library A Library B 1st project End-user #2 Core C Library C Core D Library D 2nd project 3rd project 31
- 32. Rule #2 Layer your applications No upward references No references among orchestrations or among end-users Cycles No 32
- 33. Application 2Common application Rule #3 Don’t mix owners Module 3Module 1 Module 2 Owner 1 Owner 2 Split Application 1 Module 3Module 1 Module 2 Owner 1 Owner 2 33
- 34. Common services Life Suite Property Suite Auto Suite Simulators Simulation Portal ... ... ... Auto Life Property Engines Policy Simulators Simulation Portal ... ... ... Auto Life Property Engines Policy Split Property business Auto business Life business Property business Auto business Life business Rule #4 Don’t mix sponsors 34
- 35. Library Apps Integration Services Orchestration Apps End User Apps Core Business Apps Previous example – application composition Common Services Themes Recall Supplier Audit Product Services Supplier Services Store Services Internal Theme Supplier Theme Stock Services Supplier IS Recall Supplier Audit Internal portal Supplier portal Supplier portal Supplier Audit Services Recall Services Internal portal 35
- 36. Validate your applications with Discovery • Violations prevent life cycle independence with complex deployments • To many shared services inside End user applications 36
- 37. Common Style Guide Share the look and feel among applications
- 38. Common services Application 1 Theme independent Lisbon Template Lisbon theme App1 theme Lisbon template M L M L Cloned when creating 1st module of the application Based on M L - Menu - Login flow #1 Built-in Style Guide Don’t forget to link menu entries to screens with external URLs 38
- 39. Common services Application 1 Theme independent #2 Custom Style Guide, clone a built-in Custom Style Guide Custom theme App1 theme Custom template M L M L Lisbon Template Lisbon theme Lisbon template M L Clone Don’t benefits from new versions of the built-in theme without complex merges Best performance by avoiding an extra indirection Use when the Custom Style guide introduces lots of changes 39
- 40. Common services Application 1 Theme independent #3 Custom Style Guide, specialize a built-in Custom Style Guide Custom theme App1 theme Custom template M L M L Lisbon Template Lisbon theme Lisbon template M L Clone Lower performance (extra imports of CSS and other resources) Keep inheriting new benefits from new versions of the built-in theme Use when the Custom Style guide has only minor changes and is shared by several applications 40
- 41. Common services Application 1 Theme independent #4 Build your own custom Style Guide Custom Style Guide Custom theme App1 theme Custom template M L M L Vanilla Template Vanilla theme Vanilla template M L Clone the Vanilla Template Use when the Custom Style guide can not benefit from any existing theme. The vanilla template is the correct starting point, since it contains only the minimum required structure 41
- 42. Common Style Guide Global theme Application 1 App1 theme Application 2 App2 theme M L Common Style Guide Global theme Application 1 App1 theme Application 2 App2 theme L M M Sharing a style guide - possible scenarios #3 Portal Common Menu and Login flow #2 Intranet Own menu, same login flow Global template Global template M Common Style Guide Global theme Application 1 App1 theme Application 2 App2 theme M L M L #1 Independent Apps Own Menu and Login flow Global template M L Common Menu and Login flow need to be moved to the theme Common login flow needs to be moved to the theme eSpace Standard pattern 42
- 43. Don’t forget ✓Keep iterating your architecture ✓Avoid violations ✓Follow patterns ✓Optimize application composition 43
- 44. Links How does OutSystems Platform fit in an enterprise architecture? Designing the architecture of your OutSystems applications The Discovery Tool The Electronic Canvas The Refactor
- 45. Thank you!