Book a Demo

Author Topic: Sparx users browsing a catalogue in Sparx  (Read 6046 times)

BruceTOGAF2

  • EA User
  • **
  • Posts: 74
  • Karma: +0/-0
    • View Profile
Sparx users browsing a catalogue in Sparx
« on: August 22, 2020, 12:24:22 am »
I have been asked to import a large spread-sheet of ISO standards into our Sparx repository so that Sparx users can access the following information:
Link, Standards Bodies, Standard number, Part Number, Year, Amendment, Edition, Technical Committee, Theme, Sub Theme.
The link is to ISE standard details in iso.org. Each link is to a downloadable PDF.

I have built numerous scripts that import spread-sheets into Sparx, then create packages, elements and diagrams. For this exercise, I am not sure what target to populate.
The glossary table has too few fields. I am considering the appropriate target object type and stereotype for this import e.g. Artifact/Document

Here is my question.  What object type and stereotype would best cater for Sparx users accessing and browsing this kind of catalogue?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Sparx users browsing a catalogue in Sparx
« Reply #1 on: August 22, 2020, 01:37:31 am »
I think you better create your own stereotype and add the required fields there.

Geert

BruceTOGAF2

  • EA User
  • **
  • Posts: 74
  • Karma: +0/-0
    • View Profile
Re: Sparx users browsing a catalogue in Sparx
« Reply #2 on: September 02, 2020, 06:49:36 pm »
Hi Geert, 

I have no problem creating my own stereotype and attributes/tags. How will Sparx users access and browse this kind of catalogue?  Is there a Sparx tool that would enable Sparx users to access this information in a tabular format?


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Sparx users browsing a catalogue in Sparx
« Reply #3 on: September 02, 2020, 07:34:03 pm »
Have you tried the list view and/or specification view?

IIRC you can add your own tagged value fields to those views.
An alternative is the search window with your own SQL search

Geert

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Sparx users browsing a catalogue in Sparx
« Reply #4 on: September 03, 2020, 12:19:46 am »
Hello,


What object type and stereotype would best cater for Sparx users accessing and browsing this kind of catalogue?
Well it depends on how the catalogue is intended to be used in modelling, but in general, unless you are absolutely certain you want something else, go with classes. Artifacts are weird in some respects, and you don't want to paint yourself into a corner with this stuff. Classes are marvellously generic and can be used in basically any context.

I have no problem creating my own stereotype and attributes/tags. How will Sparx users access and browse this kind of catalogue?  Is there a Sparx tool that would enable Sparx users to access this information in a tabular format?
Nothing in the box, no. Table views don't cut it -- another cute demo function that doesn't quite work.

Creating diagrams in List View mode could have been an option, but in List View, packages and elements don't open their child diagrams on double-click so that's useless for browsing. Same with Specification Views.

Just create a custom search with whatever properties are the most important. You can create a hyperlink to run the search if your users aren't able to run it themselves (they will need to go to the right diagram though).

Speaking of hyperlinks, if you just add hyperlinks to a Notes field or a tagged value they won't do you much good. Element "File" properties are your friend here. They can be launched from the property dialog, and while the browser doesn't offer the same function, a script that does that is a five-minute job. They're recognized by document generation templates too.

HTH,


/Uffe
My theories are always correct, just apply them to the right reality.