Your SlideShare is downloading. ×
0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Dom introduction-website-v1.0
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Dom introduction-website-v1.0

5,566

Published on

Cogility Dom Introduction v.1.0

Cogility Dom Introduction v.1.0

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
5,566
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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
  • Transcript

    • 1. COGILITY SOFTWARE The Leader In Model Driven Complex Event Processing<br />DOM Introduction<br />August,2009<br />Matthew Ghourdjian<br />Yngvar D. Tronstad<br />1<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 2. Problem Domain<br /><ul><li>Enterprise Challenges:
    • 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
    • 8. Technical Challenges:
    • 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
    • 14. Dealing with multi-dimensional COMPLEXITY</li></ul>.<br /><ul><li>Click to edit Master text styles
    • 15. Second level
    • 16. Third level
    • 17. Fourth level
    • 18. Fifth level</li></ul>2<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 19. Problem space and challenge with P-2-P integration<br />.<br />sales <br />support<br />billing<br />in the past, complex point-to-point integrations were used to construct an end-to-end business process<br />The disadvantages:<br /><ul><li>interface complexity
    • 20. inability to quickly modify processes following initial implementation
    • 21. expensive to maintain and extend </li></ul>customer<br /> care<br />inventory control<br />shipping<br />3<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 22. Organization with overlapping functions and data<br />.<br /><ul><li>Click to edit Master text styles
    • 23. Second level
    • 24. Third level
    • 25. Fourth level
    • 26. Fifth level</li></ul>Horizontal: Process Oriented<br />Vertical: Application Oriented<br />4<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 27. Pair matching Doesn’t Scale<br />.<br /><ul><li>Click to edit Master text styles
    • 28. Second level
    • 29. Third level
    • 30. Fourth level
    • 31. Fifth level</li></ul>5<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 32. As – is situation – is a significant barrier<br />.<br /><ul><li>Click to edit Master text styles
    • 33. Second level
    • 34. Third level
    • 35. Fourth level
    • 36. Fifth level</li></ul>Traditional waterfall process<br />R 1.0<br /><ul><li> Long development time
    • 37. High risk and development cost
    • 38. Inflexible and difficult to change
    • 39. High cost of failure
    • 40. Late visibility of project success</li></ul>P2P Architecture<br />6<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 41. Changes in enterprise projects<br />.<br />35%<br />30%<br />25%<br />20%<br />%Change or creep in requirements<br />15%<br />10%<br />5%<br />10<br />100<br />10000<br />1000<br />Project size measured in FPs http://www.wikipedia.org/wiki/FP_(complexity)<br /><ul><li>Large projects will have change – rates / requirement – creep of > 33%
    • 42. Medium sized projects have change rates around 25 %</li></ul>Change in scope and / or requirements are inevitable <br />7<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 43. Requires a Copernican shift<br />.<br />In the beginning…<br />We had it all wrong…<br />Data<br />Apps<br />Apps<br />Apps<br />Apps<br />8<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 44. Requires a Copernican shift<br />.<br />Apps<br />Data<br />Apps<br />Apps<br />Put the “smarts” in the data… watch what happens…<br />9<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 45. Cogility composite application development solution<br /><ul><li>Cogility is the unique provider of an IDE that employs a fully instantiated MDA environment for creating complex, service oriented and event-driven composite applications that solve difficult problems with process execution, web service orchestration and data synchronization simultaneously</li></ul>.<br />Process orchestration with: UML+ WS<br />Data Integration with: UML+ CWM<br />MDA+ EDA+SOA<br />10<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 46. Process oriented data synchronization<br />.<br /><ul><li>To simplify the design process:
    • 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)</li></ul>cogility studio enables collaboration between experts and application developers <br />11<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 50. Joint Data Integration Strategy<br />DIM<br />DIM<br />DIM<br />DIM<br />DIM<br />Layers of<br /><ul><li> Isolation
    • 51. Indirection</li></ul>DIM<br />DIM<br />DIM<br />Layers of<br />Abstraction<br />DIM<br />DIMz<br />DIM<br />DIM<br />MIM<br />d2m<br />m2d<br />Watch<br />List<br />Emerge<br />US Visit<br />IHRT<br />.<br />12<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 52. UML<br />Reusable CWM- Based Transforms<br />Master Information Model (MIM)<br />UML<br />UML<br />UML<br />UML<br />UML<br />CWM<br />UML<br />UML<br />Distinct Information Model (DIM) representing Enterprise Applications<br />UML<br />star schema – data modeling with transformations <br />.<br /><ul><li>Eachapplication to be integrated is modeledindependently
    • 53. The CommonViewofthe data is alsocreated as a separate model
    • 54. Transformationsconvert data betweentheindividual systems and thecentralcorporateview</li></ul>13<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 55. UML<br />Reusable CWM- Based Transforms<br />Master Information Model (MIM)<br />UML<br />UML<br />UML<br />UML<br />UML<br />CWM<br />JMS/WS<br />Based Messaging <br />Layer for triggering transformations and state machines and <br />sending notifications<br />UML<br />UML<br />Distinct Information Model (DIM) representing Enterprise Applications<br />UML<br />An example of a transformation chain<br />.<br /><ul><li>A Separate layerconvertsincomingmessages to a common format.
    • 56. ChainsofTransformationsexecutetogether to move data betweenapplications.</li></ul>14<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 57. Using Dom transformation for information exchange<br />.<br />Cogility Manager<br />JMS<br />JMS<br />JMS<br />MasInt<br />BioMetrics<br />Master<br />Information<br />Model<br />JMS<br />IWS<br />HumInt<br />WS<br />JMS<br />15<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 58. Process oriented data synchronization<br />.<br />WS<br />Request<br />JMS<br />Message<br />Cogility Manager<br />Case<br />Obj<br />internet<br />M2E<br />Conv<br />HME<br />WS<br />Logic<br />S1<br />JMS<br />Message<br />S2<br />internet<br />internet<br />Remote<br />WS2<br />Remote<br />WS1<br />16<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 59. Example Cogility Solution<br />.<br />internet<br />External Web Applications<br />IPB Planning<br />Internal Web Applications<br />Suspicious Activity<br />TTP<br />Notification<br />Analysis<br />Actions<br />Cogility Modeler<br />Cogility Manager<br />Cogility Insight<br />JMS OWS<br />UML<br />Process Model<br />CWM Data Transx<br />Enterprise Reporting & Monitoring<br />IWS<br />Java ,Message Service (JMS) / Inbound Webservice (IWS) / Outbound Webservice (OWS)<br />GCCS<br />Afatds<br />CIDNE<br />C-IED<br />JDE<br />MASINT<br />Biometrics<br />Humint<br />Known<br /> Association<br />17<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 60. To-be transformation is required<br />.<br />R 1.0<br />Traditional waterfall process<br /><ul><li> Long development time
    • 61. High risk and development cost
    • 62. Inflexible and difficult to change
    • 63. High cost of failure
    • 64. Late visibility of project success</li></ul>Transx strategy<br />P2P Architecture<br />18<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 65. To-be transformation RESULT<br />.<br />19<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 66. Our Solution Approach<br /><ul><li>The overall approach to developing the Signature Analysis System using Cogility is based on an Incremental and Iterative Development (IID) approach based on simply iterating over the following key steps:
    • 67. Information Modelling
    • 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
    • 72. Model directly executed, with real time Monitoring</li></ul>.<br />information defines the vocabulary and<br /> persistent data structure of the system<br />information<br />adaptive <br />feedback<br />Interfaces<br />interfaces define the channels of communication with the outside world<br />cogility<br />methodology<br />iterate<br />behavior<br />rt insight<br />behavior specifies the business process and logic executed in terms of the information model when an interface is invoked. <br /><ul><li>The Iterative and Incremental Development (IID) is a strategy where the system grows incrementally with new features, iteration by iterations:
    • 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 reduction</li></ul>20<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 77. Typical “wind – tunnel” plan<br />.<br />product decision<br />dev demo<br />Kick - off<br />alpha <br />demo<br />final demo<br />weeks<br />12<br />11<br />10<br />9<br />4<br />3<br />2<br />1<br />8<br />7<br />6<br />5<br /> Phase ii Planning<br />productization<br />Decision<br />requirements<br />Initial F&F<br />the evolving model becomes the defined system<br />solution threads<br />Exe<br />Model<br />auto deploy<br />test /demo<br />eval<br />linked to evolving<br /><ul><li>demo releases
    • 78. client capabilities
    • 79. risk reduction</li></ul>final demo<br />adaptive feed-back<br />Exe<br />Model<br />auto deploy<br />test /demo<br />eval<br />COI opportunity<br /> to the <br />direction<br />alpha demo<br />adaptive feed-back<br />Each Iterative and Incremental Model Evolution follow the same structure:<br />Exe<br />Model<br />auto deploy<br />test /demo<br />eval<br />development<br />21<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 80. Transformation issues<br />.<br />22<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 81. Overall benefits<br /><ul><li>Speed- 2 Development and Deployment
    • 82. Agile and dynamic processes
    • 83. Rapid modifications
    • 84. Improved data integration
    • 85. Composable services
    • 86. Layered architecture
    • 87. Improved asset management
    • 88. Business Transformation
    • 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
    • 94. Customer experience
    • 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
    • 99. Architectural leadership
    • 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 </li></ul>23<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 104. Cogility’s MDA solution in summary<br /><ul><li>Binds technology and business processes
    • 105. Simplifies the development process
    • 106. Focuses on the solution, not the build
    • 107. Rapid iterative development
    • 108. Reduce risk and cost</li></ul>24<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />
    • 109. Contact information<br />.<br />Matt Ghourdjian<br />CEO<br />Cogility Software Corp<br />mghourdjian@cogility.com<br />949.202.9877<br />Yngvar Tronstad<br />Chief Scientist,<br />Cogility Software Corp<br />Ytronstad@cogility.com<br />650.450.6364<br />www.cogility.com<br />25<br />© 2010 Cogility Software Corporation All Rights Reserved. Proprietary and Confidential. <br />

    ×