What is meant by “level “and “allow Humans to make final decisions at each level”?
Reviewing the spec is an iterative process and starts by selecting the most simple service as the first step. The second step is to tune the rules for this service if this is the first run in the organization or project (on the fly rule authoring). The third step is to select the actual offending objects and filter those not needing attention (check box filters). The third step is a pick your battles decision on the part of the analyst. Between each run the user is able to save the settings and results. These saved runs can be re-executed with new settings based on a new “day” or the results of a formal review. The tool groups the rules into services. Each service has a specific goal. If all the services were enabled, the user would be overloaded with data. The idea of a “level” is based on ability to separately select each service and each rule within a service. There is also the concept of simple services and complex services implying a “hill” that the analyst climbs.
