What are the characteristics of the quality requirements and designs?

Good quality requirements and designs will exhibit certain characteristics. It is important for a business analyst to keep these characteristics in mind when formulating requirements and designs as part of their business analysis outputs:

• Atomic: When a requirement is atomic, it can be understood independently of other requirements or designs. It is also self-contained and can stand on its own as a statement or expression. 
• Complete: The requirement must have enough detail to be able to work and continue. The level of completeness is not always the same and will depend on the perspective or methodology, as well as when in the life cycle the requirement is used. 
• Consistent: When a requirement is considered consistent, it really means that it aligns with the identified needs of the stakeholders. It also means that the requirements do not contradict any other requirements.
• Concise: A requirement is considered concise when it uses just enough information to describe itself. It doesn't contain unnecessary explanations or content.
• Feasible: A requirement is considered feasible when it is in line with the expectations of the project in terms of risk, schedule, and budget or when it is considered worthy of being explored in more detail.
• Unambiguous: A requirement is considered unambiguous when it states in a clear and straightforward way whether a solution meets the associated need.
• Testable: A requirement is considered testable when it is clear to the reader whether a requirement or design has been fulfilled by a solution or not.
• Prioritized: A requirement is considered prioritized when it shows its relative importance and/or value in relation to the other requirements it is associated with.
•  Understandable: A requirement is considered understandable when it uses terminology that the intended audience will recognize.