Versions Compared

Old Version 9

changes.mady.by.user user-32c71

Saved on

compared with

New Version 10

changes.mady.by.user user-32c71

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Content layer
id390840634
Content column
id390840638
Content block
id390840637
Excerpt

Modeling Tools*

ResourceRecommended
CPUIntel Core™ i5 or higher
RAM

16GB

The memory allocation for the modeling tool by project size:

Project Elements Count
(including used projects)		Allocated Memory 2
Earlier versions2021x and later 1
1.5 million1 million6GB
2.5 million2 million7GB
5 million3.5 million11GB
Info

The amount of required memory proportionally increases if working on multiple projects.

1 the project elements count is different due to the profiling data storing metamodel optimized in 2021x (decrease by 40-80% in SysML and UAF projects).

2 these memory requirements are indicative and may vary by project specifics.

The operations that require more memory (1, 2, and 3.5 million of 2021x project elements respectively):

  • UPDM migration to UAF - 10GB, 10GB, 36GB
  • Converting between UAF, DoDAF2, DoDAF, MODAF, NAF, NAF4 frameworks - 8GB, 9GB, 13GB
  • Element/Content History - 10GB, 15GB, 27GB
  • Project Merge - 11GB, 13GB, 21GB 3

3 strongly depends on the amount of detected changes between merged versions (in this case, the specified required memory is for merging projects with 1.5k changes in total).

Disk space

The recommended disk space for installation and configuration files is 3GB or more depending on used plugins, project type (local or server), and project size. In addition to this, large server projects require extra disk space for configuration files: 

Project Elements Count
(including used projects)		Disk Space
Earlier versions2021x and later
1.5 million1 million6GB
2.5 million2 million10GB
5 million3.5 million30GB
Info

The amount of required disk space proportionally increases if working on multiple projects.

Note: Element History and Content History features usage requires significantly more disk space due to intensive caching at the client-side.

Depending on the feature usage scenario (e.g., retrieving content history from old/distant project versions multiple times), the disk space might increase by up to 100GB.

Display resolution**Full HD (1920x1080) or higher
Operating Systems

Any Java SE 11-compatible operating system (Windows, Windows Server, Linux (RedHat/CentOS 7), Mac OS X).

Java Virtual Machine (JVM) versionJava version support


* MagicDraw, Cameo Systems Modeler, Cameo Enterprise Architecture

** 800x600, 1280x1024 display resolutions are compatible with a laptop or a projector.

Excerpt
Note
titleEarlier versions

Windows XP and earlier versions are not supported.
Mac OS 10.6 Snow Leopard and earlier versions are not supported.


FLEXnet License Server

Excerpt

For system requirements, refer to the Release Note of the specific version.


Teamwork Server

Note

Teamwork Server is discontinued beginning with version 2021x. Teamwork Cloud should be used instead. Learn more about migrating from Teamwork Server to Teamwork Cloud >>

ResourceMinimumRecommended
CPUPentiumTM 3, 800 MHzPentiumTM 4, 1.4 GHz or higher
RAM512 MB2 GB or more
Disk space***25 GB***1 TB or more***
Operating Systems

Any Java SE 8-compatible operating system (Windows, Windows Server 2019, Linux (RedHat/CentOS 7), Mac OS X).

Java Virtual Machine (JVM) versionJava version support
Note
For Unix platforms, XWindow server is required for starting Teamwork Server with GUI and Teamwork Server Console.


*** Use the formula to estimate the storage required for the Teamwork Server disk space.

Content block
id390840633

Related pages