subject: Manifestation Of The It Development, Ideal For A Planned And Structured Process [print this page] IT development (also known as application development, software design, software development, enterprise application development, platform or development) is a software product development. Can be used the term " IT development" computer programming activities, which is the process of writing and maintaining code, but a broader sense to include all involved including the concept of the desired software to the final manifestation of the software, ideal for a planned and structured process. Thus, software development may include research, new development, prototyping, modification, reuse, conversion, maintenance, or any other activities for software products.
The software can be developed for different purposes, the three most prevalent of the client / business case for custom software) in order to meet the special needs to meet the perceived need, although the potential user group with the case of commercial and open source software), or for personal use (e.g., scientist can write software to automate mundane tasks). Embedded software development, which is used to control consumer products, such as embedded software development requires to be integrated with controlled physical product development process.
Better software development process quality control resulted in the need for software engineering, which aims - to apply a systematic approach to illustrate the paradigm of software engineering process discipline.
There are several different approaches to software development, like the various political parties toward governing a country views. Some develop a more structured, engineering approach to developing business solutions, while others may take a more incremental approach, the software evolves, it is a coherent piece. Most methodologies share some combination of the following software development phases:
Market Research
The proposed collection of business requirements
The analysis of this problem
Preparation of a plan or design software-based solution
The software implementation (coding)
Software Testing
Deployment
Maintenance and debugging
These stages are often referred to as the software development lifecycle, or SDLC. Different approaches to software development may carry out these various phases of an order or for more or less time at different stages. Each stage of software development documentation for the level of detail may vary. These steps may be carried out in turn (based approach "waterfall"), or they can be repeated over various cycles or iterations more "extreme" approach). More extreme approach usually involves less planning and documentation of time spent and more time coding and automated testing. More "extreme" approaches also promote continuous testing throughout the development life cycle, as well as employment (or error) the product all the time. More structured or "waterfall" based approaches attempt to assess risk and to develop a comprehensive plan for the software, before the implementation (coding), and to avoid major design changes and re-coding the software development life cycle planning stages.
There are various methods of material advantages and disadvantages, and the best way to solve the problem using software will often depend on the type of problem. If the problem is well understood and the solution can be efficiently planned in advance, the more "waterfall" approach may work best. If, on the other hand, the problem is unique (at least the development team) and software solution structure can not easily be imagined, "extreme" incremental approach may work best. The software development process is a framework for software product development. Synonyms include software life cycle and software process. There are several models of such processes, each describing approaches to different tasks or activities that take place during the process.
Consistency of software
To ensure that the software can be developed in such a way that maintains its characteristic more to ensure that the different dimensions evolve consistently. The software has too many aspects of the general coordinate system. A good mechanism should be geared to a specific problem, such as ensuring compatibility with a UML class diagram of the code. Instead, it should be flexible enough to handle a wide range of dimensions that are actually involved in developing software.
