Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0914 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Wed Sep 14 14:51:25 PDT 2005

Contents


    Goldstein05

    1. Harry Goldstein
    2. Who killed the Virtual Case File
    3. IEEE Spectrum Magazine (Sep 2005)pp24-35
    4. =HISTORY VCF Trilogy FBI DISASTER FAILURE RISKS
    5. Demonstrates that bad management and bad process can lead to a lot of money being spent for nothing.
    6. Mistakes:
      1. Amateurism
      2. Changing goals in midstream
      3. Tightening the schedule
      4. No process or control
      5. No "system architecture"
      6. Changing bosses in midstream.
      7. Muzzling and ignoring critics.
      8. Giving very detailed requirements (position and color of buttons) but no vision or goals.
      9. Changed requirements flood in after first demo.
      10. Cost plus contract.
      11. NIH: no COTS bought in

    7. It may be cheaper to spend time writing good requirements using math and prototypes rather than hiring lawyers to wrangle over the ambiguities.

    Ross05

    1. Philip E Ross
    2. The Exterminators
    3. IEEE Spectrum Magazine (Sep 2005)pp36-
    4. =ADVERT Praxis MATH Z Spark PROTOTYPES V&V TOOLS TESTING MONDEX
    5. Company demonstrates that by getting very clear and reliable requirements expressed mathematically and using a reliable language to write the code you can reduce the number of faults to 1 for 25KLoC on project with 200KLoC.

    Charette05

    1. Robert N Charette
    2. Why Software Fails
    3. IEEE Spectrum Magazine (Sep 2005)pp-
    4. =ADVERT RISK MANAGEMENT DISASTERS COSTS
    5. p44. Hall of Shame 1992..2005
    6. Side boxes describe case studies
    7. Rounds up the usual [Charette95] suspects:
      1. Bad goals
      2. Bad estimates of needed resources
      3. Bad systems Requirement
      4. Poor project control and/or planning
      5. Bad communication
      6. ...
      7. Politics
      8. Commercial pressures

    Hassler05

    1. Susan Hassler
    2. Learning from Software Failure
    3. IEEE Spectrum Magazine (Sep 2005)p8
    4. =EDITORIAL COSTS RISKS FAILURE DISASTERS VCF
    5. Good software can transform a business: Dell Walmart.
    6. Notes that a future disaster may be when the USA digitizes and automates medical records.

End