我在哪里可以找到MVC的死简单的解释？ [英] Where can I find a dead-simple explanation of MVC?
问题描述
在我的公司，我们即将建立使用ASP.NET MVC一个新的站点。我的老板（营销人）想了解一些更多的技术，所以我试图找到MVC概念的一个非常好的，简单的教学presentation没有任何运气。他们中的大多数需要相当多的基础知识的编程。
At my company we're about to build a new site using ASP.NET MVC. My boss (marketing guy) would like to know some more about the technology so I've tried to find a really good, simple and pedagogical presentation of the MVC concept without any luck. Most of them require quite a lot of basic knowledge in programming.
有一个良好的视频，幻灯片或其他？
Any suggestions for a good video, slides or other?
推荐答案
克雷格强有大约MVC和一般如何pretty好的文章来解释它的好处业务。看看这里：更新链接。
Craig Strong has a pretty nice article about MVC in general and how to explain its benefits to business. Check it out here: Updated link.
记住，你是技术头脑，靠近code。 MVC你
是像白天一样清晰，但话说到企业的模型，视图
位指示可以给他们，你是患了IM pression
某种形式的抽动秽语综合征。 MVC将没有多大的业务，甚至
后相对于code定义它们。要获得业务
明白这是为什么的答案，至少这一切是什么，可以
多任务比预期以我的经验。即使是一些老乡
开发商有困难有时理解这个。
Define MVC in layman’s terms
Remember you’re technically minded and close to the code. MVC to you is as clear as day, but saying to the business ‘Model, View, Contoller’ could give them the impression that you are suffering from some form tourette syndrome. MVC won’t mean much to the business even after you define them in relation to the code. To get the business to understand why this is the answer and least of all what it is, can be more of a task than expected in my experience. Even some fellow developers have difficulty understanding this on occasion.
要获得听众了解MVC是什么，为什么它的工作原理是什么我
在通已经尝试是MVC适用于不同的行业，其中
听众有更多的参与。已经工作的一个例子
对我来说，在比较的财产，甚至过去
汽车。大多数人都已经处理与建设者，木匠，
水管工，电工或观看财产洪水显示了
电视。这方面的经验是一个很好的平台使用，并解释为什么
分离如MVC的作品。我知道你可能会想，
将无法正常工作，因为它是不一样的软件，但要记住你
不是要培养企业成为开发商或有一个在
MVC的深入了解，只是向他们解释分离
在生产中是必需的，这是一个MVC结构提供了什么。
To get the listener to understand what MVC is and why it works what I have tried in the pass is to apply MVC to a different industries where the listeners have had more involvement. An example that has worked for me in the past in a comparison to the property or even the vehicles. Most people have had dealing’s with builders, carpenters, plumbers, electricians or have watched the flood of property shows on the TV. This experience is a good platform to use and to explain why separation such as MVC works. I know you’re probably thinking that won’t work as it’s not the same as in software, but remember you’re not trying to train the business to become developers or have an in depth understanding of MVC, simply explaining to them that separation in production is required and that’s what an MVC structure offers.
要给出你怎么能形容这样的一个例子，我有很简单
分离解释财产是如何工作的。请记住，这是
集中在使用该系统不显影可以是一个完全
不同的角度解释。
To give an example of how you could describe this I have very briefly explained how separation works in property. Keep in mind this is focused on using the system not developing which could be a completely different angle of explanation.
MVC中的视图是presentation层。这是最终用户
一个产品会看到并与之交互。一个系统可以有多个
视图中的所有不同类型的，从命令行输出
呈现的HTML。该视图不包括大多数业务逻辑
清晰的设计。接口是适合目的和是的面积
相互作用。因此，你可以让消费者简单地输出HTML
用或输出SOAP / XML为企业互动交流。都
使用相同的业务逻辑或称为系统的背后
模型和控制器。
The view in MVC is the presentation layer. This is what the end user of a product will see and interact with. A system can have multiple views of all different types ranging from command line output to rendered HTML. The view doesn’t consist of business logic in most clear designs. The interface is fit for purpose and is the area of interaction. Therefore you could simply output HTML for consumers to interact with or output SOAP/XML for businesses to interact with. Both use the same business logic behind the system otherwise known as the models and controllers.
在财产的世界里，你能想到的观点是内部的
一个属性或属性的外层的居民
与。。。相互作用。内部可定制的目的和相同
属性可以有许多不同类型的租户。例如，一个
特定设计的特性可能包含民居。
同样的内部空间可以很容易地被用来作为办公场所，在那里
虽然在同一个酒店有不同的目的。然而，
属性结构是相同的。因此，环境中的
用户进行交互不与建筑物的结构干扰
In the world of property you could think of the view as the interior of a property or the outer layer of a property that the inhabitants interact with. The interior can be customised for purpose and the same property can have many different types of tenants. For example a property of a particular design could contain residential dwellings. The same internal space could easily be used as office space, where although in the same property has a different purpose. However the property structure is the same. Therefore the environment in which the users interact does not interfere with the structure of the building.
控制器是那里的奇迹发生，并定义业务
应用程序逻辑。这可能是其中用户发送响应
从视图，则该响应被用来处理内部
请求的运作和处理响应返回给用户。
以其中一个用户请求买一本书的典型反应。
该控制器具有用户ID，付款细节，送货地址和
项目的选择。这些元件然后通过业务处理
逻辑来完成购买。该数据通过系统
到模型层，并最终经过整个请求满足
业务定义，该命令被构造和用户
接收他们的项目。
The controller is where the magic happens and defines the business application logic. This could be where the user has sent a response from the view, then this response is used to process the internal workings of the request and processes the response back to the user. Taking a typical response where a user has requested to buy a book. The controller has the user id, payment details, shipping address and item choice. These elements are then processed through the business logic to complete a purchase. The data is passed through the system into the model layer and eventually after the entire request satisfies the business definitions, the order is constructed and the user receives their item.
如果我们比较这对一个属性，我们可以比较的排序
网上预定车削光开关。租户将轻弹
切换到上就像订购一本书。开关本身是一个
元件在视图层，其将请求发送到所述控制器
就像点击一个网站结账按钮。业务逻辑
在这种情况下安装的是什么电工和嵌入在
该属性的设计。将开关，从而完成
电路。电力贯穿所有的电线，包括保险丝盒
直通至电灯泡。就像用户接收
书，在此情况下，承租人接收光。整个过程背后
涉及电力电缆的场景不是本可见
承租人。它们简单地在该空间内，并从开关相互作用
那里的控制器处理请求。
If we compare this to a property, we could compare the ordering of a book online to turning on a light switch. A tenant will flick the switch to on just like ordering a book. The switch itself is an element in the view layer which sends the request to the controller just like clicking a checkout button on a web site. The business logic in this case is what the electrician installed and are embedded within the property designs. The switch is flicked, which completes the circuit. Electricity runs through all the wires including the fuse box straight through to the light bulb. Just like the user receiving a book, in this case the tenant receives light. The whole process behind the scenes involving the electricity cabling is not visible to the the tenant. They simply interact with the switch within the space and from there the controller handles the request.
MVC中的模型是最底层和处理的核心逻辑
系统在大多数情况下，这可以被看作是该层，其
与数据源进行交互。在使用MVC系统中，所述控制器
将信息传递到模型，以便存储和检索
数据。从下面的例子上面控制的定义，这
是存储在订单细节的地方。如其他股票数据
的水平，其中包括许多东西的书产品的物理位置
都存储在这里。如果是这样的最后一本书的股票订购，
这个项目的下一个请求会检查它是否可用，并禁止
顺序的项目不再可用。
The models in MVC are the bottom most layer and handle the core logic of the system. In most cases this could be seen as the layer that interacts with the data source. In systems using MVC, the controller will pass information to the model in order to store and retrieve data. Following on from the example above controller definition, this is where the order details are stored. Additional data such as stock levels, physical location of product of the book amongst many things are all stored here. If that was the last book in stock ordered, the next request for this item may check if it’s available and disallow the order as the item is no longer available.
与转向灯开关上的出例如，此水平，坚持
我们的结构可能是电力供应。当承租人笔触
交换机，内部电路必须请求电力供电
请求，它类似于当用户从所请求的数据
数据库，如在数据需要处理请求。如果住宅
未连接到一个供电，它不能完成该过程。
使用MVC的商业利益。
Sticking with out example of turning on a light switch, this level in our structure could be the electricity supply. When the tenant flicks the switch, the internal circuit must request electricity to power the request which is similar when the user requested data from the database, as in data is needed to process a request. If the dwelling isn’t connected to an electric supply, it cannot complete the process. Business benefits from using MVC
在您在解释MVC是什么得到的消息，然后你会
要看看有什么好处可以从中得到。我不会去
成大量的细节这里有我敢肯定，你可以申请福利
更准确地这直接关系到你的实际情况。至
清单只是一些基于MVC系统的共同利益都在这里
举几个例子：
After you get the message across explaining what MVC is, you will then have to see what benefits can be obtained from it. I’m not going to go into a huge amount of detail here are I’m sure you can apply benefits more accurately which are directly related to you actual situation. To list just some of the common benefits of an MVC based system here are a few examples:
- 不同的技术水平可以在不同的系统层面开展工作。例如设计者可以用很少的界面（视图）上工作
开发知识和开发人员可以在业务逻辑上工作
（控制器）与设计水平很少关注。然后他们
只是在完成整合在一起。 - 由于上述分离项目的结果可以管理更容易和更快。设计者可以启动前的接口
开发商，反之亦然。这一发展历程可以并行
而不是被连续因此减少了开发时间。 - 轻松拥有使用相同的业务逻辑多视图类型。
- 清除路线。你清楚地知道哪里有不同程度的系统都是。与系统的一个明确的路线，
逻辑可以共享和改进。这增加了安全性好处
你清楚知道从数据给用户的准许航线和能
有明确的安全检查沿线。 - 每一层是对自己负责。 （涉及到1点）这意味着你可以拥有它可以保持干净的文件结构
和管理比紧密结合系统，更容易和更快
你可能有很多重复的逻辑。 - 有一个清晰的结构意味着发展将是这应导致减少开发时间更透明，
如果运用得当的维护问题和发行周期。
通过该系统
这篇关于我在哪里可以找到MVC的死简单的解释？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
