There are tons of resources on the web referring to and listing code smells.  However, I've never seen information on architectural smells.  Is this defined somewhere, and is there a list available?  Has any formal research been done into architecture defects, and their impact on project speed, defects, and the like?Edit: I wasn't really looking for a list in the answers, but documentation (on the web or in a book) about architecture smells.  
Are there architecture smells?
architecture;code smell;quality
Multitier ArchitectureWhen you have Layers on Layers on Layers on Layers... you see my point here, in your application. I call it Over Layered ArchitectureOver abstraction in such way that you get lost in the code.Futuristic Architecture This happens when the solution is too futuristic. In reality no one can predict new requirements. Therefore most of the futuristic implementation is just waste of time and resource.Technology Enthusiastic  ArchitectureThe architect liked the new technology and he put in production. Without knowing if it was proven before.Over Kill Architecture A simple problem was solved by exponential factor of architecture skills and technology.Cloud ArchitectureI call it cloud architecture since architecture has no connection to the really. Its just some nice Visio diagrams.The total lack of the opposite is also true.Here is link of Top Ten Software Architecture Mistakes.