|Software development process|
|Activities and steps|
|Requirements · Specification |
Architecture · Design
Implementation · Testing
Deployment · Maintenance
|Agile · Cleanroom · Iterative |
RAD · RUP · Spiral
Waterfall · XP · Lean
Scrum · V-Model · TDD
|Configuration management |
Quality assurance (SQA)
User experience design
|Compiler · Debugger · Profiler |
GUI designer · IDE
Software can be developed for a variety of purposes, the three most common being to meet specific needs of a specific client/business (the case with custom software), to meet a perceived need of some set of potential users (the case with commercial and open source software), or for personal use (e.g. a scientist may write software to automate a mundane task). Embedded software development, that is, the development of embedded software such as used for controlling consumer products, requires the development process to be integrated with the development of the controlled physical product.
The need for better quality control of the software development process has given rise to the discipline of software engineering, which aims to apply the systematic approach exemplified in the engineering paradigm to the process of software development.
| ||This section does not cite any references or sources. |
Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2010)
- Market research
- Gathering requirements for the proposed business solution
- Analyzing the problem
- Devising a plan or design for the software-based solution
- Implementation (coding) of the software
- Testing the software
- Maintenance and bug fixing
There are significant advantages and disadvantages to the various methodologies, and the best approach to solving a problem using software will often depend on the type of problem. If the problem is well understood and a solution can be effectively planned out ahead of time, the more "waterfall" based approach may work the best. If, on the other hand, the problem is unique (at least to the development team) and the structure of the software solution cannot be easily envisioned, then a more "extreme" incremental approach may work best. A software development process is a structure imposed on the development of a software product. Synonyms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.
 Consistency in SoftwareIn order to ensure that software can evolve in a way that maintains its inherent multidimensionality, one must ensure that the different dimensions evolve together in a consistent manner.Software has too many dimensions to combine within a single framework, Not only do the different notations but they also do not interact hierarchically.A good mechanism should not be geared to a specific problem such as ensuring the consistency of a UML class diagram with the source code. Instead it should be flexible enough to handle the broad range of dimensions that are actually involved in software development.
 Software development topic
 MarketingThe sources of ideas for software products are legion. These ideas can come from market research including the demographics of potential new customers, existing customers, sales prospects who rejected the product, other internal software development staff, or a creative third party. Ideas for software products are usually first evaluated by marketing personnel for economic feasibility, for fit with existing channels distribution, for possible effects on existing product lines, required features, and for fit with the company's marketing objectives. In a marketing evaluatation generated by the marketing and development staff, the project should be pursued further. Pranay. 
In the book "Great Software Debates", Alan M. Davis states in the chapter "Requirements", subchapter "The Missing Piece of Software Development":methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations.
 See also
refer this link: http://en.wikipedia.org/wiki/Software_development