Skip to end of metadata
Go to start of metadata

Projects are the basic work unit in arKItect. A project is for arKItect what a file is for most software tools. A project is the logical entity for saving your data. We do not believe that your project can be described in a simple file; arKItect projects are too complex. An arKItect project includes a meta-model consisting of types and filters as well as objects, diversity management and many other things. Technically speaking, projects are saved in a database on the Internet. They can be accessed by multiple users (provided that the users have been granted access to the project) in order to collaborate together. A project is the place where the actual work occurs.

The controls within a project are quite strong. Everything in the project is and will stay coherent. This is one of the greatest strengths of arKItect. If you have identified independent systems that your organization wants to model, we warmly recommend that you should create one project for each independent system. If for any reason you have to create links between projects, merge them or create two projects out of one, this is possible thanks to the open APIs of arKItect; it may, however, be a little painstaking.

The following pages will show you how to create your work project before we start working with the project content:

 

  • No labels