2. The process of claim 1 , wherein the locating step comprises determining that the runtime determination boundary fits within at least one of the following categories: client-server boundaries; machine-machine boundaries; database-querying_program boundaries; web_service_provider-web_service_consumer boundaries; factory_caller-factory_instance boundaries; interface_call-implementing_class boundaries; inter-process communication boundaries.
1. A process which correlates software architecture diagrams using runtime generated data, the process utilizing in a device a memory in operable communication with at least one logical processor, the process comprising the steps of: locating a runtime determination boundary in a software architecture which is not a reflection boundary, the software architecture represented at least partially by at least one software architecture diagram; obtaining runtime information for at least one execution of an instance of the software architecture without using reflection to obtain said runtime information; correlating at least a portion of the runtime information with the at least one software architecture diagram, thereby producing an enhanced architecture diagram which documents an execution history across the runtime determination boundary, namely, an enhanced architecture diagram which spans at least two components by spanning at least one component of the software architecture on each side of the runtime determination boundary; and attaching metadata to a data source, and propagating the metadata across the runtime determination boundary.