Quantum Stock Development Sprint

Aerneth Code and Eng DK30 Fall 2023 0 0

Description

The Quantum Stock Development Sprint builds on the foundation of the Quantum Stock inventory management system, which already features a login system, SQLite database integration, and an initial dashboard design. Over the next 30 days, I will focus on completing key features such as stock modification, barcode scanning, and a fully functional dashboard. This sprint also aims to refine the UI and enhance the application’s usability for small workshop environments.

Recent Updates

Aerneth 7 months ago

I made many small improvements on the project today. The biggest change was that the chart of items now updates Average Unit Price and Total Cost from all of the item’s stock objects. I also polished up the Add Stock Object window, ensuring the calendars don’t prematurely close before the user is done selecting the date. Lastly, I removed price and quantity entries on the Add Items and Edit Items UI, as these should be populated for the item from the item’s stock objects.

I’ve encountered a challenge - removing the price field entirely from the items in the database. There are so many dependencies on that field. For now, I’m just making inline comments to not use the field, as every time I attempt to clean it up, literally everything breaks!

Edit: I just can’t take a break from this project. It’s on my mind at all times. Since I don’t really feel like messing with the code right now but still want to get something done, I’m working on documentation. I’ve added an ER Diagram of the project’s database (above) that I used DBeaver to conjure up.

Estimated Timeframe

Jan 1st - Jan 31st

Week 1 Goal

Finalize or address any lingering foundational issues.
Ensure core functionalities (e.g., login, database operations) are fully operational and stable.
Review and prioritize GitHub issues for upcoming weeks.
Begin Documentation of the software.

Week 2 Goal

Work on implementing a significant new feature (e.g., dashboard updates or barcode scanning).
Begin integrating another feature, even if it remains incomplete by week’s end.
Resolve bugs or usability concerns identified during development.
Continue Documentation.

Week 3 Goal

Refine the user interface and enhance the overall user experience.
Optimize SQLite queries and other performance-related aspects of the application.
Continue addressing high-priority issues from GitHub.
Continue Documentation.

Week 4 Goal

Tie up loose ends with any partially implemented features.
Conduct end-to-end testing to ensure the application meets expectations.
Draft user or developer documentation and reflect on progress.
Continue Documentation.