New answers tagged

3

If you really mean SPOCK then you are probably referring to the testing and specification framework for Java and Groovy applications by SpockFramework.org Spock is a testing and specification framework for Java and Groovy applications. What makes it stand out from the crowd is its beautiful and highly expressive specification language. Thanks to its JUnit ...


2

You don't. Schema can be changed at any point in future. Predicting perfect schema is impossible. I say that after doing this for 6 years now. It is simply impossible to know what can come up. With that said, you should definitely consider normalisation, adding basic security measures like using guid instead of sequential numbering, option to ensure ...


1

Strongly normalized data schema should be more flexible to change to meet evolving requirements. Ensure the schema is normalized. Beyond that, this is a quality/suitability to business requirements problem. Collect and test against your requirements. Rely on your team (although I think the most important phrase in your question is that you are the only one ...


4

You don't try to handle everything up front or predict the future. It's a waste of time and effort. As you build out the software and get stakeholder feedback, you will learn more about the true needs of the stakeholders. I'd recommend looking at the techniques of Agile Data and Agile Modeling. These two sets of practices can help you apply and integrate ...


1

Firstly, I'm not so sure this has to do with Project Management. More to the point, why bother? It's rather simple to add fields to a database - even a live one. If you're really paranoid, you could always add a few extra fields, to be named spare1, spare2, etc. and use those later. To answer the actual question of how to ensure that there is nothing left ...


Top 50 recent answers are included