* Finish BFR role play.
* Explain "Practical Software Requirements", Kovitz pg 53:
	* Requirements deals with describing problem domain and the effects the software is supposed to have on it
* Example outline of requirements
	* Document info (table of contents, preparer, revision date, related documents, change log)
	* Overview
	* Problem domain description (entities, attributes, relations, cardinalities, causal rules, events and sequence, data/file formats, information sources, hardware and software external to the system to be developed)
	* Requirements (queries, behavioral rules)
	* Platform
	* Expectations
	* Preferences
	* Glossary
* Quick preview of specification: I/O behavior, states, operating procedures.
* Get into teams to arrange meeting time, build up knowledge and understanding of problem domain, identify entities, etc.