Includes bibliographical references and index.

The internet age: An era of change -- The challenge of change -- Technology soup -- The adaptive enterprise -- e-Business in brief -- e-Commerce versus e-business -- The internet spectrum -- The challenges of e-business -- Components in brief -- Component anatomy -- Separation of concerns -- Toward object maturity: How components help -- Business components -- Component-based development -- A word on modeling -- Meeting the challenges of e-business -- Top-down: Process and architecture -- Bottom-up: Integration -- Business-IT alignment -- e-Business process improvement -- The concept of e-business process improvement -- e-Business process improvement planning -- Business process modeling (BPM) -- The business case for CBD -- Identifying business drivers -- Assessing architecture -- Assessing process -- Assessing organization -- Balancing strategy and delivery -- Component architecture -- An interface-based approach -- The separation of interface and implementation -- Interface-based design -- Integrating business processes and components -- The service-oriented view -- The criticality of architecture -- Structuring the business process model -- Value-added versus commodity components -- Architecture and e-business -- Dimensions of component architecture -- Level of abstraction -- Project versus enterprise architectures -- Architecture as integration model -- Forms of a component -- Specification versus implementation -- Architecture layering -- The main sequence -- Process guidelines -- The CBD process framework -- A track-based pattern -- Deliverables -- Integration -- Organizing deliverables within the track-based pattern -- Reuse checkpoints -- CBD process themes -- Iterative and incremental integration -- Hybrid integration -- Gap analysis -- Techniques versus deliverables -- Technique overview -- Migrating to e-business -- Legacy renewal and EAI -- First generation e-business -- Legacy renewal -- Exploiting legacy systems -- Exploiting software packages -- Enterprise application integration -- Approaches to integration -- Architecture for integration -- Strategic versus tactical integration -- Example: Migrating to e-business -- e-Business process improvement planning -- Scoping software requirements -- Building an enterprise component architecture -- First increment: Rapid delivery -- Second increment: e-Business solution -- Realizing e-business -- Welcome back to Harry's -- e-Business process improvement planning -- Third increment: Personalization -- Fourth increment: Improving the customer's experience -- Business transformation -- Adaptability -- Business process integration -- The role of CRM -- External services integration -- Provisioning strategies -- Gap analysis -- A world of choice -- Revisiting the CBD process -- Applying gap analysis -- Component provisioning keynotes -- The importance of business specification standards -- Visualizing provisioning strategy -- Component granularity -- Routes to component provision -- Purchasing components -- Outsourcing design and implementation -- Wrapping -- Adapting -- Extending interfaces -- Subscribing to virtual services -- Outsourcing using ASPs -- CBD funding strategies -- Funding challenges -- Cultural challenges -- Funding models -- Project funding -- Corporate funding -- Charging for components -- Choosing the right funding model -- 'Components in advance' -- 'Components as you go' -- 'Components by opportunity' -- Examples of funding and charging -- Metrics -- Some rules of thumb -- Component cost-benefit factors -- CBD cost factors -- Identifying IT benefit factors -- Identifying business benefit factors -- e-Business team organization -- Team roles in context -- Basic definitions -- The significance of team roles -- Traditional teams versus e-business teams -- Leadership -- Shedding IT's anorak -- Further team attributes -- Types of e-business teams -- e-Business solution-oriented roles -- Executive sponsor -- Visionary -- Ambassador user -- Adviser user -- Solution designer -- Project manager -- Team leader -- e-Challenger -- Web master -- e-Business integrator -- Component-oriented roles -- Component sponsor -- Business component architect -- Technical component architect -- Component assessor -- Reuse manager -- Business component analyst -- Business component designer -- Technical component designer -- Legacy expert -- Component librarian -- Component certifier -- Component tester -- Business-IT alignment roles -- E-vangelist -- Provisioning strategy manager -- Business process coordinator -- Component funding manager -- Organizational models -- Brief historical observations -- Customization -- Using the track-based pattern -- Appendix 1: Component-oriented technologies -- Component and internet standards -- Component execution environments -- Microsoft's COM+ -- CORBA -- EJB -- EJB and the CORBA component model -- XML -- Physical architecture -- Server-based architecture -- EAI tools -- Business modeling -- Business modeling concepts -- Business modeling notation -- Business modeling quick guide -- Business modeling tips and hints -- Business type modeling -- Business type modeling concepts -- Business type modeling notation -- Business type modeling quick guide -- Business type modeling tips and hints -- Use case modeling -- Use case modeling concepts -- Use case modeling notation -- Use case modeling quick guide -- Use case modeling tips and hints -- Component architecture modeling -- Component architecture modeling concepts -- Component architecture modeling notation -- Component architecture modeling quick guide -- Component architecture modeling tips and hints -- Interaction modeling -- Interaction modeling concepts -- Interaction modeling notation -- Interaction modeling quick guide -- Interaction modeling tips and hints -- Specification modeling -- Specification modeling concepts -- Specification modeling notation -- Specification modeling quick guide -- Specification modeling tips and hints.

We are all well aware of the growth e-business initiatives. What you may not realize is the growth in components use: According to Gartner Group "By 2003, at least 70 percent of the total number of new applications will be built primarily from building blocks" ("Component based development - the Next Wave, Research Note, Jan 1999). This book is designed to give practical help by showing how a company can evolve its e-business capability using a step by step component-based approach, providing innovation while leveraging investments in existing systems and software packages. Components provide an ideal underlying fabric for the new world of e-Business. They offer flexible services that can be reused across organizational and geographical boundaries, in different combinations which reflects the open, fluid nature of Internet business.