Search results
Results from the WOW.Com Content Network
SICP has been influential in computer science education, and several later books have been inspired by its style. Structure and Interpretation of Classical Mechanics (SICM), another book that uses Scheme as an instructional element, by Gerald Jay Sussman and Jack Wisdom; Software Design for Flexibility, by Chris Hanson and Gerald Jay Sussman
Halstead's goal was to identify measurable properties of software, and the relations between them. This is similar to the identification of measurable properties of matter (like the volume, mass, and pressure of a gas) and the relationships between them (analogous to the gas equation). Thus his metrics are actually not just complexity metrics.
Robert L. (Bob) Glass (born 1932) is an American software engineer and writer, known for his works on software engineering, especially on the measuring of the quality of software design [1] and his studies of the state of the art of software engineering research.
The software quality metrics of coupling and cohesion were invented by Larry Constantine in the late 1960s as part of a structured design, based on characteristics of “good” programming practices that reduced maintenance and modification costs.
Software researchers and practitioners have been addressing the problems of effort estimation for software development projects since at least the 1960s; see, e.g., work by Farr [8] [9] and Nelson. [10] Most of the research has focused on the construction of formal software effort estimation models.
A software design description (a.k.a. software design document or SDD; just design document; also Software Design Specification) is a representation of a software design that is to be used for recording design information, addressing various design concerns, and communicating that information to the design’s stakeholders.
Software design is the process of conceptualizing how a software system will work before it is implemented or modified. [1] Software design also refers to the direct result of the design process – the concepts of how the software will work which consists of both design documentation and undocumented concepts.
[5] The Software Engineering Institute author Paul Clemente found the first two volumes to be "the best-known catalog of architectural patterns". [6] Regarding the third volume, D. Murali recommended that software engineers should follow the "eager acquisition" pattern. [7]