This is true to an extent. At the extremities, a software system can be audited without any previous domain exposure: architecture, and implementation means (la

This is true to an extent. At the extremities, a software system can be audited without any previous domain exposure: architecture, and implementation means (language, deployment, etc.) It can be difficult to critique choices, specially in system architecture, when domain requirements are presented or falsely asserted as 'dictating the choice', but this can be addressed by directing conversations with stakeholders to nail down the conceptual model that has been implemented in architecture style x, and then the conversation is on more equal footing. Auditing language usage, libraries, development process, etc. are much less domain specific.