title: How to handle requirements in arc42
body: <p>The first three chapters in arc42 are related to software requirements:</p>
  
  <ol>
  <li>Introduction and Goals </li>
  <li>Constraints</li>
  <li>Context  </li>
  </ol>
  
  <p>Most projects start with a detailed specification (hopefully) already containing all requirements. </p>
  
  <p>Now my questions (which are - I guess - mainly best practice questions)</p>
  
  <p>Should I copy the requirements which are relevant for the architecture in case that people only read the architecture documentation?</p>
  
  <p>Or are those requirements for the template different to the main project requirements?</p>