Open WatchTh1 opened 3 years ago
Seems like this is a duplicate of matrice view feature request. If possible would be nice to get an idea when would it be at roadmap?
This is something you can implement yourself or with jArchi.
This is something you can implement yourself or with jArchi.
Yea, trying to get close with Eclipse RPC.
Yea, trying to get close with Eclipse RPC.
It would help if you could create a detailed set of functional requirements, some mock-ups for what it might look like.
Here's some things that would need to be considered...
*.archimate
file? Separate file?The user would probably want the output in a report of some kind. HTML? PDF? Excel? Raw data? And if the end result is in this format maybe it's possible to do this with jArchi and some additional JS/Java libraries?
Partialy it has been done. User stories/Usecases, wireframes, logic. Software achitecture decisions - currently a weak spot. I hardly can imagine variety of options enough detailed.
If you would help me to have some ideas i could share usage concepts and solution requirements.
With no idea on how it could match Eclipse Fwk, but I see @Phillipus answer about a set of functional requirement. That's something I can do ;-) ! My inspiration is coming from Business Intelligence pivot table (Qlik, BO or Ms BI Pivot table), it may exist some graphic java component dealing with these things (?)
So, in the archimate way of speaking, the goals may be : 1) "Manage Togaf "artifacts" (other than diagrams) matrice and catalog in order to make Archi number 1 among Togaf practitioners" 2) "Make matrices and catalogs a mean to manage, correct, input and analyse the model in a way as convenient as diagrams (~Archi views) Driver is of course : Archimate is becoming the best modeling notation to support Togaf
which means in term of (general) requirement that :
A) Interaction with the elements of a catalog (or a matrice) is same than the actual Archi view : firstly Navigator, Visualiser, Properties, hints and contextual menu fonction 'Select in model tree'... All these are available when you clik or navigate in the table (whether catalog or matrice) B) Formating the table is as easy as formating Excel Pivot table (folding, unfolding, sorting or arrange elements first, last, up and down) C) Table is always consistent with the model. that is more a principle than a requirement ;-) The requirement is that the table is generated and refreshed when displayed or when a change occurs in the model D) A table Catalog is made of one Hierachy of elements (line) and one or many cells (columns). A table matrice is made of 2 hierarchies of elements (one for the line, one for the column) and one (definition of) cell. E) Hierarchy is user defined. Hierachy is an ordered list of levels.
F) A path may be a direct relationship or a valid derived (see Archimate rules derivation 1 to 8) relationship (with a depth constraint) G) Cells (columns) in a table catalog are user defined based on attributes. The value is displayed H) Cell in a table matrice is user defined :
I) Viewpoint may apply both on hierarchy and cell to final-filter the results J) Cell is user editable :
More detailed in the attached xls file. Architool matrix and catalog.xlsx
It sounds like a list to Santa Claus !
This exercice make me think of a lot of things that couldn't be included in this list. I am at your disposal to develop or think about questions that may raise !
@LioDL Thanks for the detailed analysis, which will require deeper consideration.
As a matter of fact, @jbsarrodie and I are currently exploring how we might implement matrix/table views in Archi, so your contribution may help us. We're not sure when matrix/table views might be implemented as we are planning on implementing ArchiMate Profiles as our next task.
Phil
Great news that you have identified it even though not yet planned !
Completing the functional requirement and to be test driven, the following 2 examples should be supported (and many can be found in Togaf guide : Togaf and Archimate modeling g21e.pdf [a MUST-READ]) :
1) Catalog of requirements
2) RACI Matrice (or Actor role togaf matrice artifact) : RACI is a matrice to clarify level of implication / commitment into some activities. A stands for Accountable (decide, assess, validate), R for Responsible (produce, work), C for consulted and I for Informed. The model is :
The matrice :
Looking forward to work with even if in many months or some years !
Would be great if Archi would allow to have feature to build a table-like views for a set of elements with ability to view and namage relationships.
A good example for such alike feature will be traceability matrices, and treeview generators.
The simpliest Usecase I can imagine would be:
select concept_type|relationship_type [selector]
or maybe some kind of master.Wrapping this with filters and sorters could add amass of functionality to the instrument.