ScopeMaster Looks at Multiple Quality Characteristics
ScopeMaster will help to identify defects in the following categories
No two requirements describe the same core functionality. Requirements or user stories can be translated into designable functionality.
A user story that combines multiple transactions will be flagged as potentially defective.
The maintenance of data within a system should be complete ScopeMaster will identify any missing CRUD-type requirements.
Scopemaster will identify passive indirect terminology as potential defect. ScopeMaster will also highlight over complex language.
ScopeMaster examines all requirements individually and collectively, to ensure consistency within and across a set of requirements (or user stories).
ScopeMaster encourages that each user story describes a single transactional function in user terms.