Overview<\/h3>\n\nOften organizations who document product or application requirements maintain at least two levels of requirement types in separate documents. For example, the first document captures stakeholder’s perspective such as Business Requirements<\/i> and the second document contains Functional<\/i> and Non-functional Requirements <\/i>that are derived from the Business Requirements <\/i>defined in the first document. For deriving requirements, users need to refer to higher level (upstream) document requirements while creating lower level (downstream) requirements.<\/p>\n
To derive downstream requirements efficiently, users need to view details of upstream requirements which often exists in a separate document.<\/p>\n
TopTeam<\/i> provides a solution to this problem via Traceability Derivation OneView<\/i> feature. Traceability Derivation OneView <\/i>helps you to easily derive downstream requirements by simultaneously viewing details of upstream requirements.<\/p>\n
This document describes Traceability Derivation OneView <\/i>feature <\/i>and how it works.<\/p>\n<\/div><\/div>\n\nWho should read this?<\/h3>\n\n\n- TopTeam Users<\/li>\n<\/ul>\n<\/div><\/div>\n\n
Benefits<\/h3>\n\nTraceability Derivation OneView<\/i> makes the trace derivation process more efficient, saves time and reduces traceability errors in the following methods:<\/p>\n\n- View upstream document and simultaneously derive requirements in a downstream document.<\/li>\n
- The system automatically creates traceability between the upstream document requirements and derived downstream requirements, without the need of manually creating a trace link between requirements.<\/li>\n
- Additionally, you can also create traceability links in bulk between requirements of the two documents using drag-and-drop method.<\/li>\n<\/ul>\n<\/div><\/div>\n\n
How it works?<\/h3>\n\nTerminology<\/font><\/strong><\/p>\n\n- Source Document<\/strong>: OneView Document<\/i> from which you want to derive requirements. Typically this document contains a high level or upstream requirements. However, it is possible that a downstream document can be a source document <\/i>and you can create upstream links with the requirements in the downstream document.<\/li>\n
- Derived Document<\/strong>: OneView Document<\/i> where you want to create derived requirements.<\/li>\n<\/ul>\n<\/div><\/div>\n\n
1. Opening OneView Documents in Traceability Derivation Mode<\/h3>\n\nFirst, you have to open the Source <\/i>and Derived Documents <\/i>in Traceability Derivation Mode<\/i>. This feature helps you open the source<\/i> and derived documents<\/i> side-by-side on the screen. Typically the source<\/i> document<\/i> is displayed on the left-hand side and is in Read-Only<\/i> mode. The derived document <\/i>where you can derive requirements is displayed on the right-hand side.<\/p>\n
There are multiple methods to open Traceability Derivation OneView. Refer to the article, How do I open OneView Documents for Traceability Derivation<\/a>.<\/p>\nYou can also open the same OneView Document<\/i> as source<\/i> and derived<\/i> documents<\/i> in Traceability Derivation Mode<\/i>. Refer to the article, How to derive requirements within the same OneView Document using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n\n2. Identifying gaps<\/h3>\n\nYou can perform gap analysis using Traceability Derivation OneView<\/i>. Refer to the article, How to perform gap analysis using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n\n3. Deriving requirements<\/h3>\n\nYou can simply find and select the source document<\/i> requirements on the left-hand side and create the desired derived requirements on the right-hand side derived document<\/i>. The system automatically creates trace links between the selected requirements in the source document and the newly created requirements in the downstream document.<\/p>\n
Refer to the article, Creating derived requirements using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n\n\n![\"media_1523614078639-1-1-1-1-1-1-1.png\"](\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\")
\n<\/div>\n<\/p><\/div>\n\n4. Creating traceability links with existing requirements in a derived document<\/h3>\n\nAdditionally, if the requirement with which you want to create traceability link, already exists in the derived document<\/i>, you can simply drag-and-drop requirements from the source document<\/i> to the derived document <\/i>or vice-versa,<\/i> in order to create traceability links.<\/p>\n<\/div><\/div>\n\n\n\n<\/div>\n\nRefer to the article, Creating traceability links between records of OneView Documents using drag-and-drop method in Traceability Derivation OneView<\/a>.<\/p>\nIn this way, Traceability Derivation OneView <\/i>feature makes it easy for users to derive requirements efficiently and accurately.<\/p>\n<\/div><\/div>\n\nSee Also<\/h3>\n\nConfiguring Traceability Schema\/Rules for Record Types<\/a>
\nUsing Traceability Matrix<\/a>
\nUsing Traceability Derivation Matrix<\/a>
\nUsing Traceability Network Diagram<\/a>
\nUsing Multi-Level Traceability Report<\/a><\/p>\n<\/div><\/div>\n\n\nRevised: July 24th, 2018<\/p>\n<\/div><\/div>\n<\/p><\/div>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Overview Often organizations who document product or application requirements maintain at least two levels of requirement types in separate documents. For example, the first document captures stakeholder’s perspective such as Business Requirements and the second document contains Functional and Non-functional Requirements that are derived from the Business Requirements defined in the first document. For deriving requirements, users need to refer to higher level (upstream) document requirements while creating lower level (downstream) requirements. To derive downstream requirements efficiently, users need to view details of upstream requirements which often exists in a separate document. TopTeam provides a solution to this problem via <\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[113],"tags":[288,323],"class_list":["post-40771","post","type-post","status-publish","format-standard","hentry","category-oneview","tag-oneview","tag-traceabiity"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/paoaNA-aBB","_links":{"self":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771","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=40771"}],"version-history":[{"count":10,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771\/revisions"}],"predecessor-version":[{"id":43358,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771\/revisions\/43358"}],"wp:attachment":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/media?parent=40771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/categories?post=40771"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/tags?post=40771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Often organizations who document product or application requirements maintain at least two levels of requirement types in separate documents. For example, the first document captures stakeholder’s perspective such as Business Requirements<\/i> and the second document contains Functional<\/i> and Non-functional Requirements <\/i>that are derived from the Business Requirements <\/i>defined in the first document. For deriving requirements, users need to refer to higher level (upstream) document requirements while creating lower level (downstream) requirements.<\/p>\n
To derive downstream requirements efficiently, users need to view details of upstream requirements which often exists in a separate document.<\/p>\n
TopTeam<\/i> provides a solution to this problem via Traceability Derivation OneView<\/i> feature. Traceability Derivation OneView <\/i>helps you to easily derive downstream requirements by simultaneously viewing details of upstream requirements.<\/p>\n
This document describes Traceability Derivation OneView <\/i>feature <\/i>and how it works.<\/p>\n<\/div><\/div>\n Traceability Derivation OneView<\/i> makes the trace derivation process more efficient, saves time and reduces traceability errors in the following methods:<\/p>\n Terminology<\/font><\/strong><\/p>\n First, you have to open the Source <\/i>and Derived Documents <\/i>in Traceability Derivation Mode<\/i>. This feature helps you open the source<\/i> and derived documents<\/i> side-by-side on the screen. Typically the source<\/i> document<\/i> is displayed on the left-hand side and is in Read-Only<\/i> mode. The derived document <\/i>where you can derive requirements is displayed on the right-hand side.<\/p>\n There are multiple methods to open Traceability Derivation OneView. Refer to the article, How do I open OneView Documents for Traceability Derivation<\/a>.<\/p>\n You can also open the same OneView Document<\/i> as source<\/i> and derived<\/i> documents<\/i> in Traceability Derivation Mode<\/i>. Refer to the article, How to derive requirements within the same OneView Document using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n You can perform gap analysis using Traceability Derivation OneView<\/i>. Refer to the article, How to perform gap analysis using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n You can simply find and select the source document<\/i> requirements on the left-hand side and create the desired derived requirements on the right-hand side derived document<\/i>. The system automatically creates trace links between the selected requirements in the source document and the newly created requirements in the downstream document.<\/p>\n Refer to the article, Creating derived requirements using Traceability Derivation OneView<\/a>.<\/p>\n<\/div><\/div>\n Additionally, if the requirement with which you want to create traceability link, already exists in the derived document<\/i>, you can simply drag-and-drop requirements from the source document<\/i> to the derived document <\/i>or vice-versa,<\/i> in order to create traceability links.<\/p>\n<\/div><\/div>\n Refer to the article, Creating traceability links between records of OneView Documents using drag-and-drop method in Traceability Derivation OneView<\/a>.<\/p>\n In this way, Traceability Derivation OneView <\/i>feature makes it easy for users to derive requirements efficiently and accurately.<\/p>\n<\/div><\/div>\n Configuring Traceability Schema\/Rules for Record Types<\/a> Revised: July 24th, 2018<\/p>\n<\/div><\/div>\n<\/p><\/div>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Overview Often organizations who document product or application requirements maintain at least two levels of requirement types in separate documents. For example, the first document captures stakeholder’s perspective such as Business Requirements and the second document contains Functional and Non-functional Requirements that are derived from the Business Requirements defined in the first document. For deriving requirements, users need to refer to higher level (upstream) document requirements while creating lower level (downstream) requirements. To derive downstream requirements efficiently, users need to view details of upstream requirements which often exists in a separate document. TopTeam provides a solution to this problem via <\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[113],"tags":[288,323],"class_list":["post-40771","post","type-post","status-publish","format-standard","hentry","category-oneview","tag-oneview","tag-traceabiity"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/paoaNA-aBB","_links":{"self":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771","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=40771"}],"version-history":[{"count":10,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771\/revisions"}],"predecessor-version":[{"id":43358,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/posts\/40771\/revisions\/43358"}],"wp:attachment":[{"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/media?parent=40771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/categories?post=40771"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.technosolutions.com\/kb\/wp-json\/wp\/v2\/tags?post=40771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Who should read this?<\/h3>\n
\n
Benefits<\/h3>\n
\n
How it works?<\/h3>\n
\n
1. Opening OneView Documents in Traceability Derivation Mode<\/h3>\n
2. Identifying gaps<\/h3>\n
3. Deriving requirements<\/h3>\n
\n<\/div>\n<\/p><\/div>\n
4. Creating traceability links with existing requirements in a derived document<\/h3>\n
\n<\/div>\n
See Also<\/h3>\n
\nUsing Traceability Matrix<\/a>
\nUsing Traceability Derivation Matrix<\/a>
\nUsing Traceability Network Diagram<\/a>
\nUsing Multi-Level Traceability Report<\/a><\/p>\n<\/div><\/div>\n