Dom introduction-website-v1.0
•Download as PPTX, PDF•
0 likes•2,432 views
The document discusses Cogility Software and its model driven complex event processing approach. It addresses challenges large enterprises face with unpredictable events, system integration and decision support needs. Cogility provides a development environment that uses model driven architecture to create composite applications integrating process execution, web services and data synchronization. This allows for rapid, incremental development and reduced costs compared to traditional approaches.
![Problem Domain ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (18)
Similar to Dom introduction-website-v1.0
Similar to Dom introduction-website-v1.0 (20)
Recently uploaded
Recently uploaded (20)
Dom introduction-website-v1.0
- 1. COGILITY SOFTWARE The Leader In Model Driven Complex Event Processing DOM Introduction August,2009 Matthew Ghourdjian Yngvar D. Tronstad 1 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 3. Frequent, unpredictable and fast-changing events
- 4. A multitude of entities and systems requiring integration
- 5. Large enterprises with urgent decision support requirements between echelons
- 6. Integrated support of the edge-users
- 7. Loosely coupled organizational and technical infrastructure
- 9. Chaotic stovepipes of uncoordinated services, processes and information
- 10. Redundant functions and services
- 11. Lacking coordination, interoperability and agility
- 12. Exploiting new technologies (e.g., web services)
- 13. Predicting the impact of change
- 15. Second level
- 16. Third level
- 17. Fourth level
- 18. Fifth level2 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 20. inability to quickly modify processes following initial implementation
- 21. expensive to maintain and extend customer care inventory control shipping 3 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 23. Second level
- 24. Third level
- 25. Fourth level
- 26. Fifth levelHorizontal: Process Oriented Vertical: Application Oriented 4 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 28. Second level
- 29. Third level
- 30. Fourth level
- 31. Fifth level5 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 33. Second level
- 34. Third level
- 35. Fourth level
- 37. High risk and development cost
- 38. Inflexible and difficult to change
- 39. High cost of failure
- 40. Late visibility of project successP2P Architecture 6 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 42. Medium sized projects have change rates around 25 %Change in scope and / or requirements are inevitable 7 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 43. Requires a Copernican shift . In the beginning… We had it all wrong… Data Apps Apps Apps Apps 8 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 44. Requires a Copernican shift . Apps Data Apps Apps Put the “smarts” in the data… watch what happens… 9 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 47. the business process models are built by the system analysts
- 48. the data models and transformations are developed by the application developers
- 49. during the execution the reusable data transformations are executed as an integral part of the business process logic (processes + data)cogility studio enables collaboration between experts and application developers 11 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 51. IndirectionDIM DIM DIM Layers of Abstraction DIM DIMz DIM DIM MIM d2m m2d Watch List Emerge US Visit IHRT . 12 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 53. The CommonViewofthe data is alsocreated as a separate model
- 54. Transformationsconvert data betweentheindividual systems and thecentralcorporateview13 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 56. ChainsofTransformationsexecutetogether to move data betweenapplications.14 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 57. Using Dom transformation for information exchange . Cogility Manager JMS JMS JMS MasInt BioMetrics Master Information Model JMS IWS HumInt WS JMS 15 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 58. Process oriented data synchronization . WS Request JMS Message Cogility Manager Case Obj internet M2E Conv HME WS Logic S1 JMS Message S2 internet internet Remote WS2 Remote WS1 16 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 59. Example Cogility Solution . internet External Web Applications IPB Planning Internal Web Applications Suspicious Activity TTP Notification Analysis Actions Cogility Modeler Cogility Manager Cogility Insight JMS OWS UML Process Model CWM Data Transx Enterprise Reporting & Monitoring IWS Java ,Message Service (JMS) / Inbound Webservice (IWS) / Outbound Webservice (OWS) GCCS Afatds CIDNE C-IED JDE MASINT Biometrics Humint Known Association 17 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 61. High risk and development cost
- 62. Inflexible and difficult to change
- 63. High cost of failure
- 64. Late visibility of project successTransx strategy P2P Architecture 18 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 65. To-be transformation RESULT . 19 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 68. Interfaces to the Environment Definition
- 69. System Intent and Behaviour Definition
- 70. Automated completeness and consistency checking
- 71. Auto-deployment to the staging and production environment for acceptance testing
- 73. Each iteration includes production quality solution
- 74. Each iteration is a subset of a final system
- 75. Incremental and hot updates
- 76. Provides Early Risk reduction20 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 79. risk reductionfinal demo adaptive feed-back Exe Model auto deploy test /demo eval COI opportunity to the direction alpha demo adaptive feed-back Each Iterative and Incremental Model Evolution follow the same structure: Exe Model auto deploy test /demo eval development 21 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 80. Transformation issues . 22 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 82. Agile and dynamic processes
- 84. Improved data integration
- 87. Improved asset management
- 89. Incremental and iterative
- 90. Reduce cost of stovepipes
- 91. Remove bottlenecks through an end to end process focus
- 92. Process oriented data synchronization
- 93. Rapid response to changes
- 95. Dynamic data driven user portal
- 96. Shared access to information
- 97. Dynamic human-in-the loop interaction
- 98. Role based collaboration and access control
- 100. Greater agility and flexibility by introducing MDA
- 101. Best practices with separation of concern and layers of isolation
- 102. Directly executable models with built in scalability and reliability
- 103. MDA + SOA + EDA 23 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 105. Simplifies the development process
- 106. Focuses on the solution, not the build
- 108. Reduce risk and cost24 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
- 109. Contact information . Matt Ghourdjian CEO Cogility Software Corp mghourdjian@cogility.com 949.202.9877 Yngvar Tronstad Chief Scientist, Cogility Software Corp Ytronstad@cogility.com 650.450.6364 www.cogility.com 25 © 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential.
Editor's Notes
- Most Enterprises recognize its strategic approach—that is, harnessing the information power between and among its disparate entities and the agility that it would imbue—requires a radical departure from conventional development practices to resolve the following challenges: [Read from Slide]Additional Talking PointsBusiness Challenges: Reuse of processes, services and data across COI. The process of translating system requirements to system design, though overseen by centralized management, often misses the mark due to time compression or granularity of design review (e.g. too high level) and/or lack of familiarity with technical environment and/or end-user needs (e.g. requirement does not adequately capture ‘real requirement’).Technology Challenges: Though system design process initially starts as iterative and incremental, schedule compression often forces propagation of immature design and/or unproven approach resulting in significant ‘holes’ in functionality or disconnects at the data and/or systems integration touch points.Designing service-oriented applications often run into “new wine into old wine skins” due to lack of experience or ability to test and/or simulate implementation prior to full scale deployment.Multiple contractors working at service/unit level invariably produce software that fails to integrate at the data and/or service interface level due to lack of cross-communication or use of incompatible “open standards based” tools and technologies. Test and evaluation is not integrated with development process