1. Getting Books Into Schools
Tracking and Tracing Books: a software and interface design perspective

2. stakeholders Who are the principal stakeholders?
Who are the second-level stakeholders?
Do stakeholders have differing capabilities and capacities?
Do stakeholders have differing agendas?

3. Stakeholder questions
Questions that Could be Answered
What books should arrive at this school?
When should the books arrive?
Where are the books now?
How can I contact the person responsible for this shipment?
What other questions are there?
Can these be answered?
Can answers be short?
Can questions be short?
John Snow, Inc.

4. Designing for error
How do the people who interact with the system differ with respect to digital/device literacy, if applicable? How does capability differ?
Designing for queries and identifiers with an eye on eliminating input error
Shipment code and query are designed so that the system always checks for a letter and a number together and adds a space

5. Data that can be captured
In addition to system answers to questions, what data can be passively obtained? ….and is it important?
Location of book handoffs
Time of book handoff
Cell tower quadrant
Number of interactions per cell number
Can data be exported (e.g. CSV, images, etc.) …

6. Viewing data Is the data visible to all parties?
Could the data ever be public? How might this look?
Are there reasons to not show any data?
Can data be used maliciously?
Are there privacy issues that need to be considered? …

7. Designing for malice
While the system may have a wonderful goal, how can it be used for other, malicious purposes?
Can a person interact with the system in a way to do harm?
Can I interact with the system in such a way as to cause disruption of any sort? …

8. Attack trees
-- B. Schneier, Dr. Dobb's Journal, December 1999