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

Pages: [1] 2 3 ... 6
Automation Interface, Add-Ins and Tools / Re: VBScript OpenFileDialog
« on: January 17, 2019, 07:28:03 pm »
It works, thx!

Automation Interface, Add-Ins and Tools / Re: VBScript OpenFileDialog
« on: January 17, 2019, 12:50:58 am »
I always get 'ActiveX component can't create object: 'MSComDlg.CommonDialog'.

Automation Interface, Add-Ins and Tools / VBScript OpenFileDialog
« on: January 16, 2019, 06:35:44 pm »
I'm trying to create an openFileDialog in VBScript, but it gave an error?
Code: [Select]
dim openFileDialog
set openFileDialog = CreateObject("MSComDlg.CommonDialog")

Automation Interface, Add-Ins and Tools / Re: EAI Patterns
« on: December 08, 2018, 01:33:15 am »
Yes, the Add-in designed to extend the capability of Enterprise Architect to allow the creation of Enterprise Integration Pattern (EIP) models is available here:
Thanks a lot, this is very helpful!

In my toolbox profile I wrote the following into my diagram notes:
Alias=Activity;Notes=The toolbox for the activity diagram;

But when I save this toolbox profile with EA 14 (Design > Diagram > Edit > Advanced > Safe as Profile...), EA doesn't save the alias and notes into the xml file.
Is this a bug in EA 14, or am I doing something wrong?

In which property of the Stereotype or Metaclass could you configure the default notation kind for an action?

General Board / Re: Auto creation of a composition with ArchiMate
« on: October 11, 2018, 11:27:48 pm »
No, it doesn't.
You'll have to write a little script or add-in if you want to do that.


I remember that there was something like 'make composite' in a previous version, or am I wrong?

General Board / Auto creation of a composition with ArchiMate
« on: October 11, 2018, 10:55:23 pm »
Does EA has a feature that automatically creates a composition if you drag an ArchiMate element into another ArchiMate element?
E.g. a business process into a business proces.




   UCExtend (Extend)
   UCInclude (Include)

Isn't that what you are looking for?



How could i look over that...

And how can I put these stereotyped associations into my toolbox?

Automation Interface, Add-Ins and Tools / UML Elements for MDG Toolbox
« on: October 08, 2018, 06:05:08 pm »
I want to fill my Toolbox with some UML elements. The standard UML elements are listed below, and I can add them to the toolbox by adding them as an attribute
to the stereotype.

e.g. UML::Actor for an Actor.

But what can I use to represent a 'Use' or an 'Include' association on a use case diagram? Is there a list available of ALL (not just UML) elements and relationships that I can add to the toolbox?

Connector names for Toolbox Page definitions
   Aggregation (Aggregate)
   Association (Associate)
   AssociationClass (Association Class)
   CallFromRecursion (Call)
   CommunicationPath (Communication Path)
   Composition (Compose)
   ControlFlow (Control Flow)
   Generalization (Generalize or Inheritance)
   InformationFlow (Information Flow)
   InterruptFlow (Interrupt Flow)
   NoteLink (Note Link)
   ObjectFlow (Object Flow)
   PackageImport (Package Import)
   PackageMerge (Package Merge)
   ProfileApplication (Application)
   Realization (Realize or Implements)
   RoleBinding (Role Binding)
   SelfMessage (Self-Message)
   TagValAssociation (Tagged Value)
   TemplateBinding (Template Binding)
   TraceLink (Trace)
   UCExtend (Extend)
   UCInclude (Include)
   UseCaseLink (Use)

Element names for Toolbox Page definitions
   ActivityFinal (Final)
   ActivityInitial (Initial)
   ActivityPartition (Partition)
   ActivityRegion (Region)
   AssociationElement (Association)
   Boundary (for Use Cases)
   CentralBufferNode (Central Buffer Node)
   CollaborationOccurrence (Collaboration Use)
   Comment (Note)
   DeploymentSpecification (Deployment Specification)
   DiagramLegend (Diagram Legend)
   DiagramNotes (Diagram Notes)
   DocumentArtifact (Document Artifact or Document)
   Entity (Information)
   EntityObject (Entity)
   EntryPoint (Entry)
   ExceptionHandler (Exception)
   ExecutionEnvironment (Execution Environment)
   ExitPoint (Exit)
   FinalState (Final)
   FlowFinalNode (Flow Final)
   ForkJoinH (Fork/Join - Horizontal)
   ForkJoinV (Fork/Join - Vertical)
   Gate (Diagram Gate)
   GUIElement (UI Control)
   HistoryState (History)
   InformationItem (Information Item)
   InitialState (Initial)
   InteractionFragment (Fragment)
   InteractionState (State/Continuation)
   MergeNode (Merge)
   MessageEndPoint (Endpoint or Message Endpoint)
   MessageLabel (Message Label)
   ObjectBoundary (Boundary)
   ObjectControl (Control)
   ObjectEntity (Entity)
   ProvidedInterface (Expose Interface)
   ReceiveEvent (Receive)
   RobustBoundary (Boundary)
   RobustControl (Control)
   RobustEntity (Entity)
   SendEvent (Send)
   SequenceBoundary (Boundary)
   SequenceControl (Control)
   SequenceEntity (Entity)
   StateMachine (StateMachine)
   StateTimeLine (State Lifeline)
   StructuredActivity (Structured Activity)
   SynchState (Synch)
   TestCase (Test Case)
   UseCase (Use Case)
   UMLBoundary (Boundary)
   ValueTimeLine (Value Lifeline)

General Board / Re: Versioning with composed components
« on: July 04, 2018, 05:16:52 pm »

Right, i can use compositions as an alternative for the nesting relationships, but my diagrams become spaghetti in that manner.  8)

General Board / Re: Versioning with composed components
« on: June 22, 2018, 05:59:44 pm »
Hi MatthiasEDV,
I am behind a firewall and cannot see you diagram, so maybe I do not understand you problem entirely.

In general for such things you have just two options:
To copy or not to copy.

If you do not copy, you need somehow a 130% model (having all) mounted together and you need some kind of attributes (e.g. tags) or other measures to mark what belongs to A only, what belongs to B only and what belongs to both.

Copying is not ideal, I do not prefer that solution.

Can you see this image:

General Board / Versioning with composed components
« on: June 22, 2018, 05:15:28 pm »
We model our integration architecture and API's with ArchiMate symbols. An API (ArchiMate_ApplicationService) is composed of some components (ArchiMate_ApplicationComponent)

- API (ArchiMate_ApplicationService)
  • Gateway (ArchiMate_ApplicationComponent)
  • Java Code (ArchiMate_ApplicationComponent)
  • Integration  (ArchiMate_ApplicationService)
  • AS400 Service  (ArchiMate_ApplicationService)
  • RPG Routine  (ArchiMate_ApplicationComponent)

Suppose there is a new version of the ESB Admissibility service that impacts the whole Admissibility API so we need to deploy a new version of that API. In the Admissibility API v2.0, we will use the new ESB Admissibility v2.0, but for all the other components we reuse the v1.0 versions. A big remark is that we will stil use the Admissibility API v1.0 besides the Admissibility API v2.0 for some implementations.

The v1.0 components that we will reuse in the Admissibility API v2.0, can't be duplicated in EA as parts of the two versions of the Admissibility API, and that's a big problem...
For example the Admissibility GW v1.0 must be a part of Admissibility API v1.0 and Admissibility API v2.0, how can we handle this?

General Board / Re: How to model an API architecture
« on: June 01, 2018, 06:14:12 pm »
No one?

Pages: [1] 2 3 ... 6