Atjaunināt sīkdatņu piekrišanu

Component-Based Development for Enterprise Systems: Applying the SELECT Perspective [Mīkstie vāki]

  • Formāts: Paperback / softback, 490 pages, height x width x depth: 244x170x25 mm, weight: 770 g
  • Sērija : SIGS: Managing Object Technology
  • Izdošanas datums: 13-Jan-1998
  • Izdevniecība: Cambridge University Press
  • ISBN-10: 0521649994
  • ISBN-13: 9780521649995
Citas grāmatas par šo tēmu:
  • Mīkstie vāki
  • Cena: 78,11 €
  • Grāmatu piegādes laiks ir 3-4 nedēļas, ja grāmata ir uz vietas izdevniecības noliktavā. Ja izdevējam nepieciešams publicēt jaunu tirāžu, grāmatas piegāde var aizkavēties.
  • Daudzums:
  • Ielikt grozā
  • Piegādes laiks - 4-6 nedēļas
  • Pievienot vēlmju sarakstam
Component-Based Development for Enterprise Systems: Applying the SELECT PerspectivePalielināt
  • Formāts: Paperback / softback, 490 pages, height x width x depth: 244x170x25 mm, weight: 770 g
  • Sērija : SIGS: Managing Object Technology
  • Izdošanas datums: 13-Jan-1998
  • Izdevniecība: Cambridge University Press
  • ISBN-10: 0521649994
  • ISBN-13: 9780521649995
Citas grāmatas par šo tēmu:
Permanent link: https://www.kriso.lv/db/9780521649995.html
Keywords:
Presents the SELECT Perspective, a component-based approach that addresses the demands of large-scale, complex enterprise software development problems.

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.

Recenzijas

' this book is well worth reading, both for its solid overview of component modelling and for the thought-provoking sections on Select's Perspective. It's also an easy read, with good humour, helpful diagrams, and clear organisation. I would advise you to pick up a copy for your library, and read it on your next trip out of town'. Alan Zeichick, Software Development Online ' this book is well worth reading, both for its solid overview of component modelling and for the thought-provoking sections on Select's Perspective. It's also an easy read, with good humour, helpful diagrams, and clear organisation. I would advise you to pick up a copy from your library, and read it on your next trip out of town'. Alan Zeichick, Software Development Online

Papildus informācija

Presents the SELECT Perspective, a component-based approach that addresses the demands of large-scale, complex enterprise software development problems.
Foreword vii(2) Ed Yourdon Preface ix(8) Acknowledgments xvii 1 OVERVIEW 1(16) 1.1 Introduction 1(1) 1.2 What Is Perspective? 1(2) 1.3 Drivers of Change 3(6) 1.4 Modeling Techniques 9(2) 1.5 Architecture 11(1) 1.6 Process 12(2) 1.7 Component Management 14(1) 1.8 A Road Map for Using This Book 15(1) 1.9 Summary 15(2) 2 THE PERSPECTIVE ARCHITECTURE 17(20) 2.1 Introduction 17(1) 2.2 Problem Definition 18(1) 2.3 A Brief Historical Survey 19(5) 2.4 A Service-Based Architecture 24(3) 2.5 Object Stereotypes 27(5) 2.6 Service Categories and Object Stereotypes 32(1) 2.7 Modeling Techniques Within the Perspective Architecture 33(3) 2.8 Summary 36(1) 3 BUSINESS PROCESS MODELING 37(22) 3.1 Introduction 37(1) 3.2 BPM Principles 38(4) 3.3 BPM Notation 42(1) 3.4 BPM Techniques 43(2) 3.5 Business Processes and Component-Based Development 55(1) 3.6 Summary 56(3) 4 USE CASE MODELING 59(28) 4.1 Introduction 59(1) 4.2 Use Case Modeling Principles 60(2) 4.3 Use Case Modeling Notation 62(2) 4.4 Use Case Modeling Techniques 64(17) 4.5 Practical Guidelines for Use Case Modeling 81(5) 4.6 Summary 86(1) 5 CLASS MODELING 87(36) 5.1 Introduction 87(1) 5.2 Class Modeling Principles 88(1) 5.3 Class Modeling Notation 88(4) 5.4 Class Modeling Techniques 92(24) 5.5 Practical Guidelines for Class Modeling 116(5) 5.6 Summary 121(2) 6 OBJECT INTERACTION MODELING 123(28) 6.1 Introduction 123(1) 6.2 Object Interaction Modeling Principles 124(3) 6.3 Object Interaction Modeling Notation 127(4) 6.4 Object Interaction Modeling Techniques 131(13) 6.5 Practical Guidelines for Object Interaction Modeling 144(6) 6.6 Summary 150(1) 7 STATE MODELING 151(26) 7.1 Introduction 151(1) 7.2 State Modeling Principles 152(2) 7.3 State Modeling Notation 154(6) 7.4 State Modeling Techniques 160(12) 7.5 Practical Guidelines for State Modeling 172(4) 7.6 Summary 176(1) 8 BUSINESS-ORIENTED COMPONENT MODELING 177(32) 8.1 Introduction 177(1) 8.2 Component Modeling Principles 178(4) 8.3 Business-Oriented Component Modeling Notation 182(3) 8.4 Business-Oriented Component Modeling Techniques 185(20) 8.5 Practical Guidelines on Component Modeling 205(2) 8.6 Summary 207(2) 9 COMPONENT MODELING OF LEGACY ASSETS 209(34) 9.1 Introduction 209(1) 9.2 Modeling Principles 210(4) 9.3 Legacy System Wrapping Techniques 214(5) 9.4 Package Wrapping Techniques 219(7) 9.5 Data Wrapping Techniques 226(11) 9.6 Practical Guidelines for Component Modeling of Legacy Assets 237(4) 9.7 Summary 241(2) 10 DEPLOYMENT MODELING 243(8) 10.1 Introduction 243(1) 10.2 Deployment-Modeling Principles 243(1) 10.3 Deployment-Modeling Notation 244(1) 10.4 Deployment-Modeling Techniques 245(4) 10.5 Practical Guidelines on Deployment Modeling 249(1) 10.6 Summary 250(1) 11 THE PERSPECTIVE PROCESS 251(20) 11.1 Introduction 251(1) 11.2 Process Fundamentals 252(2) 11.3 Themes in the Perspective Process 254(7) 11.4 Solution and Component Processes 261(4) 11.5 BPM and the Perspective Process 265(6) 12 THE SOLUTION PROCESS 271(32) 12.1 Introduction 271(1) 12.2 Applicability of the Solution Process 272(2) 12.3 Solution Process Overview 274(3) 12.4 Feasibility Study 277(5) 12.5 Analysis 282(5) 12.6 Prototype 287(4) 12.7 Plan Increments to Deliver 291(2) 12.8 Design and Build an Increment 293(6) 12.9 User Acceptance of Increment 299(1) 12.10 Roll Out of Increment 300(3) 13 THE COMPONENT PROCESS 303(26) 13.1 Introduction 303(1) 13.2 Applicability of the Component Process 304(4) 13.3 Component Process Overview 308(4) 13.4 Architectural Scoping 312(3) 13.5 Assessment 315(3) 13.6 Plan Services 318(2) 13.7 Design and Build Components 320(5) 13.8 Acceptance of Components 325(2) 13.9 Roll Out Components 327(2) 14 PERSPECTIVE TEAMS 329(16) 14.1 Introduction 329(1) 14.2 Team Attributes 330(4) 14.3 Joint Application Development 334(2) 14.4 Team Types 336(1) 14.5 Team Roles 337(4) 14.6 Dynamics of Solution and Component Projects 341(1) 14.7 Examples of Team Configurations 342(2) 14.8 Summary 344(1) 15 CASE STUDY: VWX SOFTWARE INC 345(68) 15.1 Introduction 345(1) 15.2 Business Process Modeling 345(9) 15.3 Feasibility Study 354(14) 15.4 Analysis 368(24) 15.5 Prototyping 392(2) 15.6 Increment Planning 394(1) 15.7 Increment Design 394(19) APPENDIX A Deliverables 413(10) APPENDIX B Relational Mappings 423(10) Glossary 433(12) Bibliography 445(8) Index 453