Talk:Component-based software engineering

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Hi - I'm planning to contribute in a major way towards the serious improvement of this article. I would like to expand, update, and in some cases correct, as many parts of the article that I can. I strongly feel that the quality of the article at the moment is very poor for several reasons, and the subject of CBSE is very much centre-stage amongst software engineering today. I've already made a few major changes (rewritten paragraphs and the new pictures), and I will continue to do so throughout the near future. Please let me know if anyone has any feedback on any of the changes that I make. - 16/05/09.

CBSE is a cute new branch in Software engineering and should have its own page in Wikipedia. Better somebody to write the article instead merging it with something that is not appropriate. Check the searches-most people (like me) will search for CBSE, not "software componentry" (who named that?).

I agree with that... Never heard of 'software componentry' before... jytrdfguygkgtuytfjhgfvjhtd

Why merge?

CBSE (sometimes known as CBD - component based development) has been around for many years. The current article on CBSE is merely a stub; I cannot see how this article could be fleshed out without repeating stuff that is already in the Software componentry article. The merger question isn't whether CBSE and software componentry are precisely the same concept, but merely whether Wikipedia should have one article covering both concepts, with redirects where necessary. My view in this particular case is that one article would be simpler and clearer than two separate articles. However I agree with the previous comments that the term "software componentry" is relatively unusual, so it may make more sense to merge the software componentry material into the CBSE article rather than the reverse. --RichardVeryard 12:22, 20 April 2007 (UTC)[reply]

User:Radagast83 has deleted the merge tags on the grounds that there is no consensus. The original merge tag did not specify the direction, so some people interpreted it as a proposal to merge the CBSE article into the software componentry article, and objected to a merger in this direction, largely on the grounds that CBSE was an important notion and software componentry was a less well-known notion. I think this is a fair objection, but it doesn't represent opposition to a merge in the opposite direction - merging the software componentry article into the CBSE article. Nobody has disagreed with my argument for a merge in this direction. I therefore think it is reasonable to reinstate the merger proposal, but this time being more definite about the direction of the proposed merge. --RichardVeryard 21:03, 8 June 2007 (UTC)[reply]

Move software componentry to CBSE [merging as necessary] -- Jonmmorgan 23:41, 12 August 2007 (UTC)[reply]

Indeed!

I'm not even convinced this term "software componentry" is really wide used. Looking at the "in other languages" section of the other article, all links are(in the given languages of course) about "Components(Software)", not about "Software componentry"... 200.137.197.12 19:37, 19 May 2007 (UTC)[reply]

some review comments

Although many distributed computing frameworks/middlewares defined their proprietary component models, the distributed computing itself is conceptually orthogonal to CBD. Specifically, many distributed computing frameworks/middlewares in the list are not relevant to CBD. This article sent a misleading defintion of CBD, namely, a distributed computing (or good distibuted computing) framework is automatically a CBD framework or should define its own CBD model. This is not only not necessary true, but also architecturely wrong! A CBD model should better be defined orthogonal to (rather than tying to) a specific distribute model. This allows the same CBD model to work with different distributed computing models/middlewares and vice versa.

Similarly, interface description languages are also orthogonal to CBD. And many listed IDLs are irrelevant to CBD either.

I don't see why the generic programming should be mentioned in this CBD article? If GP was CBD, why C library fucntions (for instance, printf()) wasn't CBD? —Preceding unsigned comment added by Kjin101 (talk • contribs) 18:23, 29 November 2007 (UTC)[reply]

component

what is a component in a software? whether it is a kind of package or program? —Preceding unsigned comment added by 203.99.197.2 (talk) 06:29, 28 October 2008 (UTC)[reply]

Anthropomorphism?

When compared to Object-Oriented Programming, the text says CBD discourages anthropomorphism. If this is a relation to OOP, shouldn't the correct term be 'polymorphism?' Anthropomorphism relates to giving non-human things human-like characteristics, whereas polymorphism refers to inheritance and child types being equivalent to parent types, but not vice-versa. (A square is a rectangle, but a rectangle is not a square.) I'm not an expert, but I figure if you're comparing two things, the term had better relate to one of them!

66.191.95.62 (talk) 14:14, 24 December 2008 (UTC)Programmer[reply]

I never heard of it too. This must be a mistake and I am fixing it. Ramiro Pereira de Magalhães (talk) 14:14, 11 January 2009 (UTC)[reply]