I am confused , Why Software that are developed using the evolutionary approach are harder to be maintained ?

closed as unclear what you're asking by Christophe, Robert Harvey, Nicol Bolas, 17 of 26, gnat Oct 14 '18 at 6:31

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    There is a ton of context missing here. – gnasher729 Oct 13 '18 at 23:26
  • This is just a direct question that i have been asked in my exam – Ahmed Mohamed Oct 13 '18 at 23:27
  • 1
    They’re not harder to maintain... I’m confused. – Telastyn Oct 14 '18 at 0:26
  • Well, you're using two different words here: incremental and evolutionary mean two very different things. – Robert Harvey Oct 14 '18 at 0:31
  • 4
    @AhmedMohamed: "This is just a direct question that i have been asked in my exam" What did your teacher tell you during class? That's likely the answer they want. Without having sat in on the class, its impossible to know how to answer this. – Nicol Bolas Oct 14 '18 at 0:55

It's mostly because you frequently come up against design decisions where the easiest way to add a new feature to an existing program differs from the best way you would make everything if you were starting from scratch. That doesn't mean it is necessarily more difficult to maintain, but you have to make a concerted effort to continually refactor as you go along, and not everyone is conscientious enough to do so.

  • This happens to me >>a lot<< And I wouldn't call it "conscientious" (or lack thereof). Just not enough time to get the job done on schedule, and to get it done right (meaning the way I'd like to do it). Clients always (almost always) get additional ideas in their heads during the course of any non-trivial new development project. And that's to be expected -- even welcomed. It usually results in an overall better product, even if the implementation is bags-on-bags spaghetti code. If it's a good enough product, time will (maybe) eventually be made available to refactor it right, maybe v2.0 – John Forkosh Oct 14 '18 at 11:23

Not the answer you're looking for? Browse other questions tagged or ask your own question.