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 - Glassboy

Pages: 1 ... 44 45 [46] 47 48 ... 73
676
Bugs and Issues / Re: HasTag anomalies
« on: May 12, 2016, 08:04:50 am »
There is actually, a practical result of my (theoretical) argument...  You are tackling the practical problem of how do we indicate an optional tagged value when all you can define are mandatory ones?  As you saw in my argument, an mandatory attribute allowing an empty or null value is, by definition, an optional attribute.

No it isn't.  An empty value conveys meaning in exactly same way as a non-empty value.  At a very crude level it says the information does not exist or is not known.  That information helps us evaluate the completeness of what we are modeling.

The descriptor existing but not the value only says that tagged values were poorly implemented.

677
There's a registry key called MDGTechnology PathList.  If you work in a managed environment an Active Directory GPP can be configured to set this to a central location for every EA user.
Quite often the people that develop the MDG's are not the same ones who control the technical stuff like AD and registry distribution.
The strings you have to pull, and the hoops you have to jump through to get a change like that distributed often isn't worth it.

That is why I like the model distribution. The model is something we control ourselves, and we don't need anyone approval or help to get it done.

As for development and testing, we have  DEV, TEST and PROD databases to be able to develop and test the MDG, scripts, and other stuff on.

Geert

So let's get this right; you should only follow the best practice is it is a developer practice.  Perhaps if you treated operations people with a bit of respect and less hypocrisy you may find that there aren't any hoops to jump through.

If you thinking I'm sounding a little bit too scornful it's because I've actually lost count of the number of times I've stopped or minimized the damage from a developer doing something stupid which in a country with laxer employment laws would have got them fired.  Not to mention the number of times I've debugged issues caused by the arrogant attitude that doing it our own way is the best.

Not to mention that modern distribution and management environments are very powerful tools which most organisations have invested in to perform standardized distributions and reduce the complexity and cost of environments.




678
Bugs and Issues / Re: HasTag anomalies
« on: May 11, 2016, 01:49:52 pm »
However, in the case of the Tagged Value setting a value to «Empty» string should cause the Tag to be purged (as with setting the value to «Null».
I strongly disagree. Even if your methodology doesn't allow tagged values with an empty value that is not going to be the case everywhere.

At a conceptual level, (and the entire basis of this thread) there is a difference between an empty value (eg string or set), missing value (null) or a missing container.

The analogy is the Axiom of the empty set.


Null has been described as the worst mistake in computer science, and the arguments for that position all seem to be true.

I'd be interesting is seeing those arguments. I'd say the concept of a null value is essential to computer science.

The article that first brought it to my attention is here, but if you google there's plenty of discussion of it.

679
Bugs and Issues / Re: Stereotype in MDG
« on: May 11, 2016, 11:34:12 am »
Would that be https://www2.opengroup.org/ogsys/catalog/W150 ?
No, Not exactly.  Haven't read the paper thoroughly, but a quick overview suggests we're on similar lines.

The framework they try and crowbar into Archimate is interesting and worth reading properly.  The Archimate implementation is in a few words a bit ridiculous. 

680
Bugs and Issues / Re: HasTag anomalies
« on: May 11, 2016, 11:14:54 am »
One should not be allowed to create a tagged value without supplying and maintaining a value.  Then the documentation can specify:
HasTag(tagname) will evaluate to true if the Tagged Value tagname exists (regardless of the assigned value).
HasTag(tagname, tagvalue) will evaluate to true if the value of the tagname is tagvalue.

I agree.  It should be a zero-length string, which is different from null (apparently not in older versions of Oracle tho).

681
There's a registry key called MDGTechnology PathList.  If you work in a managed environment an Active Directory GPP can be configured to set this to a central location for every EA user.

682
In our environment we deploy the MDG not on user base but on amodel base, to ensure that everyone working on a certain model, is using the same version. So loading the mdg is a "one shot" activity and nobody needs to take care that there is the right mdg on the local machine.

You don't have to deploy the MDGs to the local machine.  Do you deploy keys to the local machine, so why would you do MDGs that way?

683
Bugs and Issues / Re: HasTag anomalies
« on: May 11, 2016, 08:22:50 am »
The HasTag(tagname) query method ONLY evaluates to true if the tag has a value, not if it just exists.  Which I submit is contrary to the documentation:
"Evaluates to true if the associated element has a tag with the name tagname."

To be a pedant it doesn't exist if it is null, the only thing that exists is a descriptor.  Null has been described as the worst mistake in computer science, and the arguments for that position all seem to be true.

Quote
Perversely, HasTag(tagname,””) will  fire if the tag has an empty (null) value or EVEN if the tag does not exist, which again, I submit is contrary to the documentation:
"If the second parameter tagvalue is provided, the tag tagname must be present, and the value of the tag has to be equal to tagvalue for the method to evaluate to true."

Obviously does null equal null will evaluate as true.  See previous point about null.


684
Bugs and Issues / Re: Stereotype in MDG
« on: May 11, 2016, 08:14:54 am »

685
I am quite sure that SQL server is not involved in that.
It is only somehow a problem with ADS and the internal EA security, using the windows authentication.
The thing is, that the users are logged in there machine with their account. So local IT may argue “login works” and therefore it is an EA problem.
This is why I am looking for something that might show that a request involved in the authentication needs e.g. too long.

Which is why you have to test from the client that's failing.  There's all sorts of things that it could be, from the client's DNS having a partial SRV record to token bloat to a routing problem.

686
General Board / Re: Incorporate Model Templates Problem
« on: May 11, 2016, 06:54:30 am »
I'm not sure what the consternation is. Put the model XML files in the same directory as the MDG file.  It's always worked for me.

That doesn't really work if you import the MDG in the model (because then there is no directory).

Importing an MDG in a model is ideal in terms of deployment in case you have a large corporate environment with a limited number of central database repositories.

I've never found it ideal.  I always set up a shared directory with directories for Sparx additional MDGs and custom MDGs under it.  This allows me to have the majority of users running a stable release and a small group of users running what ever I last generated.  It also allows me to distribute the MDG ahead of the models, or evolve models without re-generating the MDG.

687
From the Help topic that you refer to:

  • location: The path of the XML file that contains the XMI export of the model template Package, relative to the location of the MDG Technology file; if the XMI file is in the same folder as the technology file then this just contains the file name

I remember when that was an undocumented secret passed from MDGer to MDGer.

688
However the template file is expected to be deployed in the EA installation folder.

Nope.  Same directory as the MDG file.

689
Yes, but I am looking for something what enables me to activate my local or indian IT.
Some kind of log that in best case indicated who is not responding.
Far too often I got feedback that all works find for each party but it does not work as a whole.

What you describe is a Kerberos authentication failure between the client PC and the MSSQL database.  The why depends on what your underlying network and AD topology is.  The people having the failure should be logging a call with their local support, as root cause analysis has to start from their end and work back to the SQL server.

690
General Board / Re: Incorporate Model Templates Problem
« on: May 10, 2016, 07:33:32 am »
I'm not sure what the consternation is. Put the model XML files in the same directory as the MDG file.  It's always worked for me.

Pages: 1 ... 44 45 [46] 47 48 ... 73