Software development

From Wikipedia, the free encyclopedia

Software development process
Activities and steps
Requirements · Architecture
Design · Implementation
Testing · Deployment
Models
Agile · Cleanroom · Iterative · RAD
RUP · Spiral · Waterfall · XP · Scrum
Supporting disciplines
Configuration management
Documentation
Quality assurance (SQA)
Project management
User experience design
This box: view • talk • edit
For other uses, see Software development (disambiguation).

Software development is the translation of a user need or marketing goal into a software product.[1][2] 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.[3] 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.[4] 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":

“ 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.[5] ”

[edit] See also

[edit] References

  1. ^ Birrell, N.D. (1985). A Practical Handbook for Software Development. Cambridge University Press. ISBN 0-521-25462-0. 
  2. ^ DRM Associates (2002). New Product Development Glossary. Retrieved on 2006-10-29.
  3. ^ Jim McCarthy. "Dynamics of Software Development" (August 1, 1995), pp:10-30
  4. ^ 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
  5. ^ Alan M. Davis. Great Software Debates (October 8, 2004), pp:125-128 Wiley-IEEE Computer Society Press

[edit] 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)