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 ... 62
Every single project (operational project 1, operational project 2...) could be assigned to a sub-node of the root node (operational projects). Do you know if these s

A standard package should be fine.  I also give everyone a sandpit area so they can play in a space easy to clean out.  Rather than having them trying different things inside a project where it can be very confusing to someone else later.

As far as 1..1 (1) relationships, they need to be confirmed but aren't, prima facie, wrong.  Incorrect 1..1 associations are a common newbie, mistake, but we are usually cured of that pretty quickly.

I try to tell my wife that, but will she listen?

Until v14's row-level access has been confirmed as viable.  Then maybe you can "hide" those confidential portions of the repository using that.

I still wouldn't use the same repository in that instance.  I've seen several instances of personal grievances claims made against an employer when staff felt they were not being consulted about restructuring.  If you keep the "pie in the sky" "what if" process modelling in a separate database to the "production" repository it is completely clear that the models are not in any official or approved.

In almost all cases I've seen the single repository setup was to be preferred.

The case where it is not is if your organisation is going to perform a significant process re-engineering which might result in job losses.  In this case it is best to clone your process models into a new repository with access only given to those staff working on the re-engineering.  This also allows the what-if models to be flushed away when the modelling is over.

General Board / Re: EA v14 Beta Crashes when opening
« on: March 09, 2018, 12:17:56 pm »
The error message looks to me like our code threw an exception. (Which could be intentional)

Three developers trying to claim responsibility for a crash, I think I may need a lie down.

General Board / Re: Replica conflict resolution help
« on: March 07, 2018, 12:07:19 pm »
Oh, and even in these days of gender neutrality, Athena was a Goddess, not a God.  ;)

True but the operative word was patron and she wasn't above disguising herself as a man.

General Board / Re: Replica conflict resolution help
« on: March 07, 2018, 08:28:13 am »
I thought this advice would be like carrying owls to Athens (German proverb).
Wear thick gloves?

The patron god of Athens is Athena, and Athena's sacred animal is an owl. 

I don't know Archimate well, but your wording is a bit suspect. Modifying a language is usually not a good idea. But extending it should well be possible by creating your own MDG based on Archimate.

Adding attributes and specialising elements is kosher according to Archimate .  But you're right, functionally a MDG that specialises the whole thing is probably best.  You could go as far as some people (Sunshine?) and create your own Archimate 3 MDG.

General Board / Re: Set the Default Diagram in EA13
« on: March 06, 2018, 07:44:42 am »
I didn't find where I can set my Default Diagram in EA13 the first open.

Right click on a diagram and choose set as user default diagram.

Model default is a bit hidden.  Lay out ribbon | Manage | Set as Model Default.  User Default is also there as well.

General Board / Re: Document a whole Solution
« on: March 05, 2018, 07:38:31 am »
Geert, if you use UML for everything you will have a fully integrated model, with consistent elements and artifacts from contextual down to physical and out of context... easier, more efficient and effective than mixing multiple notations.  IMHO UML works even better at contextual-conceptual-logical than at physical level (UML was originally developed to talk to people, and a failed attempt to shoehorn it into a programming language has damaged it quite a lot...)

I really should put my doing Archimate better with UML MDG together one of these days :-)

General Board / Re: Document a whole Solution
« on: March 02, 2018, 10:02:24 am »
As for the model organisation, I prefer abstraction layer before domain

The TOGAF content meta-model is by far the best part of TOGAF and is very useful for structuring "content".

Automation Interface, Add-Ins and Tools / Re: Importing Archi Models
« on: March 01, 2018, 10:36:36 am »
Is there an easy way to import Archi models?  One of our users has a few and we'd like to save him the trouble of recreating them in Sparx EA.  He still has access to Archi, so if we need special export he can do that.

In Archi : File | Export | Model to Open Exchange File....

In EA:  Find the import where ever it has been hidden in the version you are using :-)

General Board / Re: Document a whole Solution
« on: March 01, 2018, 10:11:40 am »
Well the answer to all that is "yes".

I think the entry point is you deciding the notation you are going to use.  At your finger tips you have UML, Archimate, and SysML.  Once you've made that choice you can ask some more specific questions.

General Board / Re: Model projects/meetings w ArchiMate
« on: February 27, 2018, 09:59:01 am »
I consider aggregation and composition hierarchical relationships. As far as I now, composition: the child dies with the parent, aggregation: the child can live without the parent. That is the reason I chose composition. Perhaps it's different with Archimate?

Archimate says that composition and aggregation are inspired by UML.  I'm not convinced that any one involved with creating Archimate has a very deep understanding of UML (or modern ICT for that matter).  The difference in Archimate between composition and aggregation is an element can only be in one composition set but can be in multiple aggregation sets.

As practically you could combine two meetings into one time slot where there are common points of interest I'd tend to go with aggregation.  Any cross over of related elements would be much less messy.

General Board / Re: Model projects/meetings w ArchiMate
« on: February 26, 2018, 01:42:22 pm »
Relationship between elements
Collaboration -> Collaboration: composition
My argument is that if CWIX ESC dies, all "instances", i.e. CWIX ESC 2018/9... dies as well.

I'm not sure about this die.  It's Archimate.  Literally the only way your model knows about time is if you relate a plateau element to another element in your model.

Pages: [1] 2 3 ... 62