PPlanning is an objective of each and every activity, where we want to discover things that belong to the project. The most important task of creating a software program is extracting the requirements or requirement analysis. Clients have a typical abstract idea of what they want as an end result but do not know what software should they go for. Skilled and experienced software engineers recognize incomplete, ambiguous, or even contradictory requirements at this point. Demonstrating live codes may help reduce the risk of their requirements being incorrect.
Once the general requirements are gathered from the client, an analysis regarding the scope of development should be determined and clearly stated. This is called a scope document.
Certain functionality may be out of scope from the project as a function of cost or as a result of unclear requirement at the start of development. If the development is done externally, this document can be considered a legal document so that if there are any disputes or any ambiguity of what was promised to the client can be clarified.
IOnce the requirements are established, the design of software can be established in a software design document. This involves a pre-liminary, or high-level design of the main modules with an overall picture (such as a block diagram) of how the parts fit together. The language, operating system, and hardware components should all be known at this time. Then a detailed or low-level design is created, perhaps with prototyping as proof-of-concept or to firm up requirements.
Implementation is the part of the process where software engineers actually program the code for the project.
T
Software testing is an integral and important phase of the software development process. This part of the process ensures that defects are recognized as soon as possible. In some processes, generally known as test-driven development, tests may be developed just before implementation and serve as a guide for corrections during implementation.
Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout development. This may also include the writing of an API, be it external or internal. The software engineering process chosen by the development team will determine how much internal documentation (if any) is necessary. Plan-driven models (e.g., Waterfall) generally produce more documentation than Agile models.
DProject Development starts directly after the code is appropriately tested, approved for release, and distributed into a production environment. This may involve installation, customization (such as by setting parameters to the customer values), testing, and possibly an extended period of evaluation.
Maintaining and enhancing software to cope up with newly discovered flaws or requirements can take substantial time and effort, as missed requirements may force re-design of software.
