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.
The project risk management plan models 12 categories of potential risk to any specific project: 1. Mission and goals. Any project accepted must fit within the organization's mission and goals. Projects accepted that do not fit within the organization create tensions that affect all projects. For instance, suppose an organization exists whose mission is to develop software for
The Carnegie Mellon University's Software Engineering Institute developed a software risk model based on the Shewhart-Deming cycle. The model provides information and feedback, internal and external to the project, on the risk activities, current risks, and emerging risks. Figure
A number of models of risk management, readily usable by project managers, have been identified by the Project Management and Software Engineering Institutes and through the groundbreaking software engineering work of Barry Boehm.
Risk management is about understanding the internal and external project influences that can cause project failure. Once the project plan is built, a risk analysis should be carried out. The result of the initial risk analysis is a risk plan that should be reviewed frequently and adjusted