How yuvii-b/cs23c04_lab works
Main Components
• Lab Modules: Each top-level directory (e.g., “04_ControlStructures”, “05_Iteration”, “06_Arrays”, “07_Strings”, “08_Functions”, “09_ArraysAndFunction”, “10_PointersToArraysAndStrings”, “11_RecursiveFunctions”, “12_StructureUnionEnum”, “13_PointersToStructUnion”) corresponds to a lab session/topic. Treat each as a distinct module.
• Sub-Modules: Within some modules (like “06_Arrays”), you have further subdivisions (e.g., “A. one_dim” and “B. two_dim”). These represent further refinement of the topic.
• Reference Documents: Notice the “Questions.pdf” files in each directory, which serve as documentation or the exercise prompt for that module.
• Common Resources: The README file supplies overall context, and you might include this as a “Project Overview” component with instructions on how to compile/run, showing dependency on GCC and the command-line build process.
Relationships and Interactions
• Shared Dependency: All exercises are standalone, but they contribute to the overall educational goal. You may indicate a “Lab Course” container that houses all modules.
Architectural Patterns or Design Principles
• Modularity: Each lab session is its own module, clearly isolated in its directory. This reflects a learning progression and domain separation.
• Consistency: The uniform naming convention (e.g., “ex1.c”, “ex2.c”) across directories suggests a pattern that could be visualized as repeated standardized blocks.
• Documentation Integration: Each module includes a Questions.pdf, showing the coupling of problem statements with code implementations.
Relevant Technologies and Tools
• Language: The entire repository is in C.
• Compiler: GCC (as indicated in the README “How to Run” section).
• Documentation: Markdown for the README.
Elements
• Clear Labels: Use labels for each module and sub-module (e.g., “04_ControlStructures”, “05_Iteration”, etc.).
• Environment Block: Add a block showing “Developer Environment” that specifies the use of GCC and command-line operations as described in the README.
Detailed Architecture Steps
• Component clearly shows its name and purpose (e.g., “06_Arrays – exercises on one-dimensional and two-dimensional arrays”).