Monday, September 7, 2015

Lightweight Portal based Visual Modelling using Troux


Lightweight Portal based Visual Modelling using Troux

We have developed a simple framework using Troux APIs and a graph path based approached to data to support simple visual modelling. This allows data in a Troux system to be presented to any user using essentially any device (e.g. mobile, tablet, Mac, PC etc.).

















We have Troux an excellent solution for aggregating, analyse and present data in many ways. 

Our focus over the last decade has been on creating Troux based solutions.  In doing this we have found ways to unlock more value from data held in Troux, provide users additional ways of interacting with that data.

Our approach ensures that common data is used for all forms of presentation i.e. models, reports, charts and visualisations. This means that set of documents used in project concept and delivery are always consistent. 

Any path through the graph of related objects can be defined and presented without any need for coding (i.e. no XML configurations). Paths can be used to generate: models, reports, analytics, digarams.

There are many BI tools that allow data to presented, charted etc. (and all can be used to access data in Troux). Most adopt a tabular approach to the representation of the data (which is limiting when n-dimensional relationships need to be visualized).

Our frameworks focus predominantly on allowing information to be understood in context by enabling various diagrams or models to be to generated or defined. These diagrams may be: timelines; flow charts; cluster maps; graphs; etc.

Diagrams and visualisation can be configured by users and saved as templates for re-use.They can be presented in stand alone portals or via Troux portals. 

The visualisation framework is device agnostic and oriented at HTML5 browsers. 


Archimate in Troux



Using Archimate for Architectural Design in the Troux Portal and Troux Modelling client.

When designing for an organisation and as part of team it is useful to record and communicate why the design is as it is. We can record through the design process, as and when we see fit, how the solution relates to: requirements, decisions, features, standards, patterns, reference models, etc.



The technical and business architecture of an organisation provide a logical reference point for new solutions. It is particularly important to be able to anchor proposed changes (e.g, new solution elements) back to these when several initiatives are operating in parallel - so all expected changes can be seen and related. We can also relate the design tp the existing assets and items managed in portfolios.

We can analyse and track development of the solution.