BibTex RIS Cite

Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği

Year 2011, Volume: 4 Issue: 1 - Volume: 4 Issue: 1, - , 24.06.2016

Abstract

Yazılım güvenilirliği pek çok açıdan yazılım geliştirmede önemli hale gelmektedir. Bu çalışma yazılımcıları yazılım güvenilirliği açısından temel konularda bilgilendirmeyi ve uygulama cesareti kazandırmayı hedeflemektedir. AbstractQuality Requirements for Software Architecture: Software ReliabilityQuality Requirements for Software Architecture: Software Reliability. The aim of this paper is to give the reader a better understanding of the importance of software reliability. Furthermore it focuses on the basics of software reliability, prediction and modeling reliability, collection of data and also the relationship between the software quality and software reliability.

References

  • IEEE Std. 610.12-1990, Standard Glossary of Software Engineering Terminology, New York, IEEE Standards Board.
  • Vouk, M.A., 2000. Software Reliability Engineering, 2000 Annual Reliability and Maintainability Sym.
  • Musa, J.D., 1987. Software Reliabilty Engineering, McGraw-Hill. [4] Ebert, C., Dumke, R., Bundschuh, M., Schmietendorf, A., 2005. Best Practices in Software Measurement, Berlin: Springer-Verlag.
  • Summerville, N., Basic Reliability, An introduction to Reliability Engineering, Author House, 2004.
  • IEEE Std 982.1-1988, Standard Dictionary of Measures to Produce Reliable Software, New York, IEEE Standards Board, 1988.
  • Fenton, N.E., Pfleeger, S.L., 1997. Software Metrics: A Rigorous and Practical Approach, 2. ed., Boston: PWS Publishing.
  • Pham, H., Zhang, X., 1999. A software cost model with warranty and risk cost, IEEE Transactions on Computers 48 (1), 71-75.
  • Musa, J.D., Iannino, A., Okumoto, K., 1987. Software Reliability, Singapore: McGraw-Hill.
  • Dalal, S.R., 2003. Software Reliability Models: A Selective Survey and New Directions, Handbook of reliability engineering, Hoang Pham (ed.), Springer- Verlag.
  • Pham, H., 2006. System Software Reliability, Springer-Verlag.
  • Wallace, D., Coleman, C., 2001. Hardware and Software Reliability (323-08), NASA Software Assurance Technology Center.
  • Stutzke, M.A., Smidts, C.S., 2001. A stochastic model of fault introduction & removal during software development, IEEE Transactions on Reliability 50 (2), 184-193.
  • Lyu, M.R., 2007. Software Reliability Engineering: A Roadmap, Future of Software Engineering.
  • IEEE Std. 1044-1993, IEEE Standard Classification for Software Anomalies, New York, IEEE Standards Board.
  • The Software Engineering Program, 2005. Software Measurement Aeronautics and Space Administration, NASA-GB- 001-94.
  • Hutcheson, NASA National M.L.,
  • Software Testing
  • Fundamentals, Wiley.
  • Ahern, D.M., Clouse, A., Turner, R., 2004. CMMI Distilled: A Practical Introduction to Integrated Process Improvement, 2. ed. Addison Wesley.
  • Jung, H., Kim, S., Chung, C., 2004. Measuring Software Product Quality: A Survey of ISO/IEC 9126, IEEE Software, 88-92, September/October 2004.
  • IEEE Std. 1061-1988, Standard for a Software Quality Metrics Methodology. Piscataway, NJ,: IEEE Standards Dept.

Quality Requirements for Software Architecture: Software Reliability

Year 2011, Volume: 4 Issue: 1 - Volume: 4 Issue: 1, - , 24.06.2016

Abstract

Quality Requirements for Software Architecture:
Software Reliability. The aim of this paper is to give
the reader a better understanding of the importance
of software reliability. Furthermore it focuses on the
basics of software reliability, prediction and
modeling reliability, collection of data and also the
relationship between the software quality and
software reliability.

References

  • IEEE Std. 610.12-1990, Standard Glossary of Software Engineering Terminology, New York, IEEE Standards Board.
  • Vouk, M.A., 2000. Software Reliability Engineering, 2000 Annual Reliability and Maintainability Sym.
  • Musa, J.D., 1987. Software Reliabilty Engineering, McGraw-Hill. [4] Ebert, C., Dumke, R., Bundschuh, M., Schmietendorf, A., 2005. Best Practices in Software Measurement, Berlin: Springer-Verlag.
  • Summerville, N., Basic Reliability, An introduction to Reliability Engineering, Author House, 2004.
  • IEEE Std 982.1-1988, Standard Dictionary of Measures to Produce Reliable Software, New York, IEEE Standards Board, 1988.
  • Fenton, N.E., Pfleeger, S.L., 1997. Software Metrics: A Rigorous and Practical Approach, 2. ed., Boston: PWS Publishing.
  • Pham, H., Zhang, X., 1999. A software cost model with warranty and risk cost, IEEE Transactions on Computers 48 (1), 71-75.
  • Musa, J.D., Iannino, A., Okumoto, K., 1987. Software Reliability, Singapore: McGraw-Hill.
  • Dalal, S.R., 2003. Software Reliability Models: A Selective Survey and New Directions, Handbook of reliability engineering, Hoang Pham (ed.), Springer- Verlag.
  • Pham, H., 2006. System Software Reliability, Springer-Verlag.
  • Wallace, D., Coleman, C., 2001. Hardware and Software Reliability (323-08), NASA Software Assurance Technology Center.
  • Stutzke, M.A., Smidts, C.S., 2001. A stochastic model of fault introduction & removal during software development, IEEE Transactions on Reliability 50 (2), 184-193.
  • Lyu, M.R., 2007. Software Reliability Engineering: A Roadmap, Future of Software Engineering.
  • IEEE Std. 1044-1993, IEEE Standard Classification for Software Anomalies, New York, IEEE Standards Board.
  • The Software Engineering Program, 2005. Software Measurement Aeronautics and Space Administration, NASA-GB- 001-94.
  • Hutcheson, NASA National M.L.,
  • Software Testing
  • Fundamentals, Wiley.
  • Ahern, D.M., Clouse, A., Turner, R., 2004. CMMI Distilled: A Practical Introduction to Integrated Process Improvement, 2. ed. Addison Wesley.
  • Jung, H., Kim, S., Chung, C., 2004. Measuring Software Product Quality: A Survey of ISO/IEC 9126, IEEE Software, 88-92, September/October 2004.
  • IEEE Std. 1061-1988, Standard for a Software Quality Metrics Methodology. Piscataway, NJ,: IEEE Standards Dept.
There are 21 citations in total.

Details

Other ID JA37HT55ZZ
Journal Section Makaleler(Araştırma)
Authors

Kaan Kurtel

Şaban Eren

Publication Date June 24, 2016
Published in Issue Year 2011 Volume: 4 Issue: 1 - Volume: 4 Issue: 1

Cite

APA Kurtel, K., & Eren, Ş. (2016). Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği. Türkiye Bilişim Vakfı Bilgisayar Bilimleri Ve Mühendisliği Dergisi, 4(1).
AMA Kurtel K, Eren Ş. Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği. TBV-BBMD. June 2016;4(1).
Chicago Kurtel, Kaan, and Şaban Eren. “Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği”. Türkiye Bilişim Vakfı Bilgisayar Bilimleri Ve Mühendisliği Dergisi 4, no. 1 (June 2016).
EndNote Kurtel K, Eren Ş (June 1, 2016) Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği. Türkiye Bilişim Vakfı Bilgisayar Bilimleri ve Mühendisliği Dergisi 4 1
IEEE K. Kurtel and Ş. Eren, “Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği”, TBV-BBMD, vol. 4, no. 1, 2016.
ISNAD Kurtel, Kaan - Eren, Şaban. “Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği”. Türkiye Bilişim Vakfı Bilgisayar Bilimleri ve Mühendisliği Dergisi 4/1 (June 2016).
JAMA Kurtel K, Eren Ş. Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği. TBV-BBMD. 2016;4.
MLA Kurtel, Kaan and Şaban Eren. “Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği”. Türkiye Bilişim Vakfı Bilgisayar Bilimleri Ve Mühendisliği Dergisi, vol. 4, no. 1, 2016.
Vancouver Kurtel K, Eren Ş. Yazılım Mimarisinin Kalite Gereksinimleri:Yazılım Güvenilirliği. TBV-BBMD. 2016;4(1).

Article Acceptance

Use user registration/login to upload articles online.

The acceptance process of the articles sent to the journal consists of the following stages:

1. Each submitted article is sent to at least two referees at the first stage.

2. Referee appointments are made by the journal editors. There are approximately 200 referees in the referee pool of the journal and these referees are classified according to their areas of interest. Each referee is sent an article on the subject he is interested in. The selection of the arbitrator is done in a way that does not cause any conflict of interest.

3. In the articles sent to the referees, the names of the authors are closed.

4. Referees are explained how to evaluate an article and are asked to fill in the evaluation form shown below.

5. The articles in which two referees give positive opinion are subjected to similarity review by the editors. The similarity in the articles is expected to be less than 25%.

6. A paper that has passed all stages is reviewed by the editor in terms of language and presentation, and necessary corrections and improvements are made. If necessary, the authors are notified of the situation.

0

.   This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.