Abstract
A software development process can be considered rational if each design decision can be justified based on given facts and design decisions that were made, reviewed, and accepted earlier. This paper describes a set of documents that can serve as a “knowledge base” for more rational software development. Each of these documents can be viewed as a place where the decisions made in one phase of a software development can be recorded for those who work in the next phase. These documents make it possible to develop software in a rational and reviewable way. We describe why each document is needed, how it should be organized, and how the information in the whole set of documents can be represented in a precise, checkable, and accessible way. We illustrate the approach with a detailed discussion of one of these documents, module interface documentation.
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.
