Component Based Software Development

Component based software development (CBSD) focuses on building large software systems by integrating previously-existing software components. By enhancing the flexibility and maintainability of systems, this approach can potentially be used to reduce software development costs, assemble systems rapidly, and reduce the spiraling maintenance burden associated with the support and upgrade of large systems. At the foundation of this approach is the assumption that certain parts of large software systems reappear with sufficient regularity that common parts should be written once, rather than many times, and that common systems should be assembled through reuse rather than rewritten over and over. CBSD embodies the "buy, don't build" philosophy espoused by Fred Brooks . CBSD is also referred to as component-based software engineering (CBSE). Component-based systems encompass both commercial-off-the-shelf (COTS) products and components acquired through other means, such as nondevelopmental items (NDIs). Component Software Development alters development emphasis from programming software to composing software systems. This increases the flexibility of systems, trims down the software development, maintenance cost and time. Emergence of component integration technology enhancing efficient performance. Reuse of existing software is possible by Component software development.

It's a fact that businesses find itself being increasingly dependent on fast paced electronic interaction (among customers, partners, employees and suppliers). As the technology landscape gets complex, it becomes progressively difficult to manage and process information. The challenge is to have the right fit of technologies at the right place in the right business process. The need to integrate and make the platforms inter-operable has primarily evolved from the fact that the customers are the ultimate beneficiaries. In fact, no customer wants to get locked in a single vendor - single technology arena. Most enterprise systems need to be connected in some way to other systems, either inside the company or with the trading partners over the Internet. In most cases, the new demands make integration essential. Thus the development of Component Software focuses on building large software applications by integrating previously existing software components. Integration can reduce the time taken to make information available. It can also reduce costs. Rather than replace existing systems, integration can be used to link them. The foundation of this approach is the assumption that certain parts of large software systems should be written once rather than many times, and that common parts of large software systems should be assembled through reuse rather than rewritten all over again.

Premier implements CBSD while developing products and projects. So as to ensure reusablity of code and value created. We develop the component for showing the Tree structure Graphically. The XML structure of tags gets directly displayed on the jTable. The configuraton of the Leaf icon, and directory like symbols are completely settable. We develop the component for showing the Menu Options and the Action to be taken on its click . The XML structure of tags gets directly displayed as the menu options on the Frame. The configuraton of the icons, symbols that can be associated with each menu and sub menu are completely settable. This component that is developed needs the simple interface of its parent(where the Tollbar is to placed) and the text(item) to be displayed inside it. Here also the the icons, and their paths are mapped as per the accompaning XML file. This component that is developed needs the simple interface of its parent(where the Tollbar is to placed) and the text(item) to be displayed inside it. This chating bean component is again configurable to any business need, here you just have to configure it for the Login, and logout notification, there are many facilities like storing the log of communication, Administrator's rights which can be setted as per the need basis. This mailing component just needs the basic information of the system where it is going to get deployed, it hides all the inside complexities and give the simplest interface of mailing. We have done it, are doing it and can do it all.