Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 1
    IMO this question is too broad. Could you please split it into several smaller, simpler questions, each one addressing one specific design issue? Even the LT;DR; section is too verbose. And the final thoughts section is even more verbose. Commented Sep 3, 2016 at 1:49
  • Dear @TulainsCórdova I can't see how this can be made shorter, because the problem is one that exists at a whole-system level. If I give a high-level overview with less detail, readers are unlikely to be able to suggest a useful approach. If I ask for each single requirement out of context, answers are unlikely to fit well with each other systematically. I regret that my post is too long for your taste, and I appreciate your taking the time to suggest that it is too broad and lengthy, but perhaps then my question simply isn't for you, and someone else with a different appetite can help me. Commented Sep 3, 2016 at 1:55
  • @TulainsCórdova I don't find your voting to close (if it was you and not the other 3 people who have visited so far) to be helpful for such a young question—if the question is left open for 2 days, I can spend my own reputation to add a bounty, no skin off your nose, but if you close it people can't answer even if they desire! Consider that I would dearly love the advice of someone like you with 20 years of programming experience who is expert in "OOP, OOD, good practices, SOLID principles, software patterns and code quality". But let someone else answer if you won't/can't. Commented Sep 3, 2016 at 2:01
  • I think scope-specific questions have a better change to get useful answers, and if abstract enough, such answers' solutions can fall into place within the whole. As it is right now, one would have to ask dozens of questions in form of comments to understand the humongous scenario, spawning long discussiones below each attempt of answer. It takes a lot of commitment to read and digest the scores of business rules contained in that text-wall. Just trying to help improve the question. Commented Sep 3, 2016 at 2:06
  • Have you considered that my actual problem here could be not knowing how to break up the problem space into smaller pieces? That would mean your response is akin to "first, solve your real problem on your own, and then we can help you solve the easier sub-problems you may already know how to solve and don't need help solving!" How does that help me? Is the answer "your problem is just too hard for programmers.stackexchange, you'll have to pay real money for that level of help"? Know any experts in the Pacific Northwest that I can buy lunch for and would talk this over with me? Commented Sep 3, 2016 at 2:16