None of this precludes the architecture team and the programming team from using the same modeling tool. They just can't use the same model. Architects are less concerned with formal semantic models and more concerned with communicating broad ideas. Text and drawings are more important than rigid models. Programmers are concerned with getting the details right, which semantic models help them do.
Blueprints are as essential to software architecture as they are to building architecture.
It's not enough for software architects to communicate and direct the roles of the players involved with the building of software. That's management, not architecture. White paper on software blueprinting by an up and coming tool vendor. One of the leading design tools.