Some general tips on how to proceed.
1. What will the Front panel consist of? What buttons/actions should be provided to the user? Should events be created after clicking a button or after double-clicking a date (like many web-based calendars do)? Specifying the user interactions helps to identify how sections of your code should work together (do multiple buttons require access to the same list of events/alarms?).
2. How should the data be stored? Options vary from array/clusters with shift registers, global variables, functional global variables (FGV), to external files (.txt, .csv, or Configuration files (.ini)). Will the program be running 24/7, 5-10 minutes for grading, or through multiple computer power cycles?
3. Should you use more advanced architecture? While it may be possible to create this using a while loop and constantly checking buttons / alarms, this is an inefficient use of computer memory and it tends to result in large/messy block diagrams. An architecture such as a State Machine or Producer/Consumer may be a worthwhile investment.
Spend some time to plan how the program will look/function before you start writing it. Barging in without a clear direction is an easy way to get yourself stuck (which I've done plenty of times when I first started using LabVIEW).
It's quite probable that many routes/options are beyond the scope or needs of your class but could be worthwile if you forsee using LabVIEW in your future.
