What kind of development structure should i use?

Question

0.00/5 (No votes)

See more:

Hi,

I'm a developer. I used to with C#, MS SQL Server, UML and XML. Mostly I develop Asset Tracking System as a window application. Depending on different customers, some business logic is changed. I'd like to reduce the development time. Otherwise, every time I make a whole new project per customer. So please suggest me any way I should try, based on my knowledge.

Thank you.

Posted 13-Jun-11 4:23am

khinezw

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

parmar_punit · Answer 1 · 2011-06-13T04:27:00

Solution 1

you can use 3 tier architecture to develop application.
MVP(My personal opinion) is the best architecture for developing desktop application.

Posted 13-Jun-11 4:27am

parmar_punit

Comments

khinezw 13-Jun-11 10:37am

Thank you. Let me know the long-term of MVP.

#realJSOP · Answer 2 · 2011-06-13T04:34:00

There's really no way around slugging it out from scratch. Every customer has his own bizarre ideas about how it should work and what it should look like. The best you can do is to keep the various layers as separated as possible. Write a basic db schema, a business layer to interact with it, and in interface that interacts with the business layer. Turn each part into Visual Studio Project Templates, and when you want to start a new solution, you simnply add those projects to the solution, and you're off and running.

It will then be a simple matter to extnde the basic functionality and customize the interface to the customer's requirements.

Part of being a developer is being able to determine this kind of thing on your own.

You know what you need, you know (or at least SHOULD know) the capabilities of your tools. The rest is simply putting it down on paper, and then implementing it.