Messages

1

General Board / Re: Expose multiple model root nodes to prolaborate/ multiple designs in one EA repo

« on: December 21, 2022, 09:41:26 pm »

Thanks a lot!
Prolaborate support xpalined what to do.

See
For your information, the root node and packages of the EA model are managed in Sections of the Prolaborate(Menu > Sections). Please refer to the section “Manage Sections” in the below link for more information.
https://prolaborate.sparxsystems.com/resources/documentation/access-permission

2

General Board / Expose multiple model root nodes to prolaborate/ multiple designs in one EA repo

« on: December 16, 2022, 01:01:30 am »

Hi

We are using Prolaborate and Pro Cloud Server to host and share our EA repositories.
What I wnated to make now is one shared EA project that can contain multiple smaller designs.
Threfore i created for each design a "Model root" node and below that I added the specific designs.
My problem is now that i only see the default "Model root" node (the one that has the smal red edge as additional symbol) in prolaborate when I export the project.

This are the web ea settings I use:

[model5 : settings]
sscs_protocol = "http"
sscs_server = "localhost"
sscs_port = "1804"
sscs_db_alias = "DNB Shared Repo"
auth_code = ""
default_diagram = ""
show_discuss = "true"
add_discuss = "true"
participate_in_reviews = "true"
edit_object_notes = "true"

So my question, is there a way to share multiple "Model root" nodes in prolaborate?
Or what would be the best way to have multiple designs in one project?
What can you recommend? The designs should not interfeer with each other.

Regards

3

Uml Process / Re: Operations in instances of Components

« on: November 19, 2022, 01:59:05 am »

Hi

Thanks for the hints.
Simple said - what I wanted to represent is the relation / information between 2 instances of the same servie, which i drafted as component.


>That shouldn't be an argument, since a Component is a specialization of Class.
I also agree to that. And that was exactly also my assumption, that a intance of a coponent behaves like an instance of a class. Means I would assume i see all the methods of the parent.

Regards

4

Uml Process / Operations in instances of Components

« on: November 17, 2022, 02:51:18 am »

Hi

In my current high level component diagrams, I had to use multiple instances of one component, to visualize a data flow.
For this I created a new instance of the original component by dropping it on the diagram and selected "add as instance". I created data flows etc and everything worked fine.
I also wanted to create a sequence diagram, trying to explain the call sequencens. There I figured out that in the messages I can select operations, I have created in the original component. But these methods are not available in the instances of the component.
Shouldnt the methods be also avialable there?

If I drop the component into the sequence diagram and add it there as lifeline. The methods are available.
Means:
- an instance created in a component diagram, does not support the methods in sequence diagram.
- an instance created in a sequence diagram, does support the methods in sequence diagram.

This sounds odd to me. I am using EA 15.2

5

General Board / Way to automatically represent connectors as port in child diagram

« on: August 20, 2020, 11:46:17 pm »

Hi

Assume I have an UML diagram with two components - A and B. A and B have a data flow connector means they exchange data over an interface.
If I want to refine now the components - I add a child component diagram that represents now for example component A.
I am wondering whether there is a way to automatically represent a data flow connector as Port or Interface within this child diagram?


Regards

6

General Board / Re: Disable Feature, Author and Type in Backlog Management Diagram

« on: December 11, 2019, 02:55:34 am »

THANKS a lot sunshine - this was exactly what I was looking for......

>To change appearance you need to right click on diagram and click on Kanban. A Kanban dialog should appear on which you select appearance. From there you can pick and choose whether fields appear on the diagram by clicking in the select boxes.

This did the job.

7

General Board / Disable Feature, Author and Type in Backlog Management Diagram

« on: December 09, 2019, 09:25:06 pm »

Hi

I wanted to create some kind of ToDo List in EA. I found that the Backlog Management Diagram would perfectly fit my needs.
But in the graphical view the Author, Status and Type of the Element uses a lot of space.

These properties I want to hide in the graphical view but cant find a way.

Anyone has any good suggestions?

And how to upload an image in this Forum?

8

General Board / Re: Query all requirements from component

« on: July 29, 2019, 09:39:59 pm »

Figured something out like:

select t_object.Name, t_objectrequires.Requirement
from  t_diagram,
      t_diagramobjects,
     t_object,
     t_objectrequires
where t_diagram.Name = 'Building BLock View'
and t_diagram.Diagram_ID = t_diagramobjects.Diagram_ID
and t_diagramobjects.Object_ID = t_object.Object_ID
and t_object.Object_Type = 'Component'
and t_object.Object_ID = t_objectrequires.Object_ID

But whats the best way to represent this in the diagram? I used now a Model View - is there a better way?

9

General Board / Re: Query all requirements from component

« on: July 29, 2019, 08:52:41 pm »

Thanks for the answer @qwerty.
Do you have any tutorial etc.. you could share with me regarding this topic?
I am completely new to scripting in EA.

10

General Board / Query all requirements from component

« on: July 29, 2019, 07:47:44 pm »

Hi

I am trying to figure out a way how I can extract requirements from all components in a component diagram into some kind of legend.
Means in the dedicated component I want to configure their requirements/responsibilities.

At the bottom of the diagram i want to have some kind of legend which gets the requirements automatically from the components.
I a format like:

Component_1: Requirement_1
                      Requirement_2
Component_2: Requirement_3
                      Requirement_4