Log in

Relevant bibliographies by topics / Software architecture – Reliability / Journal articles

Journal articles on the topic 'Software architecture – Reliability'

To see the other types of publications on this topic, follow the link: Software architecture – Reliability.

Author: Grafiati

Published: 4 June 2021

Last updated: 28 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Software architecture – Reliability.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Wang, Wen-Li, Dai Pan, and Mei-Hwa Chen. "Architecture-based software reliability modeling." Journal of Systems and Software 79, no. 1 (January 2006): 132–46. http://dx.doi.org/10.1016/j.jss.2005.09.004.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

GOKHALE, SWAPNA S. "SOFTWARE RELIABILITY ANALYSIS INCORPORATING SECOND-ORDER ARCHITECTURAL STATISTICS." International Journal of Reliability, Quality and Safety Engineering 12, no. 03 (June 2005): 267–90. http://dx.doi.org/10.1142/s0218539305001768.

Full text

Abstract:

Architecture-based techniques for reliability assessment of software applications have received increased attention in the past few years due to the advent of component-based software development paradigm. Most of the prior research efforts in architecture-based analysis use the composite solution approach to solve the architecture-based models in order to estimate application reliability. Though the composite solution approach produces an accurate estimate of application reliability, it suffers from several drawbacks. The most notable drawback of the composite solution approach is that it does not allow an analysis of the sensitivity of the application reliability to the reliabilities of the components comprising the application and the application structure. The hierarchical solution approach on the other hand, has the potential of overcoming the drawbacks of the composite approach. However, in the present form, the hierarchical solution approach produces an estimate of application reliability which is only an approximation of the estimate produced by the composite approach since it does not take into consideration the second-order architectural statistics. Also, although the hierarchical solution approach can be used for sensitivity analysis, mathematical techniques to perform such analysis are lacking. Development of an accurate hierarchical solution approach to estimate application reliability based on its architecture is the focus of this paper. Using the approach described in this paper, an analytical application reliability function which incorporates second-order architectural statistics can be obtained. Sensitivity analysis techniques and expressions to determine the mean time to failure of the application are developed based on this analytical reliability function. We illustrate the reliability prediction, sensitivity analysis, and mean time to failure computation techniques presented in this paper using two case studies.

APA, Harvard, Vancouver, ISO, and other styles

3

Goševa-Popstojanova, K., and K. S. Trivedi. "Architecture-based approaches to software reliability prediction." Computers & Mathematics with Applications 46, no. 7 (October 2003): 1023–36. http://dx.doi.org/10.1016/s0898-1221(03)90116-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

EL KHARBOUTLY, REHAB A., SWAPNA S. GOKHALE, and REDA A. AMMAR. "ARCHITECTURE-BASED SOFTWARE RELIABILITY ANALYSIS INCORPORATING CONCURRENCY." International Journal of Reliability, Quality and Safety Engineering 14, no. 05 (October 2007): 479–99. http://dx.doi.org/10.1142/s0218539307002751.

Full text

Abstract:

With the growing complexity of software applications and increasing reliance on the services provided by these applications, architecture-based reliability analysis has become the focus of several recent research efforts. Most of the prevalent research in this area does not consider simultaneous or concurrent execution of application components. Concurrency, however, may be common in modern software applications. Thus, reliability analysis considering concurrent component execution within the context of the application architecture is necessary for contemporary software applications. This paper presents an architecture-based reliability analysis methodology for concurrent software applications. Central to the methodology is a state space approach, based on discrete time Markov chains (DTMCs), to represent the application architecture taking into consideration simultaneous component execution. A closed form, analytical expression for the expected application reliability based on the average execution times, constant failure rates, and the average number of visits to the components is derived. The average number of visits to application components are obtained from the solution of the DTMC model representing the application architecture. The potential of the methodology to facilitate sensitivity analysis, identification of reliability bottlenecks, and an assessment of the impact of workload and component changes, in addition to providing a reliability estimate, is discussed. To enable the application of the methodology in practice, estimation of model parameters from different software artifacts is described. The methodology is illustrated with a case study. Finally, strategies to alleviate the state space explosion issue for an efficient application of the methodology are proposed.

APA, Harvard, Vancouver, ISO, and other styles

5

Tekinerdogan, Bedir, Hasan Sozer, and Mehmet Aksit. "Software architecture reliability analysis using failure scenarios." Journal of Systems and Software 81, no. 4 (April 2008): 558–75. http://dx.doi.org/10.1016/j.jss.2007.10.029.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Alam, Tanweer, and Mohammed Aljohani. "Software Defined Networks: Review and Architecture." IAIC Transactions on Sustainable Digital Innovation (ITSDI) 1, no. 2 (March 24, 2020): 143–51. http://dx.doi.org/10.34306/itsdi.v1i2.114.

Full text

Abstract:

In the fifth-generation communication system, secured and reliable data packets will rely on the network with high availability and low latency. The 5G network enables the dynamic control of nodes with low latency. Ultra-reliability is one of the challenging tasks in software-defined networks. The ultra-reliability feature is an interface working with high availability and low latency that brings in fifth-generation networks. The Internet of Things will work in the societies so that it required ultra-reliability features to empower the peoples as well as machines for collaborating with their neighbors. The connections among ultra-reliability networks are extremely hard situations to keep low packets corruption. The Software Defined Networks (SDN) will provide a platform for measuring, controlling, monitoring and scaling the smart objects in reality or virtually. Virtualization enables IT, specialists, to combine or separate the considerable networking or create new programmable networking among virtual machines. In this article, the authors are reviewed the architecture of SDN based on virtualization under the umbrella of 5G networks.

APA, Harvard, Vancouver, ISO, and other styles

7

El Kharboutly, Rehab, and Swapna S. Gokhale. "Efficient Reliability Analysis of Concurrent Software Applications Considering Software Architecture." International Journal of Software Engineering and Knowledge Engineering 24, no. 01 (February 2014): 43–60. http://dx.doi.org/10.1142/s0218194014500028.

Full text

Abstract:

Architecture-based reliability analysis of software applications is gaining prominence as it can provide valuable guidance to software architects during early design phases. Concurrent component execution is common among modern software applications, and hence, reliability analysis considering concurrency within the context of software architecture is essential. Our preliminary analysis approach considering concurrency suffers from state-space explosion; due to which it cannot be applied to practical software applications. This paper proposes solutions to the model specification and solution challenges arising from the state-space explosion problem. The specification challenge is alleviated using the Stochastic Reward Net (SRN) modelling paradigm which can intuitively and concisely represent concurrent software architecture at a higher level of abstraction. The computational challenge is alleviated by aggregating the original state space. Our illustrations show that aggregation introduces only a small inaccuracy into the reliability estimate, and hence, preserves the utility of the original model to produce design guidance via sensitivity analysis.

APA, Harvard, Vancouver, ISO, and other styles

8

Srinivas Rao, Sabbineni. "Evaluating Software System Reliability Using Architecture Based Approach." International Journal of Intelligent Information Systems 7, no. 1 (2018): 1. http://dx.doi.org/10.11648/j.ijiis.20180701.11.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Gokhale, Swapna S. "Architecture-Based Software Reliability Analysis: Overview and Limitations." IEEE Transactions on Dependable and Secure Computing 4, no. 1 (January 2007): 32–40. http://dx.doi.org/10.1109/tdsc.2007.4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Hac, A. "Using a software reliability model to design a telecommunications software architecture." IEEE Transactions on Reliability 40, no. 4 (1991): 488–94. http://dx.doi.org/10.1109/24.93771.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Smidts, C., D. Sova, and G. K. Mandela. "Architectural model for software reliability quantification." Computer Standards & Interfaces 21, no. 2 (June 1999): 168. http://dx.doi.org/10.1016/s0920-5489(99)92186-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

KAPUR, PARMOD KUMAR, V. S. SARMA YADAVALLI, SUNIL KUMAR KHATRI, and MASHAALLAH BASIRZADEH. "ENHANCING SOFTWARE RELIABILITY OF A COMPLEX SOFTWARE SYSTEM ARCHITECTURE USING ARTIFICIAL NEURAL-NETWORKS ENSEMBLE." International Journal of Reliability, Quality and Safety Engineering 18, no. 03 (June 2011): 271–84. http://dx.doi.org/10.1142/s0218539311004135.

Full text

Abstract:

Modeling of software reliability has gained lot of importance in recent years. Use of software-critical applications has led to tremendous increase in amount of work being carried out in software reliability growth modeling. Number of analytic software reliability growth models (SRGM) exists in literature. They are based on some assumptions; however, none of them works well across different environments. The current software reliability literature is inconclusive as to which models and techniques are best, and some researchers believe that each organization needs to try several approaches to determine what works best for them. Data-driven artificial neural-network (ANN) based models, on other side, provide better software reliability estimation. In this paper we present a new dimension to build an ensemble of different ANN to improve the accuracy of estimation for complex software architectures. Model has been validated on two data sets cited from the literature. Results show fair improvement in forecasting software reliability over individual neural-network based models.

APA, Harvard, Vancouver, ISO, and other styles

13

Oplinger, Jeffrey, and Monica S. Lam. "Enhancing software reliability with speculative threads." ACM SIGOPS Operating Systems Review 36, no. 5 (December 2002): 184–96. http://dx.doi.org/10.1145/635508.605417.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Wang Beiyang. "Architecture-Based Software Reliability Analysis and Prediction Based on Weighted Software Networks." Journal of Convergence Information Technology 8, no. 4 (February 28, 2013): 1003–14. http://dx.doi.org/10.4156/jcit.vol8.issue4.115.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Nuziale, T., and N. Vagenas. "A software architecture for reliability analysis of mining equipment." International Journal of Surface Mining, Reclamation and Environment 14, no. 1 (January 2000): 19–34. http://dx.doi.org/10.1080/13895260008953295.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Goševa-Popstojanova, Katerina, and Kishor S. Trivedi. "Architecture-based approach to reliability assessment of software systems." Performance Evaluation 45, no. 2-3 (July 2001): 179–204. http://dx.doi.org/10.1016/s0166-5316(01)00034-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Goel, Amrit L. "Software reliability modeling (tutorial)." ACM SIGMETRICS Performance Evaluation Review 14, no. 1 (May 1986): 2. http://dx.doi.org/10.1145/317531.317901.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Faye, Fatou, and Mbaye Sene. "Reliability and Availability of Embedded Software Architectures: A Survey." Applied Mechanics and Materials 373-375 (August 2013): 1612–17. http://dx.doi.org/10.4028/www.scientific.net/amm.373-375.1612.

Full text

Abstract:

This paper summarizes works based on the reliability and the availability of embedded software architectures. Nowadays, the advent of the embedded systems has pulled the development of different domains (aeronautics, automobile, industry, medicines, telecommunications, household electrical appliances, so one so far). Indeed, the embedded system includes hardware and software that must collaborate to carry out well defined complex tasks. An embedded system is an integration of heterogeneous components (components of the computing and the electronics). Indeed, the implementation of the embedded systems presents some constraints which can be, for example the system cost, energy consummation, speed of execution, reliability, availability, security ...However, among these constraints enumerated briefly, the reliability and the availability of the software architecture of these systems are the object of complete study in this article.

APA, Harvard, Vancouver, ISO, and other styles

19

Okamura, Hiroyuki, and Tadashi Dohi. "Optimizing Testing-Resource Allocation Using Architecture-Based Software Reliability Model." Journal of Optimization 2018 (September 27, 2018): 1–7. http://dx.doi.org/10.1155/2018/6948656.

Full text

Abstract:

In the management of software testing, testing-recourse allocation is one of the most important problems due to the tradeoff between development cost and reliability of released software. This paper presents the model-based approach to design the testing-resource allocation. In particular, we employ the architecture-based software reliability model with operational profile to estimate the quantitative software reliability in operation phase and formulate the multiobjective optimization problems with respect to cost, testing effort, and software reliability. In numerical experiment, we investigate the difference of the presented optimization problem from the existing testing-resource allocation model.

APA, Harvard, Vancouver, ISO, and other styles

20

Li, Hong Bing, and Ming Wei Wang. "Real-Time Embedded Software Architecture Modeling and Reliability Evaluation Based on Time-Extended Petri Net." Applied Mechanics and Materials 651-653 (September 2014): 1888–92. http://dx.doi.org/10.4028/www.scientific.net/amm.651-653.1888.

Full text

Abstract:

Software reliability is one of the most important quality indices in software quality evaluation. Reliability analysis based on software architecture has become a researching hotspot. This paper makes a review on existed architecture-based reliability evaluation models, and puts forward the shortage of these models. As petri net has a good ability of description for concurrency and asynchronism, this paper focuses on the research of petri net model. Transitions are divided into time transitions and instantaneous transitions. Time-related reliability, including time-delay reliability and temporal reliability, are added. Then the reachable state transition matrix is set up and system reliability evaluation proceeds. The method above is used into a avionics embedded software. At last we accomplish the architecture modeling, reliability evaluation, proving the effectiveness and feasibility of this method.

APA, Harvard, Vancouver, ISO, and other styles

21

Wang, Jun, Wei Ru Chen, De Lin Jing, and Hong Ji Yang. "Contribution Analysis of the Component in the Process of Reliability-Oriented Software Evolution." Advanced Materials Research 187 (February 2011): 78–83. http://dx.doi.org/10.4028/www.scientific.net/amr.187.78.

Full text

Abstract:

According to the various components will play a different role in the system's reliability evolution, software architecture reliability is analyzed by architecture-based software reliability model in this paper. At the same time, the method of contribution analysis of the component in the process of reliability-oriented software evolution is proposed. The method shows that which component of the overall system plays an important or crucial role in the process of reliability evolution. The efficiency of the software evolution can be improved through contribution analysis of the component in the process of reliability-oriented software evolution.

APA, Harvard, Vancouver, ISO, and other styles

22

Shatnawi, Omar. "Testing-Effort Dependent Software Reliability Model for Distributed Systems." International Journal of Distributed Systems and Technologies 4, no. 2 (April 2013): 1–14. http://dx.doi.org/10.4018/jdst.2013040101.

Full text

Abstract:

Distributed systems are being developed in the context of the client-server architecture. Client-server architectures dominate the landscape of computer-based systems. Client-server systems are developed using the classical software engineering activities. Developing distributed systems is an activity that consumes time and resources. Even if the degree of automation of software development activities increased, resources are an important limitation. Reusability is widely believed to be a key direction to improving software development productivity and quality. Software metrics are needed to identify the place where resources are needed; they are an extremely important source of information for decision making. In this paper, an attempt has been made to describe the relationship between the calendar time, the fault removal process and the testing-effort consumption in a distributed development environment. Software fault removal phenomena and testing-effort expenditures are described by a non-homogenous Poisson process (NHPP) and testing-effort curves respectively. Actual software reliability data cited in literature have been used to demonstrate the proposed model. The results are fairly encouraging.

APA, Harvard, Vancouver, ISO, and other styles

23

Li, Qiuying, Minyan Lu, Tingyang Gu, and Yumei Wu. "Runtime Software Architecture-Based Reliability Prediction for Self-Adaptive Systems." Symmetry 14, no. 3 (March 16, 2022): 589. http://dx.doi.org/10.3390/sym14030589.

Full text

Abstract:

Modern software systems need to autonomously adapt their behavior at runtime in order to maintain their utility in response to continuous environmental changes. Most studies on models at runtime focus on providing suitable techniques to manage the complexity of software at runtime but neglect reliability caused by adaptation activities. Therefore, adaptive behaviors may lead to a decrease in reliability, which may result in severe financial loss or life damage. Runtime software architecture (RSA) is an abstract of a running system, which describes the elements of the current system, the states of these elements and the relation between the elements and their states at runtime. The main difference between RSA and software architecture at design time (DSA) is that RSA has a causal connection with the running system, whereas DSA does not. However, RSA and DSA have both symmetry and asymmetry in software architecture. To ensure that architecture-centric software can provide reliable services after adaptation adjustment, a method is proposed to analyze the impact of changes caused by adaptation strategy on the overall software reliability, which will be predicted at the runtime architecture model layer. Based on a Java platform, through non-intrusive monitoring, an RSA behavioral model is obtained followed by runtime reliability analysis model. Following this, reliability prediction results are obtained through a discrete-time Markov chain (DTMC). Finally, an experiment is conducted to verify the feasibility of the proposed method.

APA, Harvard, Vancouver, ISO, and other styles

24

Lo, Jung-Hua, Chin-Yu Huang, Ing-Yi Chen, Sy-Yen Kuo, and Michael R. Lyu. "Reliability assessment and sensitivity analysis of software reliability growth modeling based on software module structure." Journal of Systems and Software 76, no. 1 (April 2005): 3–13. http://dx.doi.org/10.1016/j.jss.2004.06.025.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

WenQinq, Li, Xu Chenguan, Rao Yao, Zhu Liangliang, and Yi Yongxian. "Research on system software reliability based on service component architecture." Journal of Physics: Conference Series 2005, no. 1 (August 1, 2021): 012022. http://dx.doi.org/10.1088/1742-6596/2005/1/012022.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Pietrantuono, Roberto, Stefano Russo, and Kishor S. Trivedi. "Software Reliability and Testing Time Allocation: An Architecture-Based Approach." IEEE Transactions on Software Engineering 36, no. 3 (May 2010): 323–37. http://dx.doi.org/10.1109/tse.2010.6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Wei, Ying, Libo Wang, and MingQian Wang. "Software reliability analysis of Hierarchical architecture based on Markov model." Procedia Engineering 15 (2011): 2857–61. http://dx.doi.org/10.1016/j.proeng.2011.08.538.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Brosch, Franz, Ralf Gitzel, Heiko Koziolek, and Simone Krug. "Combining Architecture-based Software Reliability Predictions with Financial Impact Calculations." Electronic Notes in Theoretical Computer Science 264, no. 1 (August 2010): 3–17. http://dx.doi.org/10.1016/j.entcs.2010.07.002.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Guan, Hui, Wei-Ru Chen, Ning Huang, and Hong-Ji Yang. "Estimation of reliability and cost relationship for architecture-based software." International Journal of Automation and Computing 7, no. 4 (November 2010): 603–10. http://dx.doi.org/10.1007/s11633-010-0546-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Sharma, Vibhu Saujanya, and Kishor S. Trivedi. "Quantifying software performance, reliability and security: An architecture-based approach." Journal of Systems and Software 80, no. 4 (April 2007): 493–509. http://dx.doi.org/10.1016/j.jss.2006.07.021.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Chang, Wen-Kui, and Shuen-Lin Jeng. "Impartial evaluation in software reliability practice." Journal of Systems and Software 76, no. 2 (May 2005): 99–110. http://dx.doi.org/10.1016/j.jss.2004.03.029.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Golovin, S. A., S. V. Zykov, Yu P. Korablin, and D. A. Kryukov. "Application of high-level methods of compromise optimization for control of autonomous robotized open pit mining." Russian Technological Journal 8, no. 5 (October 20, 2020): 7–18. http://dx.doi.org/10.32362/2500-316x-2020-8-5-7-18.

Full text

Abstract:

In most software engineering approaches, software design begins with defining functional requirements, which is well suited to web-based software development projects. When designing high-critical large-scale software intended for industrial use, accounting for non-functional software requirements is also required. The main idea of the proposed document-oriented approach is to design a stable architectural solution as early as possible, taking into account the nonfunctional characteristics of the software: reliability, security, maintainability and performance (quality attributes). At the same time, the key issue is the coordination of functional requirements, taking into account technical limitations and business requirements achieved during the steady interaction of customer and developer teams. To increase the flexibility of the designed solutions and prevent crisis situations when developing highly critical large-scale software, it is proposed to use the approach integrating the architecture-centric design method (ACDM), the architecture-tradeoff analysis method (ATAM) with a matrix enterprise architecture matrix (EAM). This allows getting a result that is adequate to the required level of responsibility and reliability. Consideration of quality attributes within the framework of the method of compromise analysis makes it possible to select and make certain decisions in software design taking into account the scale of the software and its scope. The main attributes of product quality are highlighted (ISO 25010 standard), critical scenarios are defined for each of them (templates and use cases). The use of these templates for detailed software design with the necessary parameters of functional requirements, business conditions and technological limitations reduces the risk of developing unpredictable and uncertain system behavior. Based on the proposed approach, an architectural solution is presented for highly critical, responsible, large-scale software for managing autonomous robotic open-pit mining of minerals. Critical attributes for creating the specified software were identified and ranked, and the architecture of the solution according to the SWEBOK software development standard was described. Further, taking into account the nature, scale and scope of the software solution, recommendations are given on high-level architectural templates for the system design, including layers, pipelines and microservices. The proposed architecture-oriented development method is suitable for industrial-level software in various subject areas.

APA, Harvard, Vancouver, ISO, and other styles

33

Hou, Xue Mei, Wei Liu, Fei Gao, and Jing Wang. "Fuzzy Multi-Objective Software Reliability Redundancy Allocation Based on MEDA-BFA Algorithm." Applied Mechanics and Materials 278-280 (January 2013): 2090–93. http://dx.doi.org/10.4028/www.scientific.net/amm.278-280.2090.

Full text

Abstract:

Software reliability allocation problem is a major problem in engineering design practices. A fuzzy multi-objective software reliability allocation model is established by analyzing the software redundancy architecture and considering some fuzzy factors to reliability. Then, the MEDA-BFA algorithm is proposed based on estimation of distribution to solve software reliability redundancy allocation problem. Finally, experimental results show that the proposed intelligence algorithm can solve multi-objective software reliability allocation effectively and correctly, can help decision makers decide between software reliability and cost.

APA, Harvard, Vancouver, ISO, and other styles

34

Kaigui Wu, and Yong Wan. "Software Reliability Prediction from Test Data." Journal of Convergence Information Technology 8, no. 5 (March 15, 2013): 1295–301. http://dx.doi.org/10.4156/jcit.vol8.issue5.149.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Pouyan, Fatemeh, Ali Azarpeyvand, Saeed Safari, and Sied Mehdi Fakharie. "Reliability‐aware simultaneous multithreaded architecture using online architectural vulnerability factor estimation." IET Computers & Digital Techniques 9, no. 2 (March 2015): 124–33. http://dx.doi.org/10.1049/iet-cdt.2013.0162.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Norouzi, Zahra, and Ali Harounabadi. "An executable software architecture model for response time and reliability assessment." Management Science Letters 4, no. 9 (2014): 2011–20. http://dx.doi.org/10.5267/j.msl.2014.8.020.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Gokhale, Swapna S., and Kishor S. Trivedi. "Analytical Models for Architecture-Based Software Reliability Prediction: A Unification Framework." IEEE Transactions on Reliability 55, no. 4 (December 2006): 578–90. http://dx.doi.org/10.1109/tr.2006.884587.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Gokhale, Swapna S., W. Eric Wong, J. R. Horgan, and Kishor S. Trivedi. "An analytical approach to architecture-based software performance and reliability prediction." Performance Evaluation 58, no. 4 (December 2004): 391–412. http://dx.doi.org/10.1016/j.peva.2004.04.003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Tian, Jeff. "Measurement and continuous improvement of software reliability throughout software life-cycle." Journal of Systems and Software 47, no. 2-3 (July 1999): 189–95. http://dx.doi.org/10.1016/s0164-1212(99)00039-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Raj Kiran, N., and V. Ravi. "Software reliability prediction by soft computing techniques." Journal of Systems and Software 81, no. 4 (April 2008): 576–83. http://dx.doi.org/10.1016/j.jss.2007.05.005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Nouman, Muhammad, Muhammad Azam, Ashraf Mousa Saleh, Abdullah Alsaeedi, and Hayfa Yousef Abuaddous. "A systematic review of non-functional requirements mapping into architectural styles." Bulletin of Electrical Engineering and Informatics 12, no. 2 (April 1, 2023): 1226–36. http://dx.doi.org/10.11591/eei.v12i2.4081.

Full text

Abstract:

Fortunately, the software attracted enough businesses to the market, allowing them to earn money in less time with less work and more accurate results. Software development life cycle (SDLC) is used for software development as it is responsible for system functionality, efficiency, maintainability, and any other non-functional system requirements. Each stage of the SDLC process is critical. However, software requirements and software architecture are both fundamental activities that play a vital role in all other SDLC stages. Non-functional requirements are critical to the success of any software because they explain all system quality attributes such as complexity, reliability, security, and maintainability, among others. The architectural styles assist you in determining which architecture may be best for your project requirements. This paper discusses several of the most important architectural styles that are best suited for mapping desired non-functional requirements for software development, as well as their comparison based on various quality attributes (non-functional requirements).

APA, Harvard, Vancouver, ISO, and other styles

42

Chondamrongkul, Nacha, Jing Sun, Ian Warren, and Scott Uk-Jin Lee. "Integrated Formal Tools for Software Architecture Smell Detection." International Journal of Software Engineering and Knowledge Engineering 30, no. 06 (June 2020): 723–63. http://dx.doi.org/10.1142/s0218194020400057.

Full text

Abstract:

The architecture smells are the poor design practices applied to the software architecture design. The smells in software architecture design can be cascaded to cause the issues in the system implementation and significantly affect the maintainability and reliability attribute of the software system. The prevention of architecture smells at the design phase can therefore improve the overall quality of the software system. This paper presents a framework that supports the detection of architecture smells based on the formalization of architecture design. Our modeling specification supports representing both structural and behavioral aspect of software architecture design; it allows the smells to be analyzed and detected with the provided tools. Our framework has been applied to seven architecture smells that violate different design principles. The evaluation has been conducted and the result shows that our detection approach gives accurate results and performs well on different size of models. With the proposed framework, other architecture smells can be defined and detected using the process and tools presented in this paper.

APA, Harvard, Vancouver, ISO, and other styles

43

Alnaim, Abdulrahman Khalid, Ahmed Mahmoud Alwakeel, and Eduardo B. Fernandez. "Towards a Security Reference Architecture for NFV." Sensors 22, no. 10 (May 14, 2022): 3750. http://dx.doi.org/10.3390/s22103750.

Full text

Abstract:

Network function virtualization (NFV) is an emerging technology that is becoming increasingly important due to its many advantages. NFV transforms legacy hardware-based network infrastructure into software-based virtualized networks. This transformation increases the flexibility and scalability of networks, at the same time reducing the time for the creation of new networks. However, the attack surface of the network increases, which requires the definition of a clear map of where attacks may happen. ETSI standards precisely define many security aspects of this architecture, but these publications are very long and provide many details which are not of interest to software architects. We start by conducting threat analysis of some of the NFV use cases. The use cases serve as scenarios where the threats to the architecture can be enumerated. Representing threats as misuse cases that describe the modus operandi of attackers, we can find countermeasures to them in the form of security patterns, and we can build a security reference architecture (SRA). Until now, only imprecise models of NFV architectures existed; by making them more detailed and precise it is possible to handle not only security but also safety and reliability, although we do not explore those aspects. Because security is a global property that requires a holistic approach, we strongly believe that architectural models are fundamental to produce secure networks and allow us to build networks which are secure by design. The resulting SRA defines a roadmap to implement secure concrete architectures.

APA, Harvard, Vancouver, ISO, and other styles

44

Z, Sayf Hussain, and Suryaa V S. "AIRBNB SOFTWARE ARCHITECTURE MODELING USING UML EXTENSIONS." International Research Journal of Computer Science 8, no. 3 (March 31, 2021): 53–61. http://dx.doi.org/10.26562/irjcs.2021.v0803.003.

Full text

Abstract:

Airbnb is a California based company that operates an online marketplace for lodging and homestays for vacation rentals, and tourism activities. Modeling a prototype of the application with all the integral features intact would help us understand the core working and success of the company. The Unified Modeling Language (UML) is a language for the specification, visualization and documentation of object-oriented software systems. In order to understand the features of the miniature Airbnb, we try to model the system using UML diagrams. In this study, the proposed extension to UML covers aspects of use case diagram, sequence diagram, activity diagram and class diagram of the miniature Airbnb model at various levels and perspectives.

APA, Harvard, Vancouver, ISO, and other styles

45

Cai, Kai-Yuan. "Software Reliability Experimentation and Control." Journal of Computer Science and Technology 21, no. 5 (September 2006): 697–707. http://dx.doi.org/10.1007/s11390-006-0697-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Li, Xiao-Dan, Yong-Feng Yin, and Lance Fiondella. "Reliability and Performance Analysis of Architecture-Based Software Implementing Restarts and Retries Subject to Correlated Component Failures." International Journal of Software Engineering and Knowledge Engineering 25, no. 08 (October 2015): 1307–34. http://dx.doi.org/10.1142/s0218194015500266.

Full text

Abstract:

High reliability and performance are essential attributes of software systems designed for critical real-time applications. To improve the reliability and performance of software, many systems incorporate some form of fault recovery mechanism. However, contemporary models of software reliability and performance rarely consider these fault recovery mechanisms. Another notable shortcoming of many software models is that they make the simplifying assumption that component failures are statistically independent, which disagrees with several experimental studies that have shown that the failures of software components can exhibit correlation. This paper presents an architecture-based model of software reliability and performance that explicitly considers a two-stage fault recovery mechanism implementing component restarts and application-level retries. The application architecture is characterized by a Discrete Time Markov Chain (DTMC) to represent the dynamic branching behavior of control between the components of the application. Correlations between the component failures are computed with an efficient numerical algorithm for a multivariate Bernoulli (MVB) distribution. We illustrate the utility of the model through a case study of an embedded software application. The results suggest that the model can be used to quantify the impact of software fault recovery and correlated component failures on application reliability and performance.

APA, Harvard, Vancouver, ISO, and other styles

47

Xu Jian, Yan Han, and Li Qianmu. "A Methodology for Software Reliability Risk Assessment." Journal of Convergence Information Technology 6, no. 4 (April 30, 2011): 188–200. http://dx.doi.org/10.4156/jcit.vol6.issue4.22.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Kazman, Rick, Len Bass, Mark Klein, Tony Lattanze, and Linda Northrop. "A Basis for Analyzing Software Architecture Analysis Methods." Software Quality Journal 13, no. 4 (December 2005): 329–55. http://dx.doi.org/10.1007/s11219-005-4250-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Tang, Jun Xi, Ying Kai Bao, Peng Jia Shi, Wen Hai Liu, Tai Ping Wang, and Chuang Xin Guo. "Research on Software Implementation of Human Reliability Analysis in Power System." Applied Mechanics and Materials 631-632 (September 2014): 1071–74. http://dx.doi.org/10.4028/www.scientific.net/amm.631-632.1071.

Full text

Abstract:

Human error has become a serious threat to the power system operation reliability and safety. As the research of human reliability in power system continues, some quantitative methods were proposed for the power operation safety assessment. In this paper, the implementation of a human reliability evaluation system for assessing the human reliability associated with power system operation is discussed. Firstly, the software architecture of the system is given. Then the detail function design is presented. Practical experiences show that the system could be a useful tool and have an extensive application prospect.

APA, Harvard, Vancouver, ISO, and other styles

50

Wang, Feng Qin, Qi Li, and Yu Liu. "Research on the Software Architecture of Information Systems Based on SOA." Applied Mechanics and Materials 380-384 (August 2013): 2548–51. http://dx.doi.org/10.4028/www.scientific.net/amm.380-384.2548.

Full text

Abstract:

Service-Oriented Architecture (SOA) is first introduced, and then the software architecture and development methods of information systems based on SOA are designed. Finally, the architecture and development methods are implemented in an enterprise information system, which can not only exchange and process a variety of information but also achieve real-time perception of information. The practice of the information system proves that systems based on SOA are of high reliability and security, good maintenance and expandability.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!