You are on page 1of 3

<?xml version="1.0" encoding="UTF-8"?

> <UMLProfile> <Documentation id="BPProfile" name="UML Profile for Business Modeling" v ersion="1" notes="A set of stereotypes and tagged values for modeling business p rocesses"/> <!-- The profile content --> <Content> <!-- List of stereotypes used in this profile--> <Stereotypes> <!-- <<UseCaseModel - EA supports this thru Package>> -> <Stereotype name="useCaseModel" notes="A model that desc ribes the busness processes of a business and their interactions with external p arties"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<UseCaseSystem>> --> <Stereotype name="useCaseSystem" notes="Top level packag e in a use case model, may contain use case packages, use cases and relations"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<Use Case Package>> --> <Stereotype name="useCasePackage" notes="A use case pack age is a package that may contain use cases and relationships"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<ObjectModel>> --> <Stereotype name="objectModel" notes="A Model whose top level package is an object system that describes the things interior to the busi ness itself"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<ObjectSystem>> --> <Stereotype name="objectSystem" notes="An object system is the top level subsystem in an object model and may contain organization units , work units, classes and relationships"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<OrganizationUnit>> --> <Stereotype name="organizationUnit" notes="An Organizati on Unit is a subsystem that may contain other organization units, work units, cl asses and relationships"> <AppliesTo>

<Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<WorkUnit>> --> <Stereotype name="workUnit" notes="A Work Unit is a subs ystem that may contain one or more entities. It is a task oriented set of object s that forms a recognizable whole to the end user, and may have a facade definin g the view of the work unit's entities relative to the task"> <AppliesTo> <Apply type="package"/> </AppliesTo> </Stereotype> <!-- <<Worker>> --> <Stereotype name="worker" cx="60" cy="60" notes="A Worke r class that represents an abstraction of a human that acts within the system. A Worker interacts with other workers and manipulates entities while particpating in use case realizations"> <AppliesTo> <Apply type="class"/> </AppliesTo> </Stereotype> <!-- <<Case Worker>> --> <Stereotype name="caseWorker" cx="60" cy="60" notes="A Case Worker is a special case of a worker that interacts directly with Actors ou tside the system"> <AppliesTo> <Apply type="class"/> </AppliesTo> </Stereotype> <!-- <<Internal Worker>> --> <Stereotype name="internalWorker" cx="60" cy="60" notes ="An Internal Worker is a special case of Worker that interacts with other worke rs and entities inside the system"> <AppliesTo> <Apply type="class"/> </AppliesTo> </Stereotype> <!-- <<Entity>> --> <Stereotype name="entity" cx="60" cy="60" notes="An ent ity is a passive class: its objects do not initiate interactions of their won. A n entity object may particpate in many use case realizations and usually outlive s any single interaction"> <AppliesTo> <Apply type="class"/> </AppliesTo> </Stereotype> <!-- <<Communicate>> --> <Stereotype name="communicate" notes="A association used for defining that instances of the associated classifiers interact"> <AppliesTo> <Apply type="association"/> </AppliesTo> </Stereotype>

<!-- <<Subscribe>> --> <Stereotype name="subscribe" notes="A subscribe associta ion between two classes states an object of the source class (subscriber) will be notified when a particular event occurs in the target (publisher)"> <AppliesTo> <Apply type="association"/> </AppliesTo> </Stereotype> </Stereotypes> </Content> </UMLProfile>

You might also like