洞察

• Score: 0-20 / 1（第 1 级 - 不合格）

  • 标准：需求文本违反多项 INCOSE 标准。缺乏结构，使用被动语态，包含含糊的术语，且语法和标点使用不当。未明确责任主体，或表述有歧义，或不具备可执行性。

• Score: 21-40 / 2（第 2 级 - 需要改进）

  • 标准：需求遵循部分标准，但存在明显问题。可能具备一定结构，但仍使用被动语态、包含免责条款，或缺乏具体、可衡量的目标。

• Score: 41-60 / 3（第 3 级 - 合格）

  • 标准：需求总体遵循标准，但存在一些小问题。可能基本具备完整结构，但包含轻微的语法错误，或缺少明确的计量单位。

• Score: 61-80 / 4（第 4 级 - 良好）

  • 标准：需求符合大多数标准。结构清晰，使用主动语态，目标具体且可衡量，但可能存在一两个小问题。

• Score: 81-100 / 5（第 5 级 - 优秀）

  • 标准：需求完全符合标准。结构清晰，使用主动语态，目标具体且可衡量，无语法错误，表述无歧义且具备可执行性。

R1 - Use a structured, complete sentence: subject, verb, object. 
R2 - Use the active voice in the main sentence structure of the need or requirement statement with the responsible entity clearly identified as the subject of the sentence. 
R3 - Ensure the subject and verb of the need or requirement statement are appropriate to the entity to which the need or requirement refers. 
R5 - Use definite article “the” rather than the indefinite article “a”.
R6 - Use appropriate units when stating quantities. All numbers should have units of measure explicitly stated.
R7 - Avoid the use of vague terms such as “some”, “any”, “allowable”, “several”, “many”, “a lot of”, “a few”, “almost always”, “very nearly”, “nearly”, “about”, “close to”, “almost”, and “approximate”. 
R8 - Avoid escape clauses such as “so far as is possible”, “as little as possible”, “where possible”, “as much as possible”, “if it should prove necessary”, “if necessary”, “to the extent necessary”, “as appropriate”, “as required”, “to the extent practical”, and “if practicable”. 
R9- Avoid open-ended clauses such as “including but not limited to”, “etc.” and “and so on”. 
R10 - Avoid superfluous infinitives such as “be designed to”, “be able to”, “be capable of”.  
R12, 13, 14 - Use correct grammar, spelling, punctuation.
R15 - Use a defined convention to express logical expressions such as “[X AND Y]”, “[X OR Y]”, [X XOR Y]”, “NOT[X OR Y]”.
R16 - Avoid the use of “not” 
R17 - Avoid the use of the oblique ("/") symbol except in units, i.e. km/hr
R18 - Write a single sentence that contains a single thought conditioned and qualified by relevant sub-clauses.
R19 - Avoid combinators that join clauses, such as “and”, “or”, ”then”, ”unless”, ”but”, ”as well as”, ”but also”, ”however”, ”whether”, ”meanwhile”, ”whereas”, ”on the other hand”, or ”otherwise”. 
R20 - Avoid phrases that indicate the purpose of the need or requirement. 
R21 - Avoid parentheses and brackets containing subordinate text.
R22 - Enumerate sets explicitly instead of using a group noun to name the set. 
R24 - Avoid the use of pronouns and indefinite pronouns.
R26 - Avoid using unachievable absolutes such as 100'%' reliability, 100'%' availability, all, every, always, never, etc.
R28 - Express the propositional nature of a condition explicitly for a single action instead of giving lists of actions for a specific condition.
R29 - Classify the needs and requirements according to the aspects of the problem or system it addresses. 
R31 - When defining design inputs avoid stating a solution unless there is rationale for constraining the design. Focus on the problem “what” rather than the solution “how”. 
R32 - Use “each” instead of “all”, “any" or “both” when universal quantification is intended. 
R33 - Define quantities with a range of values appropriate to the entity to which they apply and to which the entity will be verified or validated against.
R34 - Provide specific measurable performance targets appropriate to the entity to which the need or requirement is stated and against which the entity will be verified to meet.
R35 - Define temporal dependencies explicitly instead of using indefinite temporal keywords such as “eventually”, “until”, “before”, “after”, “as”, “once”, “earliest”, “latest”, “instantaneous”, “simultaneous”, “at last”.
R38 - Avoid the use of abbreviations.