DLS2namingthat leavesout the 2DLS2naming thatwouldnormally failstandardsCodingstandardsviolationFunctionthat couldbe staticbut isn'tCodecomplexity> 15OrphanedrequirementtagIncorrectrequirementtagCode thatshould reallyhave arequirementCode thatshould reallyhave acomment butdoesn'tGTC/GDUrequirement"Business"LogicwithinCDPUsage ofATN inreference toLink 2000+5 deepmemberaccess toa structureIncorrectlogic/bugRepeatedcode thatcould be afunction/macroUnusedfunctionor fileCommentthat doesn'treally explainthe codeTypowithin acomment"ToDo"commentCommentthat lies"//"commentNumber thatshould reallybe a defineorenumerationDemo modefunctionalitythat shouldonly beKiosksLink 2000+or FANS 1/Alogic thatshould bepostponedCoverageyogaopportunityVariablename withno vowelsRandomlycommentedout codeDLS2namingthat leavesout the 2DLS2naming thatwouldnormally failstandardsCodingstandardsviolationFunctionthat couldbe staticbut isn'tCodecomplexity> 15OrphanedrequirementtagIncorrectrequirementtagCode thatshould reallyhave arequirementCode thatshould reallyhave acomment butdoesn'tGTC/GDUrequirement"Business"LogicwithinCDPUsage ofATN inreference toLink 2000+5 deepmemberaccess toa structureIncorrectlogic/bugRepeatedcode thatcould be afunction/macroUnusedfunctionor fileCommentthat doesn'treally explainthe codeTypowithin acomment"ToDo"commentCommentthat lies"//"commentNumber thatshould reallybe a defineorenumerationDemo modefunctionalitythat shouldonly beKiosksLink 2000+or FANS 1/Alogic thatshould bepostponedCoverageyogaopportunityVariablename withno vowelsRandomlycommentedout code

FAA Data Comm Review Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
  1. DLS2 naming that leaves out the 2
  2. DLS2 naming that would normally fail standards
  3. Coding standards violation
  4. Function that could be static but isn't
  5. Code complexity > 15
  6. Orphaned requirement tag
  7. Incorrect requirement tag
  8. Code that should really have a requirement
  9. Code that should really have a comment but doesn't
  10. GTC/GDU requirement
  11. "Business" Logic within CDP
  12. Usage of ATN in reference to Link 2000+
  13. 5 deep member access to a structure
  14. Incorrect logic/bug
  15. Repeated code that could be a function/macro
  16. Unused function or file
  17. Comment that doesn't really explain the code
  18. Typo within a comment
  19. "ToDo" comment
  20. Comment that lies
  21. "//" comment
  22. Number that should really be a define or enumeration
  23. Demo mode functionality that should only be Kiosks
  24. Link 2000+ or FANS 1/A logic that should be postponed
  25. Coverage yoga opportunity
  26. Variable name with no vowels
  27. Randomly commented out code