
WEEK_4:_END-TO-END_MODULE_DEVELOPMENT_AND_PROCUREMENT_SYSTEMS
Mr. Anton
Developed end-to-end CRUD functionalities for the new Procurement Mode module. Implemented a nested Procurement Process system linked to specific procurement modes. Integrated a draggable UI feature to allow users to dynamically reorder procurement steps. Verified backend integrity by performing comprehensive endpoint testing via Postman. Conducted extensive research on government-mandated procurement reports and documentation. Collaborated on designing database schemas for various reports within Google Docs. Completed the RSMI (Report of Supplies and Materials Issued) module with support for multiple dynamic entries. Received assignment for a new report module to be developed in the following week.
Full-Stack Procurement & Draggable Logistics
This week focused on building the Procurement module from the ground up. The primary requirement was to allow users to create 'Procurement Modes' which contain multiple 'Procurement Processes.' To meet the mentor's request for flexible process ordering, I implemented a draggable reordering feature, providing an intuitive UX for sequence management. Since the QAsset codebase follows a similar architecture to our previous LMS project, I was able to rapidly move from UI development to backend CRUD operations, ensuring all data was strictly validated and tested through Postman before frontend integration.







Government Reporting & RSMI Implementation
The latter half of the week shifted toward specialized government reporting. After an intensive afternoon of researching official procurement documents, our team collaborated on drafting table schemas in Google Docs to ensure data normalization for each report type. My specific task was to build the RSMI (Report of Supplies and Materials Issued) module. I engineered a dynamic form that allows for multiple entries within a single report submission, ensuring the module handles complex, multi-row data inputs efficiently.
Working on government-standard reports like the RSMI requires a high level of precision in schema design. Completing this end-to-end module—from the initial research and schema drafting to the final functional form—has deepened my understanding of how software must adapt to rigid regulatory requirements. With the RSMI module finished by the end of the week, I am now prepared to tackle the next set of report modules assigned by my mentor.