How jgrundy2/cop2373 works
The repository contains three independent command-line programming exercises rather than one integrated product: ticket sales, email spam scoring, and monthly expense summaries. Each script prompts the user and prints its own result. The sampled source shows the ticket-sales and spam-scoring helper calls; the expense calculations are performed directly in its main function. The DOCX files and any unsampled contents are not mapped.
Main entry points: JaclynGrundy_ProgrammingExercise_2.py Spam checker · JaclynGrundy_ProgrammingExercise_1.py Ticket sales · JaclynGrundy_ProgrammingExercise_3.py Expense summary
Components 10
Other components
- User
- Ticket sales
JaclynGrundy_ProgrammingExercise_1.py - Ticket validation
JaclynGrundy_ProgrammingExercise_1.py - Sales summary
JaclynGrundy_ProgrammingExercise_1.py - Spam checker
JaclynGrundy_ProgrammingExercise_2.py - Spam terms
JaclynGrundy_ProgrammingExercise_2.py - Term matching
JaclynGrundy_ProgrammingExercise_2.py - Spam assessment
JaclynGrundy_ProgrammingExercise_2.py - Expense summary
JaclynGrundy_ProgrammingExercise_3.py - Expense report
JaclynGrundy_ProgrammingExercise_3.py
Connections 11
- User → Ticket sales: enters requests
- Ticket sales → Ticket validation: requests quantity
- Ticket validation → Ticket sales: returns valid count
- Ticket sales → Sales summary: prints totals
- User → Spam checker: enters email
- Spam checker → Spam terms: gets terms
- Spam checker → Term matching: checks email
- Term matching → Spam checker: returns score and matches
- Spam checker → Spam assessment: prints assessment
- User → Expense summary: enters expenses
- Expense summary → Expense report: prints summary