인사이트

• 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.