What is a Development Process we follow ?
A software development process of life is a structured imposed on development of software product.There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.  
Processes :
The Capability Maturity Model (CMM) is one of the leading models. Independent assessments can be used to grade organizations on how well they create software according to how they define and execute their processes There are dozens of others, with other popular ones being ISO 9000, ISO 15504, and Six Sigma.
Process Activities/Steps
Requirements Analysis : Extracting the requirements of a desired software product is the first task in creating it. While customers probably believe they know what the software is to do, it may require skill and experience in software engineering to recognize incomplete, ambiguous or contradictory requirements.
Specification : Specification is the task of precisely describing the software to be written, in a mathematically rigorous way. In practice, most successful specifications are written to understand and fine-tune applications that were already well-developed, although safety-critical software systems are often carefully specified prior to application development. Specifications are most important for external interfaces that must remain table.
Software architecture : The architecture of a software system refers to an abstract representation of that system. Architecture is concerned with making sure the software system will meet the requirements of the product, as well as ensuring that future requirements can be addressed
Implementation : Reducing a design to code may be the most obvious part of the software engineering job, but it is not necessarily the largest portion.
Testing : Testing of parts of software, especially where code by two different engineers must work together, falls to the software engineer.
Training and Support : A large percentage of software projects fail because the developers fail to realize that it doesn't matter how much time and planning a development team puts into creating software if nobody in an organization ends up using it. People are occasionally resistant to change and avoid venturing into an unfamiliar area, so as a part of the deployment phase, its very important to have training classes for the most enthusiastic software users (build excitement and confidence), shifting the training towards the neutral users intermixed with the avid supporters, and finally incorporate the rest of the organization into adopting the new software. Users will have lots of questions and software problems which leads to the next phase of software.

Creating A Patch :
When a contributor makes a change to the outputs of a project they do so by editing files available in a version control system. A version control system tracks changes to documents and source code over time. Using one makes creating a patch simple because you can always refer to the version of the source code the changes are based upon. However, there are a few steps that should be taken to maximize the chances of the patch being accepted by the maintainers of a project.

It is important that the contributor ensures that the patch complies with any documentation and coding standards adopted by the project. It is also critical to thoroughly test changes against any test suites the project provides.

Applying A Patch :
Skilled developers can read patch files and understand their implications without actually applying them to the code base. This makes it easy to provide rapid feedback to the contributor. Should the project maintainer feel that the patch looks like a solid contribution, they will apply it to their local development copy and test it. Since a good contribution will already have undergone extensive testing, this should be a simple matter for the maintainer. However, mistakes can be made and so further testing should always be carried to apply a patch is ready to be applied to the version control tree, the maintainer will ‘commit’ it. That is, they will make it available in the public version control system.

It is important that the contributor ensures that the patch complies with any documentation and coding standards adopted by the project. It is also critical to thoroughly test changes against any test suites the project provides.
Is It Really That Simple?
For things to work as smoothly as described above, it is important that contributors create patches against a recent version of the project outputs (usually software code), preferably the most recent version, from the ‘head’ of the version control system. This is because, as time passes, code will evolve. If the code in question has changed since the contributor downloaded their copy, applying the patch may not be as simple as described above, since there may be conflicting changes. Since users often want to work with a stable version of the code in a production environment, it is possible that the initial changes were not made against the latest development version of software.

Having a development environment deployed like this has the added benefit of allowing the organization to test current development versions in a non-critical environment. This, in turn, helps with the decision to upgrade or not when a new release is available
© 2016 Mozire Technologies . All rights reserved. No part of this site may be reproduced without our written permission.
Mozire Technologies
Ph -  852 - 2799 - 8938
Email Id -

Mozire simplifies IT management with affordable software service that offers the ease of use SMBs need and the powerful features the largest enterprises demand.

It is a trust that our products to manage their network securely and finding their flaws and rectifying them