This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi. I have some confusion about postcondition part in Larman's design-by-contract approach in his famous book...
Larman creates contracts for system operations. If i have (in technical way) standard system with database, and i have system operation saveEmployee(emp:Employee), what will be postcondition(s) for that system operation? Do i need to mention some postconditions related to database state, for example. "Employee was saved in database" or something like that. My confusion is even bigger with operations like readEmployee or searchEmployees...
What are the implications of these "CRUD like" system operations on domain model state in context of Larman's approach? Do i need to forget about database state in OOA process...?
I would be grateful if someone helped me. I am quite confused.
I am interested in undertanding the System Operation Contracts, am reading through the Larman's book as well.
Like you, i'm confused with the post-condition explaination. When reading through the Design By Contract by Bertrand Mayer, even confuse..
not sure how it relates..
If you finally got the answer hope you kind to share.