销售应用架构点 [英] Point of Sale Application Architecture

问题描述

我被要求建立一个餐厅POS应用。我有经验创造VB6.0 POS应用，并一直想创建一个与UX。我期待创建一个使用WPF作为前端。我pretty多心目中也是屏幕的过程画面。

I have been asked to build a POS Application for a Restaurant. I have experience creating POS application in VB6.0 and have always wanted to create one with UX. I am looking to create one with WPF as front end. I pretty much have the process picture in mind and also screens.

说了这么多，我不知道如何架构之一。

Said so much, I am not sure how to Architecture one.

这，我想起几个主要问题是：

Few Major questions that come to my mind are :

我应该使用复合应用程序指南WPF - 棱镜。如果答案是肯定的意志性能降低在POS应用程序，时间是至关重要的，客户想要及时的服务。

Should I use Composite Application Guidance for WPF - Prism. If the answer is yes will performance reduce as in POS Application, time can be critical, customers want prompt service.

我想依赖注入应该用于更好的维护。

I am thinking Dependency Injection should be used for better maintenance.

我想以后发展这个应用程序，包括库存管理和数据挖掘，管理报告。

I want to grow this application later to include Inventory Management and Data Mining, Management reports.

将使用POS用于.NET

will use POS for .NET

希望我就能得到这一切都清楚了这个周末。

Hope I will be able to get this all cleared up this weekend.

请告知。

感谢您，

月

编辑：
我仍然任由会想获得更多的意见/建议。

I am still leaving it open will like to get more views/ advises.

推荐答案

还有一般问题很多，我会尽力去触摸一点点的一切。

Lots of general questions there, I'll try to touch a little on everything.

一般来说，你应该看看应用架构指南。这是对架构的各种.NET应用程序的一个非常好的，通用引物。

In general you should check out the Application Architecture Guide. It's a very good, general primer on architecting all sorts of .NET applications.

我不认为你将不得不使用 Prisim 的任何问题。采取具体注意 MVVM模式的。在性能的问题，我觉得你真正谈论的是响应。所以allplication需要一个POS非常响应于用户。使用WVVM，你可以在你的应用程序得到很好的响应。

I don't think you are going to have any problem with Prisim. Take specific note of the MVVM Pattern. On the "performance" issue, I think what you are really talking about is "responsiveness". So a POS allplication needs to be very responsive to the user. Using WVVM, you can get very good responsiveness in your application.

就个人而言，我会从这个版本实体框架望而却步（虽然<一个href=\"http://blogs.msdn.com/adonet/archive/2009/05/18/sneak-$p$pview-entity-framework-4-0-testability-improvements.aspx\"相对=nofollow>下一个版本好看）。我认为LinqToSQL是好的（毕竟，所以使用它:)看看 NHibernate的用于.NET 如果你想ORM。

Personally, I would stay away from this version of Entity Framework (although next version is looking good). I think LinqToSQL is fine (afterall, SO uses it :) Look at NHibernate for .NET if you want ORM.

祝你好运。

这篇关于销售应用架构点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！