how to create a requirements specification template that can be reused across projects?
2 answers
However, you can do it by using the Project Template. Basically, create a project template from the project containing the artifact templates, with the Artifact Template option selected (and others if appropriate), then you can create new projects based on this project template and they will have the requirement templates built in.
If you want to add new templates to existing projects, there seems to be no easy way.
Is it your intention to have a set of requirements that are re-used as a foundation for new projects, like branching off a trunk in git? Or to have a structure of folders and modules with header hierarchies defined to be used to start new projects?
Comments
The idea is that there are certain requirements that are common to every project.
Then I would recommend the following:
If you're using the common requirements in a separate project area, you can use the template option described above, although you lose the ability to have changes made to common reflected in your other project area(s). It's a true "clone and own" scenario.
If you're using the common requirements in the same project area, and you're using DNG pre-v6, you can re-use (artifacts can exist in multiple modules or collections) the common requirements. Then when changes (attributes only... links, tags, and comments are context specific, although these changes to base artifacts can be seen in module or collection contexts) are made to common they are reflected in all their instances.
If you're using the common requirements in the same project area, and you're using DNG v6+, you can create work streams, which act like branches in git. Then you can branch from a trunk of common, and merge trunk changes to the branch or vice versa.