Systems requirements errors are numerous, persistent, andexpensive. To detect such errors, and focus on critical ones during thedevelopment of a requirements document, we have defined RootRequirements Analysis. This simple technique is based on: generalizingrequirements to form root requirements, exhaustively comparing the rootrequirements, and applying simple metrics to the resultant comparisonmatrix. Root Requirements Analysis is effective. In the case studydescribed, the technique finds that 36 percent of the case's rootrequirements interactions result in problems which require furtheranalysis. Moreover, the technique provides a specific operationalprocedure to guide the efficient iterative resolution of identifiedrequirements conflicts. The process of Root Requirements Analysis itselfis not specific to a particular methodology. It can be applied directlyto requirements in a variety of forms, as well as to the documentationof requirements development. We took this latter approach in the casestudy illustrating how Root Requirements Analysis can augment theInquiry Cycle model of requirements development. Finally, the techniqueis amenable to support through collaborative CASE tools, as wedemonstrate with our DEALSCRIBE prototype
展开▼
