"Local" Structure101 Studio projects (.hsp files) are the master.

Local projects store the settings (data file, granularity, etc.) required to construct the models, plus any artifacts (actions, specs, etc.) that you may have created for your project. The structural data itself is not saved - it will be recreated the next time the project is opened, including any changes that were made in the meantime. As such, local projects are transient - they show how the code is structured today, on your machine, but they have no notion of yesterday. Local projects are typically shared with the team (and Build) via the version control system (e.g. git), often committed with the source code.

To maintain history as your project(s) evolve over time, Structure101 has repositories. Structure101 repositories can store their data in:

A Structure101 repository is organized into a collection of projects, each containing a number of complete snapshots of a project's structure, artifacts, metrics, rules and Build results at a given point in time. This means that it is possible to open a snapshot (in any Structure101 component) without access to the underlying code. Moreover, as soon as a project contains more than one snapshot, it becomes possible to perform structural differencing to see what has changed - structurally - between the current and an older version. It is also possible to view the repository through the Dashboard or the Soda Dependency Database to see how the various structural measures have changed over time.

To get started/setup with a Structure101 Soda Dependency Database repository manually see here, or using Docker see here; for cloud-based storage see here, or for filesystem storage see here.

For more information on how projects and repositories can be used, see workflows.

Tip:

Within Structure101 Studio repository commands are on the right of the main toolbar: