Tier: Personal
Customer: Undisclosed
Repo: https://github.com/IU-Capstone-Project-2025/hypershelf

Detailed Requirements #

All of the requirements were specified in the Week 1 report and are sufficient on the current stage.

Prioritized Backlog #

Since I am working following the waterfall development model and working alone, I do not really need a specific backlog. Currently the next priorities (in the random order) are:

• Office schemas & vSphere integration
• Deep vSphere integration on the backend
• Markdown editor
• Static views for users (which columns in which order)
• Bug fixes
• UX/UI improvements

Project Progress #

Detect errors in the table #

All errors, as well as empty required fields are now highlighted

UX/UI improvements #

More field types #

All field types have validators specific to them. E.g. IP Address type has validator subnet, which is the CIDR notation subnet.

Client-side vSphere integration #

Links the Hypershelf widget to the asset using hostname (in this case portal.dev.[REDACTED]). I also want it to show the position on the office schema in the widget (plans for future)

Debug Interface #

Available for all fields, one specific field, all assets and one specific asset. Useful in plugin development to see the fields available on each field, and, obviously, for debug.

Persistent Fields #

Prevents the deletion of a specific field. Useful for plugin development to prevent ID changes. Though it is not recommended to address fields by ID, it is still possible.

Bug fixes #

Most of the bugs were fixed as the result of codebase refactor.

DX Best Practices #

Codebase for frontend was very much refactored to follow best practices of React & follow DRY.