In my (software) experience, the terms are basically interchangeable. Some people will violently defend “architect right, design wrong” and others the opposite, So uh, pretty hard for me, a normal person, to care much about which word is right for the “you sit down and think before you build” part of software engineering.

I think the analogy is to construction, not engineering.

In construction, architects and designers do different jobs. The software equivalents of those roles map reasonably well to the construction equivalents.