Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. How to improve maintainability of the application?

How to improve maintainability of the application?

Scheduled Pinned Locked Moved IT & Infrastructure
tutorialquestioncode-review
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Reddy Prakash
    wrote on last edited by
    #1

    Hi all can any one tell me what are the steps to improve the maintainability with example.

    P 1 Reply Last reply
    0
    • R Reddy Prakash

      Hi all can any one tell me what are the steps to improve the maintainability with example.

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #2

      1. Start with a well defined set of requirements. 2. Design the application so that it meets those requirements. Use NUnit or a tool like it to ensure that the application is solid and robust. 3. Design the application using techniques such as well defined patterns. 4. Don't be clever. Write code that you will understand in 6 months time. 5. Test. Test. Test. 6. Don't be clever. Attempting to save a couple of clock cycles by writing composite statements is usually a waste of time. If you're not writing a real time system, it generally doesn't matter that one algorithm takes 2 milliseconds longer than your "optimised" one. 7. Test. Test. Test. 8. Have a well defined maintenance plan. 9. Don't shoehorn things in that don't fit the requirements. There's generally a reason that things are out of scope.

      Deja View - the feeling that you've seen this post before.

      My blog | My articles

      M 1 Reply Last reply
      0
      • P Pete OHanlon

        1. Start with a well defined set of requirements. 2. Design the application so that it meets those requirements. Use NUnit or a tool like it to ensure that the application is solid and robust. 3. Design the application using techniques such as well defined patterns. 4. Don't be clever. Write code that you will understand in 6 months time. 5. Test. Test. Test. 6. Don't be clever. Attempting to save a couple of clock cycles by writing composite statements is usually a waste of time. If you're not writing a real time system, it generally doesn't matter that one algorithm takes 2 milliseconds longer than your "optimised" one. 7. Test. Test. Test. 8. Have a well defined maintenance plan. 9. Don't shoehorn things in that don't fit the requirements. There's generally a reason that things are out of scope.

        Deja View - the feeling that you've seen this post before.

        My blog | My articles

        M Offline
        M Offline
        Mark Churchill
        wrote on last edited by
        #3

        10. Don't reinvent the wheel. If it seems hard or repetitive, chances are theres a better way. Number of times we consult for some place and they seem to think they can write a better ORM solution than our commercial one with a couple of junior devs in a week. Drives me nuts (and it would still be more expensive). Usually I show them the size of our SVN repository and they change their mind :D

        Mark Churchill Director Dunn & Churchill

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups