SOFTWARE DEVELOPMENT

'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"''':

Contents

See also

External links

References

Further reading

See also

★ 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

★ Software development process ★ Software development rhythms ★ ★ Software engineering economics ★ Software industry ★ Software project management ★ Search Based Software Engineering ★ Software publisher ★ Software user experience design ★ System software ★ Video game development ★ Web application development ★ Web development

External links

★ Software Development Advice and Strategies

References

1. A Practical Handbook for Software Development, Birrell, N.D., , , Cambridge University Press, 1985, ISBN 0-521-25462-0
2. New Product Development Glossary DRM Associates
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

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)