Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have the feeling that you are trying to grab too much at once. It is fine to experiment with databases, TDD and UML diagrams; that in itself would IMHO be enough for a single project. This first experimental project will teach you a lot, based on which you will be able to do a much better job on the next project. But I would not expect this first try to bring results which can convince other developers to pick up TDD, and/or management to change its way of thinking. You need to understand and experience things at first yourself, before you can reasonably explain them to others.</p> <p>For advice on unit testing DB apps, see these threads for starters:</p> <ul> <li><a href="https://stackoverflow.com/questions/145131/whats-the-best-strategy-for-unit-testing-database-driven-applications">What’s the best strategy for unit-testing database-driven applications?</a></li> <li><a href="https://stackoverflow.com/questions/21583/unit-testing-databases">Unit-Testing Databases</a></li> <li><a href="https://stackoverflow.com/questions/202940/unit-tests-framework-for-databases">Unit tests framework for databases</a></li> <li><a href="https://stackoverflow.com/questions/2229486/testing-approach-db-junit">Testing approach - DB, Junit</a></li> </ul> <p>I am not sure what you mean by "prototyping via class diagrams". Class diagrams are fine for discussing / communicating your design to other developers, and should certainly be in the toolkit of every good developer. A whiteboard session with someone, sketching and erasing design elements on the fly is a great way to clarify the design and the forces influencing it. However, IMHO this is "prototyping" only in a very broad sense. A real prototype to me is code - that is the only way to verify whether or not your design really works in practice.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload