Thumbnail
Access Restriction
Subscribed

Author Coatta, Terry
Source ACM Digital Library
Content type Text
Publisher Association for Computing Machinery (ACM)
File Format PDF
Language English
Subject Keyword Experience ♦ Obj ♦ Development ♦ Factory ♦ Software ♦ System
Abstract A recent conversation about development methodologies turned to the relative value of various artifacts produced during the development process, and the person I was talking with said: the code has "always been the only artifact that matters. It's just that we're only now coming to recognize that." My reaction to this, not expressed at that time, was twofold. First, I got quite a sense of déjà-vu since it hearkened back to my time as an undergraduate and memories of many heated discussions about whether code was self-documenting. Second, I thought of several instances from recent experience in which the code alone simply was not enough to understand why the system was architected in a particular way.
Description Affiliation: Vitrium Systems (Coatta, Terry)
Age Range 18 to 22 years ♦ above 22 year
Educational Use Research
Education Level UG and PG
Learning Resource Type Article
Publisher Date 2010-04-01
Publisher Place New York
Journal Queue (QUEUE)
Volume Number 5
Issue Number 6


Open content in new tab

   Open content in new tab
Source: ACM Digital Library