Software development 248932 223048464 2008-07-02T10:06:38Z MER-C 1749459 Reverted edits by [[Special:Contributions/41.206.43.154|41.206.43.154]] ([[User talk:41.206.43.154|talk]]) to last version by 206.71.79.12 {{Software development process}} {{otheruses|Software development (disambiguation)}} '''Software development''' is the translation of a user need or marketing goal into a [[software]] product.<ref>{{cite book|author=Birrell, N.D.|title=A Practical Handbook for Software Development|publisher=Cambridge University Press|year=1985|id=ISBN 0-521-25462-0}}</ref><ref>{{cite web|author=DRM Associates|title=New Product Development Glossary |url=http://www.npd-solutions.com/glossary.html |date=2002|accessdate=2006-10-29}}</ref> Software development is sometimes understood to encompass the processes of [[software engineering]] combined with the research and goals of software [[marketing]] to develop [[computer software]] products.<ref>[http://www.amazon.com/dp/1556158238 Jim McCarthy. "Dynamics of Software Development" (August 1, 1995), pp:10-30]</ref> This is in contrast to marketing software, which may or may not involve [[new product development]]. It is often difficult to isolate whether engineering or marketing is more responsible for the success or failure of a software product to satisfy customer expectations. This is why it is important to understand both processes and/or facilitate collaboration between both engineering and marketing in the total software development process. Engineering and marketing concerns are often balanced in the role of a [[project manager]] that may or may not use that title. Marketing involvement is also known as [[software requirements analysis]].<ref>Won Kim: “On Assuring Software Quality and Curbing Software Development Cost”, in Journal of Object Technology, vol. 5, no. 6, July-August 2006, pp. 35-42 http://www.jot.fm/issues/issue_2006_07/column5</ref> Because software development may involve compromising or going beyond what is required by the client, a software development project may stray into processes not usually associated with engineering such as [[market research]], [[human resources]], [[risk management]], [[intellectual property]], [[budgeting]], [[crisis management]], etc. These processes may also cause the role of [[business development]] to overlap with software development. In the book ''"Great Software Debates"'', Alan M. Davis states in the chapter ''"Requirements"'', subchapter '''''"The Missing Piece of Software Development"''''': {{cquote|''Students of engineering learn engineering and are rarely exposed to finance or marketing. Students of marketing learn marketing and are rarely exposed to finance or engineering. Most of us become specialists in just one area. To complicate matters, few of us meet interdisciplinary people in the workforce, so there are few roles to mimic. Yet, software product planning is critical to the development success and absolutely requires knowledge of multiple disciplines.<ref>Alan M. Davis. Great Software Debates (October 8, 2004), pp:125-128 Wiley-IEEE Computer Society Press</ref>''}} ==See also== {| width="100%" |- valign=top |width="50%"| *[[Alliances between product software firms]] *[[Application software]] *[[Computer programmer]] *[[Custom software development]] *[[Incremental funding methodology]] *[[Functional specification]] *[[Marketing strategies for product software]] *[[Offshore software development]] *[[Software blueprint]] *[[Software company]] *[[Software design]] *[[Software developer]] |width="50%"| *[[Software development effort estimation]] *[[Software development process]] *[[Software Development Rhythms|Software development rhythms]] *[[:Category:Software distribution|Software distribution]] *[[Software engineering economics]] *[[Software industry]] *[[Software project management]] *[[Search Based Software Engineering]] *[[Software publisher]] *[[User experience|Software user experience design]] *[[System software]] *[[Video game development]] *[[Web application development]] *[[Web development]] *[[Service-Oriented Modeling]] Framework | |} ==References== {{reflist}} ==Further reading== * Luke Hohmann. "Beyond Software Architecture: Creating and Sustaining Winning Solutions" ([[January 30]], [[2003]]) * Jim McCarthy. "Dynamics of Software Development" ([[August 1]], [[1995]]), pp:10-30 * Robert K. Wysocki. "Effective Software Project Management" ([[March 27]], [[2006]]), pp:72-75 * PhD, CISM, John Rittinghouse. "Managing Software Deliverables: A Software Development Management Methodology" ([[November 12]], [[2003]]) * Dan Conde. "Software Product Management: Managing Software Development from Idea to Product to Marketing to Sales" ([[September 1]], [[2002]]), pp:24-29 * Edward Hasted. "Software That Sells : A Practical Guide to Developing and Marketing Your Software Project" ([[June 10]], [[2005]]) * A. M. Davis, "Just enough requirements management: where software development meets marketing" ([[May 30]], [[2005]]) * John W. Horch, "Two Orientations On How To Work With Objects," IEEE Software, vol. 12, no. 2, pp. 117-118, Mar., 1995. * Karl E. Wiegers, "More About Software Requirements: Thorny Issues and Practical Advice" ([[December 20]], [[2005]]) [[Category:Software development|*]] [[Category:Marketing]] [[Category:Software project management]] [[Category:Management]] [[Category:Software engineering]] [[Category:Production and manufacturing]] [[Category:Project management]] [[Category:Computer and mathematical occupations]] [[de:Softwareentwicklung]] [[fr:Développement de logiciel]] [[ko:소프트웨어 개발]] [[he:פיתוח תוכנה]] [[ja:ソフトウェア開発]] [[pt:Desenvolvimento de software]] [[vi:Phát triển phần mềm]] [[zh:软件开发]]