Using Rational Rose (Express)

Rational Rose

Use Case Diagram: Use Case Diagram

Class Diagram: Class Diagram

Object Diagram: Object Diagram

Component Diagram: Component Diagram

Deployment Diagram: Deployment Diagram

Sequence Diagram: Sequence Diagram

Collaboration Diagram: Collaboration Diagram

State diagram: Statechart Diagram

Activity Diagram: Activity Diagram

Select Toolbar Views=》Toolbars=》Configure... option, select Use Case in the window, and the custom toolbar window will pop up 

Define internal management business:

The following are the specific steps to create the corresponding classes and objects in the "Class Diagram View" in Rational Rose and associate them with the use case:

  1. In the Navigator pane on the left, select Class Diagram View.
  2. In the class diagram view, create a new class and name it "Member Information".
  3. In this class, define the properties and methods of member information. For example: name, student number, contact information, adding members, modifying members and deleting members, etc.
  4. Create another new class and name it "Meetings and Events".
  5. In this class, define properties and methods for meetings and events. For example: name, time, location, adding meetings and events, modifying meetings and events, and deleting meetings and events, etc.
  6. Associate these classes with the use cases you create in the use case view. For example: Associate the "Member Information" class with the "Member Management" use case and the "Meetings and Events" class with the "Organize Meetings and Events" use case.
  7. These classes can be associated with each other using association relationships. For example: Add an association to the "Member Information" class to associate it with the "Meetings and Events" class.

Note that this is just a common way to create classes and objects in Rational Rose and associate them with use cases, the implementation can be adjusted to your needs.

How to define the university student union management system in Rational Rose and establish the internal management business boundary, specific steps are required, for novices, specific examples are required

OK, the following are the specific steps to define the internal management business boundary of the university student union management system in Rational Rose:

  1. Open Rational Rose and create a new project.
  2. In the Navigator pane on the left, select Use Case View.
  3. In the Use Case View, create a new use case and name it "Internal Management Business Boundary".
  4. In this use case, define the functionality and behavior that you want to achieve within the internal management business boundary. For example: adding, modifying and deleting member information, organizing meetings and events, reviewing and approving budgets, etc.
  5. You can use associations to associate other use cases with this use case to better organize and manage your project. For example: Associated with the "Member Management" use case and the "Budget Management" use case.
  6. In the Navigator pane on the left, select Class Diagram View.
  7. In the class diagram view, create a new class and name it "Member Information".
  8. In this class, define the properties and methods of member information. For example: name, student number, contact information, adding members, modifying members and deleting members, etc.
  9. Create another new class and name it "Meetings and Events".
  10. In this class, define properties and methods for meetings and events. For example: name, time, location, adding meetings and events, modifying meetings and events, and deleting meetings and events, etc.
  11. Use an association relationship to relate the "Internal Management Business Boundary" use case to the "Member Information" and "Meetings and Events" classes.
  12. You can use other relationships, such as generalization and aggregation, to further organize and manage your projects.

For example, you could use an aggregation relationship to associate the "Meetings and Events" class with the "Budget Management" use case to indicate that the Budget Management use case needs access to meeting and event information to approve budgets.

Guess you like

Origin blog.csdn.net/m0_62110645/article/details/131235126
Recommended