First thing I want to tell about “StREQ”

StREQ is the name of my personal project which just started one month ago. It’s just a tentative name from the abbreviation of “Structured Requirements”. In systems/software engineering, we are always facing a kind of problem due to unclear and incomplete requirements. I believe that the root cause must be natural languages we all use.

System is logical. System requirements are expected to be logical as well. But unfortunately most requirements are written in a natural language which is not logical at all. So there should be a conversion from illogical to logical with taking some risk of terrible mistakes somewhere in the development. With respect to a format, PDF, Word, Excel with chapters (1-dimensional) or some other relational databases (2-dimensional) might be preferred by stakeholders. But these formats are not enough to manage the structure of logic with multi-dimensional, many-to-many relation.

Through my 10-year career as a system engineer in the automotive industry, one idea has been coming into my head: hey mankind, let’s get free from a chain of ambiguous natural languages and communicate specifically. In order to handle logic in a more specific way, we need a new methodology, a new data structure, a new tool which we can easily understand and control. It’s difficult to imagine Formal methods could be applicable to everyone.

Hopefully, “StREQ” will be an answer. Though its concept is still unclear now, I’m going to post my progress to Medium as much as possible.