Alexander Fedorov

35%
Flag icon
Plan the System for Change The ways of designing a system for such change are well known and widely discussed in the literature—perhaps more widely discussed than practiced. They include careful modularization, extensive subroutining, precise and complete definition of intermodule interfaces, and complete documentation of these. Less obviously one wants standard calling sequences and table-driven techniques used wherever possible. Most important is the use of a high-level language and self-documenting techniques so as to reduce errors induced by changes. Using compile-time operations to ...more
The Mythical Man-Month: Essays on Software Engineering
Rate this book
Clear rating
Open Preview