We have taken a lot of words and ideas from construction industry throughout the history of software development, and in fact we probably took to many, and I don't think there is anything left to take.
We took the whole process of having customers making a specification, then an architect planning, then engineers designing and lastly code monkeys implementing from the construction industry, and it turned out to be wholly misguided.
This is because when you build a house, if your foundation is wrong, you are effed. Seriously effed. To lift a building and replace it's foundations costs more than scrapping the whole thing and starting over. But in software it's completely possible. I've remade a client software into a client-server solution without the user noticing anything, except that I moved the modem to the server room. That's like replacing the concrete foundation with a boat while the inhabitants were sleeping.
Software is not like construction. And that's why the whole software industry turned on a time in the beginning of the naughties and the whole "waterfall" process of running projects was replaced with agile processes in just a couple of years.
As for words almost everythingmuch is taken from construction, rightly and wrongly.
Framework is the most obvious one not taken already. And there are pipes.