Project Preferences in CORE

Everyone has their own individual preferences, especially when it comes to graphics – sizing, coloring, icon templates, and more. While we each have our own personal style, projects want the output from our team to be graphically consistent and cohesive. To help project teams deliver a common graphical style, CORE 9 moved the diagram preferences from per-user settings to Project Preferences available from the Project command. Here, teams can establish common defaults for all diagrams that are shared across the team. Individuals still have the flexibility to style individual diagrams, but that’s flexibility within a common framework.

Project preferences are exported as part of the project backup (for archival purposes) and project template (for establishing initial settings for a new project).

The project preference categories include:

• COREsim

• Diagram

• General

• Activity Diagram (available in CORE Spectrum)

• Block Definition Diagram  (available in CORE Spectrum)

• Class ER Diagram

• Class Spider Diagram

• ER Diagram

• FFBD & EFFBD

• Hierarchy Diagram

• IDEF0 Diagram

• Interface Block Diagram

• Interface N2 Diagram

• Internal Block Diagram (available in CORE Spectrum)

• N2 Diagram

• Package Diagram (available in CORE Spectrum)

• Physical Block Diagram

• Physical N2 Diagram

• Requirements Diagram (available in CORE Spectrum)

• Schema Matrix Views

• Sequence Diagram (available in CORE Spectrum)

• Spider Diagram

• State Transition Diagram (available in CORE Spectrum)

• Use Case Diagram (available in CORE Spectrum)

Available Preferences CORE Essentials provides a complete model-based systems engineering (MBSE) development solution including traditional systems representations but does not include the full library of views available in CORE Spectrum. If you are licensed for CORE Essentials, you will only see the categories corresponding to the views available in CORE Essentials.

What permissions are required to edit project preferences? To edit any project preferences, you must have administrator permission for the project. All users with read access to a project can view the project preferences, but only project administrators can change the preferences.