Informacje analityczne

• Score: 0-20 / 1 (Poziom 1 — Niedostateczny)

  • Kryteria: Tekst wymagania narusza wiele standardów INCOSE. Brakuje mu struktury, używa strony biernej, zawiera niejasne terminy oraz błędy gramatyczne i interpunkcyjne. Nie wskazuje jasno podmiotu odpowiedzialnego, jest niejednoznaczny lub nie pozwala na podjęcie konkretnych działań.

• Score: 21-40 / 2 (Poziom 2 — Wymaga poprawy)

  • Kryteria: Wymaganie spełnia niektóre standardy, ale zawiera istotne uchybienia. Może mieć częściowo uporządkowaną strukturę, lecz nadal używa strony biernej, zawiera klauzule pozwalające uniknąć jego spełnienia lub nie określa konkretnych, mierzalnych celów.

• Score: 41-60 / 3 (Poziom 3 — Zadowalający)

  • Kryteria: Wymaganie zasadniczo spełnia standardy, ale zawiera drobne uchybienia. Może mieć w większości uporządkowaną strukturę, lecz zawierać drobne błędy gramatyczne lub nie określać konkretnych jednostek miary.

• Score: 61-80 / 4 (Poziom 4 — Dobry)

  • Kryteria: Wymaganie spełnia większość standardów. Ma poprawną strukturę, używa strony czynnej i określa konkretne, mierzalne cele, ale może zawierać jedno lub dwa drobne uchybienia.

• Score: 81-100 / 5 (Poziom 5 — Doskonały)

  • Kryteria: Wymaganie w pełni spełnia standardy. Ma przejrzystą strukturę, używa strony czynnej, określa konkretne, mierzalne cele, nie zawiera błędów gramatycznych, jest jednoznaczne i pozwala na podjęcie konkretnych działań.

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.