Abstract
A software module may be described precisely and completely by a set of related documents: interface specification of the module providing a “black-box” description of its behavior, internal design of the module containing its “clear-box” description, and the code itself. A special formalism is needed in each of these documents. We use the trace assertion method for specification of module interfaces, and LD-relations to specify behavior of individual programs within a module. The main purpose of our research was to formulate rules and clarify issues relating to the internal design of modules specified using the trace assertion method. Our interests emerged from participation in a broader project aimed at implementation of an integrated set of syntax-driven editors supporting the system documentation process. Many practical problems of the documentation methodology involved were recognized, and solutions were proposed and verified. In this paper we summarize our experience. Appendices contain the complete set of documents for sample modules.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
