For most of the recommended reading, I maintain local copies 
to ensure stability of access (in case web sites get reorganized).
This should not be an issue because I have obtained explicity
permission to use all of the articles that are not wikipedia
or journal.

Documents for which I do not have local copies:

	anything in the wikipedia, 
		because it will only get better

	anything on the IEEE or ACM gateways
		because these are crown jewel papers
		and the universities have negotiated access rights
	
	product documentation
			javadoc
			bugzilla
			openproject
			gprof
		because the developers maintain it

	stuff on extremeprogramming.org
			Wells: User Story Cards
		because of richness and expected stability

	stuff on agilemodeling.org
			Ambler: Examining The Big Requirements Up-Front Approach
			Ambler: Agile Modeling Principles
		because of richness and expected stability

	UML diagrams
		I'm still trying to figure out what to do

	Foote: Big Ball of Mud
		because of its richness, but I'm not sure