If this is a template Press Submit first

Specification Analysis Tool

ReStart SAT

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

Analysis Settings

PUI Mask
Imperatives
Process Only Imperatives

Strip HTML Tags
Show Processed Upload

Report Areas

Analysis Results
Accessed Words
Accessed Patterns
Metrics
Doc Shape
Reading Level

Libraries

Documents
Templates
Demo Reports
Previous Analysis

Help

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


Analysis Results

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

Accessed Words

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.

Filter Noise Words
Noise Patterns: update these patterns as needed

Search None

Number Sort

32: SAT 8: user 6: SAT 6: allow 6: web
6: document 6: rules 5: processing 5: metrics 4: using
4: rule 3: portal 3: versions 3: standard 3: include
3: files 2: same 2: service 2: packaged 2: multiple
2: Specification 2: offer 2: demonstration 2: process 2: browser
2: Criteria 2: uploaded 2: industry 2: across 2: findings
2: implemented 1: client 1: possibly 1: input 1: re-run
1: used 1: Comment 1: needed 1: Excel 1: user-uploaded
1: Hill 1: actions 1: Name 1: individually 1: Option
1: product 1: save 1: context 1: inputs 1: General
1: gather 1: sets 1: data 1: techniques 1: HTML-CGI
1: CGI 1: following 1: corrective 1: solution 1: exports
1: documents 1: specifications 1: Reject 1: services 1: minimize
1: Case 1: new 1: material 1: Delimited 1: Functions
1: different 1: server 1: Metrics 1: derived 1: system
1: accept 1: disabled 1: paragraph 1: PERL 1: prior
1: modify 1: internet 1: established 1: Shipping 1: defined
1: offered 1: Web 1: shown 1: DOORS 1: server
1: disable 1: training 1: reported 1: execute 1: Inc
1: automatically 1: Contents 1: format 1: requirement 1: Introduction
1: sample 1: scripting 1: Documents 1: Quality 1: Rule
1: descriptions 1: Portal 1: time 1: Color 1: Cassbeth
1: document-processing 1: Access 1: Requirement 1: URL 1:
1: expected 1: fields 1: pre-loaded 1: function 1: directory
1: analysis 1: shipped 1: results 1: web 1: generic
1: customer 1: downloadable 1: Tab 1: Analysis 1: run
1: Architecture 1: Reporting 1: APACHE 1: Notes 1: various
1: Figure 1: create 1: control 1: These 1: Processing
1: Tool 1: packaging 1: NJ 1: based 1: development
1: Requirements 1: Table 1: shown 1: TBD 1: Prepared
1: Reference 1: text 1: IndigoPerl 1: structure 1: unique
1: JAVA 1: enabled 1: Table 1: Cherry 1: Sensitivity
1: accessed 1: July 1: industries 1: can 1: enable
1: stages 1: original

Accessed Unique Words: 167

Alpha Sort

1: 1: CGI 1: DOORS 1: Delimited 1: Excel
1: HTML-CGI 1: JAVA 1: PERL 32: SAT 1: Tab
1: Table 1: These 1: URL 1: accept 1: accessed
2: across 1: actions 6: allow 1: analysis 1: automatically
1: based 2: browser 1: can 1: client 1: context
1: control 1: corrective 1: create 1: customer 1: data
1: defined 2: demonstration 1: derived 1: descriptions 1: development
1: different 1: disable 1: disabled 1: document-processing 6: document
1: documents 1: downloadable 1: enable 1: enabled 1: established
1: execute 1: expected 1: exports 1: fields 3: files
2: findings 1: following 1: format 1: function 1: gather
1: generic 2: implemented 3: include 1: individually 2: industry
1: input 1: inputs 1: internet 5: metrics 1: minimize
1: modify 2: multiple 1: needed 1: new 2: offer
1: offered 1: original 1: packaging 1: paragraph 3: portal
1: pre-loaded 1: prior 2: process 5: processing 1: product
1: re-run 1: reported 1: requirement 1: results 4: rule
6: rules 1: run 2: same 1: sample 1: save
1: scripting 1: server 2: service 1: services 1: sets
1: shown 1: solution 1: specifications 1: stages 3: standard
1: system 1: techniques 1: text 1: time 1: unique
2: uploaded 1: user-uploaded 8: user 4: using 1: various
3: versions 6: web 1: APACHE 1: Access 1: Analysis
1: Architecture 1: Case 1: Cassbeth 1: Cherry 1: Color
1: Comment 1: Contents 2: Criteria 1: Documents 1: Figure
1: Functions 1: General 1: Hill 1: Inc 1: IndigoPerl
1: Introduction 1: July 1: Metrics 1: NJ 1: Name
1: Notes 1: Option 1: Portal 1: Prepared 1: Processing
1: Quality 1: Reference 1: Reject 1: Reporting 1: Requirement
1: Requirements 1: Rule 6: SAT 1: Sensitivity 1: Shipping
2: Specification 1: TBD 1: Table 1: Tool 1: Web
1: directory 1: industries 1: material 2: packaged 1: possibly
1: server 1: shipped 1: shown 1: structure 1: training
1: used 1: web

Accessed Unique Words: 167


Accessed Patterns Found

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.

Number Sort

9rule 7web 2browser 2CGI 1train 1HTML
1Function 1function 1Web 1internet 1Architecture 1system
1training 1data 1Rule

Alpha Sort

1HTML 2browser 1system 2CGI 1Rule 1Web
1internet 9rule 7web 1train 1training 1data
1Architecture 1Function 1function

Accessed Patterns Not Found

shall.not \bwill\b may
might could should possible \ball\b \bany\b
\band\b \bor\b \d\.(\d\.)+ shall: ^\s*\w+\. \btable\b
\bfigure\bnnoonnee^\d\s+ ^\d\.0\s+ ^\d\.[123456789]\s+ ^\d\.\d\.\d\s+ ^\d\.\d\.\d\.\d\s+ ^\d\.\d\.\d\.\d\.\d\s+
^\d\.\d\.\d\.\d\.\d\.\d\s+3.1 Web Portal 3.2 Architecture 3.3 General Functions 3.4 Requirement Reporting 3.5 Rule Processing 3.6 Metricsshall
.*login log in logoff log off logon logout
admin[^\s]* encrypt.* decrypt.* mine.* database hmi
windows motiffunction capability capable performance response time
distributed central hybrid flexible growth flexibility
safety safe fail\s*safe fail\s*over recovery? software
hardware electrical environment power temperature humidity
salt fog shock vibration mechanical enclosure facility
faclities room maintenance maintainability support logistics
ils reliability maintainability availability EMI EMC
TEMPEST UL Ergonomics HMI MMI Machine Interface
ATCRBS Beacon Primary Secondary Mode-S track
velocity vector history mosaic flight plan fix posting
conflict alert MSAW minimum safe altitude warning flight plan probe clearance delivery security
secure log\s*on log\s*off log\sin log\s*out restricted area
track pairing ADIZ plot maps? range scale off\s*set


Metrics

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.

Lines: 60
Imperatives: 31
Shalls: 31
Wills: 1
IsReq:

Item Count Children % lines % imperative % shall % will % isreq
1. Functional kra

2

3.33

6.45

6.45

1. Level 1 Req gsa

5

8.33

16.12

16.12

11. Training kra

1

1.66

3.22

3.22

100

3. Systems kra

1

1.66

3.22

3.22

100

4. Architecture kra

1

1.66

3.22

3.22

100

6. Software kra

1

1.66

3.22

3.22

100

Compound Req

2

3.33

6.45

6.45

Directive

3

5

9.67

9.67

Fragment

13

21.66

41.93

41.93

Internal Reference

1

1.66

3.22

3.22

100

Mining dca

20

33.33

64.51

64.51

Non Shalls gca

29

48.33

93.54

93.54

Shalls gca

31

51.66

100

100

Unsure

1

1.66

3.22

3.22

100

Untestable

1

1.66

3.22

3.22

100

User Interface dca

3

5

9.67

9.67

Vague 1

3

5

9.67

9.67

Vague 3

1

1.66

3.22

3.22

100

Vague 4

1

1.66

3.22

3.22

100

z Mined Objects

36

60

Reading Level

Disabling the noise filter may reduce the reading level. Re-run the report to capture metrics for both instances.

Accessed Unique Words: 167
Accessed Unique Syllables: 384
Words with 3+ Syllables: 64
Polysyllabic Count: 32
Reading Level: 9

Document Shape

The number of children at a particular level translate to a document shape. There are diffrent document shapes and each have implications. The document shapes are: random, rectangle, pyramid, inverted pyramid, trapazoid and diamond.

There are no child counts. Try disabling all services except for: Generic Structure Analysis.

original processing URL http://localhost:4444/~sat/satpro.cgi