Problems and Pitfalls of CBD

This is certainly a rather interesting list of attractions. Here the question arises: Will components contain any downsides or challenges? Yes, indeed. To begin w'ith, an appropriate situation is critical on the off-chance you need to make the best use of pieces. Clearly, rapidly producing your own conditions over the working system is conceivable in theory. But in practice, it is not possible. In fact, reuse is one of the most motivating aspects for using components, meaning it should be conceivable to reuse a component created for another purpose, probably in another environment. It implies standardization, and in fact this is the biggest obstacle to CBD’s performance right now. Benchmarks are expected regarding the middleware the components will operate in. Middleware can mean a lot of things, but what is inferred here is a layer of communication that empowers parts to send more substantive-level messages to different segments, if appropriate in a system. Obviously, what has a place in the middleware, and so forth, is open to discussion. For example, should the dealing with trade be a piece of it? What about commitment? There are currently three contending frameworks on this field: CORBA from the Object Management Group, Microsoft’s COM/DCOM and Java’s Remote Method Invocation. In addition, these three norms are not exactly identical to each other. CORBA is a standard only, while COM/DCOM is not only a standard but also a function. CORBA is actually an independent language, COM/DCOM and RMI, as far as anyone knows, are a part of the Java standard.

Five Problems of Effort Estimation

In CBS systems, the problems with respect to effort estimation can be explained through five questions:

(1) Why are legacy techniques for cost estimation not valid for CBS?

It is always possible to underestimate or overestimate efforts for components, as these components are pure design artifacts.

Effort estimation of CBS depends upon many criteria. The two most important criteria are as follows:

  • • Interaction among components.
  • • Complexity of these interactions.

These interactions may cause interdependencies among components. CBS complexity is directly proportional to these dependencies.

Another factor which might be considered for complexity is the type of integration.

Hence, it is not easy to estimate efforts for CBS.

The complexity of CBS is much higher as compared to legacy systems, because of these reasons effort-estimating techniques, available for traditional systems do not work for CBS.

(2) What are the consequences for not evaluating efforts accurately?

Some important consequences for incorrect estimation of efforts are:

  • Cost increment: If efforts are not estimated correctly then either costs may be excessive, or in case of underestimation, costs may be reduced.
  • Delivery delay: The second result may be a delay in delivery. This may be possible either because of delivery or resource constraints.
  • Withdrawal: It may be the chance that customer withdraws projects.

Social consequences are goodwill and customer dissatisfaction.

(3) Who are most suitable team members to guide the budget?

Members of a team according to their role are known as project owners, developers, architects, profit managers, etc.

Developers are the individuals who are responsible for coding, they may give valuable suggestions to the owners.

The project manager is responsible for evaluating the method for assessment given by the process owner for evaluation of project.

(4) What is the correct time for reevaluating the expectations?

Down the line, project scope and planning may change; things may not go as expected. When it is clear, there is a need to reevaluate the expectations of the technology, the people, the condition of the platform, and the risks to the environment or specific activities.

(5) What are the areas for effectively assessing efforts?

The following areas are suggested:

  • • Scheduling and staffing.
  • • Managing cost increment during the project.
  • • Completion of project in time within a previously defined budget.
< Prev   CONTENTS   Source   Next >