354:
346:
25:
131:, it is not secondary. Secondary notation is often not a part of the formal notation itself. Rather, it is a method of organizing the formal notation to allow it to be more easily understood. Thus, secondary notation does not change the actual meaning of the formal notation, rather it allows for the meaning to be readily understood. In text such as
412:
The examples on the right show how these techniques can drastically affect the ease of understanding when looking at a process model. The model depicts a simplified process for ordering products from a website. Both diagrams contain exactly the same blocks with the same interconnections. However, the
455:
programming language requires source code to follow strict indentation rules. This is intended to improve readability of the code, by ensuring that statements that are at the same level of nesting within a block are aligned to the same column. Other types of secondary notation, however, are not part
434:
There are also differences based on level of experience/expertise when creating documents that utilize secondary notation. Experts tend to be more consistent in their use of conventions while novices tend to vary between conventions, sometimes adhering on a surface level, but failing to convey the
430:
The ability of individuals to understand and use secondary notation has been shown to vary based on experience within the relevant field. Experts in a field are generally more able to utilize the clues provided by secondary notation. Specifically, while reading diagrams, experts have been shown to
421:
While inadequate use of secondary notation can significantly increase the amount of effort necessary to understand a model, misuse of secondary notation can also be a detriment. Use of symmetry can make a graphic more visually appealing, but can also convey misconceptions if used incorrectly. For
431:
have more skill at reading the larger structure of the diagram and using it to guide their examination of the details provided by the formal notation. This compares to novices who often focus on the details of the formal notation, ignoring the hints provided by the secondary notation.
443:
In some cases, secondary notation is part of the formal notation. Such formal notations attempt to improve readability by enforcing the presence of visual cues. The trade-off is that, what in many other cases is only secondary notation (like, for example, indentation in
435:
desired information. In the case of circuit diagrams, this is illustrated by common novice mistakes such as creating visual symmetry where there is no logical symmetry and frequent transitions between differing secondary notation conventions.
422:
instance, placing unrelated items close together may cause a reader to perceive them as being related. Additionally, arbitrary use of coloring may distract a reader as they wonder about the meanings of the various colors.
276:
to separate items on a shopping list that must be bought at different stores. Indented items all must be bought at the store within which the items are nested.
562:
also uses indentation as part of the formal syntax of the language. Indentation is required in
Markdown when creating certain source code representations of
123:
Secondary notation provides redundant (more than necessary) information; if the visual cues are the only way that some information is provided, such as in
369:. Research has shown that there are a number of layout factors unincorporated into the formal notation that impact a flowchart's ease of understanding:
337:
Secondary notation is commonly used in graphical contexts to better convey information beyond what the formal notation of the graphic makes explicit.
456:
of the formal notation. For example, when wrapping long lines, every line that is a continuation of a previous line can be indented arbitrarily.
413:
one that uses better secondary notation can be readily understood whereas the other model requires careful analysis to understand its contents.
151:
Secondary notation annotates formal notation in a number of contexts which can be broken down to two main domains: text and graphics.
801:
685:
Green, T. R. G.; Petre, M. (1996). "Usability analysis of visual programming environments: A 'cognitive dimensions' framework".
756:
811:
176:
257:
68:
46:
715:
159:
There are a number of common instances of secondary notation that are seen in text. Secondary notation is common in
143:. In formal graphical notations, this can be done through the use of symmetry or proximity to indicate relatedness.
39:
721:
Marian Petre, M. Petre. Cognitive dimensions 'beyond the notation'. J. Vis. Lang. Comput., 17(4):292-301, 2006.
816:
452:
361:
A graphical representation that has been well studied and can be heavily impacted by secondary notation is a
357:
This is a poorly drawn model of the steps a user would take to place an order for some products on a website.
349:
This is a well drawn model of the steps a user would take to place an order for some products on a website.
353:
273:
784:
725:
180:
33:
743:. Lecture Notes in Business Information Processing. Vol. 39. SpringerLink. pp. 161–175.
179:
to make source code more readable and make the formal notation more understandable. The following
345:
50:
608:
578:
252:
A number of examples of secondary notation that commonly appear in
English writing include
132:
8:
583:
93:
569:#Heading 1# #Indented Markdown source code that will be rendered as source code#
772:
702:
445:
175:
Secondary notation in the form of coloring and indentation is commonly implemented in
806:
752:
657:
376:
the number of times lines cross should be kept to a minimum to ease traceability. In
706:
566:
as well as when creating sections of source code to be rendered as the code itself.
744:
694:
192:
183:
does not use secondary notation to ease the interpretation of the formal notation:
748:
733:
588:
563:
105:
89:
128:
117:
795:
732:
Schrepfer, Matthias; Wolf, Johannes; Mendling, Jan; Reijers, Hajo A. (2009).
716:
Why looking isn't always seeing: readership skills and graphical programming.
124:
632:
698:
136:
265:
164:
97:
85:
269:
which is another method of applying emphasis on a certain area of text.
160:
140:
101:
362:
170:
109:
559:
187:
int main(){while(true){printf("I'm stuck in an infinite loop!");}}
734:"The Impact of Secondary Notation on Process Model Understanding"
448:), is now part of the formal notation, and thus is not optional.
387:
386:
additional bends add to the visual complexity of the model. In
377:
366:
731:
724:
Rule, Revisiting Landin’S. Offside, and
Michael D. Adams. "
402:
textual labels are easier to read when aligned horizontally
247:
195:. As a result, the formal notation of C is easier to read:
113:
16:
Visual cues improving the readability of a formal notation
191:
The following is the same code, but with indentation and
167:
appearing as boldness, italics, and spacing/indentation.
261:
which is used to put emphasis on a certain area of text.
116:, or the regular typographic conventions often found in
726:
Principled
Parsing for Indentation-Sensitive Languages
408:
group related items together to be easily recognizable
120:
to highlight sections with the same type of content.
171:Textual secondary notation in computer source code
793:
684:
233:"I'm stuck in an infinite loop!"
438:
396:position elements symmetrically when possible
92:. Examples of secondary notation include the
380:all the arc (line) crossings are forbidden.
687:Journal of Visual Languages & Computing
69:Learn how and when to remove this message
352:
344:
248:Textual secondary notation in typography
146:
32:This article includes a list of general
272:The following example effectively uses
794:
655:
633:"PEP 8 -- Style Guide for Python Code"
425:
135:, this can be done using cues such as
88:used to improve the readability of a
545:"these words are indented"
332:
18:
741:The Practice of Enterprise Modeling
177:integrated development environments
13:
551:"for better readability"
506:"This is always printed"
154:
38:it lacks sufficient corresponding
14:
828:
609:"Python: Myths about Indentation"
390:all the line bends are minimized.
23:
718:Commun. ACM, 38(6):33-44, 1995.
649:
625:
601:
1:
678:
340:
749:10.1007/978-3-642-05352-8_13
284:Allison's Frozen Foods
7:
656:Gruber, John (2015-04-19).
572:
10:
833:
802:Human–computer interaction
439:As part of formal notation
400:Align labels horizontally:
812:User interface techniques
416:
594:
458:
279:
197:
104:for easy recognition of
521:"Hello world"
374:Minimize arc crossings:
312:2 boxes of fruit juice
53:more precise citations.
699:10.1006/jvlc.1996.0009
358:
350:
320:Jim's Formal Wear
304:Sarah's Groceries
356:
348:
147:In different contexts
133:programming languages
817:Text editor features
579:Cognitive dimensions
494:"x is odd"
384:Minimize line bends:
584:Syntax highlighting
446:free-form languages
426:Experts vs. novices
193:syntax highlighting
94:syntax highlighting
482:"x is 1"
394:Leverage symmetry:
359:
351:
308:3 boxes of cereal
300:2lb of hamburgers
82:Secondary notation
758:978-3-642-05351-1
658:"Markdown Syntax"
512:# this is illegal
451:For example, the
333:Graphical context
79:
78:
71:
824:
788:
782:
778:
776:
768:
766:
765:
738:
710:
672:
671:
669:
668:
653:
647:
646:
644:
643:
629:
623:
622:
620:
619:
605:
564:block quotations
555:
552:
549:
546:
543:
540:
537:
534:
531:
528:
525:
522:
519:
516:
513:
510:
507:
504:
501:
498:
495:
492:
489:
486:
483:
480:
477:
474:
471:
468:
465:
462:
406:Use of locality:
327:
323:
319:
315:
311:
307:
303:
299:
295:
292:Chicken patties
291:
287:
283:
243:
240:
237:
234:
231:
228:
225:
222:
219:
216:
213:
210:
207:
204:
201:
188:
106:consumer symbols
74:
67:
63:
60:
54:
49:this article by
40:inline citations
27:
26:
19:
832:
831:
827:
826:
825:
823:
822:
821:
792:
791:
780:
779:
770:
769:
763:
761:
759:
736:
681:
676:
675:
666:
664:
662:Daring Fireball
654:
650:
641:
639:
631:
630:
626:
617:
615:
613:www.secnetix.de
607:
606:
602:
597:
589:Syntactic sugar
575:
570:
557:
556:
553:
550:
547:
544:
541:
538:
535:
532:
529:
526:
523:
520:
517:
514:
511:
508:
505:
502:
499:
496:
493:
490:
487:
484:
481:
478:
475:
472:
469:
466:
463:
460:
441:
428:
419:
365:and especially
343:
335:
330:
329:
325:
324:2 dress shirts
321:
317:
313:
309:
305:
301:
297:
293:
289:
285:
281:
250:
245:
244:
241:
238:
235:
232:
229:
226:
223:
220:
217:
214:
211:
208:
205:
202:
199:
186:
173:
157:
155:Textual context
149:
118:technical books
90:formal notation
75:
64:
58:
55:
45:Please help to
44:
28:
24:
17:
12:
11:
5:
830:
820:
819:
814:
809:
804:
790:
789:
757:
729:
722:
719:
714:Marian Petre,
712:
693:(2): 131–174.
680:
677:
674:
673:
648:
637:www.python.org
624:
599:
598:
596:
593:
592:
591:
586:
581:
574:
571:
568:
459:
440:
437:
427:
424:
418:
415:
410:
409:
403:
397:
391:
381:
342:
339:
334:
331:
316:2 dozen eggs
280:
278:
277:
270:
262:
249:
246:
198:
172:
169:
156:
153:
148:
145:
125:traffic lights
84:is the set of
77:
76:
59:September 2018
31:
29:
22:
15:
9:
6:
4:
3:
2:
829:
818:
815:
813:
810:
808:
805:
803:
800:
799:
797:
786:
774:
760:
754:
750:
746:
742:
735:
730:
727:
723:
720:
717:
713:
708:
704:
700:
696:
692:
688:
683:
682:
663:
659:
652:
638:
634:
628:
614:
610:
604:
600:
590:
587:
585:
582:
580:
577:
576:
567:
565:
561:
533:" "
457:
454:
449:
447:
436:
432:
423:
414:
407:
404:
401:
398:
395:
392:
389:
388:drakon-charts
385:
382:
379:
378:drakon-charts
375:
372:
371:
370:
368:
367:drakon-charts
364:
355:
347:
338:
328:1 orange tie
275:
271:
268:
267:
263:
260:
259:
255:
254:
253:
196:
194:
189:
184:
182:
181:C source code
178:
168:
166:
162:
152:
144:
142:
138:
134:
130:
126:
121:
119:
115:
111:
107:
103:
99:
95:
91:
87:
83:
73:
70:
62:
52:
48:
42:
41:
35:
30:
21:
20:
762:. Retrieved
740:
690:
686:
665:. Retrieved
661:
651:
640:. Retrieved
636:
627:
616:. Retrieved
612:
603:
558:
450:
442:
433:
429:
420:
411:
405:
399:
393:
383:
373:
360:
336:
296:Fish sticks
288:Frozen Tuna
264:
256:
251:
190:
185:
174:
165:code editors
158:
150:
122:
100:, sizes and
96:of computer
81:
80:
65:
56:
37:
781:|work=
274:indentation
137:indentation
129:chart's key
102:color codes
98:source code
86:visual cues
51:introducing
796:Categories
764:2011-07-12
728:." (2013).
679:References
667:2015-04-19
642:2017-05-22
618:2017-05-22
341:Flowcharts
161:typography
110:bank notes
34:references
783:ignored (
773:cite book
363:flowchart
807:Notation
707:11750514
573:See also
560:Markdown
258:Boldness
141:coloring
108:such as
266:Italics
163:and in
127:, or a
47:improve
755:
705:
453:Python
417:Misuse
227:printf
36:, but
737:(PDF)
703:S2CID
595:Notes
515:print
500:print
488:print
476:print
212:while
114:coins
785:help
753:ISBN
539:join
218:true
203:main
139:and
745:doi
695:doi
527:str
200:int
112:or
798::
777::
775:}}
771:{{
751:.
739:.
701:.
689:.
660:.
635:.
611:.
467:==
461:if
318:3.
302:2.
282:1.
236:);
206:()
787:)
767:.
747::
711:.
709:.
697::
691:7
670:.
645:.
621:.
554:)
548:,
542:(
536:.
530:=
524:)
518:(
509:)
503:(
497:)
491:(
485:)
479:(
473::
470:1
464:x
326:-
322:-
314:-
310:-
306:-
298:-
294:-
290:-
286:-
242:}
239:}
230:(
224:{
221:)
215:(
209:{
72:)
66:(
61:)
57:(
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
.png)
