<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Creating NX Requirements</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic2" id="xps10_pagetitle">Creating NX Requirements</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('check_req/check_reqts_ov.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('check_req/reqts_list_ht.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('check_req/validation_op.html');return(false);">Options</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">There are specific steps you must follow in Teamcenter Requirements to populate a project with requirements for use with NX.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">Any user with write access to the project can perform these steps. </p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_topic">First, you must create the context for organizing the requirements:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item"> All data in a project must be stored in a folder. In the <b class="uiTerm">Requirements</b> module:
            </p>
            <dl compact>
               <dt>a.</dt>
               <dd> Select the project in the navigation tree.</dd>
               <p></p>
               <dt>b.</dt>
               <dd>Choose <b class="uiTerm">File</b>&rarr; <b class="uiTerm">New</b>&rarr; <b class="uiTerm"> Folder</b>. 
               </dd>
               <p></p>
               <dt>c.</dt>
               <dd>Enter the folder name and press <b class="literalText">Enter</b>. The folder can have the same name as the project. 
               </dd>
               <p></p>
            </dl>
         </li>
         <li>
            <p class="para_item">When requirements are created for use with NX, it is a good idea to import the document(s) from which the requirements are derived. This allows you to organize the requirements using the same context in which they appear. To import a document: </p>
            <dl compact>
               <dt>a.</dt>
               <dd>Select the new folder in the hierarchical content table. </dd>
               <p></p>
               <dt>b.</dt>
               <dd>Choose<b class="uiTerm"> File</b>&rarr; <b class="uiTerm">Import</b> &rarr; <b class="uiTerm">Word Document</b>. 
                  <table border="0">
                     <tr>
                        <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                        <td valign="bottom" align="left" width="100%">
                           <div class="para_note">At this time, only Microsoft Word documents can be imported. </div>
                        </td>
                     </tr>
                  </table>
               </dd>
               <p></p>
               <dt>c.</dt>
               <dd>Locate the document to import, select it, and click <b class="uiTerm">Open</b>. 
               </dd>
               <p></p>
               <dt>d.</dt>
               <dd>Select the <b class="uiTerm">Paragraph</b> subtype and click <b class="uiTerm">OK</b>. (See  Importing Documents below for more information.) 
               </dd>
               <p></p>
               <dt>e.</dt>
               <dd>After the import completes, click <b class="uiTerm">OK</b>. 
               </dd>
               <p></p>
            </dl>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_note">
                        <p class="para_note_body">This step is optional. If you choose not to import any documents, then you can create the requirements directly in the folder (see step 1 below). </p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
      </ol>
      <p class="para_topic">Now you are ready to create requirements for use with NX. You must identify data in the requirements document(s) that represent a maximum, minimum, or range of valid values for some aspect of a design. These are typically found in lists or tables of numerical data. Each one can be used to create an NX Requirement.</p>
      <p class="para_topic">To create a requirement:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">In the hierarchical content table, navigate to the section of the document that contains the requirement data and select it. </p>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_note">
                        <p class="para_note_body">To see the entire document hierarchy, select the root node of the document, choose<b class="uiTerm">View</b>&rarr; <b class="uiTerm">Expand All</b>. If no documents were imported (see step 2 above), select the folder instead. 
                        </p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
         <li>
            <p class="para_item">Choose<b class="uiTerm"> File</b>&rarr;<b class="uiTerm">New</b>&rarr; <b class="uiTerm">Child</b>, or click the <b class="uiTerm">Create New Child</b> button on the toolbar.
            </p>
         </li>
         <li>
            <p class="para_item">Enter the new requirement name and press <b class="literalText">Enter</b>. 
            </p>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_note">
                        <p class="para_note_body">Each NX Requirement should have a unique name, even if Teamcenter Requirements does not enforce it. </p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
         <li>
            <p class="para_item">In the <b class="uiTerm"> Value</b> column of the <b class="uiTerm">Properties</b> table, double-click the <b class="uiTerm">Subtype</b> value. 
            </p>
         </li>
         <li>
            <p class="para_item">Choose  NX Requirement and click <b class="uiTerm">OK</b>. 
            </p>
         </li>
         <li>
            <p class="para_item">In the <b class="uiTerm">Value</b> column of the <b class="uiTerm">Properties</b> table, double-click the <b class="uiTerm">Compare</b> value.
            </p>
         </li>
         <li>
            <p class="para_item">Choose the desired comparison operator and click <b class="uiTerm">OK</b>. The choices for the operator are:
            </p>
            <ul class="unmarkedList">
               <li>
                  <p class="para_item"><b class="literalText">Equal</b> &mdash; The Max property must be given a value.
                  </p>
                  <p class="para_item"><b class="literalText">GreaterThan</b> &mdash; The Min property must be given a value.
                  </p>
                  <p class="para_item"><b class="literalText">LessThan</b> &mdash; The Max property must be given a value.
                  </p>
                  <p class="para_item"><b class="literalText">Range</b> &mdash; The Min and Max properties must both be given values.
                  </p>
               </li>
            </ul>
         </li>
         <li>
            <p class="para_item">(Optional) If a value for <b class="uiTerm">Min</b> is required, double-click the <b class="uiTerm">Min</b> value in the <b class="uiTerm">Value</b> column of the <b class="uiTerm">Properties</b> table, enter the minimum limit value, and press Enter.
            </p>
         </li>
         <li>
            <p class="para_item">(Optional) If a value for <b class="uiTerm">Max</b> is required, double-click the <b class="uiTerm">Max</b> value in the <b class="uiTerm">Value</b> column of the <b class="uiTerm">Properties</b> table, enter the maximum limit value, and press Enter.
            </p>
         </li>
      </ol>
      <p class="para_topic">Repeat these steps for each NX Requirement you wish to create. For more information on creating and modifying requirements, see the  <em>Teamcenter Requirements User&rsquo;s Manual</em>.
      </p>
      <div class="title_division">Viewing the Requirements </div>
      <p class="para_division">You may find it easier to see the NX Requirements you have created in the hierarchical content table if you change the view as follows:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">Choose <b class="uiTerm">View</b>&rarr; <b class="uiTerm">Format Columns</b>. 
            </p>
         </li>
         <li>
            <p class="para_item"> Identify the properties you want to display, including at least  <b class="uiTerm">Compare</b>, <b class="uiTerm">Max</b>, <b class="uiTerm">Min</b> and  <b class="uiTerm">Subtype</b>, by selecting the check box next to each one until it displays a check mark. All other properties should be unselected. 
            </p>
         </li>
         <li>
            <p class="para_item">Click  <b class="uiTerm">OK</b>.
            </p>
         </li>
         <li>
            <p class="para_item">Change the order of the displayed columns. For each column that you want to move, point to the heading in the hierarchical content table, hold down MB1, and drop the heading in the new position. A good order is <b class="uiTerm">Subtype</b>, <b class="uiTerm">Compare</b>, <b class="uiTerm">Min</b>, and <b class="uiTerm">Max</b>.
            </p>
         </li>
      </ol>
      <div class="title_division">Importing Documents </div>
      <p class="para_division">In most cases, the content of the document(s) containing requirements should be imported as paragraphs, since the NX Requirements that are important to NX are derived from the content. When the content represents something you want to formally track, change the subtype of a selected paragraph to a Requirement . Change the subtype of all paragraphs which are parents of NX Requirements to mark them as such.</p>
      <p class="para_division">For more information on importing documents into Teamcenter Requirements, see the  <em>Teamcenter Requirements User&rsquo;s Manual</em>.
      </p>
   </body>
</html>