How do you prefer to split your multi-part program? [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 8 years ago.

Having a program that has several distinct parts is usual.By part I mean a graphical part that has its own windows and functionalities.(About non graphical part, I think creating a library is the preferable solution) How do you prefer to separate them ? Is it better to make each of them a static library and use them in the main program? Or the better solution is to create an executable file of each one and load them in the main program? Or even better solution?

Answer 1

I suggest that you read Code Complete or something simlar. This book and others go into the best practices or even how to know which of the best practices you should look into when you create a product.

The problem is one of scope. You need to know your specifications and the parts that join together, as well as which design practices you are going to use before you can answer this question.

I am also inclined to think that there is no right or wrong answer (depending on HOW wrong you are) and that no-one else can answer that question for you, especially since you are likely to be one of the main players in maintaining the code.

Hope that gives you some food for thought :-)