Final answer:
The database structure is easy to change during the data modeling stage. Changing a relationship from 1:N to N:M in an existing database is complex and difficult. User review is essential, and databases are typically more complex to develop than spreadsheets.
Step-by-step explanation:
During the database development process, various stages must be carefully managed to ensure the resulting database system meets the needs and requirements of end-users and stakeholders. One true statement about the database development process is that the database structure is easy to change during the data modeling stage. At this stage, the structure is being designed conceptually, and adjustments can be made relatively easily without affecting an existing system.
Changing a relationship from 1:N to N:M in an existing database, however, is indeed a complex and lengthy process. Such alterations fundamentally change how data entities relate to each other, which might necessitate significant changes in data schemas, application logic, and potentially extensive data migration. In contrast to the claim that user review is not helpful, user feedback is actually crucial in data modeling to ensure the model reflects user requirements and to reduce the risk of future changes post-deployment.
Finally, it's incorrect to say that databases are easier to develop than spreadsheets. Databases are often more complex due to their need to handle large volumes of data, maintain data integrity, and support concurrent users and complex transactions.
The use of a spiral design process, where iterations of design and evaluation take place, can significantly benefit the database development by allowing continuous improvement and adaptation but requires careful planning to manage the inherent risks of time and budget overruns.