1 / 34

Model-One: A Comprehensive Tool for Enterprise Software Architecture Modelling

Model-One is a cutting-edge, Flash-based enterprise software architecture modelling tool designed for senior managers and technologists alike. It offers visual tools to evaluate and modify architectural structures, identify system redundancies, and explore alternative solutions. With its small footprint and portability, Model-One runs on any Flash-enabled browser without the need for databases or web servers. The methodology incorporates data gathering through Excel, XML transformation, and dynamic visualizations of service relationships, allowing users to make informed decisions about their software architecture.

adlai
Télécharger la présentation

Model-One: A Comprehensive Tool for Enterprise Software Architecture Modelling

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. Enterprise Software Architecture Modelling Tool Model-One

  2. Model-One

  3. Model-One Introduction • Flash-based enterprise software architecture modelling tool • Has visual tools for senior managers • Supported by detailed data for technologists • Different views show architecture changes over time • Driver for change • Shows areas of system redundancy • Shows potential alternatives

  4. Model-One Introduction • Architecture defined by: • Logical Components • Software Systems • Services (in a Service Oriented Architecture) • Small footprint – typically < 1 Mb • Portable – runs on any Flash-enabled browser • No database or web server required for distribution

  5. Model-One Methodology System Owners Adobe Flex Microsoft Excel Data gathering XML file produced Flash file produced Direct distribution Publish to internet / intranet Flash-enabled Web Browser End Users Web Server

  6. Model-One Methodology • Initial data gathering phase • Data held in Excel and transformed into XML • XML data read by Adobe Flex application • Flex application compiled into Flash object • XML data encapsulated within Flash object • Flash file distributed as required

  7. Model-One Architecture SYSTEM 1 supports COMPONENT 1 TRADE ENTRY S1 COMPONENT 3 TRADE PRICING offers provides to requested by COMPONENT 2 REPORTING requested by provides to S2 offers supports SYSTEM 2

  8. Model-One Architecture • Based around Service Oriented Architecture (SOA) • Logical components describe aspects of the business model • Each logical component offers a number of services • These services are requested by other components

  9. Model-One Architecture SYSTEM 1 SYSTEM y SYSTEM x S1 offers provides S2 to System ... provides S1 to System 2 SYSTEM 2 S2 requests S1 from System 1 offers

  10. Model-One Architecture • Systems support various components • Implied service relationships between systems because of components • Actual service relationships between systems also stored

  11. Model-One Logical View

  12. Model-One Logical View • Default starting view for Model-One • Typically 20-25 logical components • Components can be grouped as required • Actors (non-technology components) show people, teams, external groups • Tooltips show detailed component descriptions • Components can be clicked to show detailed information

  13. Model-One Component Details

  14. Model-One Component Details • Shows detailed information about logical component (can be altered as required) • Services offered by the component • Services provided by the component to other components • Services requested by the component from other components

  15. Model-One Component Details

  16. Model-One Component Details • Shows systems supporting this component • Filters available by system or timeline view • Can see which services offered by the component are actually used by the systems

  17. Model-One System View

  18. Model-One System View • Each logical component is supported by one or more software systems • Immediately shows areas of redundancy where there are many systems supporting the same logical components • Systems colour-coded to show fate across time • Multiple user-defined views available to show architecture changes over time

  19. Model-One System Details

  20. Model-One System Details • Like logical components, each system offers, provides and requests services • Unlike logical components, these are actual services • This can validate the notional services offered by the components

  21. Model-One System Details

  22. Model-One System Details • Impact tab shows what would happen if the selected system is demised • In this case, ALGO provides a number of services to MUREX • If one service is selected, then any alternative systems that can provide the same service will be shown on the right

  23. Model-One System Details • In this case, Prism offers the “Create Limits” service, so this system may be used as an alternative to support Murex if ALGO is demised

  24. Model-One System Details • However, for the “RM Functions – UI” service, there is no alternative system • This can drive analysis and bring out issues much earlier in the development cycle

  25. Model-One Process View

  26. Model-One Process View • Business process modelling view • Business scenarios with steps defined • Each step can be linked to a service within the model • Acts as validation for the model and a useful training tool

  27. Model-One Process View • Clicking on each step highlights the components and services used

  28. Model-One Process View • As each step is selected, the previously-used components remain active

  29. Model-One Functional View

  30. Model-One Functional View • Each system can be linked to two functional groups (user-defined) • This allows a system architecture diagram to be derived

  31. Model-One Links View

  32. Model-One Links View • Dynamic visualisation of system-service connections • Nodes (systems or services) rotate and move when selected • Clearly shows related systems and how they are linked

  33. Summary • Agile development methods mean user-requested changes (new data or visualisations) can be added easily • Small footprint and use of Flash ensures ease of distribution • Blends clean information visualisation with underlying data power • Clear driver for change projects

  34. Contacts • thushan@goto10consulting.com • www.goto10consulting.com

More Related