我的软件开发方法不好吗? [英] Is my software developing method not good

查看:73
本文介绍了我的软件开发方法不好吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述





对于我的公司,我开发了一个winform应用程序,用于处理Unified COmmunication。

开发已经有1年了。我只是在单独的类中编写全局函数,并以表单或类编写代码。现在,他们希望我制作相同软件的三个单独副本(每个更改的UI)。我已经更改了所有UI和所需的一切,并制作了3份。但现在,我觉得很难纠正任何问题,或添加任何功能。我必须在我的所有三份副本中更改它。我该怎么解决这个问题。谢谢。

解决方案

重新开始,然后使用OOP原则进行设计。

从您的描述中可以看出,您创建的是一个使用C#语言而不是适当的C#应用程序的单片应用程序。正如你所看到的那样,你不太可能轻易地适应这一点 - 这也是OOP开发和推广的部分原因:鼓励模块化和独立性,而不是倾向于鼓励意大利面的整体方法。



对不起,如果这就是你制作的,那就是你的床:你必须躺在上面或咬紧牙关并从头开始重新设计。


您必须使用图层在不同的位置具有公共代码,并在每次需要时每次引用相同的代码。我们必须遵循DRY(不要重复自己)主体,如下所述:

http://en.wikipedia.org/wiki/Don't_repeat_yourself



在你的情况下,他们要求保留不同的副本,因为UI对那些不同。在这种情况下,我们可能有如下图层:



UI(用户界面)图层: 4个WinForm项目适用于通用UI控件,特定UI 1,特定UI 2,特定UI 3.所有特定项目都将引用常见UI和BL Layer。



业务逻辑层:类库项目:拥有所有业务领域类。



数据访问层:类库项目:全部与数据访问相关的课程。



如果需要,你也可以有服务层,上面只是一般性建议因为我不知道确切的方案,所以访问以下链接并做出明智的决定



http://fewagainstmany.com/blog/introduction-to-layered-architecture-part-one

http://en.wikipedia.org/wiki/Software_a结构

http://shareimppoints.wordpress.com/2013/03/05/what-is-3-tiermulti-tier-architecture-and-why-do-you-need-it/ [ ^ ]



如果有任何进一步的查询,欢迎您。

Hi,

For my company, I have developed one winform application, that handles Unified COmmunication.
It's been 1 year in development. I Just write global functions in seperate classes, and write the code in either form or class. Now They wanted me to make three seperate copies(UI of each changed) of the same Software. I have changed all UI and everything needed, and made 3 copies. But now, I feel it very difficult to correct any issues, or add any features. I have to change it in my all three copies. How can I solve this. Thanks.

解决方案

Start again, and design it using OOPs principles instead.
It sounds from your description that what you have created is a monolithic application using the C# language instead of a "proper" C# app. And it is very unlikely that you can easily adapt that, as you have seen - that is partly why OOPs was developed and promoted: in encourages modularity and independence rather than the monolithic approach which tends to encourage spaghetti.

Sorry, but if that's what you produced, then that's your bed: you will have to lie on it or bite the bullet and redesign from scratch.


You must use Layers to have common code in separate places and refer the same every time whenever needed. We must follow DRY (Do Not Repeat Yourself) principal as described here:
http://en.wikipedia.org/wiki/Don't_repeat_yourself

In your case they asked to keep different copies, just because UI is different for those. In this case we may have layers like below:

UI (User Interface) Layer: 4 WinForm Projects for Common UI Controls , Specific UI 1, Specific UI 2, Specific UI 3. All specific projects will have reference of common UI and BL Layer.

Business Logic Layer: Class Library Project: Having all business domain classes.

Data Access Layer: Class Library Project: Having all classes related to data access.

You can have service layer also if needed, above is just general suggestion as I am not aware about exact scenario, so visit below links and take a informed decision:

http://fewagainstmany.com/blog/introduction-to-layered-architecture-part-one
http://en.wikipedia.org/wiki/Software_architecture
http://shareimppoints.wordpress.com/2013/03/05/what-is-3-tiermulti-tier-architecture-and-why-do-you-need-it/[^]

In case of any further query, you are most welcome.


这篇关于我的软件开发方法不好吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆