Inventory updates: Methods, files and command line arguments: Fall 2023
Learning Objective(s)
Line: 41 to 41
In Lessons Learned, include a discussion the level of abstraction (i.e. how generic each of your methods is). The fewer methods that explicitly reference the task (inventory control) the better (as long as it is achieved while still having quality variable and method names).
Your testing should include at least 2 different types of errors and ensure that every line of code is executed at least once. Add copies of your files that you used (with appropriate links back to the test cases) at the end of the report. Try to put them in columns to save space. You might want to have different sets of files for some of the different tests.
If you used any hints, be sure to indicate that in the Outside Resources Used section
Changed:
< <
For Future Improvements include a discussing about what tasks would the program need to accomplish to make this a complete inventory control system
> >
For Future Improvements include a discussion about what tasks would the program need to accomplish to make this a complete inventory control system