The concept of “software quality” is often hard to capture for an organization. Quality models aim to make the concept more operational by refining the quality of software-development products and processes into subconcepts to the level of concrete metrics and indicators. In practice, it is difficult for an organization to produce a reliable quality model because quality depends on numerous organizational context factors, and the model, metrics, and indicators must be tailored specifically to the organization. This is a presentation of the Software Product Quality Model, with emphasis on architecture metrics, developed for Ecopetrol and its application and visualization on real software systems of Ecopetrol’s enterprise architecture. The model contains metrics helpful for analyzing the external dependencies and structure of an application based on its modeled relationships to other applications as well as the used and provided interfaces according to the interface integration type. Equally advanced visualization of the models has been created for illustrating the coupling and complexity of the enterprise architecture. The model was rolled out in 2012 and has been helpful for architects to set baselines and monitor evolution toward the organizational IT strategy as they sought to simplify and standardize the IT landscape. The model specially tailored for Ecopetrol offers architects a common language for software quality, increasing model acceptance and improving communication.