Challenge, approach, and impact

• Existing code base

  The customer initially developed a Proof of Concept (PoC) for this system independently, but it suffered from poor code quality. The system's design lacked scalability, and any attempts to upgrade it required significant effort, often resulting in additional issues.

• Lack of requirements

  The customer had a clear high-level vision for the project, but there were numerous unresolved issues beneath the surface.

• Deadlines

  Automating the requirements management process was critical for the customer to meet the ambitious deadlines of their vehicle program. Without the successful delivery of this system, they would face additional manual work, for which they lacked the necessary capacity. Therefore, delays would be inevitable, resulting in significant financial loses.