Home > Store

Component-Based Development: Principles and Planning for Business Systems

Add To My Wish List

Component-Based Development: Principles and Planning for Business Systems

By Katharine Whitehead
Published May 28, 2002 by Addison-Wesley Professional.

Book

Sorry, this book is no longer in print.

Not for Sale

Description

Sample Content

Updates

More Information

Description

Copyright 2002
Dimensions: 7-3/8x9-1/4
Pages: 224
Edition: 1st

Book
ISBN-10: 0-201-67528-5
ISBN-13: 978-0-201-67528-3

It will guide the reader through the process of introducing a component-based approach to a business from a programme-planning perspective, based on the author's experience as an industry consultant in this area.
It will also outline the need-to-know issues in designing and assembling components, including strategies for scoping components and managing their assembly.
It will provide the essential background and grounding in the components area for readers who already have a knowledge of model-based methods e.g. OO but want to spring-board over into using a component-based approach.



Sample Content

Preface.

I. INTRODUCTION TO COMPONENT-BASED DEVELOPMENT.

1. Component-based Development: Attempting to Manage Chaos.

Problems of Software Development.

Steps Toward Improving Software Development.

The Promise of Component-based Development.

The Feasibility of Component-based Development.

2. What are Components?

Definition of a Component.

Component Granularity.

Component Environment.

Components and Their Place in a Whole.

Deploying Components.

Component Models.

Component Specification.

3. Putting Components in Perspective.

The Relevance of Model-based Development.

Specification and Design Reuse.

The Relevance of Object-oriented Techniques.

Software Infrastructure and Development Automation.

Differing Needs of Different Types of Organization.

Where Component-based Development is not Relevant.

Limitations of Component-based Development.

II. THE PLANNING PROCESS.

4. Positioning Components within the Organization.

The Ownership and Scope of a Component-based Development Initiative.

Coordinating Software across Organizational Units.

The Internal Market Model.

5. Software Architecture and Infrastructure.

Areas of Architectural Concern.

Technical Environment Issues.

Software Infrastructure Issues.

Application Architecture Issues.

6. Defining Components.

A Layered Architecture.

Component Types.

Wrappers and Adapters.

Defining the Scope of Components.

Component Specification.

7. Putting Component-based Development into Practice.

Defining the Scope and Expected Benefits of a Component-based Development Initiative.

Defining a Component Blueprint.

Auditing Current Systems.

Establishing an Architectural Framework.

Organizational Considerations.

Program Planning.

Preface

This book tries to answer the questions: What is it that we are trying to achieve with components? and How can we define and implement components so that we do achieve this? It is intended to provide an insight into the specific benefits of component-based development (CBD) and to convey the conceptual issues that must be fully understood in order to be successful with CBD.

It aims to:

explain the rationale for CBD and the key concepts behind it;
outline an approach to program planning that should significantly improve the effectiveness of CBD;
provide guidance on introducing a component-based approach into the organization;
provide an understanding of the issues involved in the design and assembly of components, including strategies for scoping components and for managing their assembly.

It is left to other books in the field to provide technical insights into J2EE, .NET, etc. or to provide a full method that would necessarily have a heavy emphasis on modeling techniques. Instead, it is assumed that you will use a model-based development method (preferably OO or at least hybrid). This assumption makes it possible to concentrate in this book on issues that are specific to adopting a component-based approach, rather than discussing software development techniques that are already widely understood.

CBD is usually regarded as principally relevant to new software development. However, software development cannot take place in a vacuum. It must take account of the current application portfolio and existing software infrastructure of the organization. It is for this reason that this book pays particular attention to program planning. In this book, CBD and integration with existing systems are seen as natural partners. Software development is seen as a process of gradual migration forwards from an existing application portfolio to an improved (and more component-based) application portfolio. CBD provides a means of achieving this gradual improvement, while a component-based vision of how the application portfolio could ultimately look provides guidance as to how to move it forwards.

Audience

This book aims to meet the needs of practitioners, and in particular the needs of program planners and architects, who are likely to be responsible for achieving the introduction of CBD into the organization. Managers, designers, and developers should also find it of use.

Content and organization

The book contains the following parts and chapters:

PART 1. Introduction to component-based developmentChapter 1 Component-based development: attempting to managing chaos

This chapter explains the industry context within which CBD has emerged, and why CBD provides a way of dealing with the conflicting pressures facing software developers.

Chapter 2 What are components?

This chapter provides a definition of components and a discussion of component characteristics. It also discusses the environment required to support components, and briefly outlines the advantages and disadvantages of existing component models such as COM, CORBA, and EJB.

Chapter 3 Putting components in perspective

CBD is only a part of what is relevant for effective software development. This chapter positions CBD in relation to other development techniques, and in relation to OO. It also discusses the limitations to the potential of CBD, and the contexts in which it will not be relevant.

PART 2. The planning process

Chapter 4 Positioning components within the organization

phis chapter discusses the ownership and scope of a CBD initiative and its positioning within the organization.

Chapter 5 Software architecture and infrastructure

This chapter discusses the need for an architecture and the various aspects that an architecture for CBD needs to cover.

Chapter 6 Defining components

This chapter covers the principles affecting component definition:

coarse- versus fine-grained components;
types of component and how they can be fitted together;
defining component scope.

Emerging standards are discussed.

Chapter 7 Putting component-based development into practice

This chapter builds on the previous three chapters and outlines a set of tasks that can be carried out to create an initial CBD strategy and to refine this strategy over time.

Chapter 8 Pragmatics of program planning

This chapter discusses how the CBD strategy can be put into effect over time, as part of program planning. It covers the process of reconciling an ideal vision with short-term requirements and messy reality.

Chapter 9 Organization for component-based development

This chapter discusses alternative organizational structures for implementing a zBD program. It discusses roles and team structures for strategy planning, component acquisition, and component assembly.

PART 3. Building and assembling components

Chapter 10 Acquiring components

This chapter covers issues that are specific to procuring components as opposed to packages.

Chapter 11 Designing components

This chapter discusses how to design components for flexibility [ and where to draw the line in designing for reuse.

Chapter 12 Assembling components

This chapter discusses some of the issues that arise when fitting components together.

Chapter 13 Testing, certification, and maintaining a component catalog

This chapter outlines issues relating to the management and maintenance of a portfolio of components, including a consideration of what is needed to make a component available for reuse or sale.

PART 4. A brief case study

Chapter 14 Managing chaos with components

This chapter contains a brief (fictional) case study of the use of CBD in an organization with existing mainframe-based applications that is evolving toward a component-based approach, as it introduces call centers and Internet-based systems.

Acknowledgments

The origins of this book lie in work on components that my colleagues and I carried out while I was working at Seer Technologies. I owe much to Jon Cogdale, who was my collaborator on our original research into components, and my examples in Chapter 7 are based on his. Graham Berrisford contributed lively and thought-provoking discussion of the concepts, and the order processing examples in Chapter 12 owe much to discussions with him. Amongst my colleagues, Doug Kime, Rob Allen, Tony Phillips, Bernard Londeix, Mark Gilbert, and Martin Carter also offered valuable advice.

I also learned from the experiences our customers shared with us, from the CBDi Forum run by David Sprott and Lawrence Wilkes, as well as from other literature and work in the field.

0201675285P04152002



Updates

Submit Errata



More Information



InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address