书籍详情
UML与Visual Basic应用程序开发（影印版）
作者：（美）里德（Reed,R.R.） 编
出版社：科学出版社
出版时间：2003-05-01
ISBN：9787030114051
定价：¥60.00
购买这本书可以去
内容简介
本书以作者在面向对象的客户／服务器系统开发方面的丰富经验为基础，介绍了如何在Visual Basic中用 UML进行企业级应用程序的建模和开发。对UML基础知识和Visual Basic中易被误用的面向对象属性进行了详细的叙述，并借助一个大型案例，让读者亲历项目开发周期的各个阶段：需求分析、建模、设计原型、创建体系结构到编码，让读者了解UML的设计优势，告诉读者如何把UML规范转换成Visual Basic代码，如何结合DNA，DCOM和MTC技术及ASP等工具开发面向对象的Visual Basic应用和网络应用。本书内容实用，适合VB及UML程序开发人员使用。
作者简介
暂缺《UML与Visual Basic应用程序开发（影印版）》作者简介
目录
Foreword
Foreword
Preface
Acknowledgments
CHAPTER 1 The Project Dilemma
Goals
The Project Dilemma
Iterative and Incremental Software Development
Risk-Based Development
The Iterative Software Process Model
Combining Iterative with Incremental:Multidimensional View
The Synergy Process Model
Selling the Idea of a Software Process to the Business
The Unified Modeling Language
The UML and Its Place in the Software Process
The Essence of Modeling
The UML Diagrams
The Unified Modeling Language and the “4+1”View of Architecture
Using the UML Diagrams in Context
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 2 Visual Basic,Object-Oriented,and the UML
Goals
Visual Basic as an Industrial Strength Development Tool
Visual Basic and the Concept to Object-Oriented
Visual Basic and Classes
Visual Basic and Complex Types
Visual Basic and Message-Passing
Visual Basic and Encapsulation
Visual Basic and Inheritance
Visual Basic and Interface Inheritance
Visual Basic's Alternative to Implementation Inheritance
Visual Basic and Polymorphism
Why the UML and Visual Basic?
Class Diagram
Sequence Diagram
Component Diagram
Deployment Diagram
Visual Modeling Tool Support
Checkpoint
Where We Have Been
Where We Are Going
CHAPTER 3 Getting the Project Started
Goals
Establishing the Project Charter
The Process Model
Working Template of the Project Charter
The Actors
Event List and Event Table
Project Charter:Iteration One
Iteration One Complete
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 4 Use Cases
Goals
The Sample Project
The Process Model
Use Cases
Finding the Pathways through the Use Case
Finding the Happy Path
Finding the Alternate Pathways
Finding the Exception Pathways
Shadow Use Cases
Detailing the Happy Path
Completed Process Orders Use Case
Preparing the Preliminary Architecture
Project Charter:Increments and Estimates
Increments
Estimates
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 5 Classes
Goals
Elaboration Phase
Detailing Pathways
Identifying and Categorizing Business Rules
Uncovering Classes
Iteration 1:Role of the UML Class Diagram
What makes a Good Class?
Applying filter Rules
Types of Classes
Entity Classes
Interface Classes
Control Classes
Relationships
Establishing Associations
Establishing Roles
Establishing Multiplicity
Advanced Associations
Aggregation and Composition Associations
Link Associations
Reflexive Associations
Qualification Associations
Generalization
Creating the Class Diagram
Identifying Attributes and Operations
Attributes
Operations
Object Diagram
Finishing Up:The Analysis Model
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 6 Building an Early Prototype
Goals
Building an Early Prototype
The Prototype
Requirements Gathering
User Interface Prototype
Actor and Use Case Boundaries
User Interface Artifacts
Use Case Coupling
Iteration One
Screen Structure Charts
Creating the Prototype
Collecting User Feedback by Using
Screen Dialogs
Learning from the Prototype
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 7 The Dynamic Elements of the Application
Goals
Next Step of the Elaboration Phase
Dynamic Modeling
Types of Dynamic Models
The Sequence Diagram
Sequence Diagram of the Happy Path
Sequence Diagram for an Alternate Pathway
Transferring Knowledge to the Class Diagram
Walking the Sequence Diagram
The Collaboration Diagram
The State Diagram
Modeling the State Diagram of the Remulak Productions Order Class
Alternative Way to View State Diagrams
The Activity Diagram
Selecting the Right Diagram
Non-UML Extensions in the Design:Usage Matrices
Event/Frequency Matrix
Object/Location Matrix
Object/Volume Matrix
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 8 The Technology Landscape
Goals
Next Phase of the Elaboration Phase
Separating Services
Logical versus Physical Tiering
Microsoft's Tiering Strategy
Communication among the Six Layers
Inter-Process Communication Architecture
Layer communication Architecture
Inside COM Communication
Five Options on Which to Base an Infrastructure Architecture
Managing Transaction Scope within the Application and Micrisoft Transaction Server
Incorporation the Internet into the solution
Remulak Productions Execution Architecture
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 9 Data Persistence:Storing the Objects
Goals
Construction Phase
Object-Oriented and Translating to the Physical Design
Mapping Classes to Tables
Mapping simple Associations
Mapping Inheritance to the Relational Database
Mapping Aggregation and Composition to the Relational Database
Mapping Reflexive Associations to the Relational Database
Key Structures and Normalization
Using a Visual Modeling Tool to Generate the Data Definitioin Language
Enhancing the Visual Modeling Tool
Stored Procedures and Triggers and the Object-Oriented Project
Visual Basic Support of Data-Aware Classes
The Data Translation Services and Data Access SErvices Layers
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 10 Applying the Infrastructure
Goals
Construction Phase
Synergy Process
Component-Infrastructure Issues and Communicating with All the Layers
Component-Exploring the Presentation Services Layer
Component-Exploring the Business Context Services Layer
Component-Exploring the Business Rule Services Layer
Component-Cooperating Classes:Interface,Control,and Entity
Component-Layer communication
Component-Implementation of the Infrastructure
Component-Revisiting the UML Class diagram to Refine Operation Signatures
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 11 Generating Code from the UML Class Diagram(Part 1)
Goals
Construction Phase
Synergy Process
Visual Modeling-The Mission of the Visual Modeling Tool as It Pertains to the Project
Visual Modeling-The Mission of the Visual Modeling Tool as It Pertains to the Program code Generation
Review the Setup Issues in Preparing to Generate Program Code
Modifying the Code Generation Parameters
Assigning Classes to Components
Generating Our First code from the Visual Modeling Tool
Generating Our First Code from the Visual Modeling Tool
Generating the Remaining Code from the Visual Modeling Tool-Data Translation Services
Generation the Remaining Code from the Visual Modeling Tool-Business Rule Services
Generating the Remaining Code from the Visual Modeling Tool-Presentation SErvices
Review Items to Watch Out for after Generation Is Complete
Explore How to Reengineer Program Code Back into the Visual Modeling Diagram
Adding Code to Realize a Use Case Pathway
Explore the Necessary Code That Must Be Added to Support a Simple Transaction from Start to Finish
Data Access Service Layer:DASVC Component
Connecting to the Data Source and Executing a Select query
Closing the Connection to the Data Source
Connecting to the Data Source and Executing an Insert,Update,or Delete Query
Data Translation Service Layer:DTSVC Component
Building the SQL to Be Executed by the Data Access Services Layer
Business Rule Service Layer:BRSVC Component
Building the Rules That Govern Processing
Presentation Service Layer:UISVC Component
What the User Sees:Attaching the User Interface to the Business Rule Services Layer
Building Blocks for the Future
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 12 Gemerating Code from the UML Class Diagram(Part 2)
Goals
Construction Phase
Enhancing the customer Inquiry and Introducing the Notion of Shallow and Expanded Objects
Code Changes to the Customer Relationship Inquiry
Code Changes to Support Expanding Objects
Making Life Easier for the User Interface:User-Defined Types
Client-side Objects or No Client-Side Objects
A Disturbing Trend with the Advent of Distributed Implementations
Updating Information from the User Interface to the Back-End
Persisting the Objects
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 13 Creating a Distributed Implementation:DCOM and MTS
Goals
Construction Phase
Synergy Process
Construction-Distributed Applications:Nirvana or Overkill?
Construction-The Remulak Productions Partitioning Strategy-Payback Time
Remote Solutions-Distributed Component Object Model
Construction-Preparing the Components for DCOM Distribution
Construction-Distributing the Server Components
Construction-Installing the Components on the Server
Construction-Getting the Client Ready to Test the CDOM Installation
Construction-Creating a Client Install Package
Remote Solutions-Microsoft Transaction Server
Construction-Getting to the Interface
Construction-Types of Transactions
Construction-Remulak Productions Transaction Types
Construction-MTS Administration
Construction-Modifying Remulak to use MTS Transaction Management
Construction-Supporting the Right to Vote
Construction-Remulak Changes:Give and Take
MTS-Round 1 Changes
MTS-Round 2 Changes
MTS-Round 3 Changes
Construction-Transaction Management
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 14 Alternative Interfaces:The Internet
Goals
Construction Phase
Synergy Process
The Role of the Web
Web Technologies
Component Reconfiguration
Crafting the Web Components
Order Inquiry HTML Form
Active Server Pages
A More Dynamic Client with JavaScript
Other Possibilities
Checkpoint
Where We Have Been
APPENDIX A Estimating Projects Using Use Cases
Actors
Use Cases
Technical Factors
Project Participants
Use Case Points
The Project Estimate
APPENDIX B Adding Additional Functionality to Rational Rose Data Definition Language Capability
Enhancements-Persistent and Transient Attributes
Modifying Rational Rose-Persistent Attribute Setup
Modifying Rational Rose-Running the Definition Script
Modifying Rational Rose-Changing the Script to Recognize the attribute
Other Areas of Change
APPENDIX C An Object-Oriented Primer
What Does Object-Oriented Mean?
Object-Oriented-Right in Your Own Backyard
By-Products of Object-Oriented
Inheritance
Encapsulation
Polymorphism
No Silver Bullet
APPENDIX D Component Object Model and COM+
COM-The Plumbing
COM-Infrastructure
COM at Work
Visual Basic-Version Compatibility
No Compatibility
Project Compatibility
Binary Compatibility
COM+
APPENDIX E Object-Oriented Project Plan
The Plan
APPENDIX F Sample Project Output
Use Cases-Use Case Details for Increment I
Use Cases-Happy Path Task Steps
Database Support
Bibliography
Suggested Readings
Index
Foreword
Preface
Acknowledgments
CHAPTER 1 The Project Dilemma
Goals
The Project Dilemma
Iterative and Incremental Software Development
Risk-Based Development
The Iterative Software Process Model
Combining Iterative with Incremental:Multidimensional View
The Synergy Process Model
Selling the Idea of a Software Process to the Business
The Unified Modeling Language
The UML and Its Place in the Software Process
The Essence of Modeling
The UML Diagrams
The Unified Modeling Language and the “4+1”View of Architecture
Using the UML Diagrams in Context
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 2 Visual Basic,Object-Oriented,and the UML
Goals
Visual Basic as an Industrial Strength Development Tool
Visual Basic and the Concept to Object-Oriented
Visual Basic and Classes
Visual Basic and Complex Types
Visual Basic and Message-Passing
Visual Basic and Encapsulation
Visual Basic and Inheritance
Visual Basic and Interface Inheritance
Visual Basic's Alternative to Implementation Inheritance
Visual Basic and Polymorphism
Why the UML and Visual Basic?
Class Diagram
Sequence Diagram
Component Diagram
Deployment Diagram
Visual Modeling Tool Support
Checkpoint
Where We Have Been
Where We Are Going
CHAPTER 3 Getting the Project Started
Goals
Establishing the Project Charter
The Process Model
Working Template of the Project Charter
The Actors
Event List and Event Table
Project Charter:Iteration One
Iteration One Complete
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 4 Use Cases
Goals
The Sample Project
The Process Model
Use Cases
Finding the Pathways through the Use Case
Finding the Happy Path
Finding the Alternate Pathways
Finding the Exception Pathways
Shadow Use Cases
Detailing the Happy Path
Completed Process Orders Use Case
Preparing the Preliminary Architecture
Project Charter:Increments and Estimates
Increments
Estimates
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 5 Classes
Goals
Elaboration Phase
Detailing Pathways
Identifying and Categorizing Business Rules
Uncovering Classes
Iteration 1:Role of the UML Class Diagram
What makes a Good Class?
Applying filter Rules
Types of Classes
Entity Classes
Interface Classes
Control Classes
Relationships
Establishing Associations
Establishing Roles
Establishing Multiplicity
Advanced Associations
Aggregation and Composition Associations
Link Associations
Reflexive Associations
Qualification Associations
Generalization
Creating the Class Diagram
Identifying Attributes and Operations
Attributes
Operations
Object Diagram
Finishing Up:The Analysis Model
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 6 Building an Early Prototype
Goals
Building an Early Prototype
The Prototype
Requirements Gathering
User Interface Prototype
Actor and Use Case Boundaries
User Interface Artifacts
Use Case Coupling
Iteration One
Screen Structure Charts
Creating the Prototype
Collecting User Feedback by Using
Screen Dialogs
Learning from the Prototype
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 7 The Dynamic Elements of the Application
Goals
Next Step of the Elaboration Phase
Dynamic Modeling
Types of Dynamic Models
The Sequence Diagram
Sequence Diagram of the Happy Path
Sequence Diagram for an Alternate Pathway
Transferring Knowledge to the Class Diagram
Walking the Sequence Diagram
The Collaboration Diagram
The State Diagram
Modeling the State Diagram of the Remulak Productions Order Class
Alternative Way to View State Diagrams
The Activity Diagram
Selecting the Right Diagram
Non-UML Extensions in the Design:Usage Matrices
Event/Frequency Matrix
Object/Location Matrix
Object/Volume Matrix
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 8 The Technology Landscape
Goals
Next Phase of the Elaboration Phase
Separating Services
Logical versus Physical Tiering
Microsoft's Tiering Strategy
Communication among the Six Layers
Inter-Process Communication Architecture
Layer communication Architecture
Inside COM Communication
Five Options on Which to Base an Infrastructure Architecture
Managing Transaction Scope within the Application and Micrisoft Transaction Server
Incorporation the Internet into the solution
Remulak Productions Execution Architecture
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 9 Data Persistence:Storing the Objects
Goals
Construction Phase
Object-Oriented and Translating to the Physical Design
Mapping Classes to Tables
Mapping simple Associations
Mapping Inheritance to the Relational Database
Mapping Aggregation and Composition to the Relational Database
Mapping Reflexive Associations to the Relational Database
Key Structures and Normalization
Using a Visual Modeling Tool to Generate the Data Definitioin Language
Enhancing the Visual Modeling Tool
Stored Procedures and Triggers and the Object-Oriented Project
Visual Basic Support of Data-Aware Classes
The Data Translation Services and Data Access SErvices Layers
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 10 Applying the Infrastructure
Goals
Construction Phase
Synergy Process
Component-Infrastructure Issues and Communicating with All the Layers
Component-Exploring the Presentation Services Layer
Component-Exploring the Business Context Services Layer
Component-Exploring the Business Rule Services Layer
Component-Cooperating Classes:Interface,Control,and Entity
Component-Layer communication
Component-Implementation of the Infrastructure
Component-Revisiting the UML Class diagram to Refine Operation Signatures
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 11 Generating Code from the UML Class Diagram(Part 1)
Goals
Construction Phase
Synergy Process
Visual Modeling-The Mission of the Visual Modeling Tool as It Pertains to the Project
Visual Modeling-The Mission of the Visual Modeling Tool as It Pertains to the Program code Generation
Review the Setup Issues in Preparing to Generate Program Code
Modifying the Code Generation Parameters
Assigning Classes to Components
Generating Our First code from the Visual Modeling Tool
Generating Our First Code from the Visual Modeling Tool
Generating the Remaining Code from the Visual Modeling Tool-Data Translation Services
Generation the Remaining Code from the Visual Modeling Tool-Business Rule Services
Generating the Remaining Code from the Visual Modeling Tool-Presentation SErvices
Review Items to Watch Out for after Generation Is Complete
Explore How to Reengineer Program Code Back into the Visual Modeling Diagram
Adding Code to Realize a Use Case Pathway
Explore the Necessary Code That Must Be Added to Support a Simple Transaction from Start to Finish
Data Access Service Layer:DASVC Component
Connecting to the Data Source and Executing a Select query
Closing the Connection to the Data Source
Connecting to the Data Source and Executing an Insert,Update,or Delete Query
Data Translation Service Layer:DTSVC Component
Building the SQL to Be Executed by the Data Access Services Layer
Business Rule Service Layer:BRSVC Component
Building the Rules That Govern Processing
Presentation Service Layer:UISVC Component
What the User Sees:Attaching the User Interface to the Business Rule Services Layer
Building Blocks for the Future
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 12 Gemerating Code from the UML Class Diagram(Part 2)
Goals
Construction Phase
Enhancing the customer Inquiry and Introducing the Notion of Shallow and Expanded Objects
Code Changes to the Customer Relationship Inquiry
Code Changes to Support Expanding Objects
Making Life Easier for the User Interface:User-Defined Types
Client-side Objects or No Client-Side Objects
A Disturbing Trend with the Advent of Distributed Implementations
Updating Information from the User Interface to the Back-End
Persisting the Objects
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 13 Creating a Distributed Implementation:DCOM and MTS
Goals
Construction Phase
Synergy Process
Construction-Distributed Applications:Nirvana or Overkill?
Construction-The Remulak Productions Partitioning Strategy-Payback Time
Remote Solutions-Distributed Component Object Model
Construction-Preparing the Components for DCOM Distribution
Construction-Distributing the Server Components
Construction-Installing the Components on the Server
Construction-Getting the Client Ready to Test the CDOM Installation
Construction-Creating a Client Install Package
Remote Solutions-Microsoft Transaction Server
Construction-Getting to the Interface
Construction-Types of Transactions
Construction-Remulak Productions Transaction Types
Construction-MTS Administration
Construction-Modifying Remulak to use MTS Transaction Management
Construction-Supporting the Right to Vote
Construction-Remulak Changes:Give and Take
MTS-Round 1 Changes
MTS-Round 2 Changes
MTS-Round 3 Changes
Construction-Transaction Management
Checkpoint
Where We Have Been
Where We Are Going Next
CHAPTER 14 Alternative Interfaces:The Internet
Goals
Construction Phase
Synergy Process
The Role of the Web
Web Technologies
Component Reconfiguration
Crafting the Web Components
Order Inquiry HTML Form
Active Server Pages
A More Dynamic Client with JavaScript
Other Possibilities
Checkpoint
Where We Have Been
APPENDIX A Estimating Projects Using Use Cases
Actors
Use Cases
Technical Factors
Project Participants
Use Case Points
The Project Estimate
APPENDIX B Adding Additional Functionality to Rational Rose Data Definition Language Capability
Enhancements-Persistent and Transient Attributes
Modifying Rational Rose-Persistent Attribute Setup
Modifying Rational Rose-Running the Definition Script
Modifying Rational Rose-Changing the Script to Recognize the attribute
Other Areas of Change
APPENDIX C An Object-Oriented Primer
What Does Object-Oriented Mean?
Object-Oriented-Right in Your Own Backyard
By-Products of Object-Oriented
Inheritance
Encapsulation
Polymorphism
No Silver Bullet
APPENDIX D Component Object Model and COM+
COM-The Plumbing
COM-Infrastructure
COM at Work
Visual Basic-Version Compatibility
No Compatibility
Project Compatibility
Binary Compatibility
COM+
APPENDIX E Object-Oriented Project Plan
The Plan
APPENDIX F Sample Project Output
Use Cases-Use Case Details for Increment I
Use Cases-Happy Path Task Steps
Database Support
Bibliography
Suggested Readings
Index
猜您喜欢
