Component-Based Development for Enterprise Systems: Applying the SELECT PerspectiveCambridge University Press, 13 ene 1998 - 462 páginas This ground-breaking book distills the experience of the authors in dealing with problems in industry that can be solved by using the SELECT Perspective. A pragmatic, component-based approach for the development of enterprise systems, the SELECT Perspective comprises a unique blend of techniques, architecture, and process. Enterprise software development presents challenges of sheer scale and complexity that continue to accelerate at a terrific pace. Businesses are becoming increasingly adaptive and are calling for software that is more and more flexible. Component technology holds the promise of solving these problems, but there are some complications. For example, many organizations continue to struggle with the challenge of integrating their legacy systems with the newer technology. The approach in this book offers a streamlined set of modeling techniques based on Unified Modeling Language (UML); uses a serviced-based architecture that provides an overall design philosophy for reusable software that addresses the needs of the business, not the technology; and is a clearly defined software process that provides guidance on how to employ the knowledge base of available techniques. |
Índice
Foreword | vii |
Preface | ix |
Acknowledgments | xvii |
OVERVIEW | 3 |
13 Drivers of Change | 5 |
14 Modeling Techniques | 9 |
15 Architecture | 11 |
16 Process | 12 |
93 Legacy System Wrapping Techniques | 214 |
94 Package Wrapping Techniques | 219 |
95 Data Wrapping Techniques | 226 |
96 Practical Guidelines on Component Modeling of Legacy Assets | 237 |
97 Summary | 241 |
DEPLOYMENT MODELING | 243 |
103 DeploymentModeling Notation | 244 |
104 DeploymentModeling Techniques | 245 |
17 Component Management | 14 |
18 A Road Map for Using This Book | 15 |
THE PERSPECTIVE ARCHITECTURE | 17 |
22 Problem Definition | 18 |
23 A Brief Historical Survey | 19 |
24 A ServiceBased Architecture | 24 |
25 Object Stereotypes | 27 |
26 Service Categories and Object Stereotypes | 32 |
27 Modeling Techniques Within the Perspective Architecture | 33 |
28 Summary | 36 |
BUSINESS PROCESS MODELING | 37 |
32 BPM Principles | 38 |
33 BPM Notation | 42 |
34 BPM Techniques | 43 |
35 Business Processes and ComponentBased Development | 55 |
36 Summary | 56 |
USE CASE MODELING | 59 |
42 Use Case Modeling Principles | 60 |
43 Use Case Modeling Notation | 62 |
44 Use Case Modeling Techniques | 64 |
45 Practical Guidelines for Use Case Modeling | 81 |
46 Summary | 86 |
CLASS MODELING | 87 |
52 Class Modeling Principles | 88 |
54 Class Modeling Techniques | 92 |
55 Practical Guidelines for Class Modeling | 116 |
56 Summary | 121 |
OBJECT INTERACTION MODELING | 123 |
62 Object Interaction Modeling Principles | 124 |
63 Object Interaction Modeling Notation | 127 |
65 Practical Guidelines for Object Interaction Modeling | 144 |
66 Summary | 150 |
STATE MODELING | 151 |
72 State Modeling Principles | 152 |
73 State Modeling Notation | 154 |
74 State Modeling Techniques | 160 |
75 Practical Guidelines for State Modeling | 172 |
76 Summary | 176 |
BUSINESSORIENTED COMPONENT MODELING | 177 |
82 BusinessOriented Component Modeling Principles | 178 |
83 BusinessOriented Component Modeling Notation | 182 |
84 BusinessOriented Component Modeling Techniques | 185 |
85 Practical Guidelines on BusinessOriented Component Modeling | 205 |
86 Summary | 207 |
COMPONENT MODELING OF LEGACY ASSETS | 209 |
92 Legacy Asset Component Modeling Principles | 210 |
105 Practical Guidelines on Deployment Modeling | 249 |
106 Summary | 250 |
THE PERSPECTIVE PROCESS | 251 |
112 Process Fundamentals | 252 |
113 Themes in the Perspective Process | 254 |
114 Solution and Component Processes | 261 |
115 BPM and the Perspective Process | 265 |
THE SOLUTION PROCESS | 271 |
122 Applicability of the Solution Process | 272 |
123 Solution Process Overview | 274 |
124 Feasibility Study | 277 |
125 Analysis | 282 |
126 Prototype | 287 |
127 Plan Increments to Deliver | 291 |
128 Design and Build an Increment | 293 |
129 User Acceptance of an Increment | 299 |
1210 Roll Out of Increment | 300 |
THE COMPONENT PROCESS | 303 |
132 Applicability of the Component Process | 304 |
133 Component Process Overview | 308 |
134 Architectural Scoping | 312 |
135 Assessment | 315 |
136 Plan Services | 318 |
137 Design and Build Components | 320 |
138 Acceptance of Components | 325 |
139 Roll Out Components | 327 |
PERSPECTIVE TEAMS | 329 |
142 Team Attributes | 330 |
143 Joint Application Development | 334 |
144 Team Types | 336 |
145 Team Roles | 337 |
146 Dynamics of Solution and Component Projects | 341 |
147 Examples of Team Configurations | 342 |
148 Summary | 344 |
CASE STUDY VWX SOFTWARE INC | 345 |
153 Feasibility Study | 354 |
154 Analysis | 368 |
155 Prototyping | 392 |
156 Increment Planning | 394 |
Deliverables | 413 |
Relational Mappings | 423 |
Glossary | 433 |
445 | |
Términos y frases comunes
analysis application approach Assess associated attributes BAY SLOT behavior Book Job business class business event business objects business process modeling business requirements business services CANCEL chapter class diagram class model client collaboration diagrams component modeling component packages component process component project course type data objects data services database dependency diagrams described Description DSDM example external first-cut hierarchy diagram identified implementation increment iterative Job for Customer legacy assets legacy systems logical data model modeling techniques NAME nonfunctional requirements notation object interaction model object-oriented operations Perspective process postconditions primary key process group prototyping Public Booking Request reusable reuse role scenarios scheduled public course Search sequence diagram Service and Repair service class service package shown in Figure software development solution process solution project specific structure Table timeboxing user interface user objects user services vehicle VENUE Viability wrapper