面向对象设计的UML实践(英文影印版)
[绝版]基本信息
- 原书名:Practical Object-Oriented Design with UML
- 原出版社: McGraw-Hill
- 作者: Mark Priestley
- 丛书名: 大学计算机教育丛书(英文影印版)
- 出版社:清华大学出版社
- ISBN:7302040982
- 上架时间:2001-2-5
- 出版日期:2000 年12月
- 页码:356
- 版次:1-1
- 所属分类:
计算机 > 软件工程及软件方法学 > UML
内容简介回到顶部↑
面向对象方法及技术的发展推动了对象建模技术的发展,而后者的发展又促进了前者的进步。本书完整详尽地给出了对象建模表示法严格的一致性形式化定义,以及从设计到实现的面向对象开发全过程。书中UML的表示法采用了,兼容以OMT为主,以及Booch、Cood—Yourdon等目前主要流行的三种建摸表示法。
主要内容:1. UML对象建模的基本概念、方法、技术和表示法的详细内容,提供了可视化、文档化、可构造的系统体系结构规格说明设计的论述。2.介绍了一种基于文本的对象约定语言OCL。该语言不但处理标准约定,并且处理完整的、一般化的、任意性的约定条件(包括上下文、流向、联接、集合及反复等结构)。为提高和保证系统的软件质量,这种规格说明在面向对象的设计中尤为重要。3.结合大量实例,提供了从面向对象设计到面向对象代码实现清晰的关系和详细的过程。具体例子的实现采用JAVA l.0及C++语言,易于广大读者阅读和实践。4.每章末尾提供大量练习, 有助于读者加深理解内容和进行面向对象设计开发的试验。5.在www.mcgrow-hill.co.uk/textbooks/priestley网站上,能找到书中例子和练习的全部资料。
本书对于无论是在面向对象软件开发颇有经验的工程技术人员,还是开始接触面向对象软件开发的人员,都有很好的参考价值。作为软件工程的一种潮流发展技术,本书也可作为大学教师、研究生和高年级学生的参考书。
主要内容:1. UML对象建模的基本概念、方法、技术和表示法的详细内容,提供了可视化、文档化、可构造的系统体系结构规格说明设计的论述。2.介绍了一种基于文本的对象约定语言OCL。该语言不但处理标准约定,并且处理完整的、一般化的、任意性的约定条件(包括上下文、流向、联接、集合及反复等结构)。为提高和保证系统的软件质量,这种规格说明在面向对象的设计中尤为重要。3.结合大量实例,提供了从面向对象设计到面向对象代码实现清晰的关系和详细的过程。具体例子的实现采用JAVA l.0及C++语言,易于广大读者阅读和实践。4.每章末尾提供大量练习, 有助于读者加深理解内容和进行面向对象设计开发的试验。5.在www.mcgrow-hill.co.uk/textbooks/priestley网站上,能找到书中例子和练习的全部资料。
本书对于无论是在面向对象软件开发颇有经验的工程技术人员,还是开始接触面向对象软件开发的人员,都有很好的参考价值。作为软件工程的一种潮流发展技术,本书也可作为大学教师、研究生和高年级学生的参考书。
目录回到顶部↑
1 introduction to uml
1.l models and modelling
1.2 methodologies
1.3 the unified modeling language
1.4 design models and code
1.5 the software development process
1.6 summary
1.7 exercises
2 modelling with objects
2.1 the object model
2.2 objects
2.3 object properties
2.4 avoiding data replication
2.5 links
2.6 message passing
2.7 polymorphism
2.8 dynamic binding
2.9 class diagrams
2.1o the applicability of the object model
2.11 summary
1.l models and modelling
1.2 methodologies
1.3 the unified modeling language
1.4 design models and code
1.5 the software development process
1.6 summary
1.7 exercises
2 modelling with objects
2.1 the object model
2.2 objects
2.3 object properties
2.4 avoiding data replication
2.5 links
2.6 message passing
2.7 polymorphism
2.8 dynamic binding
2.9 class diagrams
2.1o the applicability of the object model
2.11 summary
前言回到顶部↑
Mr Palomar's rule had gradually altered: now he needed a gleat variety of models, perhaps interchangeable, in a combining process, in order to find the one that would best fit a reality that. for its own part, was always made of many different realities, in time and in space.
-----Italo Calvino
This book is a revised edition of my earlier book Practical Object-Oriented Design. It shares the same aims as the earlier book, namely to provide a practical introduction to design which will be of use to people with experience of programming who want to learn how to express the design of object-oriented programs more abstractly.
The most significant change from the earlier book is that the notation used is now that of UML, the Unified Modeling Language. UML is to a large extent an evolutionary development of the OMT language used in the earlier book. so this. change has not necessitated great changes in the structure and content of the book.
As with the earlier book, much emphasis is placed on clearly explaining the constructs and notation of the design language, and demonstrating the close relationship between the design and the implementation of object-oriented programs. Unlike questions of methodology and process, these issues are treated rather superficially in many books. If they are not clearly understood, however, it is difiicult to make meaningful use of a notation such as UML.
In addition, the book addresses a number of pragmatic issues which are often omitted from design books, such as the integration of a design with an existing framework, the use of patterns in design, dealing with persistent data, and the physical design of object-oriented programs.
UML is a much larger and more complex language than OMT, and when learningit there is a danger of being overwhelmed by details of the notation. In order to avoidthis, the book uses a subset of UML that is sufficient to express all the significantfeatures of medium-sized object-oriented programs. The most significant omissions areany coverage of concunency, activity diagrams, and anything other than a brief mentionof component and deployment diagrams. These aspects of the language are obviouslyimponant for 'industrial-strength' applications of UML, but these lie somewhat outsidethe experience of the intended audience of this book.
The Java language is used for programming examples. In order to ensure maximumponability, the use of the language has been kept as straightforward as possible and theJava 1.0 event model is used in preference to later, more complex, models. For thebenefit of readers who prefer to use C++, the book's web site will provide altemativeversions of those sections of the book which are specific to the Java language.
STRUCTURE OF THE BOOK
'Following an introductory chapter, Chapter 2 introduces the basic concepts of objectmodelling in the context of a simple programming example. Chapters 3 to 5 contain amore extended example of the ose of UML in designing a diagram editor application,while chapters 6 to 8 present the most imponant UML notations systematically.
Chapters 2 to 5 introduce many features of UML in the context of extendedexamples before a more systematic presentation of the language is given in chapters6 to 8. However, the diagram editor case study in chapters 3 to 5 is not referred to inthe text of chapters 6 to 8, so readers who prefer to cover the language systematicallybefore looking at its use can move directly from chapter 2 to chapter 6, returning laterto chapters 3 to 5.
Chapters 9 to 13 are more or less independent of each other and can be read inany order. Chapter 9 covers the use of constraints with UML, and the OCL language.Chapter IO presents systematic techniques for the implementation of designs, buildingon some basic material presented in Chapter 5. Chapter 11 covers some miscellaneousissues including the relationship between logical and physical design, and the impactof non-functional requirements on a design, and Chapter 12 discusses some imponantprinciples of object-oriented design, and the popular area of design pattems. A casestudy is presented in Chapter 13, and it is planned that further case studies will beavailable from the book's web site.
FURTHER RESOURCES
A web page for this book has been set up, providing access to the source code for thecase studies used in the book. solutions to selected exercises, additional case studies andother related material. It can be found at the following URL:
http: //www.mcgraw-hill . co . uk/textbooks/priestley '
A instructor's manual, including suggested solutions to all exercises, is availableto bona fide academics. Information on how to obtain the manual can be found on the publisher's web site.
ACKNOWLEDGEMENTS
In the preparation of this book, my most significant debt is to the readers of the earlierbook who have taken the trouble to communicate to me their opinions. I have much appreciated this steady trickle of, on the whole, positive feedback. It is in the nature of publishing that the only concrete way I have of expressing my gratitude is to hope that you will all immediately buy this new book, and find it just as useful.
The enthusiasm of Elizabeth Robinson for this new edition was instrumental inmotivating me to complete the book, and I would. also like to thank the anonymousreviewers of the manuscript for their helpful comments. Thanks also to Alison, forproviding some breaks that neither of us really needed, and a big thank you to Rosemary,Felix and Alasdair.
-----Italo Calvino
This book is a revised edition of my earlier book Practical Object-Oriented Design. It shares the same aims as the earlier book, namely to provide a practical introduction to design which will be of use to people with experience of programming who want to learn how to express the design of object-oriented programs more abstractly.
The most significant change from the earlier book is that the notation used is now that of UML, the Unified Modeling Language. UML is to a large extent an evolutionary development of the OMT language used in the earlier book. so this. change has not necessitated great changes in the structure and content of the book.
As with the earlier book, much emphasis is placed on clearly explaining the constructs and notation of the design language, and demonstrating the close relationship between the design and the implementation of object-oriented programs. Unlike questions of methodology and process, these issues are treated rather superficially in many books. If they are not clearly understood, however, it is difiicult to make meaningful use of a notation such as UML.
In addition, the book addresses a number of pragmatic issues which are often omitted from design books, such as the integration of a design with an existing framework, the use of patterns in design, dealing with persistent data, and the physical design of object-oriented programs.
UML is a much larger and more complex language than OMT, and when learningit there is a danger of being overwhelmed by details of the notation. In order to avoidthis, the book uses a subset of UML that is sufficient to express all the significantfeatures of medium-sized object-oriented programs. The most significant omissions areany coverage of concunency, activity diagrams, and anything other than a brief mentionof component and deployment diagrams. These aspects of the language are obviouslyimponant for 'industrial-strength' applications of UML, but these lie somewhat outsidethe experience of the intended audience of this book.
The Java language is used for programming examples. In order to ensure maximumponability, the use of the language has been kept as straightforward as possible and theJava 1.0 event model is used in preference to later, more complex, models. For thebenefit of readers who prefer to use C++, the book's web site will provide altemativeversions of those sections of the book which are specific to the Java language.
STRUCTURE OF THE BOOK
'Following an introductory chapter, Chapter 2 introduces the basic concepts of objectmodelling in the context of a simple programming example. Chapters 3 to 5 contain amore extended example of the ose of UML in designing a diagram editor application,while chapters 6 to 8 present the most imponant UML notations systematically.
Chapters 2 to 5 introduce many features of UML in the context of extendedexamples before a more systematic presentation of the language is given in chapters6 to 8. However, the diagram editor case study in chapters 3 to 5 is not referred to inthe text of chapters 6 to 8, so readers who prefer to cover the language systematicallybefore looking at its use can move directly from chapter 2 to chapter 6, returning laterto chapters 3 to 5.
Chapters 9 to 13 are more or less independent of each other and can be read inany order. Chapter 9 covers the use of constraints with UML, and the OCL language.Chapter IO presents systematic techniques for the implementation of designs, buildingon some basic material presented in Chapter 5. Chapter 11 covers some miscellaneousissues including the relationship between logical and physical design, and the impactof non-functional requirements on a design, and Chapter 12 discusses some imponantprinciples of object-oriented design, and the popular area of design pattems. A casestudy is presented in Chapter 13, and it is planned that further case studies will beavailable from the book's web site.
FURTHER RESOURCES
A web page for this book has been set up, providing access to the source code for thecase studies used in the book. solutions to selected exercises, additional case studies andother related material. It can be found at the following URL:
http: //www.mcgraw-hill . co . uk/textbooks/priestley '
A instructor's manual, including suggested solutions to all exercises, is availableto bona fide academics. Information on how to obtain the manual can be found on the publisher's web site.
ACKNOWLEDGEMENTS
In the preparation of this book, my most significant debt is to the readers of the earlierbook who have taken the trouble to communicate to me their opinions. I have much appreciated this steady trickle of, on the whole, positive feedback. It is in the nature of publishing that the only concrete way I have of expressing my gratitude is to hope that you will all immediately buy this new book, and find it just as useful.
The enthusiasm of Elizabeth Robinson for this new edition was instrumental inmotivating me to complete the book, and I would. also like to thank the anonymousreviewers of the manuscript for their helpful comments. Thanks also to Alison, forproviding some breaks that neither of us really needed, and a big thank you to Rosemary,Felix and Alasdair.








点击看大图




加载中...

