问题描述
在一家大公司中，哪些图表（例如活动或类）是在开发特定应用程序之前创建的？
On a big company, which diagrams (such as activity or class) are created before the development of a specific application?
你们建议这种做法
谢谢
推荐答案
最终取决于公司使用的开发方法类型。而且，说实话，这取决于团队的专业知识，所开发系统的类型，客户需求以及许多其他因素。
That is pretty open-ended and depends quite a bit on the type of development methodology the company is using. And, honestly, it depends on the expertise of the team, the type of system being developed, customer requirements, and many other factors as well.
根据我的经验，通常会看到（在大型的面向瀑布的公司中）行为（用例，活动），然后进行互动和互动。类图。根据大小，您可能还会在项目的早期阶段看到一些高级架构图-组件/部署。
In my experience, you will typically see (in a big, waterfall oriented company) behavioral (use cases, activity) , then interaction & class diagrams. Depending on the size, you may also see some high level architectural diagrams in the early phases of a project as well -- component/deployment.
每个项目都应标识图这将帮助他们构建软件，而不是使用千篇一律的方法。我建议使用最少的图表，让您考虑问题，记录将来的解决方案，并将问题/解决方案传达给构建软件的人员。
Every project should identify the diagrams that will help them build the software, rather than using a cookie cutter approach. I would suggest the minimum diagramming that lets you think about the problem, document the solution for the future, and convey the problem/solution to the people building the software. What that means depends on the developer.
例如，如果您以前构建了10个与要构建的应用程序非常相似的小型应用程序，则可能不会根本需要很多文档。如果您是该领域的新手，或者您的客户想要特定的图表，或者您的团队地理位置分散，那么您可能还需要另一套图表。
For example, if you have previously built 10 small applications that are very similar to the application you are about to build, you may not need much documentation at all. If you are brand new to the domain, or if you have a customer that wants specific diagrams, or your team is geographically dispersed, then you may need yet a different set of diagrams.
顺序图通常最有助于理解系统的行为，而类图通常最有助于理解系统的结构。
Sequence diagrams tend to be most helpful in understanding the behavior of your system while class diagrams tend to be most helpful in understanding the structure of your system.
这篇关于UML图-讨论的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！