传统的软件开发还不够吗？ [英] Is traditional software development still enough?

问题描述

大家好，



我对传统软件解决方案的功能有疑问。我习惯为合理规模的组织开发管理系统。但是，组织越大，系统越复杂，使用传统（标准）应用程序的可能性也越大。我想知道为什么会这样。



例如，我一直在构建的系统是使用WinForms / C＃，ASP.NET，SqlServer和最多2000个存储过程完成的。 。如果我今天要开办一家新银行，这是否足够（技术上和实际上）？或者为什么不呢？



对我来说，没有什么比WinForms开发的灵活性和简单性更好。我知道有些OOA / D很难实现，但易用性使它（在我看来）成为任何（桌面）管理应用程序的不错选择。



我知道有许多新的软件开发方法，但问题是这些软件经常会在一段时间后消失。对我来说，使用具有良好记录并且已经存在并且稳定多年的解决方案是非常有意义的 - 特别是对于需要极其可靠的软件的组织（例如银行）。 br />


您是否同意或者是否b / b
。为什么BIG系统需要更强大的（？）软件解决方案的一个很好的理由/>


2.一个很好的理由（除了OO整洁）为什么使用WinForms - ASP.NET - 关系数据库组合不再适用了？



爱所有人，



Petter

Hi all,

I have a question regarding the power of traditional software solutions. I am used to developing administrative systems for reasonably sized organizations. However, the larger the organization, the more complex the system, and also the increased likelihood of the use of less traditional (standard) applications. I wonder why this is.

For example, the systems I have been building have been accomplished using WinForms/C#, ASP.NET, SqlServer and up to 2000 stored procedures. If I were to start a new bank today, would this suffice (technically and practically)? Or why not?

To me, nothing really beats the flexibility and simplicity of WinForms development. I know that some OOA/D is hard to accomplish with it, but the ease of use makes it (in my opinion) a good choice for any (desktop) administrative applications.

I know that there are many new ways of developing software, but the problem is that these often disappear after a short while. To me, it makes a lot of sense to work with solutions that have a proven track record and that have been around and stable for a number of years - especially for an organization in need of extremely reliable software (such as a bank).

Do you agree or is there
1. a good reason why more powerful (?) software solutions are needed for a BIG system

2. a good reason (apart from OO neatness) why working with the WinForms - ASP.NET - relational DB combo is not suitable anymore?

Love to all,

Petter

推荐答案

WPF击败WinForms为了灵活性，它不是那么容易理解和使用。



ASP.NET MVC击败ASP.NET以更清晰地分离模型和视图但它并不是那么简单。



据我所知，WPF和ASP.NET MVC也更容易测试。对于大型应用程序，测试涵盖更多应用程序可能会带来巨大好处。事实上，对于需要可靠软件的组织来说，使用测试驱动的软件开发可能是一个好主意，因此使用更可测试的技术可能是一个巨大的好处。

WPF beats WinForms for the flexibility but it is not as simple to understand and use properly.

ASP.NET MVC beats ASP.NET for cleaner separation of the model and the view but it is not as simple.

As far as I know both WPF and ASP.NET MVC are more testable too. For large application, it might be huge benefit to have more of the application covered by tests. In fact, for organisation that need reliable software, it is probably a good idea to use test driven software develpment and thus using technologies that are more testable mightbe a huge benefit.

有这么多在进入一组新平台之前的因素。

这可能取决于你的技能，要求是什么以及客户要求的是什么。



银行集团从事后台工作可能对在Windows窗体上开发的基于Intranet的软件感到满意。



前端银行集团甚至可能需要基于移动应用程序的软件，因为他们的客户可能正在进行前端交易在应用程序上。



新东西可能不是更强大。它可能适合移动应用程序等新的要求，但如果您/您的客户没有寻找Web / app部署，则不一定提供任何特别的东西。



如果你是看着更新自己的技能，也许你可以使用这些新工具。

There are so many factors before moving into a new set of platforms.
It could depend on your skill sets, what the requirements are and what the clients demand.

A banking group doing back-office work may be happy with an intranet based software developed on windows forms.

A front end banking group may even want mobile app based software since their customers might be doing front end transactions on the app.

Newer stuff is probably not more powerful. It may suit newer requirements like mobile applications etc but is not necessarily providing anything extraordinary if what you / your client is not looking for web / app deployment.

If you are looking at updating your own skills then perhaps you can use some of these new tools.

这篇关于传统的软件开发还不够吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！