• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

new client, should we duplicate the project or write a factory?

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
HI all,

We've completed a project 6 months ago for a major client of ours; the project is a struts application that provides well organized data and graphs for the end-users. There are some upgrades that we perform from time to time but thanks to our design it is quite easy to maintain it.

One of the branches of our client wants to use the same system, but since they have different strategies (and different currency) they wish to customize if for their needs. So on our end we need to re-write the PDF (wordings) provide different graphs (not to many).

My question is this: Should we duplicate the project and make the relevant changes (so in a way we'll have projectA and projectB).
OR
should we change the code (as in Factory) to determine who is the client and based on that make the changes. This way, say we'll find a bug in the future we will not have to address 2 projects.

Thanks for any input (my apologies if my question is not in the right forum)
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would recommend to say nothing to your customer in order to cash the integration and reuse the code.
Just change it a little bit of code and make double money

This is the interesting point with modeling because once it is developed you can generate a code from your model. You just need to add new requirements and click on a buttom to generate the code. Once this code is generated you manually merge existing code and new code in order not to loose implementation code, and job done
You can go fishing and spend more time with your family and still make good living

btw, if you can not hide it to your customer then I would recommend to produce another project because you will charge double money on maintenance and refactoring next year.
On technical point of view I think you just need to add conditions and use the same project, but you will make less money and your boss will not be happy
 
reply
    Bookmark Topic Watch Topic
  • New Topic