Information Technology Reference
In-Depth Information
memory
12
. The DFSS team should document the SFMEA and store it
in a widely acceptable format in the company in both electronic and
physical media.
Software FMEA return on investment (ROI) is calculated in terms of a cost
avoidance factor—the amount of cost avoided by identifying issues early in the
software life cycle. This is calculated by multiplying the number of issues found
by the software cost value of addressing these issues during a specific DFSS phase.
The main purpose of doing a SFMEA is to catch defects in the associated DFSS
phases (i.e., catching requirements defects in the identify phase, design defects in the
conceptialize phase, and so on).
The ROI of SFMEA is many folds: more robust and reliable software, better
quality of software, focus on defect prevention by identifying and eliminating defects
in the software early developmental phases to help drive quality upstream, reduced
cost of testing when measured in terms of
cost of poor quality
(COPQ). The proactive
identification and elimination of software defects saves time and money. If a defect
cannot occur, then there will be no need to fix it. In addition, dividends can be gained
with enhanced productivity by way of developing a higher quality software in less
time—a competitive edge. Prioritization of potential failures based on risk helps
support the most effective allocation of people and resources to prevent them.
Because the SFMEA technique requires detailed analysis of expected failures,
it results in a complete view of potential issues, leading to more informed and
clearer understanding of risks in the software. Engineering knowledge persists in
future software development projects and iterations. This helps an organization avoid
relearning what is already known, guide design and development decisions, and gear
testing to focus on areas where more testing is needed.
Practically, the potential time commitment required can discourage satellite DFSS
team members' participation. Focus area documentation does not exist prior to the
SFMEA session and needs to be created, adding to the time needed. Generally,
the more knowledgeable and experienced the session participants are, the better the
SFMEA results. The risk is that key individuals are often busy and, therefore, are
unable or unwilling to participate and commit their time to the process.
16.4
SOFTWARE QUALITY CONTROL AND QUALITY ASSURANCE
Control plans are the means to sustain any software DFSS project findings. However,
these plans are not effective if not implemented within a comprehensive software
12
Companies should build a “Corporate Memory” that will record the design best practices, lesson learned,
transfer functions and retain what corrective actions were attempted and what did and did not work and
why. This memory should include pre-and postremedy costs and conditions including examples. This is a
vital tool to apply when sustaining good growth and innovation strategies and avoiding attempted solutions
that did not work. An online “Corporate Memory” has many benefits. It offers instant access to knowledge
at every level of management and design staff.
Search WWH ::
Custom Search