This entry identifies the factors that control software reliability and the approaches that are needed to achieve desired reliability targets. Common reliability measures are defined. The factors that impact defect density and defect finding rates are discussed and software reliability growth modeling is introduced. Both test-timeand test-coverage-based models are introduced. Modeling for secur...

Software Risk Management is a critical area among the nine knowledge areas used in Software project management. This paper describes different frameworks and paradigms used in risk management. A framework or a model is decided for managing risks in a project. This model acts as a tool for efficient risk management. It has basic steps of Risk identification, risk planning, risk assessment, risk ...

By ‘believable software management’ we shall understand a “state of software development” (as an established practice) in which all developers, that is, programmers and managers at all levels, in their conscience, are confident that everybody is working according to state-of-the-art methods. In this Software Engineering Encyclopedia entry on ‘believable software management’ we shall therefore s...

It is difficult to imagine our world without software. Since software is so ubiquitous, we need to stay in control. We have to make sure that the systems and their software run as we intend – or better. Only if software has the right quality, we will stay in control and not suddenly realize that things are going awfully wrong. Software quality management is the discipline that ensures that the ...

In order to organize and manage a software development project successfully, one must combine specific knowledge, skills, efforts, experience, capabilities, and even intuition. They are all necessary in order to be able answer questions such as: What artifacts to manage and control during software development? How to organize the development team? What are the indicators and measures of the pro...

This paper describes the software system being developed for Cm*, a distributed mUlti-microprocessor. This software provides for flexible, yet controlled, sharing of code and data via a capability addressed virtual memory, creation and management of groups of processes known as task forces, and efficient interprocess communication. Both the software and hardware are currently under construction...

This paper presents a holistic vision of the risk-based methodologies for Software Risk Management (SRM) developed at the Software Engineering Institute (SEI). SRM methodologies address the entire life cycle of software acquisition, development, and maintenance. This paper is driven by the premise that the ultimate efficacy of the developed methodologies and tools for software engineering is to...

Project Management (PM) principles are rapidly changing due to business globalization and information technology (IT) advances which support distributed and virtual project teams. Traditional PM focuses on a single project at a single location [11] and is more concerned with project inputs and outputs than with the project work itself [42]. Traditional PM emphasizes scheduling, planning and tra...

The Cleanroom software developmentThis paper is a report of an application of the meth-approach is intended to produce highly reliableod described in [Albrecht83].software by integrating formal methods for specification and design, nonexecution-based program de-Berger85velopment, and statistically based independent testing. In an empirical study, 15 three-person teams<lb...

W henever I start a new software project, I look at the infrastructure the team has in place for doing things like setting up a development workspace, building, doing version management, and so on—the things that belong to the larger topic known as software configuration management (SCM). I worry about these elements because, in a sense, I’m lazy. I want to direct my energies into producing cod...