Requirements Documents<\/h3>\n\nIn TopTeam<\/i>, all textual requirements go into a Requirements Document<\/i>. You can have one or more Requirements Documents<\/i>, each with their own set of Requirement Types<\/i>, in a project. A default Requirements Document<\/i> is automatically added to each project, you can either add requirements to the default Requirements Document<\/i> or add additional Requirements Documents<\/i>.<\/p>\n
Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document Editor<\/a>.<\/p>\n<\/div>\n<\/div>\n\nRequirement Types<\/h3>\n\nWhen you add a requirement in TopTeam<\/i> repository, it needs to be of a certain Requirement Type<\/i>. TopTeam<\/i> ships with a number of default Requirement Types<\/i> such as Business Requirements, Functional Requirements, Business Rules,<\/i> etc. However, if you need to enter specific Requirement Types<\/i> that are not available in the repository by default, you can create custom Requirement Types<\/i> and add them to Requirements Documents<\/i>.<\/p>\n<\/div>\n<\/div>\n\nEditors available for authoring and editing textual requirements<\/h3>\n\nTopTeam<\/i> provides several interfaces for editing requirements. Each editor provides a unique view of the requirements and is best used in a particular usage scenario. You should choose the appropriate interface depending on your current editing goals. The features of the different editors are explained below.<\/p>\n<\/div>\n<\/div>\n\n1. Repository Explorer<\/h3>\n\nRepository Explorer <\/i>provides access to all artifacts in the repository, including requirements.<\/p>\n
You can expand the Requirements Documents<\/i> node and then expand the desired Requirements Document <\/i>to access the requirements within that document. When you select a requirement on the repository node (left-side repository tree), the corresponding record (detail) editor displays on the right-side pane.<\/p>\n<\/div>\n<\/div>\n\n![\"wpid33101-media_1478596197626.png\"](\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\")
<\/div>\n<\/div>\n\nWhat is it used for?<\/h3>\n\nYou can add new, edit and delete requirements in Repository Explorer<\/i>. This interface is sufficient for basic requirements editing.<\/p>\n<\/div>\n<\/div>\n\nWhat it does NOT provide?<\/h3>\n\nYou cannot perform advanced requirements operations such as copying requirements from other projects, changing Requirement Type<\/i>, bulk edit of requirements attributes, etc. in Repository Explorer.<\/i><\/p>\n
For a more efficient, user-friendly and powerful interface for editing requirements, use the editors mentioned below.<\/strong><\/p>\nRefer to the video\u00a0demonstration Video \u2013 Getting Started with Repository Explorer<\/a>.<\/p>\n<\/div>\n<\/div>\n\n2. Requirements Tree Editor<\/h3>\n\nRequirements Tree<\/i> editor is a hierarchical spreadsheet-like editor for authoring and editing requirements and their attributes.
\nYou can also create custom Requirement Types<\/i>, for more information, refer to the How to define a new Requirement Type<\/a>.<\/p>\n<\/div>\n<\/div>\n\n<\/div>\n<\/div>\n\nWhat is it used for?<\/h3>\n\nRequirements Tree<\/i> is available in ribbon toolbar providing various features in different tabs. You can perform basic and advanced editing functions. You can also use Views<\/i> and Filters <\/i>to change or limit display respectively in the Tree.<\/i><\/p>\n
Use this editor when you need a concise hierarchical view of requirements, their status and other attributes. You can also perform simultaneous bulk editing of requirements attributes.<\/p>\n<\/div>\n<\/div>\n
\nWhat it does NOT provide?<\/h3>\n\nRequirements Tree<\/i> does not provide a single scrolling view that is available in Requirements Document View<\/i> editor (shown below).<\/p>\n
Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Tree<\/a>.<\/p>\n<\/div>\n<\/div>\n\n3. Requirements Document View Editor<\/h3>\n\nRequirements Document View<\/i> editor is similar to a Word processing editor for authoring and editing requirements.<\/p>\n<\/div>\n<\/div>\n\n<\/div>\n<\/div>\n\nWhat is it used for?<\/h3>\n\nYou can perform basic and advanced editing functions in Requirements Document Editor<\/i>. You can also use requirements filters to focus and view important requirements in Document View<\/i>.<\/p>\n
Use this editor when you need a single scrolling Word processor-like view of all the requirements within a document. You can perform in-place<\/i> editing<\/i> of requirements with the look and feel<\/i> of a Word processor.<\/p>\n<\/div>\n<\/div>\n\nWhat it does NOT provide?<\/h3>\n\nRequirements Document Editor <\/i> does not provide a spreadsheet-like view where you can view and edit attributes of all requirements.<\/p>\n
Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document View<\/a>.<\/p>\n<\/div>\n<\/div>\n\nSee Also<\/h3>\n\nHow to add a Requirement Type to a Requirements Document\/Project<\/a>
\nAuthoring Requirements in TopTeam<\/a><\/p>\n<\/div>\n<\/div>\n\n\nRevised: April 17th, 2020<\/p>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Requirements Documents In TopTeam, all textual requirements go into a Requirements Document. You can have one or more Requirements Documents, each with their own set of Requirement Types, in a project. A default Requirements Document is automatically added to each project, you can either add requirements to the default Requirements Document or add additional Requirements Documents. Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document Editor. Requirement Types When you add a requirement in TopTeam repository, it needs to be of a certain Requirement Type. TopTeam ships with a number of default Requirement Types such as Business Requirements, <\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[286],"class_list":["post-4764","post","type-post","status-publish","format-standard","hentry","category-requirements","tag-requirements"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/paoaNA-1eQ","_links":{"self":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/comments?post=4764"}],"version-history":[{"count":20,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764\/revisions"}],"predecessor-version":[{"id":49873,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764\/revisions\/49873"}],"wp:attachment":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/media?parent=4764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/categories?post=4764"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/tags?post=4764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
In TopTeam<\/i>, all textual requirements go into a Requirements Document<\/i>. You can have one or more Requirements Documents<\/i>, each with their own set of Requirement Types<\/i>, in a project. A default Requirements Document<\/i> is automatically added to each project, you can either add requirements to the default Requirements Document<\/i> or add additional Requirements Documents<\/i>.<\/p>\n
Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document Editor<\/a>.<\/p>\n<\/div>\n<\/div>\n When you add a requirement in TopTeam<\/i> repository, it needs to be of a certain Requirement Type<\/i>. TopTeam<\/i> ships with a number of default Requirement Types<\/i> such as Business Requirements, Functional Requirements, Business Rules,<\/i> etc. However, if you need to enter specific Requirement Types<\/i> that are not available in the repository by default, you can create custom Requirement Types<\/i> and add them to Requirements Documents<\/i>.<\/p>\n<\/div>\n<\/div>\n TopTeam<\/i> provides several interfaces for editing requirements. Each editor provides a unique view of the requirements and is best used in a particular usage scenario. You should choose the appropriate interface depending on your current editing goals. The features of the different editors are explained below.<\/p>\n<\/div>\n<\/div>\n Repository Explorer <\/i>provides access to all artifacts in the repository, including requirements.<\/p>\n You can expand the Requirements Documents<\/i> node and then expand the desired Requirements Document <\/i>to access the requirements within that document. When you select a requirement on the repository node (left-side repository tree), the corresponding record (detail) editor displays on the right-side pane.<\/p>\n<\/div>\n<\/div>\n You can add new, edit and delete requirements in Repository Explorer<\/i>. This interface is sufficient for basic requirements editing.<\/p>\n<\/div>\n<\/div>\n You cannot perform advanced requirements operations such as copying requirements from other projects, changing Requirement Type<\/i>, bulk edit of requirements attributes, etc. in Repository Explorer.<\/i><\/p>\n For a more efficient, user-friendly and powerful interface for editing requirements, use the editors mentioned below.<\/strong><\/p>\n Refer to the video\u00a0demonstration Video \u2013 Getting Started with Repository Explorer<\/a>.<\/p>\n<\/div>\n<\/div>\n Requirements Tree<\/i> editor is a hierarchical spreadsheet-like editor for authoring and editing requirements and their attributes. Requirements Tree<\/i> is available in ribbon toolbar providing various features in different tabs. You can perform basic and advanced editing functions. You can also use Views<\/i> and Filters <\/i>to change or limit display respectively in the Tree.<\/i><\/p>\n Use this editor when you need a concise hierarchical view of requirements, their status and other attributes. You can also perform simultaneous bulk editing of requirements attributes.<\/p>\n<\/div>\n<\/div>\n Requirements Tree<\/i> does not provide a single scrolling view that is available in Requirements Document View<\/i> editor (shown below).<\/p>\n Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Tree<\/a>.<\/p>\n<\/div>\n<\/div>\n Requirements Document View<\/i> editor is similar to a Word processing editor for authoring and editing requirements.<\/p>\n<\/div>\n<\/div>\n You can perform basic and advanced editing functions in Requirements Document Editor<\/i>. You can also use requirements filters to focus and view important requirements in Document View<\/i>.<\/p>\n Use this editor when you need a single scrolling Word processor-like view of all the requirements within a document. You can perform in-place<\/i> editing<\/i> of requirements with the look and feel<\/i> of a Word processor.<\/p>\n<\/div>\n<\/div>\n Requirements Document Editor <\/i> does not provide a spreadsheet-like view where you can view and edit attributes of all requirements.<\/p>\n Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document View<\/a>.<\/p>\n<\/div>\n<\/div>\n How to add a Requirement Type to a Requirements Document\/Project<\/a> Revised: April 17th, 2020<\/p>\n<\/div>\n<\/div>\n<\/div>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Requirements Documents In TopTeam, all textual requirements go into a Requirements Document. You can have one or more Requirements Documents, each with their own set of Requirement Types, in a project. A default Requirements Document is automatically added to each project, you can either add requirements to the default Requirements Document or add additional Requirements Documents. Refer to the video\u00a0demonstration Video \u2013 Getting Started with Requirements Document Editor. Requirement Types When you add a requirement in TopTeam repository, it needs to be of a certain Requirement Type. TopTeam ships with a number of default Requirement Types such as Business Requirements, <\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[286],"class_list":["post-4764","post","type-post","status-publish","format-standard","hentry","category-requirements","tag-requirements"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/paoaNA-1eQ","_links":{"self":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/comments?post=4764"}],"version-history":[{"count":20,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764\/revisions"}],"predecessor-version":[{"id":49873,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/4764\/revisions\/49873"}],"wp:attachment":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/media?parent=4764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/categories?post=4764"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/tags?post=4764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Requirement Types<\/h3>\n
Editors available for authoring and editing textual requirements<\/h3>\n
1. Repository Explorer<\/h3>\n
<\/div>\n<\/div>\n
What is it used for?<\/h3>\n
What it does NOT provide?<\/h3>\n
2. Requirements Tree Editor<\/h3>\n
\nYou can also create custom Requirement Types<\/i>, for more information, refer to the How to define a new Requirement Type<\/a>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
What is it used for?<\/h3>\n
What it does NOT provide?<\/h3>\n
3. Requirements Document View Editor<\/h3>\n
<\/div>\n<\/div>\n
What is it used for?<\/h3>\n
What it does NOT provide?<\/h3>\n
See Also<\/h3>\n
\nAuthoring Requirements in TopTeam<\/a><\/p>\n<\/div>\n<\/div>\n