Requirements capture
Typically, requirements are described to a developer by an expert and the developer must translate those requirements into a working system. This inevitably causes problems later down the line as new requirements are added, which requires further testing and can make it difficult to record all the requirements, particularly on a complex project.The Erudine approach is to turn requirements capture on its head and carry it out as the system is developed. The expert enters requirements into the system directly, allowing requirements to be refined seamlessly at any point during development. The system is operational from the first moment behaviour is added, learning its functionality and testing it against requirements as soon as it is committed. The system rapidly learns to handle almost all of the simple requirements and behaviour.
The behaviour of a system is held together with all test cases in a single unit, offering much higher accuracy when tracing requirements through to functionality.
Scope creep becomes less of an issue, and the slipping deadlines and increasing costs that come with it. The software captures most of the system requirements at the outset but if new requirements are uncovered they can be added safely and quickly, with any conflicts found and resolved almost immediately.