How bangoc/it3120 works
• Case Studies: The “CaseStudy” directory (with files such as “PattersonSuperstore_vi.pdf” and supporting resources) illustrates real-world examples of system design application.
• Demo Applications: Under the “demo” folder you have multiple sample projects arranged by their design patterns or languages:
• Java-based examples (e.g., “spring-cardb”, “mvc-clock/java”, “model2clock”)
• C++ examples (e.g., “guess-number-cpp”, “guess-number-mv-cpp”, “guess-number-observer-cpp”)
• Separate modules for various concerns, such as Data Access (customers in “dam” and “dao”) and UI components.
• Auxiliary / Legacy Materials: Folders like “qb” and “old” offer past resources and additional exercises, which can be seen as supplementary layers.
Relationships and interactions between components
• Within Demo Applications: Identify layers typical of a full-stack design when applicable. For instance:
• In “spring-cardb”, separate the Presentation (controllers, views), Business logic, and Data Access layers (repositories).
• In the various guess-number implementations (DAM, MVC, Observer), illustrate how the Controller, Model, and View components interact and how patterns such as Observer are implemented.
• Legacy and initial drafts (“first-cut”, “old”) can be represented as earlier iterations feeding into mature designs present in the demos and documentation.
Architectural patterns and design principles
• Modularity: The separation between demonstration code and academic/research documentation underscores layered design principles.
Relevant technologies and frameworks
• For Java demos (spring-cardb, model2clock, mvc-clock): note the use of Maven/Gradle, Spring Framework, and typical Java web artifacts (web.xml, JSP files, etc.).
• For C++ demos: include clues from CMakeLists.txt, and note reliance on simple graphical resources (bitmaps) and custom event loops in games.
• For UML and design documents: refer to modeling tools (e.g., Modelio given the .mdj files) and standard UML conventions.