imported>Daask: Replace Attempto Controlled English in see also with the class to which it belongs Controlled natural language

2024-01-18T20:53:56Z

Replace Attempto Controlled English in see also with the class to which it belongs Controlled natural language

New page

'''Structured English''' is the use of the [[English language]] with the [[programming language syntax|syntax]] of [[structured programming]] to communicate the design of a computer program to non-technical users by breaking it down into logical steps using straightforward English words. Structured English gives aims to get the benefits of both the programming logic and natural language: program logic helps to attain precision, whilst natural language helps with the familiarity of the spoken word.<ref>"[http://www.wisegeek.com/what-is-structured-english.htm#didyouknowout "What is Structured English"], Wisegeek.com, retrieved 23 April 2014</ref>

It is the basis of some programming languages such as SQL (Structured Query Language) "for use by people who have need for interaction with a large database but who are not trained programmers".<ref>[http://cis.csuohio.edu/~matos/notes/cis-611/Papers/Implementation%20of%20a%20structured%20English%20query%20language-astrahan.pdf "Implementation of a Structured English Query Language"] M.M. Astrahan and D.D. Chamberlain, IBM Research Division, San Jose, ACM, May 1975 (retrieved from Cleveland State University website, April 2014)</ref>

== Elements ==
'''[https://dailyvocabshay.blogspot.com/2022/12/advanced-english-structure-pdf.html Advanced English Structure]''' is a limited-form "[[pseudocode]]" and consists of the following elements:
#Operation statements written as English phrases executed from the top down
#Conditional blocks indicated by keywords such as IF, THEN, and ELSE
#Repetition blocks indicated by keywords such as DO, WHILE, and UNTIL

The following guidelines are used when writing Structured English:<ref>[http://it.toolbox.com/blogs/enterprise-solutions/guidelines-for-structured-english-in-documenting-specifications-15987 "Guidelines for Structured English in Documenting Specifications"], Craig Borysowich, IT Toolbox, 29 April 2007</ref>
#All logic should be expressed in operational, conditional, and repetition blocks
#Statements should be clear and unambiguous
#Logical blocks should be indented to show relationship and hierarchy
#Use one line per logical element, or indent the continuation line
#Keywords should be capitalized
#Group blocks of statements together, with a capitalized name that describes their function and end with an EXIT.
#Underline words or phrases defined in a data dictionary.
#Mark comment lines with an asterisk

== Example of Structured English ==
APPROVE LOAN
IF customer has a Bank Account THEN
IF Customer has no dues from previous account THEN
Allow loan facility
ELSE
IF Management Approval is obtained THEN
Allow loan facility
ELSE
Reject
ENDIF
ENDIF
ELSE
Reject
ENDIF
EXIT

==Criticism==
Though useful for planning programs, modules and routines, or describing algorithms it is less useful when numerous decisions need to be made.<ref>[http://www.hit.ac.il/staff/leonidM/information-systems/ch60.html#Heading3 "Ch. 60 Structured English, Strengths and Weaknesses"], The Information Systems: Analysis and Design, Meyzin Leonid, Holon Institute of Technology, retrieved 23 April 2014</ref>

=== Other specification tools ===
System processes at a lower level involve lot of computations and require more precision and clarity. This can be achieved with tools such as [[decision tree]]s or [[decision table]]s.

==See also==
*[[Natural language programming]]
*[[Self-documenting code]]
*[[Structured programming]]
*[[Pseudocode]]
*[[Decision tree]]
*[[Decision table]]
*[[Controlled natural language]]

==References==
{{Reflist}}

[[Category:Structured English| ]]
[[Category:Algorithm description languages]]

Structured English - Revision history

imported>Daask: Replace Attempto Controlled English in see also with the class to which it belongs Controlled natural language