Many people prefer to write requirements in Markdown. One reason is the seamless integration into GitHub. It just renders nicely there. Markdown also has a lower entry barrier for most software developers, compared to the TRLC language (in version 3.3 of the LRM).
For that reason we propose a feature to parse markdown, and interpret that as TRLC record types. Obviously this means that the markdown file has to follow a clear structure.
Many people prefer to write requirements in Markdown. One reason is the seamless integration into GitHub. It just renders nicely there. Markdown also has a lower entry barrier for most software developers, compared to the TRLC language (in version 3.3 of the LRM).
For that reason we propose a feature to parse markdown, and interpret that as TRLC record types. Obviously this means that the markdown file has to follow a clear structure.