Inventory 2.0 Technical Design #6349

In order to organize and plan the next iteration of inventory (see #6104 ), we need a diagram and technical work list of all the items to be complete for both MVP and 2.1.

Acceptance Criteria

The diagram and high level features are agreed to, and technical list is produced (which can be turned into GitHub epic and tickets).

Sketch

First create a working diagram of the services, features, and planned technologies documented. Get these reviewed and approved before proceeding.

Next create a technical list of the work to be accomplished. Can/should work in categories. Focus on working features and blockers. For example base database setup needs to be created before a table defining contact points can be created.

Don't forget setup and cleanup steps. For example, we need a repository to house this information. CI/CD should be setup to dev cloud.gov initially. Build the database with possible DB migration. But for cleanup, we may want to "reset" the DB on version 1.0 and remove all the complex migrations, and then plan for future migrations.

Some ideas of things to consider:

• Repository setup (code scanning, basic flask app with hello world, testing framework in place and connected to pull requests)
• Cloud.gov integration (CI/CD to dev/stage/prod, automated service creation)
• Application development (class by class CRUD and UI form, draft vs live state implementation, import/export features, changelog tracking)
• Access management (login.gov integration, user permissions access of admin/read/edit)
• Audit step setup (URL scanning for live assets, abandoned catalogs, etc)
• 2.1 planning