Title: Sheffield Trading Project


Description of Problem:
	Bucky and Connie are futures brokers. They want software that
	will keep track of their daily trades faster, easier and more
	reliably than their current system (which is basically Connie
	doing it all by hand).
	They need to be able to enter orders into the system as they
	get them and then enter trades as they are filling the orders.
	They also need a way to keep track of a couple levels of
	verification that the trades were actually executed as they
	entered them.  They also want the system to generate different
	kinds of reports (daily trade reports, monthly invoices, monthly
	revenue sheets, etc.).

Users:
	Mostly Connie, sometimes Bucky, sometimes a temporary replacement
	for Connie

Feature Priorities:
	1.
		- keep track of all customers and their accounts
		- be able to enter trades into a database
		- group trades by account and order
		- generate mid-day reports (excel)
		- generate day-end reports (excel)
		- generate monthly invoices (excel)
		- generate month-end revenue sheet (excel)
		- generate year-end revenue sheet (excel)
	2.
		- keep track of trade verification levels
		- email generated reports at click of mouse
		- generate arbitrary report (based on template [xml?])
	3.
		- automatically parse and check CBOT trade prelims and
		  recaps against database
		- automatically parse and check CBOT account statements
		  against database
	4.
		- monitor quote ticker and display relavent quotes/spreads
		  based on current open orders
		- take an excel spreadsheet made with certain special
		  tags and convert it to a report template
	5.
		- color code and/or sort quotes based on nearness to
		  order price

UI:
	The requirements are primarily functional.  A number of UIs
	will get the job done, so a particular UI should be designated
	in the specifications.
	The UI will need to be:
		simple
		intuitive
		well organized
		fast
		"designed primarily for Connie"

Reliability:
	- most operations should take no more than 2 seconds
	- the system can NEVER crash
	- the system can NEVER corrupt or lose data
	- in the event of an external problem (IO issues, network issues,
	  etc), the system should report the problem so the user can try
	  to get it fixed immediately

Documentation:
	- there should be a help option in the menu bar of every window
	  that leads to information about how to use the current window
	- in addition, there should be some kind of README that goes with
	  the software and explains the software from a more general
	  perspective
	- the README should also include an outline that links to the same
	  help pages as are displayed by the help menu options