Frequently Asked Questions
Component Based Development (CBD), Service Oriented Architectures (SOA), Legacy Rejuvenation schemes, in particular automatic conversion of old COBOL programs, as well as Model Driven Environments (MDE) are recent and innovative approaches. So it is obviously quite normal that a newcomer to these domains as well as a potentially interested customer may have various questions about the way these various concepts can be implemented.
In this chapter you can find the answers to the most frequently asked questions. Our aim is to update these pages as dynamically as possible to provide you with a useful guide through the intricacies of these innovative and highly interesting paradigms. Visit this site frequently!
- Component Based Development : choosing between J2EE, .Net or another environment?
- What are the valid reasons for adopting a Model Driven Environment (MDE) ?
- Comparison between Web Services and Service Oriented Architectures
- Components and Services : what is common and what is different?
- The successive steps for converting legacy COBOL applications to a modern environment
- An efficient way for creating an Enterprise Service Portfolio
- Component Based Development : choosing between J2EE, .Net or another environment?
When listening to the Java supporters, a Component Based Development supposes the J2EE norm, whereas Microsoft tries to demonstrate that .Net is the only possible solution. Here is a question : if you want to use another deployment environment do you really have to forget about a CBD type development?
- What are the valid reasons for adopting a Model Driven Environment (MDE) ?
Model driven development is a concept that has existed in the IT world for about 20 years. It is known both as Model Driven Environment (MDE) or Model Driven Architecture (MDA). The vital question : Is this development paradigm really operational or does it represent another example of virtual concepts without any practical implementations? Supposing that this scheme really works, are there good reasons to adopt it?
- Comparison between Web Services and Service Oriented Architectures
The expressions Web Services (WS) and Service Oriented Architectures (SOA) are often used in the same context which may sometimes be the reason for a certain confusion; in fact there are some aspects that appear to be common to WS and SOA, but fundamentally these two concepts are covering domains that are disconnected to a large extent.
- Components and Services : what is common and what is different?
Though Components and Services are two concepts which have become increasingly popular over the years, their precise meaning is not always well understood. Are CBD and SOA two approaches that are completely different or is there a certain convergence? Is Component Based Development to be considered as completely old-fashioned and is it really necessary to replace CBD by a Service Oriented Architecture, as is recommended by a certain number of major actors on the IT market?
- The successive steps for converting legacy COBOL applications to a modern environment
The methodology that has been adopted by CompoSys for rejuvenating legacy COBOL applications may seem complex at first view, but is in fact a very low risk and efficient approach. Describing hereafter the successive steps of such a conversion project will hopefully bring a lot of information and much clearer concepts to the persons who are facing the nightmare of this type of rejuvenation.
- An efficient way for creating an Enterprise Service Portfolio
In order to evolve to a Service Oriented Architecture (SOA) a vital preliminary step is to create an Enterprise Service Portfolio. What are the elements that must be included and what are the necessary steps for creating such a portfolio in an efficient way? We will try to answer these various questions in the following paragraphs.
 |