title: Correct classification of client requirements for UML diagrams?
body: <p>I needed to classify the following RQs as a </p>
  
  <ul>
  <li>Design objective, </li>
  <li>Design Decisions, </li>
  <li>Functional Req, </li>
  <li>Non-Functional Req</li>
  </ul>
  
  <p>(so I can do class diagram and use case diagram based on them later).</p>
  
  <p>I wanted to know if I'm on the right track here (the bold face is my guess for each requirement):</p>
  
  <p><strong>Requirement document</strong>
   Purchase Commitment System.</p>
  
  <ol>
  <li><p>The software is to calculate a number of details needed to purchase by a factory in order to produce its products. <strong>(Design decision)</strong></p></li>
  <li><p>The software must be written in C++ or Java Programming Languages on the computer IBM PC. <strong>(Design decision)</strong></p></li>
  <li><p>The number of products should be equal to 4. <strong>(Non-Functional Req)</strong></p></li>
  <li><p>A general aim in the design of the software is to improve the portability of software. <strong>(Non-Functional Req)</strong></p></li>
  <li><p>The system should accept as input (make as a text file) the data about a number, amount and price of detail for every type of products. <strong>(Functional Req)</strong></p></li>
  <li><p>A number of details for every type of products should not be less than 5.</p></li>
  <li><p>The first and second type of products should have 2 same details. The second and fourth type of products should have one same detail. The third type of products should have 2 same details with the fourth type and one same detail with the first type of products. <strong>(Design Objective)</strong></p></li>
  <li><p>The operator should be logged in and logged out to the system by login and password. <strong>(Design Objective)</strong></p></li>
  <li><p>At the beginning an operator must provide the following items of data (a validation of input data should be provided):</p>
  
  <ul>
  <li>A number of every type of products to be produced by the factory for 3 months ahead.   <strong>(Functional Req)</strong></li>
  </ul></li>
  <li><p>The software must produce for each action of an operator a report (the report should be saved in a file by the operator's request). The report must consist of :    <strong>(Functional or Design Objective Req)</strong> 
  -A number of every detail needed to purchase.</p>
  
  <ul>
  <li>The total price for every detail.</li>
  <li>The total price for all the details</li>
  </ul></li>
  </ol>