Back عملية تطوير البرمجيات Arabic Proqram təminatı prosesi Azerbaijani সফটওয়্যার উন্নয়ন প্রক্রিয়া Bengali/Bangla Procés de desenvolupament de programari Catalan پرۆسەی داھێنانی نەرمامێر CKB Proces vývoje softwaru Czech Διαδικασία ανάπτυξης λογισμικού Greek Proceso del desarrollo del software Spanish فرایند توسعه نرمافزار Persian Processus de développement logiciel French
 | This article needs additional citations for verification. (December 2010) |
| Part of a series on |
| Software development |
|---|
A software development process prescribes a process for developing software. It typically divides an overall effort into smaller steps or sub-processes that are intended to ensure high-quality results. The process may describe specific deliverables – artifacts to be created and completed.[1]
Although not strictly limited to it, software development process often refers to the high-level process that governs the development of a software system from its beginning to its end of life – known as a methodology, model or framework. The system development life cycle (SDLC) describes the typical phases that a development effort goes through from the beginning to the end of life for a system – including a software system. A methodology prescribes how engineers go about their work in order to move the system through its life cycle. A methodology is a classification of processes or a blueprint for a process that is devised for the SDLC. For example, many processes can be classified as a spiral model.
Software process and software quality are closely interrelated; some unexpected facets and effects have been observed in practice.[2]
- ^ "Selecting a development approach" (PDF). Centers for Medicare & Medicaid Services (CMS) Office of Information Service. United States Department of Health and Human Services (HHS). March 27, 2008 [Original Issuance: February 17, 2005]. Archived from the original (PDF) on June 20, 2012. Retrieved October 27, 2008.
- ^ Suryanarayana, Girish (2015). "Software Process versus Design Quality: Tug of War?". IEEE Software. 32 (4): 7–11. doi:10.1109/MS.2015.87.