Sold Out
Book Categories |
Foreword | xi | |
Preface | xiii | |
Chapter 1 | Component Systems | 1 |
1.1 | Component Goals | 1 |
1.2 | Component Principles | 2 |
1.3 | Component Forms | 4 |
1.3.1 | Example: Microsoft Word | 6 |
1.3.2 | What a Component Isn't | 7 |
1.4 | Component and System Architectures | 9 |
1.4.1 | System Architectures | 10 |
1.4.2 | Component Architectures | 13 |
1.5 | Specifying Contracts | 16 |
1.5.1 | Usage Contracts | 18 |
1.5.2 | Realization Contracts | 20 |
1.5.3 | Interfaces versus Component Specifications | 21 |
1.6 | Model Levels | 22 |
1.7 | Summary | 23 |
Chapter 2 | The Development Process | 25 |
2.1 | Workflows | 26 |
2.2 | The Impact of the Management Process | 28 |
2.2.1 | The Evolution of Software Processes | 28 |
2.2.2 | Accommodating Change | 29 |
2.3 | Workflow Artifacts | 31 |
2.4 | The Specification Workflow | 33 |
2.4.1 | Component Identification | 33 |
2.4.2 | Component Interaction | 35 |
2.4.3 | Component Specification | 35 |
2.5 | Summary | 36 |
Chapter 3 | Applying UML | 37 |
3.1 | Why Do We Need This Chapter at All? | 37 |
3.1.1 | Tools | 38 |
3.2 | Extending UML with Stereotypes | 39 |
3.3 | Precision, Accuracy, and Completeness | 39 |
3.4 | UML Modeling Techniques | 40 |
3.5 | Business Concept Model | 43 |
3.6 | Use Case Model | 44 |
3.6.1 | Use Case Diagrams | 45 |
3.6.2 | Use Case Descriptions | 45 |
3.6.3 | Use Case Instances | 47 |
3.6.4 | Inclusions, Extensions, and Variations | 47 |
3.7 | Business Type Model | 48 |
3.7.1 | Types | 49 |
3.7.2 | Structured Data Types | 51 |
3.7.3 | Interface Type | 52 |
3.7.4 | Invariants | 54 |
3.8 | Interface Specification | 55 |
3.8.1 | Interface Specification Package | 55 |
3.8.2 | Information Model | 57 |
3.8.3 | Operation Specification | 57 |
3.9 | Component Specification | 59 |
3.9.1 | Component Object Interaction | 61 |
3.9.2 | Specification, Not Implementation | 62 |
3.10 | Component Architectures | 63 |
3.11 | Summary | 64 |
Chapter 4 | Requirements Definition | 67 |
4.1 | Business Processes | 68 |
4.2 | Business Concept Model | 69 |
4.3 | System Envisioning | 71 |
4.4 | Use Cases | 71 |
4.4.1 | Actors and Roles | 72 |
4.4.2 | Use Case Identification | 73 |
4.4.3 | Use Case Descriptions | 77 |
4.4.4 | Quality of Service | 80 |
4.5 | Summary | 81 |
Chapter 5 | Component Identification | 83 |
5.1 | Identifying Interfaces | 84 |
5.2 | Identifying System Interfaces and Operations | 86 |
5.2.1 | Make a Reservation | 86 |
5.2.2 | Take Up Reservation | 87 |
5.3 | Identifying Business Interfaces | 88 |
5.3.1 | Create the Business Type Model | 88 |
5.3.2 | Refine the Business Type Model | 89 |
5.3.3 | Define Business Rules | 90 |
5.3.4 | Identify Core Types | 92 |
5.3.5 | Create Business Interfaces and Assign Responsibilities | 92 |
5.3.6 | Allocating Responsibility for Associations | 94 |
5.4 | Creating Initial Interface Specifications | 96 |
5.5 | Existing Interfaces and Systems | 97 |
5.6 | Component Specification Architecture | 98 |
5.6.1 | System Component Specifications | 99 |
5.6.2 | Business Component Specifications | 99 |
5.6.3 | An Initial Architecture | 100 |
5.7 | Summary | 101 |
Chapter 6 | Component Interaction | 103 |
6.1 | Discovering Business Operations | 104 |
6.1.1 | Some Simple Interactions | 106 |
6.1.2 | Breaking Dependencies | 109 |
6.2 | Maintaining Referential Integrity | 112 |
6.2.1 | Component Object Architecture | 112 |
6.2.2 | Controlling Intercomponent References | 113 |
6.3 | Completing the Picture | 115 |
6.4 | Refining the Interfaces | 116 |
6.4.1 | Factoring Interfaces and Operations | 119 |
6.5 | Summary | 119 |
Chapter 7 | Component Specification | 121 |
7.1 | Specifying Interfaces | 121 |
7.1.1 | Operation Specification | 123 |
7.1.2 | Interface Information Models | 123 |
7.1.3 | Pre- and Postconditions | 125 |
7.2 | A Systematic Process | 128 |
7.2.1 | From Business Type Model to Interface Information Model | 129 |
7.2.2 | Invariants | 131 |
7.2.3 | Snapshots | 132 |
7.2.4 | Exactly What Does a Postcondition Guarantee? | 134 |
7.3 | Specifying System Interfaces | 135 |
7.3.1 | Business Rule Location | 136 |
7.4 | Specifying Components | 137 |
7.4.1 | Offered and Used Interfaces | 138 |
7.4.2 | Component Interaction Constraints | 139 |
7.4.3 | Inter-Interface Constraints | 141 |
7.5 | Factoring Interfaces | 142 |
7.6 | Summary | 144 |
Chapter 8 | Provisioning and Assembly | 147 |
8.1 | What Do We Mean by Target Technology? | 147 |
8.2 | Components Realize Component Specifications | 149 |
8.3 | Realization Mappings and Restrictions | 150 |
8.3.1 | Operation Parameters | 150 |
8.3.2 | Error and Exception Handling Mechanisms | 151 |
8.3.3 | Interface Inheritance and Interface Support | 154 |
8.3.4 | Operation Sequence | 155 |
8.3.5 | Interface Properties | 155 |
8.3.6 | Object Creation | 155 |
8.3.7 | Raising Events | 156 |
8.4 | Application Architecture Correspondence | 157 |
8.4.1 | Business Components | 158 |
8.5 | Subcomponents | 160 |
8.6 | Integrating Existing Systems | 162 |
8.7 | Purchasing Components | 163 |
8.8 | Assembly | 164 |
8.9 | Summary | 165 |
8.10 | A Final Thought | 166 |
References | 167 | |
Index | 169 |
Login|Complaints|Blog|Games|Digital Media|Souls|Obituary|Contact Us|FAQ
CAN'T FIND WHAT YOU'RE LOOKING FOR? CLICK HERE!!! X
You must be logged in to add to WishlistX
This item is in your Wish ListX
This item is in your CollectionUML Components: A Simple Process for Specifying Component-Based Software
X
This Item is in Your InventoryUML Components: A Simple Process for Specifying Component-Based Software
X
You must be logged in to review the productsX
X
X
Add UML Components: A Simple Process for Specifying Component-Based Software, Developers using component technologies such as COM+ and Enterprise JavaBeans need to be able to define and express specifications for their components. They can do so using the Unified Modeling Language (UML), whether or not the components are being impl, UML Components: A Simple Process for Specifying Component-Based Software to the inventory that you are selling on WonderClubX
X
Add UML Components: A Simple Process for Specifying Component-Based Software, Developers using component technologies such as COM+ and Enterprise JavaBeans need to be able to define and express specifications for their components. They can do so using the Unified Modeling Language (UML), whether or not the components are being impl, UML Components: A Simple Process for Specifying Component-Based Software to your collection on WonderClub |