《UML业务流程建模》由会员分享，可在线阅读，更多相关《UML业务流程建模（32页珍藏版）》请在金锄头文库上搜索。
1、 BUSINESS PROCESS MODELING WITH UMLAuthor: Craig DewaltInstructor: Karthik Shyamsunderfor Johns Hopkins University7 December 19992CONTENTSABSTRACT and KEYWORDS.3 UML INTRODUCTION.4 BUSINESS PROCESS MODELING 6 IDEF0 MODELS.9 INFOMARKET.COM.11 MODELING PROCESSES IN USE CASE DIAGRAMS.12 HIGH LEVEL PROC
2、ESSES WITH UML PACKAGES .15 SEQUENCE DIAGRAMS VERSUS ACTIVITY DIAGRAMS.16 ADVANCED MODELING CONCEPTS.18 CONCLUSION.20 DEFINITIONS31 WORKS CITED.32LIST OF ILLUSTRATIONSEXAMPLE 1 IDEF0 Basic Semantics.9 EXAMPLE 2 Register Account Use Case.21 EXAMPLE 3 Seller Services Use Case Diagram.22 EXAMPLE 4 I Pa
3、ckages23 EXAMPLE 5 Register Account Sequence Diagram.24 EXAMPLE 6 Register Account Activity Diagram27 EXAMPLE 7 Modified Register Account Activity Diagram 293ABSTRACTThe Unified Modeling Language (UML) is a powerful notation for building software blueprints. This report shows UML diagrams of busines
4、s processes that are used for analyzing information instead of building software blueprints. The diagrams capture business process information for a fictional internet company. Since the diagrams show both general and detailed information, they demonstrate that UML is capable of displaying various k
5、inds of information. Flexible, easy to comprehend, and easy to build are traits that make UML diagrams a superior choice for business process modeling. KEYWORDSAbstraction, Actor, Activity Diagram, Business Process, Class, Extensibility Mechanism, Interaction Diagram, IDEF, Model, Object-Oriented An
6、alysis, Object, Package, Sequence Diagram, Use Case, Use Case Diagram4UML INTRODUCTIONThe Unified Modeling Language (UML) is a standard language for writing software blueprints that premiered with version 1.1 in 1997. Three prominent object-oriented programming professionals, Gray Booch, Ivar Jacobs
7、en, and James Rumbaugh are the principle authors of UML. UML establishes a collection of graphical symbols as well as semantics to support and define these symbols. This collection can be broken down into three kinds of building blocks: things, relationships, diagrams. Things are the abstractions th
8、at are first-class citizens in a model; relationships ties these things together; diagrams group interesting collections of things. There are nine different kinds of diagrams in UML: class, object, use case, sequence, collaboration, statechart, activity, component, and deployment (Booch, Jacobsen, R
9、umbaugh, The Unified Modeling Language Users Guide 13-18). UML traces is origins to the software development field. Many of the definitions for UML artifacts and notation define rules and semantics based on the assumption that the purpose is building or designing software elements. An element is an
10、atomic constituent of a model (Booch, Jacobsen, Rumbaugh, The Unified Modeling Language Users Guide 461). What if, however, the purpose was not to build models in support of a software system, but instead to map out business processes? Is UML still expressive enough so that it is useful in capturing
11、 information that is not going to be used to produce software? One early indication that UML is well suited for this task is that many of the concepts in UML previously existed in object-oriented programming. One part of object-oriented programming is object-oriented analysis. Object-oriented analys
12、is is a method 5of analysis that examines requirements from the perspective of the classes and objects found in the vocabulary of the problem domain (Booch 39). An object is something you can do things to (Booch 516). A class is a set of objects that share a common structure and a common behavior (B
13、ooch 512). The significance of object-oriented analysis is to build objects that directly represent things in the physical world. Other techniques try to capture information and translate that information into some kind of container that is well suited for constructing software but may not exist out
14、side of the software. Object-oriented analysis equates a real entity to a corresponding software entity as closely as possible. Since UML is built upon many of the principles of object-oriented programming including object-oriented analysis, it is likely that UML is also effective at representing re
15、al-world entities. One limitation to building UML diagrams that are not going to be directly used to build a software system is that many definitions in UML include references to software systems. Some degree of interpretation is therefore necessary in order to use UML outside its intended purpose. 6BUSINESS PROCESS MODELINGA model is a representation of a set of components of a process, system, or subject area (United States General Accounting Office
