Fault prevention includes iterative refinement of the system requirements and engineering software specifications with modeling, verifiable design techniques, and best-of-breed coding practices. Prevention occurs during the product development phases of a project where the
Fault forecasting is the predictive approach to software reliability engineering. Forecasting is a front-end product development life cycle exercise. It is done during system exploration and requirements definition. Mature development organizations use fault forecasting as part of
Software reliability has been listed as a key quality measure for as long as software engineering has been defined. Figure 1 represents the quality factor topology as presented by McCall, Richards, and Walters in their 1977 work. These factors are discussed in this blog. Particular
The SWEBOK is focused on the body of knowledge particularly for software engineering. The 34 competencies for the software project management certification program emphasize the management of software development projects. As can be seen from the six segments
Other sections in this blog refer to the SEI CMM, particularly with regard to the way that model supports the blog topic - life cycles, peer reviews, metrics, etc. The CMM is divided into five maturity levels. They are well-defined evolutionary plateaus aimed toward achieving a
The software engineering body of knowledge is an all-inclusive term that explains the sum of knowledge within the profession of software engineering. Since it is n not possible to put the full body of knowledge of even an emerging discipline, such as software engineering, into a
To define a software we need some historical context. The term software engineering (see Box 1, Box 2, and Box 3) was not coined until 1968, 18 years after the mid-point of the twentieth century, and one year before a human walked on the moon.
Software engineering is not computer science nor is it merely rendering an idea into an abstract computer programming language. First coined in 1968, software development is the youngest recognized branch of engineering: "The phrase 'software engineering' was deliberately
Developing a risk management plan is just a matter of following the following five steps. By beginning with the previously defined 12 risk categories, the analyst ranks and sorts the risks into a manageable set. The plan then is a direct result of the risk identification, categorization, and prioritization processes.