In order to improve the quality and stability of software, software quality factors must be considered in the early stages of system development as in [1]. Moreover, in the design stage, we use Failure modes and effects analysis (FMEA) to analyze the abnormal situation. Different to traditional exception handling, FMEA is a systematic way of identifying failure modes of a system, and take actions to eliminate or reduce failures before the failures occur as in [2]. Consequently, the cost and rework of software development could be reduced, and the defect removal efficiency (DRE) could be increased. Based on McCall’s software quality factors and FMEA, we derive the quality problems that may be encountered in the software development stage and the failure scenarios that may be confronted during the operation phase. Furthermore, we analyze the failure mode and calculate their risk priority number (RPN). Following the systematic engineering thinking as in [3], we conclude the early design issues, and propose the built-in features which are worth to be designed in the early stage. Finally, we illustrate the multiple effects after its implementation.
[1]
Alain Abran,et al.
The Guide to the Software Engineering Body of Knowledge
,
1999,
IEEE Softw..
[2]
C A Anderson,et al.
The time is now.
,
2017
.
[3]
Jez Humble,et al.
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
,
2010
.
[4]
Panos Markopoulos,et al.
Collaboration in Creative Design
,
2016,
Springer International Publishing.
[5]
P Haapanen,et al.
Failure mode and effects analysis of software-based automation systems
,
2002
.
[6]
Leonardo Solarte-Pazos,et al.
The body of knowledge of the Project Management Institute-PMBOK® Guide, and the specificities of project management: a critical review
,
2010
.
[7]
Gregor Kiczales,et al.
Aspect-oriented programming
,
1996,
CSUR.
[8]
Joseph P. Cavano,et al.
A framework for the measurement of software quality
,
1978
.