Feasible: The requirements must be technically, economically, and operationally possible.
Necessary: The requirements must represent the real needs of the organization.
Prioritized: The requirements must be ranked according to the value of the function or feature to the organization.
Unambiguous: The requirements must be clear so that they will be interpreted consistently across stakeholder groups.
Complete: The requirements must represent all the functions and features needed to meet the business objectives.
Verifiable: The requirements must be testable.
Consistent: The requirements must be In harmony with one another and must not contradict each other.
Correct: The requirements must accurately represent business functions and adhere to business rules.
Modifiable: The requirements must be flexible so that they can be adapted to changing business needs.
Traceable: The requirements must be structured so that they can be traced to hardware, software, test cases, training manuals, and documentation artifacts throughout the solution development life cycle.
Usable after development: The requirements must be detailed enough to support maintaining and enhancing the business system during the operations and maintenance (O&M) phase of the Business Solutions Life Cycle (BSLC).