4 ;;Quote: specifications specify the system and its attributes; e.g., functions, data elements, interfaces, security, performance, packaging

15 ;;Quote: describing software requires more than a word processor; e.g., software literature uses graphics, tables, fonts

23 ;;Quote: can base software languages on natural language with restricted syntax and semantics, e.g., COBOL; easy to learn and use; not good for complex structures

27 ;;Quote: can base software languages on operators and operands in a database and data dictionary, e.g., some report generators; great potential

35 ;;Quote: can base software languages on 2-d text, e.g., decision tables; excellent for organizing information but difficult to read and use

37 ;;Quote: can base software languages on diagrams with text, e.g., flowcharts; useful for humans but difficult to process

39 ;;Quote: can base software languages on graphics derived from text, e.g., structured diagrams; most powerful category for humans and processing

45 ;;Quote: can base software languages on graphical representation of actual components; widely used in other fields, e.g., circuit diagrams

48 ;;Quote: text, graphics and tables are all needed for software