Difference between revisions of "software development"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(→‎Overview: link to new "web development" page)
(links to 2 wikipedia articles)
Line 7: Line 7:
  
 
==Links==
 
==Links==
 +
===Reference===
 +
* '''Wikipedia''':
 +
** [[wikipedia:Software engineering|Software engineering]]
 +
** [[wikipedia:Software development methodology|Software development methodology]]
 +
===Concepts===
 
* '''2007-11-01''' [http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx Technical Debt] by [[Steve McConnell]]: [[technical debt]] is a term "coined by [[Ward Cunningham]] to describe the obligation that a software organization incurs when it chooses a design or construction approach that's expedient in the short term but that increases complexity and is more costly in the long term."
 
* '''2007-11-01''' [http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx Technical Debt] by [[Steve McConnell]]: [[technical debt]] is a term "coined by [[Ward Cunningham]] to describe the obligation that a software organization incurs when it chooses a design or construction approach that's expedient in the short term but that increases complexity and is more costly in the long term."

Revision as of 18:22, 30 April 2009

Navigation

{{#lst:creating software|navbar}}: development

Overview

This page is about the art of developing software, from conceptualization to user deployment. It is a subpage of creating software, which goes beyond the deployment phase and also looks at larger issues.

This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!

Types

Links

Reference

Concepts

  • 2007-11-01 Technical Debt by Steve McConnell: technical debt is a term "coined by Ward Cunningham to describe the obligation that a software organization incurs when it chooses a design or construction approach that's expedient in the short term but that increases complexity and is more costly in the long term."