[School] The method of shifting requirements analysis and management of software requirements

We only 11 method fundamental shift alone, very memorable ;). It is located in three main groups like this.

  1. Copy: When requests no changes can we identical copy of it downstairs.
  2. Removed: When requesting unnecessary , not feasible or does not match the other requirements we should abandon it.
    ———
  3. analyze: When the request is not atomic (no single) we can split it up into one or more requests
  4. Combined: The requirement redundant and overlapping let combining them
  5. Unified: When these requirements conflict uniform let them
  6. Generalizable: Removing unnecessary details of the request
    ———
  7. Repair: Corrected spelling, syntax errors and error if no exact requirements
  8. Make bright: Purification or explain the vague requirements
  9. Full employment: If a request is incomplete, we need to add other requirements to complete it downstairs
  10. More Details: If the requirements are not only accurate, add details to it
  11. Qualify: Additional restrictions or conditions required for better quality