Design Fault Management using DS Fault Scrutinize and DCE Diversy Model

Authors

  • Jigna B. Prajapati BCA, AMPICS, Ganpat University, Gujarat, India
  • N. K. Modi S.V.Institute of Computer Studies Kadi, Gujarat, India

DOI:

https://doi.org/10.37591/josettt.v1i3.208

Abstract

Day by day the numbers of software systems are increasing in IT Industry, but the successful software developing is very low as per enrollment of system. There are various crucial reasons behind it. One of them is fault reside or arise within system. Faults can reside and arise anywhere anytime. In this research, the requirement writing to design creation of system is represented with few supported elements to enhance the basic SDLC phases. Firstly, this research focuses on system development life phase by embedding with fault phase. The Design, Code and Environment (DCE) diversy Model will manage the faults at specific phase. DCE diversy Model will not pass faults in next phase. On occurrence of faults it will follow specific diversy. Further in this research, enlightening about the importance of design and specification along with design issues. An effective and precise specification of requirements is indispensable for the appropriate system design. Design faults must be identified before testing. Faulty design should not carry to code section. Now, the exploration of design diversy and monitoring the design specification of system by Requirements to Design Specification (DS) Fault scrutinize model. It uses various listener and logs with fault listener and fault log to manage the faults within system.

Keywords: Fault, design, diversy, specification, system life phase

References

Failure Rate, IT Project Failure Rate: http://www.it-cortex.com/Stat_Failure_Rate.htm#The Robbins-Gioia Survey, 2001.

Fact and Figures, Available from: http://calleam.com/WTPF/?page_id=1445

IEEE Standard Glossary for Software Engineering Terminology, ANSI/IEEE Std 610.12-1990, 1–84p.

Senn J. A., Analysis and Design of Information Systems, 4th Ed. Chap 3, 4McGraw Hill: 56–76p.

TechTarget, Available from: http://searchvb.techtarget.com/sDefinition/0 sid8_gci7550 68,00. html, February 2004.

D. Howe (Ed.), The Free On-line Dictionary of Computing, http://foldoc. doc.ic.ac.uk/ foldoc/foldoc.cgi? query= lifecycle, 1996.

NIH System Development Life Cycle (SDLC) IT Security Activities Matrix, Viewed on http://irm.cit.nih. gov/security/nih-sdlc.html, December 2006.

DOJ, The Department of Justice Systems Development Life Cycle Guidance Document, Viewed on http://www.usdoj.gov/jmd/irm/lifecycle/table.htm, January 2003.

Cohen S., A Multi-Tier System Development Life Cycle Model for Off-the-Shelf Software with Market and Organizational Effects, [Ph.D.] Dissertation, Faculty of Industrial Engineering and Management, Technion, Haifa, Israel, 2007.

Basem Y. Alkazemi, On Verification of Software Components, Int. J. Softw. Eng. Appl. (IJSEA), 2012; 3(5): 1–13p.

Catal C., Diri B., Software Fault Prediction with Object Oriented Metrics Based Artificial Immune Recognition System, PROFES, LNCS 4589, 2007, 300–314p.

Grottke M., Trivedi K. S., A Classification of Software Faults, Sixteenth International IEEE Symposium on Software Reliability Engineering, 2005, 4.19–4.20p.

Chillarege R., What Is Software Failure? IEEE T. Reliability, 1996; 45(3): 354–355p.14. Westland J. C., The Cost of Errors in Software Development: Evidence from Industry, J. Syst. Softw. 2002; 62: 1–9p.

Hiller M., Jhumka A., Suri N., et al. An Approach for Analyzing the Propagation of Data Errors in Software, Architecture Design for Soft Errors. Morgan Kaufmann Publishers Inc., 2008.

Roman G. C., A Taxonomy o f Current Issues in Requirements Engineering, IEEE Comp. 1985; 18(4): 14–23p.

Jones C. B., Systematic Software Development Using VDM, Prentice Hall International, 1986.

Georgiadou E., Software Process and Product Improvement: A Historical Perspective, Cybern. Syst. Anal. 2003; 39(1): 125–142p.

Downloads

Published

2014-12-01

Issue

Vol. 1 No. 3 (2014)

Section

Research Articles

License

Declaration and Copyright Transfer Form

(to be completed by authors)

I/ We, the undersigned author(s) of the submitted manuscript, hereby declare, that the above manuscript which is submitted for publication in the STM Journals(s), is not published already in part or whole (except in the form of abstract) in any journal or magazine for private or public circulation, and, is not under consideration of publication elsewhere.

  • I/We will not withdraw the manuscript after 1 week of submission as I have read the Author Guidelines and will adhere to the guidelines.
  • I/We Author(s ) have niether given nor will give this manuscript elsewhere for publishing after submitting in STM Journal(s).
  • I/ We have read the original version of the manuscript and am/ are responsible for the thought contents embodied in it. The work dealt in the manuscript is my/ our own, and my/ our individual contribution to this work is significant enough to qualify for authorship.
  •  I/We also agree to the authorship of the article in the following order:

Author’s name                                    

 

1. ________________

2. ________________

3. ________________

4. ________________

 

We  Author(s) tick this box and would request you to consider it as our signature as we agree to the terms of this Copyright Notice, which will apply to this submission if and when it is published by this journal.