How kiyarashkia/oop345-project works
Main Components
• Utilities Module – A helper class for tokenizing input strings. It is used by almost all other modules (Station, CustomerOrder, etc.) to parse configuration files and order data.
• Station Module – Encapsulates the attributes and operations of a single station (such as item name, serial numbers, and inventory) on the assembly line.
• CustomerOrder Module – Represents customer orders including a list of items (dynamically allocated) that need to be filled. This module handles order status, filling actions, and display.
• Workstation Module – Inherits from or extends the functionality of Station. It adds a processing queue for CustomerOrders and defines operations to fill and move orders. Note that there are global deques (g_pending, g_completed, and g_incomplete) which represent the state of orders as they move through the system.
• LineManager Module – Orchestrates the entire simulation by configuring the sequence of Workstations (using the AssemblyLine input file), pushing orders from the pending queue into the assembly line, and iterating over the fill/move operations.
File Structure for Architectural Clues
• Three main directories (MS1, MS2, MS3) represent the three milestones. Each one contains its own solution (.sln file), project (.vcxproj, etc.) and corresponding executable builds. This shows incremental builds and testing processes.
• Source files for core modules (e.g., Station.cpp, Utilities.cpp, CustomerOrder.cpp, Workstation.cpp, LineManager.cpp) reside within their respective milestone directories, suggesting that each phase builds on the previous one.
• The repositories also include several text-based resources (e.g., Stations1.txt, Stations2.txt, CustomerOrders.txt, AssemblyLine.txt) that provide configuration data and order information for the simulation.
Relationships and Interactions
• Utilities is a shared helper used throughout:
• Station:
• This module with a node “Station” that holds station-specific details (item name, inventory, serial number).
• CustomerOrder:
• That it uses Utilities for parsing, and that it interacts with Station/Workstation during the fill operation.
• Workstation:
• An association with CustomerOrder (through the “push/pop order” operations) and a unidirectional link to the next Workstation (or chain of stations).
• That it supports operations to fill orders, attempt to move orders, and display the current station status.
• Global Order Queues:
• LineManager:
• LineManager as the central “orchestrator” connecting the sequence of Workstations.
• That it uses an input file (AssemblyLine.txt) to configure linkages among Workstations, reordering them to form a proper pipeline.
• Operations that move a CustomerOrder one step at a time along the chain of Workstations.
Architectural Patterns and Technologies
• Object-Oriented design with a clear separation between data (CustomerOrder, Station) and the orchestration/control logic (LineManager).
• That the design follows a pipeline or processing chain pattern (orders move from one Workstation to the next) with each Workstation having clear responsibilities.
• A mention of the use of standard C++ libraries and STL (e.g., std::deque for order queues, std::vector within LineManager, and I/O manipulators for formatting display).
• That there’s careful resource management (pointer arrays in CustomerOrder) and that move semantics are used in CustomerOrder (to prohibit copying and enable efficient transfers).
• To show data/invocation flow from Utilities into the creation and processing in Station and CustomerOrder.
• To show the pipeline of orders: g_pending → Workstation chain → (g_completed or g_incomplete).
• To illustrate that LineManager coordinates the initialization and iterative processing along the Workstation chain.
• Notes on:
• The use of inheritance/polymorphism (Workstation extending Station).
• The configuration dependency via the AssemblyLine input file and the use of STL algorithms in LineManager (as noted in the README).
• Data processing components (modules handling order data) versus
• Controller or orchestration components (LineManager, global queues).
• Optionally, include an inset that shows the incremental build structure (MS1, MS2, MS3 directories) to indicate project evolution over milestones.