enterprise software architecture modelling tool

34
Enterprise Software Architecture Modelling Tool

Upload: jeffery-richards

Post on 30-Dec-2015

224 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: Enterprise Software Architecture Modelling Tool

Enterprise Software Architecture Modelling Tool

Page 2: Enterprise Software Architecture Modelling Tool
Page 3: Enterprise Software Architecture Modelling Tool

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

Page 4: Enterprise Software Architecture Modelling Tool

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

Page 5: Enterprise Software Architecture Modelling Tool

Data gatherin

gXML file produced

Adobe Flex

Flash file produce

d

Direct distribution

End Users

Web Server

Publish to internet / intranet

System Owners

Flash-enabled

Web Browser

Microsoft Excel

Page 6: Enterprise Software Architecture Modelling Tool

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

Page 7: Enterprise Software Architecture Modelling Tool

offersprovides to

requested by

offers

provides to

requested by

supports

supports

Page 8: Enterprise Software Architecture Modelling Tool

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

Page 9: Enterprise Software Architecture Modelling Tool

offers

provides S1 to System 2

offers

provides S2 to System ...

requests S1 from System 1

Page 10: Enterprise Software Architecture Modelling Tool

Systems support various components

Implied service relationships between systems because of components

Actual service relationships between systems also stored

Page 11: Enterprise Software Architecture Modelling Tool
Page 12: Enterprise Software Architecture Modelling Tool

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

Page 13: Enterprise Software Architecture Modelling Tool
Page 14: Enterprise Software Architecture Modelling Tool

Shows detailed information about logical component (can be altered as required)

Services offered by the componentServices provided by the component

to other componentsServices requested by the

component from other components

Page 15: Enterprise Software Architecture Modelling Tool
Page 16: Enterprise Software Architecture Modelling Tool

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

Page 17: Enterprise Software Architecture Modelling Tool
Page 18: Enterprise Software Architecture Modelling Tool

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

Page 19: Enterprise Software Architecture Modelling Tool
Page 20: Enterprise Software Architecture Modelling Tool

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

Page 21: Enterprise Software Architecture Modelling Tool
Page 22: Enterprise Software Architecture Modelling Tool

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

Page 23: Enterprise Software Architecture Modelling Tool

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

Page 24: Enterprise Software Architecture Modelling Tool

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

Page 25: Enterprise Software Architecture Modelling Tool
Page 26: Enterprise Software Architecture Modelling Tool

Business process modelling viewBusiness scenarios with steps

definedEach step can be linked to a service

within the modelActs as validation for the model and

a useful training tool

Page 27: Enterprise Software Architecture Modelling Tool

Clicking on each step highlights the components and services used

Page 28: Enterprise Software Architecture Modelling Tool

As each step is selected, the previously-used components remain active

Page 29: Enterprise Software Architecture Modelling Tool
Page 30: Enterprise Software Architecture Modelling Tool

Each system can be linked to two functional groups (user-defined)

This allows a system architecture diagram to be derived

Page 31: Enterprise Software Architecture Modelling Tool
Page 32: Enterprise Software Architecture Modelling Tool

Dynamic visualisation of system-service connections

Nodes (systems or services) rotate and move when selected

Clearly shows related systems and how they are linked

Page 33: Enterprise Software Architecture Modelling Tool

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