'''Software development''' is the translation of a user need or marketing goal into a software product.<ref></ref><ref></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"''''':

==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 distribution
*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
*Service-Oriented Modeling Framework

'''Pembangunan perisian''' merupakan terjemahan keperluan pengguna atau matlamat pemasaran kepada keluaran perisian.<ref></ref><ref></ref> Pembangunan perisian kadang kala difahami sebagai merangkumi proses kejuruteraan perisian (''software engineering'') digabung dengan penyelidikan dan matlamat pemasaran perisian bagi membangunkan keluaran perisian komputer (''computer software'').<ref>[http://www.amazon.com/dp/1556158238 Jim McCarthy. "Dynamics of Software Development" (August 1, 1995), pp:10-30]</ref> Ini berbeza dengan pemasaran perisian, yang mungkin atau tidak membabitkan pembangunan keluaran baru. 

Ia nya adalah sukar untuk mengasingkan samaada kejuruteraan atau pemasaran adalah lebih bertanggung jawab bagi kejayaan atau kegagalan keluaran perisian bagi memenuhi jangkaan pelanggan. Oleh itu adalah penting bagi memahami kedua-dua proses dan/atau membantu kerjasama antara kedua jurutera dan pemasaran dalam proses pembangunan perisian keseluruhan. Kepentingan kejuruteraan dan pemasaran seringkali diimbangkan dalam bentuk pengurus projek yang mungkin menggunakan atau tidak menggunakan gelaran tersebut. 

Pembabitan pemasaran juga dikenali sebagai analisa keperluan perisian (''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> Oleh kerana pembangunan perisian mungkin membabitkan tolak-ansur atau melampaui apa yang diperlukan oleh pelanggan, projek pembangunan perisian mungkin terbabas kepada proses yang biasanya tidak dikaitkan dengan kejuruteraan seperti penyelidikan pasaran, sumber manusia, pengurusan risiko, intellectual property, budgeting, crisis management, dll. Proses ini juga mungkin menyebabkan peranan pembangunan perniagaan bertindan dengan pembangunan perisian.

Dalam buku ''"Great Software Debates"'', Alan M. Davis menyatakan dalam bab ''"Requirements"'', subbab '''''"The Missing Piece of Software Development"''''':

==Lihat juga==
{| width="100%"
|- valign=top
|width="50%"| 
*Perisian aplikasi
*Pengaturcaraan komputer
*Pembangunan perisian khas
*Methodologi pembiayaan meningkat
*Spesifikasi fungsi
*Strategi pemasaran bagi perisian keluaran
*Pembangunan perisian luar pantai
*Cetakan biru perisian
*Syarikat perisian
*Reka bentuk perisian
*Pengaturcara perisian
|width="50%"| 
*Anggaran usaha pembangunan perisian
*Proses pembangunan perisian
*Ekonomi kejuruteraan perisian
*Industri perisian
*Pengurusan projek perisian
*Kejuruteraan Perisian Berasaskan Pencarian
*Penerbit perisian
*Perisian Sistem
*Pembangunan permainan video
*Pembangunan applikasi Web
*Pembangunan Web
*Rangka Kerja Model Berasaskan Perkhidmatan 