Developing Applications with Visual Basic and UML
Paul R. Reed Jr.
- 出版商: Addison Wesley
- 出版日期: 1999-11-14
- 售價: $1,670
- 貴賓價: 9.5 折 $1,587
- 語言: 英文
- 頁數: 592
- 裝訂: Paperback
- ISBN: 0201615797
- ISBN-13: 9780201615791
-
相關分類:
UML、Visual Basic
已絕版
買這商品的人也買了...
-
$1,200$1,176 -
$480$408 -
$680$537 -
$650$553 -
$920$727 -
$490$417 -
$860$731 -
$2,350$2,233 -
$1,860$1,767 -
$399CCNA Self-Study: CCNA Basics (CCNAB) (Hardcover)
-
$1,900$1,805 -
$690$587 -
$420$328 -
$620$558 -
$600$474 -
$550$435 -
$580$458 -
$350$333 -
$580$458 -
$690$538 -
$820$697 -
$750$675 -
$560$504 -
$550$468 -
$390$304
相關主題
商品描述
Table Of Contents
1. The Project Dilemma. Goals.
The Project Dilemma.
The Synergy Process Model.
The Unified Modeling Language.
Checkpoint.
The Project Dilemma.
The Synergy Process Model.
The Unified Modeling Language.
Checkpoint.
2. Visual Basic, Object-Oriented, and the UML.
Goals.
Visual Basic as an Industrial Strength Development Tool.
Visual Basic and the Concept of Object-Oriented.
Why the UML and Visual Basic?
Checkpoint.
Visual Basic as an Industrial Strength Development Tool.
Visual Basic and the Concept of Object-Oriented.
Why the UML and Visual Basic?
Checkpoint.
3. Getting the Project Started.
Goals.
Establishing the Project Charter.
Checkpoint.
Establishing the Project Charter.
Checkpoint.
4. Use Cases.
Goals.
The Sample Project.
The Process Model.
Finding the Pathways through the Use Case.
Shadow Use Cases.
Detailing the Happy Path.
Completed Process Orders Use Case.
Preparing the Preliminary Architecture.
Project Charter: Increments and Estimates.
Checkpoint.
The Sample Project.
The Process Model.
Finding the Pathways through the Use Case.
Shadow Use Cases.
Detailing the Happy Path.
Completed Process Orders Use Case.
Preparing the Preliminary Architecture.
Project Charter: Increments and Estimates.
Checkpoint.
5. Classes.
Goals.
Elaboration Phase.
Detailing Pathways.
Identifying and Categorizing Business Rules.
Uncovering Classes.
Relationships.
Creating the Class Diagram.
Identifying Attributes and Operations.
Object Diagram.
Finishing Up: The Analysis Model.
Checkpoint.
Elaboration Phase.
Detailing Pathways.
Identifying and Categorizing Business Rules.
Uncovering Classes.
Relationships.
Creating the Class Diagram.
Identifying Attributes and Operations.
Object Diagram.
Finishing Up: The Analysis Model.
Checkpoint.
6 Building an Early Prototype.
Goals.
Building an Early Prototype.
Requirements Gathering.
Iteration One.
Checkpoint.
Building an Early Prototype.
Requirements Gathering.
Iteration One.
Checkpoint.
7. The Dynamic Elements of the Application.
Goals.
Next Step of the Elaboration Phase.
Dynamic Modeling.
The Sequence Diagram.
The Collaboration Diagram.
The State Diagram.
The Activity Diagram.
Selecting the Right Diagram.
Non-UML Extensions in the Design: Usage Matrices.
Checkpoint.
Next Step of the Elaboration Phase.
Dynamic Modeling.
The Sequence Diagram.
The Collaboration Diagram.
The State Diagram.
The Activity Diagram.
Selecting the Right Diagram.
Non-UML Extensions in the Design: Usage Matrices.
Checkpoint.
8. The Technology Landscape.
Goals.
Next Phase of the Elaboration Phase.
Separating Services.
Logical versus Physical Tiering.
Microsoft's Tiering Strategy.
Managing Transaction Scope within the Application and Microsoft Transaction Server.
Incorporating the Internet into the Solution.
Remulak Productions Execution Architecture.
Checkpoint.
Next Phase of the Elaboration Phase.
Separating Services.
Logical versus Physical Tiering.
Microsoft's Tiering Strategy.
Managing Transaction Scope within the Application and Microsoft Transaction Server.
Incorporating the Internet into the Solution.
Remulak Productions Execution Architecture.
Checkpoint.
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 Definition Language.
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.
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 Definition Language.
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.
10. Applying the Infrastructure.
Goals.
Construction Phase.
Checkpoint.
Construction Phase.
Checkpoint.
11. Generating Code from the UML Class Diagram (Part 1).
Goals.
Construction Phase.
Adding Code to Realize a Use Case Pathway.
Data Access Service Layer: DASVC Component.
Data Translation Service Layer: DTSVC Component.
Business Rule Service Layer: BRSVC Component.
Presentation Service Layer: UISVC Component.
Building Blocks for the Future.
Checkpoint.
Construction Phase.
Adding Code to Realize a Use Case Pathway.
Data Access Service Layer: DASVC Component.
Data Translation Service Layer: DTSVC Component.
Business Rule Service Layer: BRSVC Component.
Presentation Service Layer: UISVC Component.
Building Blocks for the Future.
Checkpoint.
12. Generating Code from the UML Class Diagram (Part 2).
Goals.
Construction Phase.
Checkpoint.
Construction Phase.
Checkpoint.
13. Creating a Distributed Implementation: DCOM and MTS.
Goals.
Construction Phase.
Remote Solutions-Distributed Component Object Model.
Remote Solutions-Microsoft Transaction Server.
Checkpoint.
Construction Phase.
Remote Solutions-Distributed Component Object Model.
Remote Solutions-Microsoft Transaction Server.
Checkpoint.
14 Alternative Interfaces: The Internet.
Goals.
Construction Phase.
Checkpoint.
Construction Phase.
Checkpoint.
Appendix A Estimating Project Using Use Cases.
Actors.
Use Cases.
Technical Factors.
Project Participants.
Use Case Points.
The Project Estimate.
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.
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.
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.
COM +.
COM-Infrastructure.
COM at Work.
Visual Basic-Version Compatibility.
COM +.
Appendix E Object-Oriented Project Plan.
Appendix F Sample Project Output.
Use Cases-Use Case Details for Increment I.
Use Cases-Happy Path Task Steps.
Database Support.
Use Cases-Happy Path Task Steps.
Database Support.
Bibliography.
Suggested Readings.
Index. 0201615797T04062001