Core UML Diagrams

The following three diagrams will cover 80 percent of your object-modeling needs when building a business application using

object technology.

1. user-case diagrams

　　a.Provide an overview of all or part of the usae requirements for a system or organization in the form of an essentail model

or a business model.

　　b.Communicate the scope of a development project.

　　c.Model the analysis of your usage requirements in the form of a system use-case model.

 

　　

2.sequence diagrams

　　To analyze the use cases and map to your classes.

　　a.Validate and flesh out the logic of a usage scenario.

　　b.Explore your design, sequence diagrams provide a way for you to visually step through the invocation of the operations

　　defiend by your classes.

　　c.To detect bottlenecks within an object-oriented design.

　　d.To indicate complex classes in your application.

3.class diagrams

　　To explore the structure of your objected-oriented software.

　　a. Explore domain concepts in the form of a domain model.

　　b.Analyze requirements in the form of a conceptual/analysis model.

　　c.Depict the detailed design of object-oriented or object-based software.

 

Other UML Diagrams

4.Activity Diagrams

　　a.A complex operation

　　b.A complex business rule

　　c.A single use cases

　　d.A business process

　　e.Software process

The following activity diagram,showing the logic of how someone logs on to the system and create an order. The filled circle

represents the starting point of the activity diagram,effectively a placeholder,and the filled circle with a border represents the

ending point.

 

5. State Char Diagrams

　　Depict the dynamic behavior of an entity based on its response to events,showing how the entity reacts to various

events,depending on the current state that is in.

6.Deployment Diagrams

    A UML deployment diagram depicts a static view of the runtime configuration of hardware nodes and the

software components that run on those nodes.