It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,114
×5,943
×1

question asked: May 11 '16, 12:34 p.m.
question was seen: 2,041 times
last updated: May 13 '16, 2:33 a.m.

Related questions

how to create a requirements specification template that can be reused across projects?

0
John Lambe (13●1●2) | asked May 11 '16, 12:34 p.m.
How can we create global requirements that apply to every project?. Create a separate project with the global requirements and link to the project.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered May 12 '16, 1:09 a.m.
You can't "link" a project to any other project for this purpose.

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.
0
permanent link
Koak Lodge (156●2●10) | answered May 12 '16, 3:52 a.m.

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
John Lambe commented May 12 '16, 4:47 p.m.

The idea is that there are certain requirements that are common to every project.

Koak Lodge commented May 13 '16, 2:33 a.m.

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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.