Softspec Lab 3 - 29 Jan 2015
Getting requirements
- Interview the user
- Requirement workshop - drawing mockups, longer than interview
- Observation - see how the user work
- Survey - go to the customer site and ask people on how they work
- Research
Requirements
- Should be clear, unambiguous
- Unique, don't repeat it several times
- Consistent
- Feasible - possible to do
-
Verifiable - system never crash can't really be verified
-
If requirements keeps adding it is called requirements creep or feature creep
Use case guideline
- Do: cashier enters item code
- Don't: cashier needs to enter barcode (this is implementation details)
- Do: POS display item description and price
- Don't: there are many items in the inventory (it's not something the POS do)
- Do: Cashier enters item code
- Don't: The cashier locate the barcode symbol on the item and enter the item's barcode in the systems
- Do: Cashier enters item code
- Don't: Cashier scans the item barcode (avoid putting implementation details)
Homework
Do the homework in the wiki. Use the brief use case format:
- UC1: ...
- Primary actor and Goal: ...
- blah blah blah