SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science Assignment #1 Worth: 15% of final grade Veterinarian Clinic System Milestone Worth Due...

Please see the attachment


SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science Assignment #1 Worth: 15% of final grade Veterinarian Clinic System Milestone Worth Due Date 1 5% March 27 (23:59 EST) 2 5% April 3 (23:59 EST) 3 5% April 10 (23:59 EST) Introduction This assignment has been broken down into critical deadlines called milestones. Implementing projects using milestones will help you stay on target with respect to timelines and balancing out the workload. By the end of milestone #3, you will have created a basic patient (pet) appointment system for a veterinary clinic. Patient contact information will be managed as well as the scheduling and management of appointments. Each milestone will build upon the previous, adding more functionality and components. Milestone #1 is focused on providing helper functions that will aid you in the development of the overall solution in future milestones. These functions will streamline your logic and simplify the overall readability and maintainability of your program by providing you with established routines that have been thoroughly tested for reliability and eliminate unnecessary code redundancy (so use them whenever possible and don't duplicate logic already done). Each milestone will be released weekly and can be downloaded or cloned from GitHub: https://github.com/Seneca-144100/IPC-Project Reflections will be graded based on the published rubric: https://github.com/Seneca-144100/IPC-Project/tree/master/Reflection%20Rubric.pdf Preparation Download or clone the Assignment 1 from GitHub. In the directory: A1/MS1 you will find the Visual Studio project files ready to load. Open the project (a1ms1.vcxproj) in Visual Studio. Note: the project will contain only one source code file which is the main tester “a1ms1.c”. Milestone – 1 (Weight: 50%) Milestone-1 includes a unit tester (a1ms1.c). A unit tester is a program which invokes your functions, passing them known parameter values. It then compares the results returned by your functions with the correct results to determine if your functions are working correctly. The tester should be used to confirm https://github.com/Seneca-144100/IPC-Project https://github.com/Seneca-144100/IPC-Project/tree/master/Reflection%20Rubric.pdf SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science your solution meets the specifications for each “helper” function. The helper functions should be thoroughly tested and fail-proof (100% reliable) as they will be used throughout your assignment milestones. Development Suggestions You will be developing several functions for this milestone. The unit tester in the file “a1ms1.c” assumes these functions have been created and, until they exist, the program will not compile. Strategy – 1 You can comment out the lines of code in the “a1ms1.c” file where you have not yet created and defined the referenced function. You can locate these lines in the function definitions (after the main function) and for every test function, locate the line that calls the function you have not yet developed and simply comment the line out until you are ready to test it. Strategy – 2 You can create “empty function shells” to satisfy the existence of the functions but give them no logic until you are ready to program them. These empty functions are often called stubs. Review the specifications below and identify every function you need to develop. Create the necessary function prototypes (placed in the .h header file) and create the matching function definitions (placed in the .c source file), only with empty code blocks (don’t code anything yet). In cases where the function MUST return a value, hardcode (temporarily until you code the function later) a return value so your application can compile. Specifications Milestone-1 will establish the function “helpers” we will draw from as needed throughout the three milestones. These functions will handle routines that are commonly performed (greatly reduces code redundancy) and provide assurance they accomplish what is expected without fail (must be reliable). 1. Create a module called “core”. To do this, you will need to create two files: “core.h” and “core.c” and add them to the Visual Studio project. 2. The header file (.h) will contain the function prototypes, while the source file (.c) will contain the function definitions (the logic and how each function works). • Copy and paste the commented section provided for you in the a1ms1.c file (top portion) to all files you create • Fill in the information accordingly 3. The “core.c” file will require the usual standard input output system library as well as the new user library “core.h”, so be sure to include these. 4. Review the “a1ms1.c” tester file and examine each defined tester function (after the main function). Each tester function is designed to test a specific helper function. 5. Two (2) functions are provided for you. Here are the function prototypes you must copy and place into the “core.h” header file: // Clear the standard input buffer void clearInputBuffer(void); SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science // Wait for user to input the "enter" key to continue void suspend(void); The source code file “core.c” must contain the function definitions (copy and place the function definitions below in the “core.c” file): // As demonstrated in the course notes: // https://intro2c.sdds.ca/D-Modularity/input-functions#clearing-the-buffer // Clear the standard input buffer void clearInputBuffer(void) { // Discard all remaining char's from the standard input buffer: while (getchar() != '\n') { ; // do nothing! } } // Wait for user to input the "enter" key to continue void suspend(void) { printf(" to continue..."); clearInputBuffer(); putchar('\n'); } 6. Each function briefly described below will require a function prototype to be placed in the “core.h” file, and their respective function definitions in the “core.c” file. The function identifiers (names) are provided for you however you are responsible for constructing the full function prototype and definitions based on the descriptions below (there are seven (6) functions in total): • Function: inputInt This function must: o return an integer value and receives no arguments. o get a valid integer from the keyboard. o display an error message if an invalid value is entered (review the sample output for the appropriate error message) o guarantee an integer value is entered and returned. o Hint: You can use scanf to read an integer and a character ("%d%c") in one call and then assess if the second value is a newline character. If the second character is a newline (the result of an key press), scanf read the first value successfully as an integer. https://intro2c.sdds.ca/D-Modularity/input-functions#clearing-the-buffer SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science o If the second value (character) is not a newline, the value entered was not an integer or included additional non-integer characters. If any invalid entry occurs, your function should call the clearInputBuffer function, followed by displaying an error message and continue to prompt for a valid integer. Review the flowchart below that describes this process. SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science • Function: inputIntPositive This function must: o return an integer value and receives no arguments. o perform the same operations as inputInt but validates the value entered is greater than 0. o display an error message if the value is a zero or less (review the sample output for the appropriate error message). o continue to prompt for a value until a value is greater than 0. o guarantee a positive integer value is entered and returned. • Function: inputIntRange This function must: o return an integer value and receives two arguments: ▪ First argument represents the lower-bound of the permitted range. ▪ Second argument represents the upper-bound of the permitted range. Note: ▪ A range is a set of numbers that includes the upper and lower limits (bounds) ▪ You must provide meaningful parameter identifiers (names) o performs the same operations as inputInt but validates the value entered is between the two arguments received by the function (inclusive). o display an error message if the value is outside the permitted range (review the sample output for the appropriate error message). o continue to prompt for a value until a value is between the permitted range (inclusive) o guarantee an integer value is entered within the range (inclusive) and returned. • Function: inputCharOption This function must: o return a single character value and receives one argument: ▪ an unmodifiable C string array representing a list of valid characters. Note: You must provide a meaningful parameter identifier (name) o get a single character value from the keyboard. o validate the entered character matches any of the characters in the received C string argument. Reminder: A C string will have a null terminator character marking the end of the array o display an error message if the entered character value is not in the list of valid characters (review the sample output for the appropriate error message) Note: Include in the error message the C string permitted characters o Continue to prompt for a single character value until a valid character is entered. o Guarantee a single character value is entered within the list of valid characters (as defined by the C string argument received) and returned. SDDS Winter – 2022 School of Software Design and Data Science SDDS School of Software Design and Data Science • Function: inputCString The purpose of this function is to obtain user input for a C string value with a length (number of characters) in the character range specified by the 2nd and 3rd arguments received (inclusive). This function: o must receive three (3) arguments and therefore needs three (3) parameters: ▪ 1st parameter is a character pointer representing a C string Note: Assumes the argument has been