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 2 3 [4] 5 6 ... 61
But at least we now have some reference data. It's like when I order from AliExpress or Banggood; I know it's going to take at least a month to get to me with free shipping.

Now I'm wondering whether banggood is safe to look at from work :-)

Icons in the Windoze world: The Diskette. I don't remember when Apple abandoned it, but it was probably the last millennium. I guess even the Windoze guys don't remember what the blue square is standing for. Still using that, though.

Circa 1998.  Before that they used to boast that their firm floppy was much better than floppy floppies.

But then again when was the last time you "dialled" anyone.  Millennials probably never have.  Language contains all sorts of apparently dead concepts.  Like why we call you lot Germans

General Board / Re: Relationship Matrix - hide empty "source"
« on: October 20, 2017, 11:22:53 am »
Just make the selection query MORE selective, only include those items with existing relationships.   But that's the "scenic" route, considering it should be a display option.

Well I already have to go and look in the Archimate MDG to find out what types to filter on.  I don't want to have to move my elements with relationships into different packages to the ones that don't.

The "customer" packages contain an actor for each agency who qualifies under a particular scheme, organised by agency type.  If I move them I ruin my list of qualifying agencies.  Qualification could be considered an attribute of customer but I have no need to model anyone who doesn't qualify so I'm happy that the package signifies qualifying.

Once they take up a service (product) I add the serving relationship.  Archimate doesn't allow for instances so by necessity I use the actor from the "scheme" portion of the model in the actualised portio of the model.

Quote from: Paolo F Cantoni
Pop in a Feature request!  It has my support!

I'll wait and see whether one of the Sparxians pops up with one of the "Do you know about this feature buried five steps down in this obscure menu".

Bugs and Issues / Re: Bug when copying package
« on: October 20, 2017, 09:17:09 am »
I know, my life would be so much simpler if you didn't.

If it's any consultation I spend a significant amount of my week harassing our product teams too about making features work for customers :-)

General Board / Re: Relationship Matrix - hide empty "source"
« on: October 20, 2017, 09:04:28 am »
Or is there another way I can visually depict Archimate 3 Product serving Archimate 3 Business Actor, in a way that is useful to export out of EA into a Word document or an email.

General Board / Relationship Matrix - hide empty "source"
« on: October 20, 2017, 08:54:42 am »
Can I create a relationship matrix where the rows displayed for source are only those where a relationship exists to one of the targets?

Alternatively can I only show source and target where a relationship exists?

Bugs and Issues / Re: Bug when copying package
« on: October 20, 2017, 08:52:25 am »
I could add the word "conceptually". Of course not all relationships have direction conceptually (eg. Association has two or more ends where each end can be owned by the association or the classifier) in which case you would need to use a different method to determine if adding it is changing each end. Some relationships aren't technically changing either end. (eg. Dependency is technically not changing either end, it's intentionally too abstract to have any concrete meaning)

Yes.  The point being we don't use your software conceptually.  We [mis]use it to do all sorts of horrible analysis of all sorts of horrible business problems.

Bugs and Issues / Re: Bug when copying package
« on: October 20, 2017, 08:12:06 am »
adding a relation to an element should be considered changing it as much as adding an attribute
Depends on the direction.
Depends on how the tool treats the relationship :-)  If it does something irrespective of the direction then the direction is absolutely irrelevant.

Bugs and Issues / Re: Test, Issue, Defect, Requirement dependencies
« on: October 20, 2017, 08:10:10 am »
It should also be noted that EA's requirements are a bit of a hack. There are requirement types, which can be configured in a project (meaning the configuration is stored in the project database) along with weights which are used in project estimation. The type is stored in the stereotype column of individual requirements, and that's where Sparx went wrong -- it should have been a tagged value.

In the last five years I seem to have become an architectural archaeologist doing anything from digging into running processes on servers to find applications and then mapping them back through users to organisational functions, or looking at deployed business services and trying to determine whether they align to the original requirements.

The functionality in EA could be incredibly useful to me with even a few simple changes.  Things like supporting the MoSCoW method as standard.  No "customer" of mine has ever cared about the priority and status fields.

I guess that is the reason why they developed the profile helper.
I'm lucky as I never had to work without it, so I never payed much attention to the actual resulting attributes.

I teach people to use it because rolling it all by hand you're much more prone to simple errors (such as spelling), especially if you fall somewhere on the dyslexia/dyscalculia spectrum.

General Board / Re: Sorting of a Model View?
« on: October 20, 2017, 07:54:14 am »
I have created a Model View which lists all elements of a specific stereotype but I am not able to sort the list in alphabetical order?

If your question is "Am I able to sort alphabetically in a model view" then I believe the answer will be "yes you can".  You'll need some kind of ORDER BY in the SQL statement.

General Board / Re: Non-visual associations
« on: October 20, 2017, 07:49:20 am »
Yes, it is important to be consistent about relationships.  There shouldn't be two kinds of relationships - those expressed by "magic" and those expressed visually.  We create visualisations for our "magic" relationships but hide them by default.

I'm pretty sure VKN's "solution" will cause those relationships to appear on any diagram with both ends of the relationship present, even where normally the relationship would normally be hidden when one element is embedded in the other.

I can't be bothered testing that to' :-)

Bugs and Issues / Re: EA clear the file. Now 's empty 0Ko
« on: October 17, 2017, 07:26:44 am »
(This is probably a furphy, but anyway.)
I recall that about a million years ago there used to be a problem with the Jet engine when the MDB file was stored on a network drive. I did a bit of a search through the forum but cannot find anything apropos. All I really can remember is that one symptom was "suddenly" empty mdb files.  It was not an EA problem, as I said it was something about the Jet engine. 
Anyway I would presume that by now that issue would have been resolved, so this is probably a furphy.

I wouldn't be surprised if that was still an issue.  MDB files are generally excluded in all of Microsoft's replication mechanisms like Offline files for exactly this reason.

Bugs and Issues / Re: EA clear the file. Now 's empty 0Ko
« on: October 16, 2017, 07:58:46 am »
Not being picky but just ignorant: where does Windoze store the creator in file attributes? I can only see Size, Created/Modified/Accessed and R/W.

My crystal ball doesn't tell me what version of Windows you're using or which of the approximately 5 local file systems it supports.  Or if you're looking at a network drive how good the underlying implementation of CIFS is :-)

But in general some metadata will be in the Master File Table (MFT), some will be in meta-files and some in Alternate Data Streams (forks).

What you see depends on the exact file system, and Windows, OSX, and *NIX all implement the same concepts in different ways.

BTW what's the reason to have multiple items representing the same element on a diagram?

There is as much design that goes into a creating a view as goes into the underlying model.  There's a direct relationship between the number of times connectors cross and the difficulty in understanding what the view is trying to tell the viewer.

Sometimes you want the same element in different places on the page to untangle the birds nest.

Pages: 1 2 3 [4] 5 6 ... 61