UML建模语言与方法：概念详解与实践指南

需积分: 11 4 浏览量更新于2024-07-18 收藏 4.86MB PDF 举报

"《使用UML进行建模》是一本由Bernhard Rumpe所著的软件工程专著，针对近年来软件开发领域日益增长的复杂性和多样性，该书深入探讨了统一建模语言（Unified Modeling Language, UML）在软件工程中的应用。UML作为一套标准化的图形化工具和方法论，旨在提供一套定制化的解决方案，以适应不同系统的应用领域、关键性需求以及复杂程度。在书中，Rumpe详细介绍了UML语言、概念和方法，包括但不限于项目管理、配置管理、变型和质量保证、软件产品线、开发过程、规格说明技术、分析与设计模式以及特定任务的最佳实践。这些元素构成了软件工程领域的广泛技术组合，帮助工程师们有效地设计、理解和构建软件系统。 UML作为一种通用的建模语言，它不仅仅局限于编程语言本身，而是涵盖了系统架构、交互图、类图、序列图、活动图等多种视图，使得跨团队沟通和协作更加顺畅。通过UML，开发人员可以创建出可视化的模型，以便于理解和维护复杂的软件系统，提高软件质量，缩短开发周期，并且支持软件的演化和适应性。本书不仅适合软件工程师和技术领导者，也对研究者和教育工作者有着重要的参考价值。它的目标读者群体是那些希望通过掌握UML来提升软件开发效率和质量的专业人士。版权方面，本书基于德国柏林-海德堡Springer Verlag出版社的原版，经过翻译，保留了所有权利，包括但不限于翻译权、再版权、复制权等，强调了对知识产权的尊重。《使用UML进行建模》是一本实用的指导手册，它为读者提供了丰富的理论知识和实践经验，帮助他们在现代软件开发环境中更好地利用UML这一强大的工具。"

1.2 Overview 3

language proﬁle UML/P explained in this book and the development tech-

niques based thereon are thus based on Java.

Bridge Between UML and Agile Methods: At the same time, both books

form an elegant link between the approaches of agile methods not yet inte-

grated optimally and the modeling language UML. Agile methods such as

Extreme Programming are equipped with a range of interesting techniques

and principles enriching the software engineering portfolio for certain types

of projects. Characteristics of these techniques include sparse use of docu-

mentation, concentration on ﬂexibility, optimization of time to market and,

minimization of necessary personnel resources together with concurrent re-

tention of the desired quality. Therefore, agile methods are well suited as a

foundation for the targets of this book.

Agile Methods Based on UML/P: UML is used as a notation for a num-

ber of activities such as use case modeling, target performance analysis, as

well as architectural and detailed design at different levels of granularity.

UML artifacts represent an essential foundation for planning and controlling

milestone-driven software engineering projects. Therefore, UML is mostly

implemented in plan-driven projects with relatively high documentation and

the inﬂexibility resulting from that. However, UML is more compact, seman-

tically more ample, and better suited to describe complex facts than a pro-

gramming language. That is why it has crucial advantages for modeling of

test cases and transformational evolution of software systems. Based on a

discussion of agile methods and the concepts contained therein, the second

book will outline an agile method which uses the UML/P language proﬁle

as a base for several activities without importing the inﬂexibility of typical

UML-based methods.

1.2 Overview

Chapter 2 includes a deﬁnition of the components of class diagrams, a dis-

cussion on the deployment of views and representations, and a proposal for

the deﬁnition of stereotypes and tags.

Chapter 3 introduces the design of the Object Constraint Language (OCL)

in all its semantic facets and syntactically adjusted to Java. For speciﬁcation

purposes, a two-valued logic is introduced and the expressiveness of OCL

discussed. Constructs for set comprehension, introduction of local functions,

and special OCL opera tors for ﬂattening of data structures and transitive

closure of an association are presented.

Chapter 4 contains the introduction of object diagrams as an independent

notation in UML/P. A bilateral integration of OCL and object diagrams per-

mits use of diagrams as OCL predicates and also the description of complex

constraints within a diagram through OCL. OCL logic operators are used to

describe unwelcome situations, alternatives, and the composition of object

diagrams.

1.4 Placement of UML/P 5

single keywords are highlighted or underlined. For stereotypes, transforma-

tions, test patterns, and refactoring rules, a template is presented in Table

2.19, which allows for a systematic description of the element introduced.

The following additional characters are used in the text:

• Therepresentation indicators “...” and “



” are formal parts of UML/P

and d escribe whether the representation shown in a diagram is complete

or not.

• Stereotypes are given in the form



StereotypeName



. Tags have the form

{TagName=Value} or {TagName}.

• Nonterminals are shown as Name. We add the deﬁnition number of the

nonterminal, as in OCLConstraint

C.7

, when we use a nonterminal in

another section.

1.4 Placement of UML/P

1.4.1 Importance and Scope of UML

Especially for developer communication, there are a number of advantages

of graphical notations compared with textual forms of expression. They en-

able the viewer to get a quick overview and simplify the perception of the

system’s parts and their relations. But due to their two-dimensional charac-

ter, graphical description methods also have disadvantages. They need, for

instance, considerably more space when shown or printed. This lower infor-

mation density easily leads to a lack of overview, especially with regard to

large models. Furthermore, precise deﬁnition of the syntax and semantics of

a graphical language is generally regarded to be more difﬁcult.

With the dominance of the object-oriented programming paradigm in al-

most every ﬁeld of software and system development, and systems becom-

ing increasingly complex, quite a number of object-oriented modeling ap-

proaches have been deﬁned.

The Uniﬁed Modeling Language (UML) [OMG10a] was successful in in-

tegrating different notations and, thus, became a standard modeling lan-

guage for software engineering. UML is now widely used. To allow this, the

separation of methodological considerations and the notations used within

methods was crucial. The aim of UML is to offer a modeling technique

for preferably all application domains in software engineering. Accordingly,

UML/P language proﬁle deﬁned in this book is partly methodically neu-

tral, although it is especially suited for generative projects with Java as tar-

get language. Similar approaches are shown in recent books working on

the relationship between UML and a programming language such as Java

[Lan09, Lan05].

With UML, integration of several existing modeling languages has been

achieved. Syntactic differences have been harmonized and concepts from dif-

6 1 Introduction

fering ﬁelds ha ve been integrated into the core language. Although this cre-

ated a rather large and partly overloaded language, it can be expected that

UML will claim to be the essential language standard for at least one more

decade.

1.4.2 UML Language Proﬁles

UML is no longer understood as a language deﬁned completely in all its syn-

tactic and semantic details but as a language framework or language family

[CKM

99, Gr¨o10, GRR10] which allows, due to extension mechanisms and

semantic variation possibilities, creation of language proﬁles that can be ad-

justed to the respective purpose of the application. Thus, UML has the char-

acteristic of a colloquial language such as English which also allows for ad-

justing the vocabulary in the form of technical language and dialects.

[OMG99] already deﬁned the essential requirements for UML proﬁle con-

cept, and [CKM

99] discussed how this affects the manifestation of business-

or project-speciﬁc language proﬁles.

[Gr¨o10, GRR10] reveal how the organization of syntactic and semantic

variations of a part of UML in the form of features and language conﬁgu-

rations can be shown and how it can be applied for the conﬁguration of a

language which suits the project.

Example language proﬁles include the specialization of UML to real-

time systems [OMG09], Enterprize Distributed Object Computing (EDOC)

[OMG04], multimedia applications [SE99b, SE99a], and frameworks [FPR01].

The [SE99b, SE99a], and frameworks [FPR01]. vocabulary is introduced di-

rectly into the model through the deﬁnition of classes, methods, attributes or

states. In addition, proﬁles offer lightweight extension capabilities for UML

syntax, such as the stereotypes and tags discussed in Fig. 2.17, and heavy-

weight extensions with new modeling constructs.

According to [ OMG99], the concept for deﬁning a UML proﬁle has,

among others, the following purposes:

• Precise deﬁnition of tags, stereotypes, and constraints is possible.

• Description of semantics using natural language is allowed.

• A more speciﬁc proﬁle can adjust a more general proﬁle to the desired

form.

• The combination of proﬁles allows for simultaneous use of multiple pro-

ﬁles.

• Mechanisms for managing the proﬁles’ compatibility are provided.

However, the goal of simple exchangeability and combinability of lan-

guage proﬁles cannot be fulﬁlled that easily. On the contrary, tool-based lan-

Common languages also allow for the imprint of new vocabulary through the def-

inition of terms. New modeling constructs would correspond to grammatical ex-

tensionbutarenotcommoninotherlanguages.

剩余287页未读，继续阅读

xptao

粉丝: 0
资源: 2

UML建模语言与方法：概念详解与实践指南

Business Modeling with UML.pdf

Business Modeling with UML：Business Patterns at Work.pdf

Use Case Driven Object Modeling with UML

英文资料 Entity Relationship Modeling with UML

Applying Use Case Driven Object Modeling with UML

Business Modeling with UML Business Patterns at Work.

Object-Oriented Analysis and Design for Information Systems Modeling with UML

Addison Wesley - Applying Use Case Driven Object Modeling with UML.chm

Use Case Driven Object Modeling with UML pdf（非扫描版）

Effective Business Modeling with UML-Describing Business Use Cases and Realizations-TheRationalEdge_Nov2002.pdf

最新资源