Skip to main content link. Accesskey S
  • Help
  • IBM Logo
  • IBM Notes and Domino Application Development wiki
  • All Wikis
  • All Forums
  • THIS WIKI IS READ-ONLY. Learn more...
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
  • API Documentation
Search
Community Articles > Designing Applications > Designing Composite Applications > Designing composite applications: Component design
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Click to view profileIBM contributorDeanna Drschiwiski
Contribution Summary:
  • Articles authored: 76
  • Articles edited: 227
  • Comments Posted: 8

Recent articles by this author

Getting started with XPages

Need help getting started with XPages? This guide provides links to overview content, videos, tutorials, and other content that will get you up to speed quickly.

XPages Domino Object Map 8.5.2

This topic contains a map of the domino objects contained in XPages.

Best practice to develop a good Notes application from the globalization perspective

This presentation shows the best practice to develop a good Notes application from the globalization perspective

Introducing of Domino Global WorkBench 8.5

This presentation shows how to localize Domino templates with Domino Global WorkBench 8.5

XPages Extensibility API Developers Guide

Welcome to the XPages Extensibility API Developers Guide; the Official Resource for Development using the XPages Extensibility API.
Community articleDesigning composite applications: Component design
Added by IBM contributorDeanna Drschiwiski on October 29, 2009 | Version 1
  • Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: composite applications, interaction
This article charts some basic approaches for designing components for composite application development that have maximum reuse. You can use many different strategies to provide the optimum components.

It takes a village

Composite application components have a very open definition. The ability to do almost anything you like is powerful, but it can also lead to uncertainty about what you should do and how to establish a standard approach to development. Keep in mind that the categories of elements given in this article are suggestions for one possible approach. No approach is wrong. Any one approach either works for your company or does not. If you think our suggestions work for you, then adopt them. Feel free to change them if you have other requirements.

This sort of integration, though, does not happen purely by creating composite applications. It is possible to create components that operate no better together than two separate Web pages side by side. The key to a successful deployment of the component application architecture is establishing a common forum where dialogue takes place about the different development efforts. Be sure to create development processes in your organization for coordinating these efforts and for ensuring that you can capitalize on the potential benefits of composite application design.

If your company has something akin to an architecture review board, that may be an appropriate place for such dialogue to happen. If your company is smaller, even nominating a single person to be the data type owner serves this need. Such an organization must not slow down development. Too much focus on process cancels out the benefits you may otherwise gain. Instead, the review board is more of a brainstorming center, where different groups can inform each other of their ideas, and can realize the potential for benefit across all groups.

Want to read the rest of the article? See Designing composite applications: Component design on the developerWorks website.

This article is the second in a series of articles on composite applications being published on developerWorks® Lotus. See the previous developerWorks articles,"The Lead Manager application in IBM Lotus Notes V8: An Overview," "Designing composite applications: Design patterns," "Designing composite applications: Unit testing," "Designing composite applications: Writing an Eclipse component for IBM Lotus Notes,"and "Designing composite applications: IBM Lotus Notes components".


  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (1)Oct 29, 2009, 7:27:51 PMDeanna Drschiwiski  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkThe Social Lounge
  • Wiki Help
  • Forgot user name/password
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use