using ubuntu , that's all about the project no more info

PBL-Phase Motivation The R&D department would like to develop needed code for server's administrator to run on a Linux server to help in creating folders for different coding projects of different teams in different courses then utilize it for auto grading, recording coding attempts and verifications of code correctness for development teams. You are required to do that in two ways: A. Using system bash scripting for Linux B. Using C system programming for Linux File system structure Folders structure should be automatically created in the file system given input files. These files include: a list of course and their instructors; a list of teams and members of teams for each course; a list of projects for each course. The idea is to organize teams' projects in appropriate folders to be used by the system. Teams can submit multiple versions of a specific project and your code should be able to provide versioning of these files. The final score of the auto grading is for the last submitted version. For now, the projects of different teams can be placed manually in these folders. You have to come up with a strict naming convention for the folders and the submitted projects' files by teams. The internal structure of each folder depends on the type of the project. Think about the most appropriate structure for a C/Java/bash projects. Auto grading The auto grading works only for projects that does not require user interaction. The input of such projects is either self-contained within the code or can be read from file(s). Such projects are designed in either one of those two ways for input. The auto grading script compiles/executes a project and saves the results of the execution in a feedback file in the same folder of the project. The feedback files should have only view permission by teams. You also need to come up with appropriate naming convention for these feedback files. In case the project requires input file(s), they should be provided and manually placed in one subfolder named testcase in the folder of that project. In some cases, a project might have more than one input testcase and in that case it should be tested for all of the available scenarios and feedback should be recorded as well. List all possible feedback. How do you verify that the code is correct and produces the expected results at all times? What other information/files do you need to check that the results are correct? What additional process do you need to provide a grade for a project ...etc. Logging Another code will run once projects are due and grading is complete. This script should record useful information about teams' attempts, grade, and other information from feedback files. Think of what information you need to record about attempts, grades, and feedback and in what format is the most useful for the instructors. PBL-Phase Motivation The R&D department would like to develop needed code for server's administrator to run on a Linux server to help in creating folders for different coding projects of different teams in different courses then utilize it for auto grading, recording coding attempts and verifications of code correctness for development teams. You are required to do that in two ways: A. Using system bash scripting for Linux B. Using C system programming for Linux File system structure Folders structure should be automatically created in the file system given input files. These files include: a list of course and their instructors; a list of teams and members of teams for each course; a list of projects for each course. The idea is to organize teams' projects in appropriate folders to be used by the system. Teams can submit multiple versions of a specific project and your code should be able to provide versioning of these files. The final score of the auto grading is for the last submitted version. For now, the projects of different teams can be placed manually in these folders. You have to come up with a strict naming convention for the folders and the submitted projects' files by teams. The internal structure of each folder depends on the type of the project. Think about the most appropriate structure for a C/Java/bash projects. Auto grading The auto grading works only for projects that does not require user interaction. The input of such projects is either self-contained within the code or can be read from file(s). Such projects are designed in either one of those two ways for input. The auto grading script compiles/executes a project and saves the results of the execution in a feedback file in the same folder of the project. The feedback files should have only view permission by teams. You also need to come up with appropriate naming convention for these feedback files. In case the project requires input file(s), they should be provided and manually placed in one subfolder named testcase in the folder of that project. In some cases, a project might have more than one input testcase and in that case it should be tested for all of the available scenarios and feedback should be recorded as well. List all possible feedback. How do you verify that the code is correct and produces the expected results at all times? What other information/files do you need to check that the results are correct? What additional process do you need to provide a grade for a project ...etc. Logging Another code will run once projects are due and grading is complete. This script should record useful information about teams' attempts, grade, and other information from feedback files. Think of what information you need to record about attempts, grades, and feedback and in what format is the most useful for the instructors