UDK УДК 004.41(075.8) Vestnik SibGAU. 2014, No. 3(55), P. 78–92
ANALYSIS OF PROBLEMS IN THE RESEARCH AREA OF SOFTWARE RELIABILITY: A LOT OF STAGES AND ARCHITECTURAL ASPECT
I. V. Kovalev
Siberian State Aerospace University named after academician M. F. Reshetnev 31, Krasnoyarsky Rabochy Av., Krasnoyarsk, 660014, Russia E-mail: kovalev.fsu@mail.ru
In the survey, it is shown that estimation and reliability analysis should be performed at each step, create a failover. Due to the fact that there is no single approach, methods and parameters for estimating the reliability of Software, there are many models and algorithms, tested virtually, but has several disadvantages. The main drawback of all mod-els is "specialization". Models are always tied to any one phase of software development, and sometimes have a purely theoretical value due to the fact that they must be used the data obtained at other stages of development, and the au-thors of such models usually consider this fact of secondary importance. The most promising approach is aimed at creating some hybrid model, which includes all the advantages of a well-validated models and algorithms. Existing models and algorithms need to be modified so that the output of one model became the input for the other; to provide a unifying parameters, units of measure conversion, normalization of data and satisfying the current requirements and trends, such as object-oriented analysis and programming. From this re-view we can see that it is very important to use as much a priori information before beginning each phase of creation, as this will provide the most appropriate and accurate results. The analysis of methods, models and methodologies in the field of creation of reliable, fault-tolerant (Software) is carried out. Attempts to systematize and unify the existing methodology are made. The multiple steps involved in the creation and architectural aspect within the entire life-cycle fault-tolerant software are taken into account.
Software reliability, software architecture, development stage, resiliency, life cycle.
References

1. Lipaev V. V. Obespechenie kachestva programmnyh sredstv [Quality assurance software]. Moscow, Nauka Publ., 2001, 380 p.

2. Lipaev V. V. Nadezhnost' programmnyh sredstv. [The reliability of software]. Moscow, Nauka Publ., 1998.

3. Lyu M. R. Software Fault Tolerance. Edited by Michael R. Lyu Published by John Wiley & Sons Ltd, 1996.

4. Kovalev I. V., Zolotarjov V. V., Zhukov V. G., Zhukova M. N. [A method of constructing models of security of automated systems]. Programmnye produkty i sistemy. 2012, no. 2, p. 16. (In Russ.)

5. Avizhenis A. N., Lapri. Zh.-K. [Dependable computing: from ideas to implementation projects]. TIIER, 1986., vol. 74, no. 5, p. 8–21. (In Russ.)

6. Avizienis A. The N-Version approach to fault-tolerant software. IEEE Trans. on Software Engineering. 1985, Vol. 11, no. 12, p. 1491–1501.

7. Tai A. Performability Enhancement of Fault-Tolerant Software. IEEE Trans. on Reliability. 1993, Vol. 42, no. 2, p. 227–237.

8. Lipaev V.V. Testirovanie komponentov i kompleksov programm [Testing of components and systems programs]. Moscow, SINTEG Publ., 2010, 400 p.

9. Bojem B. Harakteristiki kachestva programmnogo obespechenija [Characteristics of software quality]. Moscow, Mir Publ., 1981, 208 p.

10. Bojem B. U. Inzhenernoe proektirovanie programmnogo obespechenija [Engineering design software]. Moscow, Radio i svjaz Publ., 1985, 512 p.

11. Boehm B. W. Information Processing. Data Automation Implications of Air Force Command and Control Requirements in the 1980’s (CCPI – 1985), Vol. I: Highlights, Report SAMSO/XRS-71-1, U.S. Air Force Systems Command (NTIS: AD 900031L), Los Angeles, CA, 1982.

12. Ashrafi N. Optimization Models for Selection of Programs. Considering Cost & Reliability. IEEE Transaction on reliability. 1992, Vol. 41, no 2, p. 281–287.

13. Zahedi F. Software reliability allocation based on structure, utility, price, and cost. IEEE Trans. on Software Engineering, April 1991,Vol. 17, no. 4, p. 345–356.

14. Lyu M. Software diversity metrics and measurements. IEEE COMPSAC 1992. 1992 Chicago, p. 69–78.

15. Elmendorf W. Fault-tolerant programming. In Digest of 2-nd FTCS. June 1972, p. 79–83.

16. Lipaev V. V. Jekonomika proizvodstva slozhnyh programmnyh produktov [The economy of the production of complex software products]. Moscow, SINTEG Publ., 2008, 432 p.

17. Lipaev V. V. Tehnologija proektirovanija kompleksov programm ASU [Design technology software systems ACS]. Moscow, Radio i svjaz Publ., 1983, 264 p.

18. Lipaev V. V. Testirovanie programm [Testing programs] Moscow, Radio i svjaz Publ., 1986, 234 p.

19. Kovalev I. V. Sistema mul'tiversionnogo formirovanija programmnogo obespechenija upravlenija kosmicheskimi apparatami. Dis. dok. tehn. nauk. [System multiversioned views of the formation of the software control of spacecraft. Dr. techn. sci.diss]. Krasnojarsk, KGTU, 1997. 228 p.

20. Kovalev I. V. [Multiversioned views method for increasing software reliability information and telecommunication technologies in corporate structures]. Telekommunikacii i informatizacija obrazovanija. 2003, no. 2, p. 50–55. (In Russ.)

21. Kovalev I. V., Dgioeva N. N., Slobodin M. Ju. The mathematical system model for the problem of multi-version software design. Mezhdunarodnaja konferencija po modelirovaniju i imitacii MS'2004 AMSE. International Conference on Modelling and Simulation, MS'2004. AMSE, French Research Council, CNRS, Rhone-Alpes Region, Hospitals of Lyon. Lyon-Villeurbanne, 2004.

22. Kovalev I. V., Carev R. Ju., Kapulin D. V. Arhitekturnaja nadezhnost' programmnogo obespechenija informacionno-upravljajushhih system [Architectural software reliability information management systems]. Ministry of agriculture of the Russian Federation, Krasnoyarsk state agrarian University, Krasnoyarsk, 2011.

23. Kovalev I. V., Novoj A. V., Shtencel A. V. [Reliability estimation multiversioned views of software architecture, control systems and information processing.]. Vestnik SibGAU. 2008, no. 3 (20), p. 50–52. (In Russ.)

24. Kovalev I. V., Novoj A. V. [Calculation of reliability of fault-tolerant software architectures.]. Vestnik SibGAU. 2007, no. 4 (17), p. 14–17. (In Russ.)

25. Kovalev I. V., Carev R. Ju., Zav'jalova O. I. [Analysis of architectural software reliability information management systems]. Pribory. 2010, no. 11, p. 24–26. (In Russ.)

26. Antamoshkin A. N., Kovalev I. V., Carev R. Ju. Matematicheskoe i programmnoe obespechenie otkazoustojchivyh sistem upravlenija i obrabotki informacii [Mathematical and software fault-tolerant control systems and information processing]. Ministry of agriculture of the Russian Federation, Krasnoyarsk state agrarian University, Krasnoyarsk, 2011.

27. Choi J. G. Reliability Estimation of nuclear digital I&C systems using Software Functional Block Diagram and control flow. FastAbstract ISSRE Copyright. 2000.

28. Berman O. Choosing an Optimal Set of Libraries. IEEE Transaction on reliability. June 1996, vol. 45, no 2, p. 303–307.

29. Choi J. G. Reliability Estimation of nuclear digital I&C systems using Software Functional Block Diagram and control flow. FastAbstract ISSRE Copyright. 2002.

30. Costa D. On the Extention of Exception to Support Software Faults Models. FastAbstract ISSRE Copyright. 2000.

31. David Ph. Development of a fault tolerant computer system for the Hermes Space Shuttle. IEEE Trans., 1993, p. 641–648.

32. Dunham J. R. Eds. Production of reliable flight crucial software: Validation method research for fault-tolerant avionics and control systems sub-working-group. NASA Conf. Pub. 2222, NASA, 1985.

33. Grams T. The Poverty of Reliabiliy Growth Models. FastAbstract ISSRE Copyright 1999.

34. Goseva-Popova K. How Different Architecture Based Software Reliability Models are Reealated. FastAbstract ISSRE Copyright. 2000.

35. Hamlet D. Foundational Theory of Software Component. FastAbstract ISSRE Copyright 2000.

36. Hecht H. Fault tolerant software. IEEE Trans. Reliability. 1979, vol. 28, p. 227–232.

37. Hui-Qun Z. A. New Method for Estimating the Reliability of Software System Based on Components. FastAbstract ISSRE and Chillarege Corp. Copyright. 2001.

38. Hudak J. Evaluation & comparition of fault-tolerant software techniques. IEEE Trans. Reliability. 2009, vol. 14, p. 1229–1237.

39. Karunanithi N. Prediction of Software Reliability Using Connectionist. IEEE transactions on reliability Models. July 1992, vol. 18, no. 7.

40. Kaszycki G. Using Process Metrics to Enhance Software Fault Prediction Models. FastAbstract ISSRE Copyright. 1999.

41. Keene S. Progressive Software Reliability Modeling. FastAbstract ISSRE Copyright, 1999.

42. Knight C. J. An experimental evaluation of the assumption of independence in Multiversion programming. IEEE Trans. Software Engineering, 1986, vol. 12,
p. 96–109.

43. Levendel Y. Reliability analysis of large software systems: Defect data modeling. IEEE Trans. Software Engineering, 1990, vol. 16, p. 141–152.

44. Liestman A. Fault-Tolerant Scheduling Problem. IEEE Trans. on Software Engineering, 1986, vol. 12,
p. 1089–1095.

45. Pai G. J. Enhancing Software Reliability Estimation Using Bayaesan Network and Fault. ISSRE and Chillarege Corp. Copyright, 2001.

46. Shooman M. L. Software Reliability for Use During Proposal and Early Design Stages. FastAbstract ISSRE Copyright, 2009.

47. Wattanapongsakorn N. Reliability Optimization for Software Systems with Multiple Applications. FastAbstract ISSRE and Chillarege Corp. Copyright, 2001.

48. Xie M. Regression Goodness-Of-fit Test for Software Reliability Model Validation. FastAbstract ISSRE Copyright, 2000.

49. Lyu M.R. Handbook of Software Reliability Engineering . IEEE Computer Society Press and McGraw-Hill Book Company, 1996, 819 p.

50. Rosenberg L. Software Metrics and Reliability. Software reliability engineering was presented at the 9-th International Symposium, “Best Paper” Award, November, 1998.

51. Kovalev I. V., Slobodin M. Ju., Stupina A. A. [Mathematical formulation of the problem of designing n-version software systems]. Problemy mashinostroenija i avtomatizacii. 2005, no. 3, p. 16–23. (In Russ.)

52. Kovalev I. V., Carev R. Ju., Rusakov M. A., Slobodin M. Ju. [Models support multi-stage analysis
of software reliability of automated control systems]. Problemy mashinostroenija i avtomatizacii. 2005, no. 2, p. 30–35. (In Russ.)

53. Kovalev I. V., Stupina A. A., Gavrilov E. S. [Transactional reliability of data processing technology in information and control systems]. Vestnik SibGAU. 2005, no. 3, p. 52–57. (In Russ.)

54. Engel E. A., Kovalev I. V. [Information processing using intelligent algorithms by solving wcci 2010 tasks]. Vestnik SibGAU. 2011, no. 3 (36), p. 4–8. (In Russ.)

55. Golovkin B. A. Raschet harakteristik i planirovanie parallel'nyh vychislitel'nyh processov [Calculation of characteristics and planning of parallel computing processes]. Moscow, Radio I Svyaz Publ., 1983, 272 p.

56. Gudman S. Vvedenie v razrabotku i analiz algoritmov [Introduction to the design and analysis of algorithms]. Moscow, Mir Publ., 1981, 366 p.

57. Mamikonov A. G. Tipizacija razrabotki modul'nyh sistem obrabotki dannyh [Typing the development of modular data processing systems]. Moscow, Nauka Publ., 1989, 165 p.

58. Mamikonov A. G. Sintez optimal'nyh modul'nyh sistem obrabotki dannyh [Synthesis of optimal modular data processing systems]. Moscow, Nauka Publ., 1986.

59. Mihalevich V. S. Vychislitel'nye metody issledovanija i proektirovanija slozhnyh sistem [Computational methods for the study and design of complex systems]. Moscow, Nauka Publ., 1982, 286 p.

60. Kovalev I. V., Nurgaleeva Ju. A., Ezhemanskaja S. N., Erygin V. Ju. [Diversified management work on the development of n-variant software systems]. Fundamental'nye issledovanija. 2011, no. 8–1, p. 124–127. (In Russ.)

61. Kovalev I. V. Fault-tolerant software architecture creation model based on reliability evaluation. Journal of AMSE. 2002, vol. 48, no. 3, p. 31–43.


Kovalev Igor Vladimirovich – Doctor of Engineering Science, Professor of System analysis Department, Siberian State Aerospace University named after academician M.F. Reshetnev. e-mail: kovalev.fsu@mail.ru.