Language Driven Development 

At AgileAlgo, we strive to provide End User Organisation or System Integrators to code generate through written requirements. We call it Language Driven Development.

All system project starts with requirements, to be exact, a software requirement specification. The requirements describe what the software will do and how it will be expected to perform. That is our start point.

For this platform, we use an Agile style of requirement writing. Requirements are called User Stories. A user story is usually written from the user's perspective and follows the format: “As [a user persona], I want [to perform this action] so that [I can accomplish this goal].”

User stories must be easy for anyone to understand. They also represent bite-sized deliverables that can fit into an overall outcome called an Epic.

In Agile, the quality of the user story can be evaluated through a set of criteria. The acronym INVEST represent the need to be Independent, Negotiable, Valuable, Estimate-able, Small, and Testable. Essentially the user story needs to be implementable. This form the basis of how our platform ingest requirements, interpret them and intelligently match it with the required codes.

It is expected that not all codes are available and we need to over-time build the first set and feed back the system to learn and reuse subsequently.