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