1 / 0

The Worse the Application, the Longer it Lives

The Worse the Application, the Longer it Lives. GLSEC 2011 Ivan Assenov. About Ivan. Information Systems Architect – CSi i_assenov@yahoo.com iassenov@compliancesystems.com http://twitter.com/#!/ivanassenov http://www.linkedin.com/in/ivanassenov. Preamble. Evaluation Period.

opal
Download Presentation

The Worse the Application, the Longer it Lives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Worse the Application, the Longer it Lives

    GLSEC 2011 Ivan Assenov
  2. About Ivan Information Systems Architect – CSi i_assenov@yahoo.com iassenov@compliancesystems.com http://twitter.com/#!/ivanassenov http://www.linkedin.com/in/ivanassenov
  3. Preamble
  4. Evaluation Period
  5. Evaluate the Software Using Metrics
  6. 3D Code Metrics Java Development Kit (JDK) v1.5
  7. Plug UML to Work for You
  8. Search for Dead Code
  9. Look for Existing Unit Tests
  10. Run Performance Tools
  11. Run Database Tools if Database is Present
  12. Explore Public API with Regard to Documentation
  13. Extract All Bugs Reported Over Time
  14. Examine Behavior
  15. Improvement Period
  16. GoTo Redo
  17. Add All Code to Repository
  18. Extract All Business Knowledge
  19. Meta Knowledge Tree
  20. Meta Knowledge Tree
  21. Add Unit Test Framework
  22. Ability to Test Private, Protected Methods
  23. Ability to Test Catch Exceptions, Throw Exceptions
  24. Repair Unit Test
  25. Add Unit Tests
  26. Code Coverage
  27. GUI Automation Test
  28. Create/Modify Builds
  29. Add Continuous Integration
  30. Remove All Warnings
  31. Design by Contract
  32. Add New Languages
  33. Always Require Acceptance Test
  34. Code Reviews–No Longer Than 20 Min
  35. Release Often
  36. Benchmarks
  37. Easy Integration
  38. Maintainability – Easy Software
  39. Used Materials Photos: http://creativecommons.org/licenses/by/2.5/ http://www.freephotos.com Free Stock Photo:
  40. Tools S Expert - http://www.modelingsoft.com/ Code City - http://www.inf.usi.ch/phd/wettel/codecity.html Pex - http://research.microsoft.com/en-us/projects/pex/ Code Contracts - http://research.microsoft.com/en-us/projects/contracts/ http://www.codeproject.com/KB/cs/testnonpublicmembers.aspx http://codebox.jimomighty.com/random/AssertExtended_CSharp.html http://peter.brightman.de/
More Related