Roleware™: The tools which support the creation, dissemination and maintenance of Role Models and Role-based business practices.

The Roleware UseCase Development System simplifies the process of building and maintaining graphical and text representations of RoleModeling Domains. The RoleModel Documenter produces either Microsoft Word or direct-printed representations of a stored Domain.

A Domain can include Role Models, hierarchical UseCases, and Scenarios.   The Development System supports modeling at several levels of detail and maintains consistency among the Domain elements. At the simplest level, models can just contain Role definitions. At the next level, Responsibilities are identified for the Roles. Then the Collaborations each Role participates in can be added. The system automatically maintains forward and backward (Has Collaborators and Is A Collaborator Of) collaboration traces.

Domain Directory Window Showing Roles in the Model

At a more detailed level of modeling it is possible to identify Tasks which a Role performs and Information Items for which a Role is responsible (i.e., items it saves). You can also identify the Information Items   communicated to a Collaborator when it is requested to perform one of its tasks.

UseCases can contain (sub)UseCases. Nested UseCases form a hierarchy of UseCase relationships, from the highest level to the most detailed. This hierarchy can also be used to preserve a record of requirements which change or have changed over time. The UseCase hierarchy is independent of Role definitions. 

UseCase Window

A UseCase can have one or more Scenarios associated with it. Multiple Scenarios per UseCase arise if a UseCase is applied to more than one Model (i.e., set of Role definitions).

UseCase and Scenario portions of the Domain Directory

Scenarios can be built with several levels of detail. At the simplest level, a Scenario can just have a text description of the sequence of Events involved. Then the Events can be explicitly entered into the system. The Role Instance which Triggers the Event and the Role Instance which is invoked by the  Event (its Collaborator) can then be identified. A a more detailed level, the Task which is invoked can be noted and then values of the Information Items communicated to that Task can be entered as can the resulting values of the Information Items saved by the Collaborator.

Scenario Form showing its Role Instances page

Graphical Scenario Views can be produced to show or hide the details of a Scenario.

Portion of a Scenario View

[ Welcome ] [ Up ]

For further information send mail to info@rolemodeling.com
If you havequestions or comments about this web site please submit a  feedback form or send mail to webmaster@rolemodeling.com.