blocks|key|2235014|text|存在一个名为UWA+(Ubiquitous+Web+Application)的metodology，它不仅允许您描述数据结构，还允许您描述导航、表示和事务模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2235015|UWA方法有一个以用户为中心的方法，它改进了需求和设计定义。由于这种metodology是专门为web应用程序建模而开发的，因此它允许清晰地分离内容、导航、事务、发布和操作元素。|2235016|UWA从面向目标的需求工程开始，自然地出现在后期设计阶段，揭示了应该实现的关键功能。这导致了对一些需求的推理，这些需求可能没有事先确定，或者可能被低估了。|2235017|你可以找到更多关于UWA+here的信息。|2235018|即使您决定不应用此方法，它也可以为您提供一些使UML图适应web应用程序的技巧。|2235019|entityMap|0|LINK|mutability|MUTABLE|url|http://www.academia.edu/2445027/Model-driven_development_of_web_applications_with_UWA_MVC_and_JavaServer_faces|1|http://citeseerx.ist.psu.edu/viewdoc/similar;?doi=10.1.1.216.8011&type=ab^0|B|Q|0|0|0|0|D|4|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

There exist a metodology named UWA (<a href="http://www.academia.edu/2445027/Model-driven_development_of_web_applications_with_UWA_MVC_and_JavaServer_faces" rel="nofollow">Ubiquitous Web Application</a>) that allows you to describe not only the data structure, but also the navigation, presentation and transaction models.

The UWA methodology has a user-centered approach, which improves the requirement and design definitions. Since this metodology was developed specifically for modelling web applications, it allows a clear separation of content, navigation, transaction, publishing and operational elements. 

UWA begins with a goal-oriented requirements engineering that naturally arise to later design stages, revealing key features that should be implemented. This leads to reasoning about some requirements that might have not been identified beforehand, or may have been underrated.

You may find additional information about UWA <a href="http://citeseerx.ist.psu.edu/viewdoc/similar;?doi=10.1.1.216.8011&amp;type=ab" rel="nofollow">here</a>.

Even if you decide not to apply this methodology, it may provide you with some tips about adapting UML diagrams to web applications.

blocks|key|2235061|text|您可能想尝试健壮性图表，有时也称为MVC图表。请参见示例here和there。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2235062|它不是一个真正的UML图，但是大多数UML工具通过构造型和自定义图标来管理它。我使用的工具Magicdraw使用类图，但我想我听说过使用通信图的工具(虽然不确定)。|2235063|但是，它可能满足您的期望，也可能不满足您的期望，因为它是一个非常全局的图表。|2235064|entityMap|0|LINK|mutability|MUTABLE|url|http://iconixprocess.com/iconix-process/analysis-and-preliminary-design/robustness-analysis/|1|http://alvinalexander.com/uml/uml-model-view-controller-mvc-diagram^0|S|4|0|X|5|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

You may want to try the Robustness diagram, also sometimes called MVC diagram.
See for example <a href="http://iconixprocess.com/iconix-process/analysis-and-preliminary-design/robustness-analysis/" rel="nofollow">here</a> and <a href="http://alvinalexander.com/uml/uml-model-view-controller-mvc-diagram" rel="nofollow">there</a>.

It is not really a UML diagram, but most UML tools manage it through stereotypes and custom icons. The tool I use, Magicdraw UML, uses a class diagram, but I think I heard of tools that use communication diagrams (not sure, though).

However, it may or may not meet your expectations, as it is a very global diagram.

blocks|key|111581|text|你以前遇到过用例图吗？严格来说，它不是勾勒系统架构的图表，但它确实提供了在给定的“用例”(或过程)期间与系统的其他部分/外部参与者进行通信的良好可视化表示。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|111582|例如：用户(执行元)+-->更新状态(用例)--包括-->(登录)|111583|这里我们有一个用户想要更新他们的状态。为了做到这一点，他们需要登录到站点(一个包含的用例)。在MVC模式中考虑这一点，我们知道"Update+Status“和"Log+in”都是控制器方法，它们都将与被吸引的网站数据库(也是一个参与者)通信，从而演示系统内的通信路径。|111584|系统的参与者可以是在过程中与实际系统通信的任何东西，通常是外部的，因此用户、浏览器、数据库、客户端等。就MVC体系结构建模而言，类图最好完成这一点，但用例图也有助于可视化表示。|111585|在我开始编码之前，我总是把用例和类图一起画出来，作为提取系统需求并在工作设计中展示它们的一种方式。UML图毕竟是设计工具--在你写完系统代码之后，创建一个图并没有多大意义！|111586|无论如何，只是一些需要思考的事情-希望这能有所帮助！brief+overview+of+basic+use-case+diagrams|111587|entityMap|0|LINK|mutability|MUTABLE|url|http://www.agilemodeling.com/artifacts/useCaseDiagram.htm^0|6|3|0|0|0|0|Q|6|0|Q|15|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|P|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

Have you ever come across a Use Case Diagram before? It's not strictly a diagram to outline a systems architecture, but it does provide a good visual representation of communication with other parts of the system/ external actors, during a given "use case" (or process). 

For example:
User(Actor) --> Update Status(Use Case)--includes-->(Log in)

Here we have a user wanting to update their status. In order to do this, they need to be logged into the site (an included use case). Thinking about this in MVC mode, we know that "Update Status" and "Log in" would both be controller methods, which would both communicate with the attracted website database (also an actor), thus demonstrating the communication path within a system.

Actors of a system can be anything that communicates with the actual system during a process, usually externally, so users, browsers, database, clients etc. 
In terms of modelling the MVC architecture, this is done best by the Class diagram, but a Use Case diagram would also aid in the visual representation. 

I always draw up a Use Case and Class Diagram together before I start coding, as a way of extracting the system requirements and laying them out in a working design. UML diagrams are design tools after all- there's not really much point in creating one after you've written the system code!

Just something to think about anyway- hope this helps!
<a href="http://www.agilemodeling.com/artifacts/useCaseDiagram.htm" rel="nofollow">brief overview of basic use-case diagrams</a>

I'm building a rails application and I'm having trouble working out how create diagrams for the application architecture.

I've created UML class diagrams in the past, so consequently that's where I headed. I've found the railroady gem that generates UML class diagrams via a rake task, however it separates the models from the controllers - which feels fragmented to me.

What I want to know is whether there is another (preferably better) way to model an MVC (rails) web application.

I'm not necessarily looking for a gem to generate the diagram for me, I'm happy to create it manually in visio, I just don't know what type of diagram I should be using.

Other than a class diagram is there another way (with or without UML) to model an MVC web application design?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在构建一个rails应用程序，但我在解决如何为应用程序架构创建图表时遇到了麻烦。我在过去创建过UML类图，因此这就是我要去的地方。我已经找到了通过rake任务生成UML类图的railroady gem，但是它将模型与控制器分开了--这让我感觉很零碎。我想知道的是，是否有另一种(最好是更好的)方法来为MVC (rai...

问除了类图之外，是否还有其他方法(使用或不使用UML)来对MVC web应用程序设计进行建模？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问除了类图之外，是否还有其他方法(使用或不使用UML)来对MVC web应用程序设计进行建模？EN