What buzzwords, phrases and expressions used in the IT industry do you consider to be ridiculous, overused and often to project an inaccurate meaning?

1) The number one position is a tie between Business Logic, Data Access, the word layer or tier, and Domain model.
2) ORM
3) CRUD
4) J2EE - What ever happened to calling it Java?, I guess because the third E in J2EE stands for Enterprise, people may view using the term J2EE to be more prestigious?
5) EAV

Ridiculous, overused and innacurate phrases from my personal experience:

1. AutoNumber
   This is SQL Server - grow up
2. Every table should have an autonumber primary key
   I've been forced to implement this even when there's a natural key.
3. Stick that on George's queue
   Why does all the bull land up in my workload queue?

Damn that's put me in a bad mood.

Yes, I will absolutely agree with you about the use of Autonumber. On that subject, I still find myself amazed at the number of people who confuse the concept of a surrogate key with a natural key.

George, have you also found there to be many developers who are not aware of the UNIQUE constraint in databases, and that many tables have two such constraints, including the primary key. The number of issues relating to "duplicates" that arise as a result of the database not being in First Normal Form is quite remarkable.

I think you'll find that there are more developers who are not aware of the PRIMARY KEY constraint in databases...
They'll know exactly what IDENTITY(1,1) does, but they have no idea that this is just not enough

Oh and this link arrived in my inbox just in time:
http://thecutest.info/top.html

Hands up - I use autonumber all the time. It's a habit, but all the database I support fail when it comes to identitying a straightforward primary key (e.g. one database would require three fields, one of which is often adjusted at a later date by the user).

And, yes I have grown lazy over the years.

So shoot me ....

"Data Warehouse", hands down. The most ill-defined term in database development.

With "Denormalization" in a very close second.

That's a good shout Blindman.
Here's one for the pile

User Acceptance Testing

"I logged in and out - everything seems fine"

Every problem needs a help desk ticket
- fine, but if I set up a ticket then at least contact me when it's closed / cancelled

Major problems that affect multiple clients must also receive approval from Management at the weekly meeting
- huh? So we wait one week before doing something that is imperative.

Upgrade - why does this always seem to include the loss of functionality?

@georgev I think I had those users too