设计类和分析类有什么区别? [英] what is the difference between design classes and analysis classes?

问题描述

我正在尝试创建分析类图和绘图类图，我无法详细了解每一个来阐述它们的图.任何人都可以解释其中的区别，我使用的是 MVC 架构模式，我将非常感谢提供的任何提示.

I am trying to create the analysis class diagram and the drawing class diagram, I cannot understand each one in detail to elaborate their diagrams. Anyone can explain the difference, I am using the MVC architecture pattern, I will be very grateful for any tip presented.

推荐答案

好消息是 1) 您可以将 UML 用于不同的目的 2) UML 始终是 UML:

The good news is that 1) you can use UML for different purposes and 2) UML is always UML:

• 分析旨在了解问题和要求.分析模型将重点放在业务领域，而不影响解决方案的内部结构.因此，如果您正在考虑 MVC，则该模型将只关注 M.

• The analysis has the purpose to understand the problem and the requirements. An analysis model puts the focus on the business domain, without prejudice of how the solution's internals could look like. So if you're thinking of MVC, this model would focus on the M only.

设计有目的想出适合解决问题和满足要求的解决方案.MVC 的美会出现在设计模型中，因为 MVC 是解决方案的一部分，而不是(功能)需求的一部分.

The design has the purpose to think of a solution suitable to solve the problem and fulfill the requirements. The beauty of MVC would appear in the design model since MVC is part of the solution and not of the (functional) requirements.

分析模型的结束和设计模型的开始取决于方法框架:

Where the analysis model ends and the design model starts depends on the methodological framework:

• 很多时候，您只会在分析中发现域对象.该设计将通过有关内部结构的附加类来丰富分析模型.
• 在《统一软件开发过程》一书中，UML 之父解释了如何他们认为它可以用于迭代和用例驱动的方法.然后，分析模型有一些表示用例的类(使用 Entity-Contol-Boundary)
• Scott Ambler 的 Agile UP 已将分析模型重命名为需求模型.对他来说，设计模型应该是整体解决方案的草图，有足够的细节来理解它是如何工作的，但不要太多，因为设计可能会发展.我完全赞同这个观点.

• Very often, you'll find in the analysis only domain objects. The design would enrich the analysis model with additional classes about the internals.
• In the book "The Unified Software Development Process", the fathers of UML explain how they think it could be used in an iterative and use case driven approach. The analysis model then has some classes that represent the use-cases (with Entity-Contol-Boundary)
• Scott Ambler's Agile UP has renamed the analysis model into requirement model. For him the design model should be a sketch of the overall solution, with sufficient details to be able to understand how it works, but not too much because the design might evolve. I fully subscribe to this point of view.

最后，值得一提的是，有些人将分析模型视为一个临时模型，将被丰富为设计模型.其他人将它们视为两种不同的模型.是否维护它是另一个需要在项目中澄清的方法论问题.

Finally, it's worth mentioning that some see the analysis model as a temporary model that will be enriched to become the design model. Others see them as two different models. Whether to maintain it or not is then another methodological question to be clarified in the project.

这篇关于设计类和分析类有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！