Prior to uploading your file, set your report options. Also check the rules and modify them as desired.
File to upload
New 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 Incomplete Find Duplicate Objects rptdup Generic Structure Analysis gsa Domain Structure Analysis dsa Generic Capabilities Analysis gca Domain Capabilities Analysis dca Key Reqs Analysis kra Other Domains or Industries - Constitutions odic
Add New Sevice Name Remove Last Sevice: Other Domains or Industries - Constitutions
Requirement Text Analysis: This looks for word and phrase patterns that typically result in less than optimal reqs. In the past these rules have been encoded in check lists or kept in senior staff heads. Most organizations have different takes on these rules and they tend to change with time. This is a basic service but critical if the project expects to succeed. This should be the starting point of all your analysis.
1. 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. . . . Vague 2: Requirement Text Analysis possibly 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. SAT-65 SAT metrics shall not be disabled at any time. . . . 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.
11. 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.
12. SAT-67 SAT metrics shall be based on the function in paragraph 3.3. . . . Internal Reference: Requirement Text Analysis paragraph 3 1 Round and round we go where we stop no one knows. This leads to confusion and a break down of understanding.
13. 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.
14. 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.
15. SAT-72 The directory structure of SAT is shown in Figure TBD. . . . Directive: Requirement Text Analysis Figure 1 Reqs that are in a table or figure are not standalone. Some communities beleave that tables and figures add understandability to a spec. However, in proof like settings of certification, they lead to missed tests and misinterpretation of contents. Figures and tables should be moved to design documents. . . . Incomplete: Requirement Text Analysis TBD 1 Incomplete specifications vary in severity. This is the worst case of incompleteness. Once the TBDs are gone more sophistocated techniques are needed to address this area. The other SAT services can help in this area along with SRDB parent child reports.
16. SAT-73 The versions of SAT shall be as shown in Table 4. . . . Directive: Requirement Text Analysis Table 1 Reqs that are in a table or figure are not standalone. Some communities beleave that tables and figures add understandability to a spec. However, in proof like settings of certification, they lead to missed tests and misinterpretation of contents. Figures and tables should be moved to design documents.
17. SAT-74 SAT shall be downloadable ?? from the internet. . . . Incomplete: Requirement Text Analysis ?? 1 Incomplete specifications vary in severity. This is the worst case of incompleteness. Once the TBDs are gone more sophistocated techniques are needed to address this area. The other SAT services can help in this area along with SRDB parent child reports.
18. 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.
No results to report.
Lines: 60Imperatives: 31Shalls: 31Wills: 1IsReq:
2
3.33
6.45
6
10
19.35
1
1.66
3.22
100
3
5
9.67
18
30
58.06
Accessed Unique Words: Accessed Unique Syllables: Words with 3+ Syllables: Polysyllabic Count: 0 Reading Level: Select any rule option: Count Accessed Words or select: Generic Capabilites Analysis service.
There are no child counts. Try disabling all services except for: Generic Structure Analysis.
original processing URL http://localhost:4444/~sat/satpro.cgi