A software development process is a structure imposed on the development of a software product.

Process being a fundamental tool for carrying out community consensus and facilitating very large number of people to work together on a collaborative project. On the assumption and subject to endless debate that a methodical approach to software development results in fewer defects and, therefore, ultimately provides shorter delivery time and better value. The necessity of selecting and following a formal process for software development is to provide desired discipline to deliver a quality product for business success and to avoid wastage of time, money, demoralization in developers etc. Domain Analysis Often the first step in attempting to design a new piece of software, whether it be an addition to an existing software, a new application, a new subsystem or a whole new system, is what is generally referred to as "Domain Analysis". Assuming that the developers (including the analysts) are not sufficiently knowledgeable in the subject area of the new software, the first task is to investigate the so-called "domain" of the software. The more knowledgeable they are about the domain already, the less the work required. Another objective of this work is to make the analysts who will later try to elicit and gather the requirements from the area experts or professionals, speak with them in the domain's own terminology and to better understand what is being said by these people. Otherwise they will not be taken seriously. So, this phase is an important prelude to extracting and gathering the requirements. Software Elements Analysis The most important task in creating a software product is extracting the requirements. Clients typically know what they want, but not what software should do, while incomplete, ambiguous or contradictory requirements are recognized by skilled and experienced software engineers. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect. Specification Specification is the task of precisely describing the software to be written, possibly in a 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 stable. Implementation (or coding) 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

People are occasionally resistant to change and avoid venturing into an unfamiliar area so. Software 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. Documentation An important (and often overlooked) task is documenting the internal design of software for the purpose of future maintenance and enhancement. Most maintenance is extending systems to do new things. Users will have lots of questions and software problems which lead to the next phase of software. About ? of all software engineering work is maintenance. Not only may it be necessary to add code that does not fit the original design but just determining how software works at some point after it is completed may require significant effort by a software engineer. especially where code by two different engineers must work together falls to the software engineer. as a part of the deployment phase. A small part of that is fixing bugs. it is 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. but this statistic can be misleading. Documentation is most important for external interfaces. and finally incorporate the rest of the organization into adopting the new software.Testing of parts of software. which in many ways can be considered new work . Maintenance Maintaining and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software.

money. a new subsystem or a whole new system. In practice. Another objective of this work is to make the analysts who will later try to create and gather the needs of the area experts or professionals. The need to select and follow a formal process for software development is to provide the discipline to deliver a quality product for business success and avoid wasting time. speak with them in the terminology of the field and to better understand what is said by these people. Frequently demonstrate direct code can help reduce the risk that the requirements are not correct. the less work required. is what is generally referred to as "Domain Analysis ". Specifications are most important for external interfaces that must remain stable. Usually. finally gives the shortest delivery time and better value. clients know what they want but not what software should do. Process to be a fundamental tool for achieving community consensus and facilitate large numbers of people to work together on a collaborative project. this phase is an important prelude to extracting and gathering requirements. therefore. Otherwise. ambiguous or contradictory are recognized by skilled and experienced software engineers.A software development process is a structure imposed on the development of a software product. a new application. etc. Implementation (or coding) Reducing a design code may be the most visible part of the software engineering job. the demoralization of developers. Test . Elements of Analysis Software The most important task in creating software involves extracting the requirements. Assuming that developers (including analysts) are not sufficiently informed about the subject matter of the new software. Domain Analysis Often the first step in trying to design new software. perhaps in a rigorous manner. the first task is to investigate the so-called "domain" software. In the event and the subject of endless debates that a methodical approach to software development results in fewer defects and. but it is not necessarily the most part. they will not be taken seriously. an addition to existing software. most successful specifications are written to understand and refine the applications that were already well advanced. even if critical software systems are often carefully defined before implementation. Specification Specification is the task of precisely describing the software to write. The more sophisticated than they are already on the field. Thus. then that needs incomplete.

2. Documentation An important task (and often neglected) is documenting the internal design of software for future maintenance and improvement. Users will have many questions and software problems that lead to the next phase of the software. and finally add the rest of the organization by adopting the new software.Test pieces of software. 4. Most maintenance is extending systems to do new things. Not only can it be necessary to add code that does not match the original design but just determining how software works at some point after it is completed may require significant effort by a software engineer. People are sometimes resistant to change and avoid venturing into an unfamiliar area. 5. shifting the training towards the neutral users mixed with fervent supporters. 3. especially when code from two different engineers must work together to grave software engineer. A small part of that is fixing bugs. Maintenance Maintain and improve the software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software. it is very important to have training courses for software users the most enthusiastic (create enthusiasm and confidence). which in many respects can be considered as new work 1. Software training and support A high percentage of projects fail because software developers fail to realize that it does not matter how much time and planning a development team puts into creating software if nobody in organization ends up using it. so as part of the deployment phase. but this statistic can be misleading. What (Analysis) How (Design) Do It (Implementation) Test (Testing and Debugging) Use (Operation or Deployment) Maintain (Refinement) . Documentation is most important for external interfaces. 6. About? all software engineering work is maintenance.

Sign up to vote on this title
UsefulNot useful