Prior to uploading your file, set your report options. Also check the rules and modify them as desired.
File to upload
Previously Uploaded File: C:\z-cassbeth\sat\documents\sat-spec.txt
PUI Mask Imperatives Process Only Imperatives Strip HTML Tags Show Processed Upload
Analysis Results Accessed Words Accessed Patterns Metrics Doc Shape Reading Level
Documents Templates Demo Reports Previous Analysis
Help Regular Expressions Audio Overview (PPT) Audio Demo (PPT)
Services
Requirement Text Analysis rta Show Simple Rules Show Complex Rules . . . Untestable Unsure Vague 1 Vague 2 Vague 3 Vague 4 Compound Req Internal Reference Not Standalone Fragment Directive Find Duplicate Objects rptdup Show Simple Rules Show Complex Rules . . . Duplicates Generic Structure Analysis gsa Show Simple Rules Show Complex Rules . . . 1. Level 1 Req 2. Level 2 Req 3. Level 3 Req 4. Level 4 Req 5. Level 5 Req 6. Level 6 Req Domain Structure Analysis dsa Show Simple Rules Show Complex Rules . . . 3.1 Web Portal 3.2 Architecture 3.3 General Functions 3.4 Req Reporting 3.5 Rule Processing 3.6 Metrics Generic Capabilities Analysis gca Show Simple Rules Show Complex Rules . . . Shalls Non Shalls Domain Capabilities Analysis dca Show Simple Rules Show Complex Rules . . . Security Mining User Interface Key Reqs Analysis kra Show Simple Rules Show Complex Rules . . . 1. Functional 2. Performance 3. Systems 4. Architecture 5. Safety 6. Software 7. Hardware 8. Environmental 9. Mechanical 10. Facilities 11. Training 12. Maintenance 13. Support 14. RMA 15. EMI 16. Ergonomics 17. ATC RDP 18. ATC FDP 19. ATC Automation 20. Security 21. Air Defense Other Domains or Industries - Constitutions odic
Add New Sevice Name Remove Last Sevice: Other Domains or Industries - Constitutions
Processing previously uploaded file
Requirement Text Analysis:
Find Duplicate Objects: shown as duplicates, if the mask pattern is good.
Generic Structure Analysis: This service looks for and counts reqs at particular levels. It works by triggering a count of reqs following an accessed pattern such as paragraph numbers. These are considered children. This is a higher level service that becomes useful when you have a collection of specifications.
Domain Structure Analysis: This service looks for and counts reqs that represent specific capabilities at each level of interest. It should be viewed as a more narrow filter of the Generic Structure Analysis Service. It works by triggering a count of reqs following an accessed pattern such as paragraph number and title. These are considered children. This is a higher level service that becomes useful when you have a collection of specifications.
Generic Capabilities Analysis: This service looks for and counts all word instances in the accessed object. Selecting a word from the list and submitting the report will provide the related text. These word instances can be subjected to an internal noise filter to remove words. The user can also enter word patterns to remove additional noise words. This is a higher level service that relies on human ability to recognize patterns when a word or group of words is provided.
Domain Capabilities Analysis: This service looks for and counts all word or phrase instances set in the access field. Selecting a word from the list and submitting the report will provide the related text. Since these are user defined words there is no reason to enable noise word filters. This is a higher level service that relies on human ability to recognize their capability from a single word or phrase.
Key Reqs Analysis: Key reqs should be methodically sought by asking each stakeholer what they feel are their key reqs. These reqs are cost and or schedule drivers. They can be found by asking:
1. have we done this before 2. has someone else done this before 3. is a new technology, process, or method needed 4. is a new product needed...
This service looks for and counts all word or phrase instances set in the access field. Selecting a word from the list and submitting the report will provide the related text. Since the user defines these words there is no reason to enable noise word filters. This is a very high level service that relies on human ability to recognize their key req from a single word or phrase.
1. SAT-17 Table Of Contents . . . Directive: Requirement Text Analysis Table 1 Reqs that are in a list are not standalone. Some communitiesd beleave that tables and figures add understandability to a spec. However, in proof like settings of certification, thet lead to missed tests and misinterpretation of contents. Figures and tables should be moved to design documents.
2. SAT-22 1 Introduction . . . 1. Level 1 Req: Generic Structure Analysis 1 1
3. SAT-23 2 Reference Documents . . . 1. Level 1 Req: Generic Structure Analysis 2 1
4. SAT-24 3 Requirements . . . 1. Level 1 Req: Generic Structure Analysis 3 1
5. SAT-25 3.1 Web Portal . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
6. SAT-26 A web portal shall be established for the SAT system. . . . 3. Systems: Key Reqs Analysis system 1
7. SAT-30 SAT could possibly be used in other industries. . . . Vague 1: Requirement Text Analysis could 1 There are different levels of vague. This is the worst type of vague. You must commit to your reqs and move anything that is vague to studies.
8. SAT-31 3.2 Architecture . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
9. SAT-31 3.2 Architecture . . . 4. Architecture: Key Reqs Analysis Architecture 1
10. SAT-35 SAT shall be implemented using standard HTML-CGI techniques and minimize the use JAVA scripting. . . . Compound Req: Requirement Text Analysis and 1 Multiple req claims are open to missing or poor tests. Split compound reqs into single stand alone reqs.
11. SAT-36 3.3 General Functions . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
12. SAT-36 3.3 General Functions . . . 1. Functional: Key Reqs Analysis Function 1
13. SAT-41 3.4 Requirement Reporting . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
14. SAT-44 SAT shall allow the user to individually enable or disable each rule prior to document processing. . . . Compound Req: Requirement Text Analysis or 1 Multiple req claims are open to missing or poor tests. Split compound reqs into single stand alone reqs.
15. SAT-46 3.5 Rule Processing . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
16. SAT-54 1. Name . . . Fragment: Requirement Text Analysis 1. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
17. SAT-55 2. Color . . . Fragment: Requirement Text Analysis 2. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
18. SAT-56 3. Case Sensitivity Option . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
19. SAT-57 4. Access Criteria . . . Fragment: Requirement Text Analysis 4. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
20. SAT-58 5. Reject Criteria . . . Fragment: Requirement Text Analysis 5. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
21. SAT-59 6. Comment . . . Fragment: Requirement Text Analysis 6. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
22. SAT-61 3.6 Metrics . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
23. SAT-64 SAT metrics shall be offered only if there is data to report. . . . 6. Software: Key Reqs Analysis data 1
24. SAT-65 SAT metrics shall not be disabled at any time. . . . Untestable: Requirement Text Analysis shall not 1 This is a neg req and as such is untestable. Re-write as a positve statement. . . . Vague 4: Requirement Text Analysis any 1 This is prone to false alarms. There are different levels of vague. This is one of the worst types of vague. You must commit to your reqs and move anything that is vague to studies.
25. SAT-66 SAT will be shipped with training material. . . . Unsure: Requirement Text Analysis will 1 Sounds like you are trying to maintain 2 sets of req books. This is very destructive. Comit to the req and use the SRDB attributes to track req types.
26. SAT-66 SAT will be shipped with training material. . . . 11. Training: Key Reqs Analysis training 1
27. SAT-67 SAT metrics shall be based on the function in paragraph 3.3. . . . Internal Reference: Requirement Text Analysis 3.3. 1 Round and round we go where we stop no one knows. This leads to confusion and a break down of understanding.
28. SAT-67 SAT metrics shall be based on the function in paragraph 3.3. . . . 1. Functional: Key Reqs Analysis function 1
29. SAT-69 3.7 Shipping . . . Fragment: Requirement Text Analysis 3. 1 Reqs that are in a list are not standalone. This leads to confusion and untestable results. The only time list reqs are permitted if the list is sequence dependent. This typically occurs when algorithms are described using English rather than formal methods.
30. SAT-70 SAT may be packaged with the APACHE web server. . . . Vague 1: Requirement Text Analysis may 1 There are different levels of vague. This is the worst type of vague. You must commit to your reqs and move anything that is vague to studies.
31. SAT-71 SAT might be packaged with IndigoPerl. . . . Vague 1: Requirement Text Analysis might 1 There are different levels of vague. This is the worst type of vague. You must commit to your reqs and move anything that is vague to studies.
32. SAT-72 The directory structure of SAT is shown in Figure TBD. . . . Directive: Requirement Text Analysis Figure 1 Reqs that are in a list are not standalone. Some communitiesd beleave that tables and figures add understandability to a spec. However, in proof like settings of certification, thet lead to missed tests and misinterpretation of contents. Figures and tables should be moved to design documents.
33. SAT-73 The versions of SAT shall be as shown in Table 4. . . . Directive: Requirement Text Analysis Table 1 Reqs that are in a list are not standalone. Some communitiesd beleave that tables and figures add understandability to a spec. However, in proof like settings of certification, thet lead to missed tests and misinterpretation of contents. Figures and tables should be moved to design documents.
34. SAT-75 SAT shall include all needed packaging. . . . Vague 3: Requirement Text Analysis all 1 This is prone to false alarms. There are different levels of vague. This is one of the worst types of vague. You must commit to your reqs and move anything that is vague to studies.
35. SAT-77 4 Quality . . . 1. Level 1 Req: Generic Structure Analysis 4 1
36. SAT-78 5 Notes . . . 1. Level 1 Req: Generic Structure Analysis 5 1
Filter Noise Words Noise Patterns: update these patterns as needed . | \d+ | the | of | a | in | by | as | was | it | this | that | as | there | their | on | was | then | it | for | were | was | which | such | and | to | be | or | with | all | each | into | from | if | an | upon | shall | will | should | could | might | may | more | at | they | them | other | against | have | so | having | any | make | chosen | had | every | report | directed | provide | meet | not | how | would | place | promptly | like | been | take | but | order | already | who | done | when | over | taken | after | be | put | except | exception | particular | no | those | day | become | ourselves | form | consist | appear | our | use | providing | under | whole | do | than | most | nothing | proceed | only | cannot | some | is | are | has | does | it.?
Search None
Accessed Unique Words: 167
Lines: 60Imperatives: 31Shalls: 31Wills: 1IsReq:
2
3.33
6.45
5
8.33
16.12
1
1.66
3.22
100
3
9.67
13
21.66
41.93
20
33.33
64.51
29
48.33
93.54
31
51.66
36
60
Accessed Unique Words: 167 Accessed Unique Syllables: 384 Words with 3+ Syllables: 64 Polysyllabic Count: 32 Reading Level: 9
There are no child counts. Try disabling all services except for: Generic Structure Analysis.
original processing URL http://localhost:4444/~sat/satpro.cgi