软件分析阶段可使用的UML图有哪些？类图是否允许使用？

Hey there! Let’s dive into which UML diagrams are commonly used during the software analysis phase, and clear up whether class diagrams have a place here.

First, remember: the analysis phase is all about understanding requirements, modeling the business domain, and defining what the system needs to do—not how it will be built. With that in mind, here are the UML diagrams that fit this stage:

• Use Case Diagrams: The bread and butter of analysis. These map out system actors (users, external systems) and the core functionalities (use cases) they interact with. They’re perfect for capturing high-level user needs without getting bogged down in implementation details.
• Activity Diagrams: Great for visualizing business processes or user workflows. For example, mapping the steps a customer takes to place an order (from browsing to confirmation). They help teams align on the logical flow of business operations, not system internals.
• State Machine Diagrams: Useful when you need to model the lifecycle of a domain object. Think: an order moving through "Pending Payment" → "Paid" → "Shipped" → "Delivered" states. These focus on business rules around state changes, not technical state management.
• High-Level Sequence Diagrams: You can sketch simplified sequence diagrams to show how actors and system components interact for key use cases. For instance, the flow of messages when a user resets their password. The goal here is to clarify interaction logic, not to define method-level calls.
• Domain Class Diagrams: Now, to your main question—yes, class diagrams absolutely apply here! But note: this isn’t the same as the implementation-focused class diagrams you’d create in the design phase. Analysis-phase class diagrams (called domain models) focus on core domain entities, their attributes, and relationships (e.g., Customer has many Orders, Order contains Products). They’re used to formalize the structure of the business domain, not to define methods, interfaces, or technical dependencies.

The key distinction between analysis and design phase UML is that analysis diagrams prioritize business logic and user needs, while design diagrams shift to technical implementation details.

内容的提问来源于stack exchange，提问作者Mohamad