Repository Structure

Depending on whether you follow an Agile or Waterfall approach, you would set up your Repository accordingly. We either way recommend creating Component folders And within those, you will place your section folders.

Have a component folder that includes templates and references. Template folders contain sample structures with your naming conventions that you can reuse as you add new components to your Tosca project.

Have a Component folder that includes content that is relevant for all projects. That would be Libraries and Modules for example. 

Have one component folder for each project. Within the folder, use the project name and the Requirements, TestCaseDesign, TestCases, Execution and Module folders.

It is also important to define an appropriate naming convention throughout these folders. 

Four Prinicipals 

1. InWork
2. Ready for Approval
3. Approved/ Completed

New aertifacts should only be created within "In Work" folders and then moved to "Ready for approval" folders. 

As soon as they're approved by someone else, they can be moved into the "Approved" folders where they can be used.

Additionally "In Work"  and "Ready for approval" should include one folder for each Tosca user.

Applying those Best Practices when working with Tosca will ensure easier maintenance, greater efficiency and higher readability. 

By following these Best Practices, you will ensure a consistency throughout your project, better readability and communication. And that's not only within your team, but also other business stakeholders.