Quality Money Management : Process Engineering and Best Practices for Systematic Trading and Investment

Endnotes 283

3. Taina, Juha. 2005. “ A brief introduction to function points. ” http://www.cs.helsinki.fi/u/tiana/ohtu.fp.html.
   October.


4. Atwood, Jeff. 2005. “ Are all programming languages the same? ” http://www.codinghorror.com/blog/
   archives/000365.html


5. Prechelt, Lutz. 2000. “ An empirical comparison of C, C  , Java, Python, Rexx, and Tcl. ”
   Submission to IEEE Computer.


6. Read, Nick, and Jonathan Batson. 1999. “ Spreadsheet modelling best practices. ” Business Dynamics.
   Published by the Institute of Chartered Accountants for England and Wales.


7. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press.


8. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press.


9. http://www.eusprig.org. 2007.


10. Cullen, Drew. 2003. “ Excel snafu costs firm $ 24 m. ” TheRegister.com. June 3. http://www.theregister.
    co.uk/2003/06/19/excel_snafu_costs_firm_24m/


11. Boehm, Barry, and Victor R. Basili. January 2001. “ Software defect reduction top 10 list. ” Computer.


12. Hesse, Rick. 1996. Managerial Spreadsheet Modeling and Analysis. Richard D. Irwin, p. 19ff.


13. Grossman, Thomas A., and Ozgur Ozluk. 2004. “ A paradigm for spreadsheet engineering method-
    ologies. ” European Spreadsheet Risks Interest Group, 5th Annual Symposium, Klagenfurt, Austria.


14. Hesse, Rick. 1996. Managerial Spreadsheet Modeling and Analysis. Richard D. Irwin, p. 19ff.


15. Grossman, Thomas A., and Ozgur Ozluk. 2004. “ A paradigm for spreadsheet engineering method-
    ologies. ” European Spreadsheet Risks Interest Group, 5th Annual Symposium, Klagenfurt, Austria.


16. Gordon, V. Scott, and James M. Bieman. 1994. “ Rapid prototyping: lessons learned. ” IEEE Software.

Chapter 11

1. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press, p. 69ff.


2. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press, p. 69ff.


3. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press, p. 69ff.


4. McConnell, Steve. 1996. Rapid Development. Redmond, WA: Microsoft Press, p. 69ff.


5. Panko, Raymond R. 2006. “ Recommended practices for spreadsheet testing. ” EuSpRIG 2006
   Conference Proceedings, p. 73ff.


6. Fagan, M.E. 1976. “ Design and code inspections to reduce errors in program development. ” IBM
   Systems Journal , pp. 182–211.


7. Fagan, M.E. 1986. “ Advances in software inspections. ” IEEE Transactions on Software Engineering.
   July, pp. 744–751.


8. Panko, Raymond R. 2006. “ Recommended practices for spreadsheet testing. ” EuSpRIG 2006
   Conference Proceedings, p. 73ff.


9. Grossman, Thomas A. 2007. “ Source code protection for applications written in Microsoft Excel
   and Google Spreadsheet. ” EuSpRIG 2007 Conference Proceedings, p. 84.

Chapter 12

1. Dunham, David J. 2007. “ Gate meetings: speed bump versus acceleration ramp. ” http://www.pdma.org/
   visions/print.php?doc=jul99/dunham.html


2. Cooper, Robert G., Scott J. Edgett, and Elko J. Kleinschmidt. 2001. Portfolio Management for New
   Products. 2nd edition. Basic Books, p. 22.


3. Cooper, Robert G. 2001. Winning at New Products. 3rd edition. Basic Books. p. 246ff.


4. Cooper, Robert G. 2001. Winning at New Products. 3rd edition. Basic Books. p. 246ff.


5. Cooper, Robert G. 2001. Winning at New Products. 3rd edition. Basic Books. p. 246ff.


6. Cooper, Robert G. 2001. Winning at New Products. 3rd edition. Basic Books. p. 246ff.


7. Cooper, Robert G. 2001. Winning at New Products. 3rd edition. Basic Books. p. 246ff.