Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - adepreter

Pages: 1 [2] 3 4 ... 7
16
Thank you! Very useful.

17
That is anyway very useful information Geert. Thank you  :)

Since it is working with your MDG, I will try to figure out what makes mine invisible in the Resources window (Though it might be hard to find out because the MDG is quite large)

18
No, I don't have any reference to an MDG file.

Even if I remove the MDG, regenerate the MDG using Sparx 14 and import it, I still can't see the MDG in the resources window.

NB:
Using the "Technologies / Manage" option, there is a button '"Remove" that is activated for our technology.
And from Resources Window I can still import the MDG => It gets imported and activated, but it is still not visible in the Resources window.
For checking the existence of the MDG in the database: SELECT * FROM t_document where DocType = 'TECHNOLOGY' and DocName ='TechnologyName'

19
All users have 13.5 installed and our MDG is stored in our shared repository.
The MDG includes our architecture workspace layout which is critical since the default layout in Sparx is focusing on analysis, design and development.

The problem is that we cannot deploy Sparx 14 on users machines (there are many) without having tested on our own machines.

So we need both to coexist for some time.

20
Our MDG that was built and deployed with version 13.5 was deployed in our shared SQL Server repository.

After upgrading to Sparx 14 and opening that repository, the MDG is not visible in the resources window though it is activated.
Same problem with all of our other test repositories in Access and in SQL Server.


21
I implemented the _MeaningForwards and _MeaningBackwards in a connector metaclass of type Transition.
The initial values of _MeaningForwards and _MeaningBackwards  are set to a description of the meaning of the connector in each direction exactly as described ion the documentation:
http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/supportedattributes_2.html

But when I look in the traceability window, I still get the default verbs defined for the UML Transition.

NB: It does work for metaclasses of type association and dependency


22
I know this is a weird situation but...

If an MDG XYZ is stored in a repository
and an AddIn is installed that loads the same MDG (or another version of it)

then  the MDG that is activated is the one from AddIn (as expected)
and the quicklinks defined in the MDG loaded from the AddIn are ignored (BUG)

Alain

23
Thank you very much to all.
It works :-)

24
I didn't know I would start such passionate discussion :-)

How can we wrap/unwrap the zipbin MDG content (to/from the t_document table)?

A.

25
Hello,
We would like to DYNAMICALLY update the quicklinks in our model repository where our MDG is stored (without changing the MDG).
Does anybody know where these quicklinks are stored?
Thanks,
Alain

Why do we want to do this?
The model validation features of our addin dynamically adapts to metamodel changes without having to change anything in opur MDG.
Our formal metamodel is used 1) for model validation 2) for quicklinks generation 3) for documentation
See an example here: http://www.labnaf.one/guidance/index.html?guid=5049F7C5-210B-43b3-82BB-C6315222113A

The only thing missing to make it entirely dynamic is to update the quicklinks in the repostory when the metamodel gets changed.

We do *NOT* want to use a metamodel defined in the MDG as this is not dynamic.



26
Agree. That's what I was talking about in this post:

Simplified language definition and user experience (not based on UML profiles):

http://www.sparxsystems.com/forums/smf/index.php/topic,38934.msg241268.html#msg241268

27
That works fine. Thank you Geert!

Result is:

{Note.Formatted}

referring to the following query:

SELECT
Perspective = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Perspective'),
Code = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Code'),
t_object.Name as Name, t_object.Note as "Note.Formatted",
Implications = (select tv.notes from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Implications'),
Rationale = (select tv.notes from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Rationale')
FROM t_object
where t_object.stereotype = 'NMBS_Principle'
and t_object.package_id = #PACKAGEID#
order by Code


28
Hello,
In a template fragment I am selecting elements of a certain types in the current package using #PACKAGEID# (see select clause below).
I use that fragment only to be able to sort elements by a certain tagged value in a package.

The select clause collects notably the element Note.
The fragment also formats the resulting values in a table.

Problem: The generated Note field value, referred as {Note} in the document, shows the source HTML text including <LI> etc...

Any idea how to fix this problem?

Cheers,
Alain

SELECT
Perspective = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Perspective'),
Code = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Code'),
t_object.Name as Name, t_object.Note,
Implications = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Implications'),
Rationale = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Rationale')
FROM t_object
where t_object.stereotype = 'NMBS_Principle'
and t_object.package_id = #PACKAGEID#
order by Code


29
Workarounds are also not compatible with our model validation addin that uses a clean language metamodel as configuration data.

30
We don't want workarounds (e.g. creating instances)

We need clean and direct traceability between elements as we are generating lots of excel reports and governance charts.

Alain

Pages: 1 [2] 3 4 ... 7