Messages

1

Automation Interface, Add-Ins and Tools / Re: Import value from excel to enumerate type

« on: January 24, 2020, 07:48:32 pm »

Thanks a lot,

Regards

2

Automation Interface, Add-Ins and Tools / Import value from excel to enumerate type

« on: January 23, 2020, 07:47:01 pm »

Dear all,

We are importing an Excel file into a customised Stereotype with MGD Office Integration (EA v15). Customised Stereotype contains a Resolution property (tagged value) with is an enumeration type: {HR, MR, LR}.

We have an excel like this:

Sensor Name/Value
OPTA034 LR
OPTA035 MR
OPTA036 HR


We want to import the value column into the Customised Stereotype’s Resolution property (which is an enumerate) but it is imported as a string, not as an enumerate with a value.

Is any way to import it as enumerated value and not as string? Excel file can be re-formatted as needed.

Thanks in advance.

3

General Board / Increment Element version number automatically

« on: August 01, 2019, 05:21:06 pm »

Good Morning,

Is any way to increment Element version number automatically?



Thanks

4

General Board / Re: Mixing operational and development phases in the model

« on: May 01, 2018, 12:59:42 am »

Search the forum for TAM (time aware modeling) and its (in-)abilities to support what you're asking for.

q.

Thanks!

5

General Board / Mixing operational and development phases in the model

« on: April 30, 2018, 07:38:11 pm »

Hi,

I would like to ask you the best approach in order to mix operational and development phases in the model, that is, to model an operational system (operational phase) and its evolutions (development phase). We have an operational model of our operating system, but we would like to include in the model the evolutions/changes in the operational model which at this moment are not operational (development phase) but they will be operational in the future, therefore, that will be part of the operational model after some time. We do not want to duplicate effort. May it be done creating "branches" of our current operational model during the development phases and including them into the baseline in the operational phase?

We are using EA 13.5 and our repository is in a database. At this moment we are using the baseline functionality instead of the version control (is it true that Version Control can produce model inconsistencies in the long term?).

Thanks

6

General Board / Re: One repository and multiple projects vs one repository per project

« on: March 14, 2018, 10:21:33 pm »

Thank you very much for your feedback.

Kind Regards

7

General Board / Re: One repository and multiple projects vs one repository per project

« on: March 14, 2018, 12:28:35 am »

Hi all,

Thank you very for your comments. They are very useful.

We are are going to create two repositories in order to isolate operational projects from development projects. In this way, operational team and development team have different repositories. They are isolated at data-base level.

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 sub-nodes requires a special property or just a standard package is enough?

The operational repository contains several operational projects (sub-nodes) and they can be read by the whole operational team. Nevertheless, we need to restrict the write rights creating user groups in EA 13.5 to only certain sub-nodes. In this way, a group of users can only write in a group of projects but they can read everything in the repository (user group 1 can write in project 1 and project 2, user group 2 can write into project 3 only, etc...). I think this second security layer can be done via EA v13.5 security functionalities: https://www.sparxsystems.com/enterprise_architect_user_guide/13.5/team_support/usersecurity.html. Is it correct?

Thanks for your comments.

Kind Regards

8

General Board / Re: One repository and multiple projects vs one repository per project

« on: March 10, 2018, 01:41:46 am »

In almost all cases I've seen the single repository setup was to be preferred.
Just make sure you enable security with the option "Require user lock to edit". This will make the whole model read-only by default, which is usually enough to avoid accidental changes.

You can also add version control, but I would only do that if it is really worth the overhead.

In terms of performance the size of the database, or the number of concurrent users usually doesn't really matter that much. (Just don't use Oracle)

Geert

Thanks, Geert.

We are going to use SQL server 2014 for creating the database for the repository.

Kind Regards

9

General Board / One repository and multiple projects vs one repository per project

« on: March 10, 2018, 12:34:17 am »

Hi all,

We are going to create a new repository (DBMS) for EA 9. I would like to ask you what better approach is: one repository and multiple projects or one repository per project.

Our context is the following one. My department is planning to migrate our projects to Enterprise Architect (our current EA version is 12 Ultimate but an upgrade to 13.5 is scheduled). Our projects are large and complex and based on SysML. They can be grouped into operational projects and projects under-development. Additionally, there are elements that are common to all the projects, and therefore they should be shared between the different projects. After some time a project under development is moved from the under-development group to the operational group.

Each project is assigned to a different team. A team can only access to its project and to the common elements. All users are local.

We would like to use a database management system (DBMS) –specifically SQL server- to store the repository/repositories: (https://www.sparxsystems.com/enterprise_architect_user_guide/13.5/model_repository/upsizingtosqlserver.html).

Key points for us are:

• Integrity and preservation of the projects.
• Team working (concurrent access).
• Sharing elements between projects / Common elements.
• Version control / Baseline creation.
• Access rights for each project.
• Backup.
• Performance.
• Potential limitations (model size, database size, commit and merge limitations, etc…).

One repository in one database

What do you think that it is the best approach, one repository in one database for multiple projects or one database for each project?

Thank you very much.