New Project

The New Project command (accessible from the home page of the project explorer as well as the administrative tools) allows you to create a new project. Each project in CORE represents a separate namespace with its own schema, data, settings, and access control.

When creating a new project, you must specify:

• Name - the name for the new project. The project name uniquely identifies a project and must be unique within a repository. If you are connected to a remote repository using CORE Server, you may have a local project and a remote project with the same name. However, you cannot have two projects with the same name either within your local repository or on the server. Though CORE maintains a unique ID for each project, CORE does enforce project name uniqueness to avoid user confusion.
• Permission Level - to provide you with the appropriate level of control over each project, you have the opportunity to specify the granularity of access control when you create a new project. Specifying the permission level is a trade-off – a finer level of granularity provides a lower-level of control over access but requires more effort to manage that control. CORE provides three different schemes from which to choose.

• • Coarse - this defines access control only at the project level. Users are granted permission to read, write, etc the project, and these permissions control access to all elements. Under this scheme, there is no capability to limit access to an individual element or attribute.

  • Medium - this defines access control at the project and element level. In addition to the permissions specified for the project, permissions are specified for each element. This permits global control via the project permissions with finer control via the element permissions. Under this scheme, there is no capability to limit access to an individual attribute. This is the recommended permission level for most projects.

  • Fine - this defines access control at the project, element, and attribute level. This provides a very fine level of control with the ability to grant or deny access to individual attributes. This scheme is recommended only for those projects where there is a known need to prevent users from reading or changing specific attributes.

• Baseline Schema - the initial set of classes, relationships, attributes, facilities, and perspectives. Vitech provides base schemas tailored for systems engineering efforts as well as DoDAF projects. In addition to the latest versions of theses schemas, previous baseline schemas are included for legacy support and project migration purposes. When creating a new project, you can select the schema that best matches the needs and purposes of the project. You can then extend the schema as desired.

• Enable Versioning - if versioning is enabled, as attribute values evolve throughout the life of a project, CORE will track the values over time for those attributes marked for tracking. This setting can be changed at any point during the life of a project.

• Enable Audit Logs - if audit logging is enabled, CORE maintain a basic textual log of all changes made to an element and stores it in the element's audit log attribute. This setting can be changed at any point during the life of a project.

• Repository - the repository indicates where the project definition and data will be stored. If you are connected to a remote repository on a CORE Server, you have the option of creating the new project in that repository. Whether or not you are connected to a remote repository, you may create the project in your local repository.

What permissions are required to create a project? To create a project, you must have create project privilege which is defined on the individual user account. Because of the utility of projects as independent workspaces to explore design alternatives and sandbox solutions, it may be desirable for each user to have the create project privilege.