quartz/content/notes/requirements-guidelines.md

title	tags
requirements-guidelines	info201

• understandable by all stakeholders including the users
• non prescriptive i.e., should define what, and not how
• correct as judged by user
• complete. i.e., there should be nothing missing from each individual requirement nor the compete set requirements
• consistent. i.e., They should not contradict each toher
• unambiguous. i.e., There should be only one one possible interpretation
• also
  • precise, concise, cohesive, feasible, relevant, up to date, testable, traceable