Integration of Two Kinds of Syntax for Requirements Description and Its Future Development

EARS covers the semantic weakness of a requirements syntax called "SLP" developed by us. SLP has only one type of syntax. EARS has five types of syntax. We introduced EARS syntax into SLP and improved SLP description capability. SLP has become able to semantically represent the subject matter properly. On the other hand, by introducing the description notation of SLP into EARS, it has become possible to examine whether the terms are appropriate and whether the sentences are not contradictory. We integrated both as "SLP_EARS". SLP is based on predicate logic. Therefore, the integrated SLP_EARS can be described according to the level of meaning of the object. SLP_EARS can describe both the rough-grain sized requirement and the fine-grain program implementation level. This seems to allow the continuity, i.e. the level of granularity of the various kinds of documents including the program to be de-fined at multiple levels. Why is it sometimes necessary to return to the requirement development phase from a later phase of development? We would like to aim to optimize the development cycle by developing new semantic syntax like EARS and applying such syntax to various fields.