我应该使用哪种开发结构? [英] What kind of development structure should i use?

问题描述

我是开发人员.我曾经使用过C#，MS SQL Server，UML和XML.通常，我将资产跟踪系统开发为窗口应用程序.根据不同的客户，某些业务逻辑会更改.我想减少开发时间.否则，每次我为每个客户创建一个新项目时.因此，请根据我的知识向我建议我应该尝试的任何方式.

谢谢.

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.

推荐答案

您可以使用3层体系结构来开发应用程序.
MVP(我个人认为)是开发桌面应用程序的最佳体系结构.

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

实际上没有办法从头开始将其淘汰.每个客户对于其工作方式和外观都有自己的怪异想法.您能做的最好的事情就是使各个层尽可能地分开.编写一个基本的数据库模式，一个与之交互的业务层以及一个与业务层交互的接口.将每个部分都转换为Visual Studio项目模板，然后要开始新的解决方案时，只需将这些项目添加到解决方案中，然后就可以开始运行了.

然后，扩展基本功能并根据客户需求自定义界面将是一件简单的事情.

成为开发人员的一部分就是能够自己确定这种事情.

您知道需要什么，知道(或至少应该知道)工具的功能.剩下的只是把它放在纸上，然后实现它.

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.

这篇关于我应该使用哪种开发结构?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！