Blueprints should be indexed and cross-referenced in every way that makes sense. And online search engines make referring to the blueprints easy for stakeholders. Avoid code generation from architectural models Blueprints for software architecture range from simple text and drawings to elaborate semantic models and hypertext documents. UML may eventually provide a standard form for software blueprints, but it has not achieved universal acceptance yet, so people are looking at various formal notations, languages, and tools. And while formalism can be useful, it may not be sufficient.
Many architects use text with accompanying block diagrams.
The development community suffers from a near-universal urge to quit planning and start coding. They claim this unifies the development process, from architecture to deployment, and reduces the amount of rote coding needed. This sounds appealing, of course. And for program models it is. But not for architecture models.