Abstract: In terms of the role modeling, a more complete analysis method is discussed-using role use case for UML. It is proposed that the use case of UML should be defined with the view of roles and the conceptual role use case model should be used to define and analyze the system requirements. It is also proposed that the combination of role use case and UML with the 3R （refinement, realization, and reflection） mechanism and AOP should be used to build a bridge on the gap between analysis and design. Some new methods or approaches are provided for developing constructible, extensible open software systems.