Software Architecture Due Diligence for an Acquired Product
What will the buyer inherit? Business obligation → inspected evidence → bounded finding → receiving owner → closure evidence Proposed review sequence. An unfilled register is not a completed assessment. Software architecture due diligence for an acquired product should answer whether the buyer can operate, change and recover the product under the ownership arrangement being considered. The useful output is an evidence register tied to business obligations and post-close actions. A diagram of services or a count of outdated packages cannot answer that question on its own. Start with the obligations the acquisition would transfer. Then connect each material concern to an observed artifact, the limits of that observation and a named receiving owner. Keep unanswered questions visible. A missing recovery demonstration is an evidence gap until further inspection establishes a defect; it is not proof that recovery will fail. This guide provides a proposed review method and an unfilled regis...