UML is widely accepted as a standard. It is competent in system level modeling and static structure analysis but lacks constructs for enterprise and business process modeling: areas which are vital for a competent technique: especially given the trend to use object technology to support enterprise engineering and implement value chains transcending organizational boundaries.
The author previously extended the Martin/Odell OOA/D methods to incorporate stakeholder, enterprise, value chain and business modeling techniques. In 1998, equivalent extensions were proposed to UML to cope with enterprise and business process modeling. The approach has since been refined through experience and has proven effective in supporting sustainable business engineering. This paper reports the results of this experience and proposes the replacement of Use Cases and other dynamic models within UML with process models which transition seamlessly from stakeholder to design level. The suggested notation represents a Use Case and Activity Diagram superset.
?Date?
?Keywords?
Published?