I have been tasked with replacing a legacy system written in Oracle Forms & Reports and with an Oracle Database. The system contains around 100 tables and about 200 screens and reports. There can be 3-4 developers maintaining the system at any given time.
From what I’ve seen with CUBA, it looks very promising. However, most of the tutorials that I’ve seen with CUBA Studio illustrates going from nothing to something. In other words, it goes through entity creation and database creation, adding business logic and screens all in the same project. I don’t see how this could work when there can be multiple developers working on the same application, but different screens/reports, at the same time. I would guess from my limited research that application components would come into play here because in most of our screens/reports, it uses the employee table/entity.
So I’m a little confused on whether CUBA would be able to fit my needs. If so, how would one go about structuring projects so that multiple developers can work on different aspects of the system? Can one project be one screen whereby the underlying tables it uses would be application components? Am I making any sense here?