CAS-SA

• Specific – unambiguous and consistent
• Measurable – objectively and independent of human interest
• Attainable – it is in principle possible to build it
  • (Sometimes Assignable, can be assigned to someone)
• Realistic / Realizable – state what results can realistically be achieved, given available resources.
• Traceable - Can be traced throughout its complete lifecycle, from first draft to marked as done
  • (Sometimes Time-related – specify when the result(s) can be achieved.)

o Purpose: Describe the purpose
- A single clear sentence of what the product aims to achieve
o Advantage: What advantages should the product bring?
- Cost Reduction/Simplify Business
- Increase profits
- Improve service
- Comply with laws
o Measure: how to measure the benefits?
 

Independent We want to be able to develop in any sequence.

Negotiable Avoid too much detail; keep them flexible so the team can adjust how much of the story
to implement.

Valuable: Users or customers get some value from the story.

Estimable The team must be able to use them for planning.

Small Large stories are harder to estimate and plan. By the time of iteration planning, the story
should be able to be designed, coded, and tested within the iteration.

Testable Document acceptance criteria and the definition of done for the story, which lead to
test cases.

• Functional Suitability
• Performance Efficiency
• Compatibility
• Usability
• Reliability
• Security
• Maintainability
• Portability

• Functional completeness
• Functional correctness
• Functional appropriateness

• Time-behaviour
• Resource utilisation
• Capacity

• Co-existence
• Interoperability

• Appropriateness recognizability
• Learnability
• Operability
• User Error protection
• User Interface aesthetics
• Accessibility