Messages

1

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.

Geert

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

2

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.

Thanks,

Matthias

3

Automation Interface, Add-Ins and Tools / Re: UML Elements for MDG Toolbox

« on: October 08, 2018, 08:41:20 pm »

•   UCExtend (Extend)
•   UCInclude (Include)

Isn't that what you are looking for?

Geert

Yes!

How could i look over that...

4

Automation Interface, Add-Ins and Tools / Re: UML Elements for MDG Toolbox

« on: October 08, 2018, 07:26:11 pm »

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

5

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
•   Abstraction
•   Aggregation (Aggregate)
•   Assembly
•   Association (Associate)
•   AssociationClass (Association Class)
•   CallFromRecursion (Call)
•   CommunicationPath (Communication Path)
•   Composition (Compose)
•   Connector
•   ControlFlow (Control Flow)
•   Delegate
•   Dependency
•   Deployment
•   Extension
•   Generalization (Generalize or Inheritance)
•   InformationFlow (Information Flow)
•   InterruptFlow (Interrupt Flow)
•   Invokes
•   Manifest
•   Message
•   Nesting
•   NoteLink (Note Link)
•   ObjectFlow (Object Flow)
•   Occurrence
•   PackageImport (Package Import)
•   PackageMerge (Package Merge)
•   Precedes
•   ProfileApplication (Application)
•   Realization (Realize or Implements)
•   Recursion
•   Redefinition
•   Representation
•   Represents
•   RoleBinding (Role Binding)
•   SelfMessage (Self-Message)
•   Substitution
•   TagValAssociation (Tagged Value)
•   TemplateBinding (Template Binding)
•   TraceLink (Trace)
•   Transition
•   UCExtend (Extend)
•   UCInclude (Include)
•   Usage
•   UseCaseLink (Use)


Element names for Toolbox Page definitions
•   Action
•   ActionPin
•   Activity
•   ActivityFinal (Final)
•   ActivityInitial (Initial)
•   ActivityParameter
•   ActivityPartition (Partition)
•   ActivityRegion (Region)
•   Actor
•   Artifact
•   AssociationElement (Association)
•   Boundary (for Use Cases)
•   CentralBufferNode (Central Buffer Node)
•   Change
•   Choice
•   Class
•   Collaboration
•   CollaborationOccurrence (Collaboration Use)
•   Comment (Note)
•   Component
•   Constraint
•   Datastore
•   Decision
•   DeploymentSpecification (Deployment Specification)
•   Device
•   DiagramLegend (Diagram Legend)
•   DiagramNotes (Diagram Notes)
•   DocumentArtifact (Document Artifact or Document)
•   Entity (Information)
•   EntityObject (Entity)
•   EntryPoint (Entry)
•   Enumeration
•   ExceptionHandler (Exception)
•   ExecutionEnvironment (Execution Environment)
•   ExpansionRegion
•   ExitPoint (Exit)
•   Feature
•   FinalState (Final)
•   FlowFinalNode (Flow Final)
•   ForkJoinH (Fork/Join - Horizontal)
•   ForkJoinV (Fork/Join - Vertical)
•   Gate (Diagram Gate)
•   GUIElement (UI Control)
•   HistoryState (History)
•   Hyperlink
•   InformationItem (Information Item)
•   InitialState (Initial)
•   InteractionFragment (Fragment)
•   InteractionState (State/Continuation)
•   Interface
•   InterruptibleActivityRegion
•   Issue
•   Junction
•   Lifeline
•   MergeNode (Merge)
•   MessageEndPoint (Endpoint or Message Endpoint)
•   MessageLabel (Message Label)
•   Metaclass
•   Node
•   Object
•   ObjectBoundary (Boundary)
•   ObjectControl (Control)
•   ObjectEntity (Entity)
•   Package
•   PackagingComponent
•   Part
•   Port
•   Primitive
•   PrimitiveType
•   Process
•   Profile
•   ProvidedInterface (Expose Interface)
•   ReceiveEvent (Receive)
•   Requirement
•   RobustBoundary (Boundary)
•   RobustControl (Control)
•   RobustEntity (Entity)
•   Screen
•   SendEvent (Send)
•   SequenceBoundary (Boundary)
•   SequenceControl (Control)
•   SequenceEntity (Entity)
•   Signal
•   State
•   StateMachine (StateMachine)
•   StateTimeLine (State Lifeline)
•   Stereotype
•   StructuredActivity (Structured Activity)
•   SynchState (Synch)
•   Table
•   Terminate
•   TestCase (Test Case)
•   Text
•   UseCase (Use Case)
•   UMLBoundary (Boundary)
•   ValueTimeLine (Value Lifeline)

6

General Board / Re: Versioning with composed components

« on: July 04, 2018, 05:16:52 pm »

Paulo,

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

7

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:
https://imgur.com/7S1rzYh

8

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?

9

General Board / Re: How to model an API architecture

« on: June 01, 2018, 06:14:12 pm »

No one?

10

Automation Interface, Add-Ins and Tools / EAI Patterns

« on: May 31, 2018, 07:37:22 pm »

Does anyone know if there's an MDG available to model EAI patterns?

11

General Board / How to model an API architecture

« on: April 11, 2018, 10:04:25 pm »

I search some examples of the modelling of an API architecture in EA. Starting from the canonical/logical data model, over inner API's to consumer API's and the front-end.

The intention is to describe a layered design:

- Front-end (HTML5 /JS)
- Consumer API
- Consumer Java code
- Inner API
- Inner Java code
- ESB
- Legacy System
- Database

The data model is located between the ESB and the Inner Java Code, because the ESB will translate the legacy data to the new data model that will be accessed through the API's. For each attribute we have to keep track of the source attribute, in order to create a mapping table afterwards.

12

Uml Process / AS400/RPG to Java API migration

« on: April 07, 2018, 05:34:54 pm »

In our company we have a monolithic as400 system with a DB2 database. The long term plan is to migrate everything to a new service oriented Java API platform.

The architectural plan is to expose the necessary RPG Routines as SOAP Web Services (1 on 1), and then transform them to REST services with the help of IBM Integration Bus. The REST services must already be based on the new data model. On top of the IIB layer we will create a Java API layer (with API Connect above) to provide data to the consumer applications. In fact, we will do SOA/API.

The problem is that the whole project approach is bottom-up, we do not have any contact with the business, only with the AS400 analyst/developers (dinosaurs  .

One of the steps in the whole plan is to create use cases, use cases that will be used to create the granularity for the API's. So, my question is, what is the best approach to create use cases, bottom up, from AS400 RPG routines?

13

Automation Interface, Add-Ins and Tools / Generate data model subset + JSON

« on: December 22, 2017, 02:19:03 am »

With the Message Composer from Geert Bellekens it's possible to create a subset from the canonical data model.
But if you want to generate JSON files you have to run the Schema Composer and create a new schema from that subset.

Is there a solution to do this in a simple way: create subset + generate json file?

Thanks

14

General Board / Re: Associations & the Schema Composer

« on: May 12, 2017, 03:17:29 am »

Thanks Geert!

15

Automation Interface, Add-Ins and Tools / Re: JSON Importer?

« on: May 11, 2017, 11:59:40 pm »

Paolo, what's the status about this?

I'm dealing with the same problem