Featured Columns View, for the primary activity of the programming there can be no right method [2], since the creative process of theory building is inherently not a method or rule driven activity. Thus the argument of the agile methodologists [1] for interaction, cooperation and collaboration, during development, rather than communication by formal documents, is given weight by a theory building perspective. For such dynamic interaction and communication is a necessary part of the process of developing the jointly owned 'theory of the world' to be represented in the software artifact arising from the project. It follows then that documentation is not necessary if the programming team can jointly own and hold the theory of the world in their heads. This of course is the mindset of the novice programmer who sees the code, the code and nothing but the code as the key artifact from a software project. Having the likes of Kent Beck [3] advocating extreme programming then, is a great support for students who can code passably but either hate, or are barely able to write a coherent sentence. Perhaps this also helps explain the programmer mentality about documentation as something external, something "other"
End of preview. The entire article is 2 pages. To view the full-text, please rent this article to continue.
/lp/association-for-computing-machinery/documentation-and-agile-methods-striking-a-balance-W7oYSSiJQY
Welcome to DeepDyve! Rent Premier Research Articles and Save Up to 90%
Documentation and agile methods: striking a balance
Clear, Tony
Follow ACM SIGCSE Bulletin
, Volume 35 (2)
Association for Computing Machinery – Jun 1, 2003
More Info
More Like This Article
View All dataSource[]=actageo&dataSource[]=aspet&dataSource[]=aaos&dataSource[]=aacc&dataSource[]=aacr&dataSource[]=aea&dataSource[]=aip&dataSource[]=ajnr&dataSource[]=ams&dataSource[]=aps_physical&dataSource[]=appi_book&dataSource[]=appi_journal&dataSource[]=apha&dataSource[]=asip&dataSource[]=asm&dataSource[]=asn&dataSource[]=aspb&dataSource[]=avs&dataSource[]=annual_reviews&dataSource[]=arxiv&dataSource[]=acm&dataSource[]=berghahn&dataSource[]=cabi&dataSource[]=clinical_trials&dataSource[]=dailymed&dataSource[]=degruyter&dataSource[]=du_press&dataSource[]=esa&dataSource[]=eu_press&dataSource[]=elsevier&dataSource[]=emerald&dataSource[]=ejtr&dataSource[]=emea&dataSource[]=epo&dataSource[]=faseb&dataSource[]=gsa&dataSource[]=health_affairs&dataSource[]=hindawi&dataSource[]=imanager&dataSource[]=imedpub&dataSource[]=informa_healthcare&dataSource[]=informs&dataSource[]=iop&dataSource[]=iucr&dataSource[]=iospress&dataSource[]=jbjs&dataSource[]=leftcoast&dataSource[]=lu_press&dataSource[]=mesharpe&dataSource[]=mary_ann_liebert&dataSource[]=medline&dataSource[]=mit_press&dataSource[]=nature&dataSource[]=oxford&dataSource[]=pier_professional&dataSource[]=pnas&dataSource[]=portlandpress&dataSource[]=psyc_articles&dataSource[]=psyc_books&dataSource[]=psyc_critiques&dataSource[]=plos_journal&dataSource[]=pubmed_central&dataSource[]=rsna&dataSource[]=rockefeller&dataSource[]=rcn&dataSource[]=ria&dataSource[]=rsc&dataSource[]=sage&dataSource[]=spie&dataSource[]=springer_journal&dataSource[]=springer&dataSource[]=taylor_francis&dataSource[]=aps&dataSource[]=the_scientist&dataSource[]=uc_press&dataSource[]=uspto_abstract&dataSource[]=wiley&dataSource[]=pct
© 2012 DeepDyve, Inc. All rights reserved.
Terms of Service | Privacy Policy
