FAQ 6.01 What is the purpose of this chapter? FAQ 6.02 Should users of a member function rely on what the code actually does or on the specification? FAQ 6.03 What are the advantages of relying on the specification rather than the implementation? FAQ 6.04 What are advertised requirements and advertised promises? FAQ 6.05 How are the advertised requirements and advertised promises of the member functions specified? FAQ 6.06 Why are changes feared in development organizations that don't use specification? FAQ 6.07 How do developers determine if a proposed change will break existing code? FAQ 6.08 What are the properties of a substitutable (backward compatible) change in a specification? FAQ 6.09 How can it be shown that the implementation of a member function fulfills its specification? FAQ 6.10 Is it possible to keep the specification synchronized with the code? |