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 . . . Vague Subjective Choice or Option Implicit Expressions Weakness Under Specification Multiplicity Service DescriptionThis service has been changed to reflect a set of rules, as interpreted by SAT staff, from a CMISEI presentation given at Incose Local Chapter meeting in 2005.
Rule 1 Name Color Norm Metric Case Sensitive Access Object Reject Object There are some false alarms. In instances where the req is vague, make the commitment. Comment
Rule 2 Name Color Norm Metric Case Sensitive Access Object Reject Object This is unexplored context. You must commit to your reqs and move anything that is optional to studies. Comment
Rule 3 Name Color Norm Metric Case Sensitive Access Object Reject Object You must commit to your reqs and move anything that is vague to studies. Comment
Rule 4 Name Color Norm Metric Case Sensitive Access Object Reject Object Req Comment
Rule 5 Name Color Norm Metric Case Sensitive Access Object Reject Object This is a form of under specification. It suggests a need for a choice function or future req. Make the commitment. Comment
Rule 6 Name Color Norm Metric Case Sensitive Access Object Reject Object Many words need a second noun to make the use specific. This is typically a hyphenated qualifier (e.g. SAT-Report). Comment
Rule 7 Name Color Norm Metric Case Sensitive Access Object Reject Object Multiple req claims are open to missing or poor tests. Split compound reqs into single stand alone reqs. Comment
New Requirement Text Analysis Rule 8 Name Color Norm Metric Case Sensitive Access Object Reject Object Comment
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 service has been changed to reflect a set of rules, as interpreted by SAT staff, from a CMISEI presentation given at Incose Local Chapter meeting in 2005.
1. SAT-30 SAT could possibly be used in other industries. . . . Choice or Option: Requirement Text Analysis possibly 1 You must commit to your reqs and move anything that is vague to studies. . . . Weakness: Requirement Text Analysis could 1 This is a form of under specification. It suggests a need for a choice function or future req. Make the commitment.
2. SAT-35 SAT shall be implemented using standard HTML-CGI techniques and minimize the use JAVA scripting. . . . Multiplicity: 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-36 3.3 General Functions . . . Under Specification: Requirement Text Analysis Functions 1 Many words need a second noun to make the use specific. This is typically a hyphenated qualifier (e.g. SAT-Report).
4. SAT-44 SAT shall allow the user to individually enable or disable each rule prior to document processing. . . . Multiplicity: Requirement Text Analysis or 1 Multiple req claims are open to missing or poor tests. Split compound reqs into single stand alone reqs.
5. SAT-45 SAT shall only report the results of rule processing for enabled rules. . . . Under Specification: Requirement Text Analysis report 1 Many words need a second noun to make the use specific. This is typically a hyphenated qualifier (e.g. SAT-Report).
6. SAT-49 SAT shall consist of multiple rule sets that can be accessed by a user. . . . Implicit Expressions: Requirement Text Analysis that 1 Req . . . Weakness: Requirement Text Analysis can 1 This is a form of under specification. It suggests a need for a choice function or future req. Make the commitment.
7. SAT-57 4. Access Criteria . . . Under Specification: Requirement Text Analysis Access 1 Many words need a second noun to make the use specific. This is typically a hyphenated qualifier (e.g. SAT-Report).
8. SAT-67 SAT metrics shall be based on the function in paragraph 3.3. . . . Under Specification: Requirement Text Analysis function 1 Many words need a second noun to make the use specific. This is typically a hyphenated qualifier (e.g. SAT-Report).
9. SAT-70 SAT may be packaged with the APACHE web server. . . . Weakness: Requirement Text Analysis may 1 This is a form of under specification. It suggests a need for a choice function or future req. Make the commitment.
No results to report.
Lines: 60Imperatives: 31Shalls: 31Wills: 1IsReq:
1
1.66
3.22
100
2
3.33
6.45
4
6.66
12.9
3
5
9.67
9
15
29.03
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