2. Process – Traditional Approach
• Have a meeting to
decide what to do
• Lock yourself in a
room and keep
coding until it's done
• Show users the
finished product and
make some minor
adjustments
Antony Quinn
3. Process – new EBI approach
• Talk to users first to find
what they really, really want
• Rapid sketching and
prototyping to get the
design right
• Clear specification to
inform coding and artwork
• Continuous testing and
feedback from users
Antony Quinn
4. Basic software documentation
in a collaborative project
• Requirements
– User feedback
– Sketching and prototyping
• Deliverables
- Time line (what and when)
• Software development
– Specification
– Code repository
– Issue tracker
– Testing protocols
• How to’s
Requirements: Statements identifying the necessary capabilities of a system in order for it to have value and utility to a user.
Specification: Technical requirements. Description of software or hardware that may be used to develop an implementation. It describes what the system should do, not (necessarily) how the system should do it.