Well written & list is so impressive with good books thanks for sharing with us.

Object-Oriented Software Construction, Bertrand Meyer : I liked Test-Driven Development a lot more when it was called Design by Contract.
A Discipline of Programming, E.W. Dijkstra : I liked Test-Driven Development a lot more when it was called Correctness by Construction.
Structure and Interpretation of Computer Programming, Abelson and Sussman : The “Art of Electronics” of computer programs.
Introduction to Database Systems, C.J. Date : Just because SQL is a steaming pile of dung doesn’t mean the relational theory is obsolete.
Design Patterns, GO4 : Possibly the most widely misunderstood software book of the 1990’s.
Refactoring, Martin Fowler: Before he jumped the Agile shark.
Introduction to General Systems Thinking, Jerry Weinberg : Try not to confuse your tools and models with reality.
Total Design, Stuart Pugh : Cross-functional evolutionary feature teams…from the 1980’s.
Axiomatic Design, Nam Suh : Design decisions are a consequence of functional requirements. Functional requirements are a consequence of design decisions. We’re going to need a rigorous theory of design to make sense of this.
Lean Thinking, Womack and Jones : Any work that has a sequence of activities can be made to flow.
Managing the Design Factory, Don Reinertsen : Seminal interpretation of lean thinking for product development.
The Mythical Man-Month, Fred Brooks : Interpersonal communication is what makes software development hard.
Rapid Development, Steve McConnell : You mean there’s more than one way to do it…who knew?
Principles of Software Engineering Management, Tom Gilb : I liked Agile better when it was called Evolutionary Delivery.
Pragmatic Programmer, Hunt and Thomas : Pragmatism! Imagine that.
Software by Numbers, Denne and Huang : Incremental delivery is less risky AND more profitable.

Other favorites you mentioned: Refactoring (Fowler), _all_ the ones in “Fundamentals”, Head First Design Patterns, and some of the ones listed in “Requirements”