A Comprehensive Exploration of Challenges in Architecture-Based Reliability Estimation

Krka, Ivo; Edwards, George; Cheung, Leslie; Golubchik, Leana; Medvidović, Nenad

doi:10.1007/978-3-642-10248-6_9

Cited by 16 publications

(19 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The focus of our previous research has been on (1) classifying and discovering architectural defects [24] and (2) analyzing and extracting operational profile information from various information sources [3,15]. In SHARP, we analyze the impact of the discovered architectural defects (e.g., mismatches between components' operation protocols) on the system's reliability and enrich the initial component and scenario models with the extracted operational profile information.…”

Section: Prior Workmentioning

confidence: 99%

“…Our previous work [3,15] provides an in-depth treatment of the information sources from which these inputs are derivable; note that SHARP does not require more input information than other existing techniques. Based on the inputs, SHARP produces a system reliability estimate, as well as the reliability estimates for the smaller scenario sequences.…”

Section: Introductionmentioning

confidence: 99%

“…A number of existing approaches quantify the reliability of a system by analyzing its architectural models (recently surveyed in [8,12,13,15]). These existing techniques generate a stochastic reliability model from software architectural models, and most of them assume a sequential system for which a reliability model only needs to keep track of the currently running component.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Architecture-level reliability prediction of concurrent systems

Cheung

Krka

Golubchik

et al. 2012

Proceedings of the 3rd ACM/SPEC International Conference on Performance Engineering

Self Cite

View full text Add to dashboard Cite

Stringent requirements on modern software systems dictate evaluation of dependability qualities, such as reliability, as early as possible in a system's life cycle. A primary shortcoming of the existing design-time reliability prediction approaches is their lack of support for modeling and analyzing concurrency in a scalable way. To address the scalability challenge, we propose SHARP, an architecture-level reliability prediction framework that analyzes a hierarchical scenario-based specification of system behavior. It achieves scalability by utilizing the scenario relations embodied in this hierarchy. SHARP first constructs and solves models of basic scenarios, and combines the obtained results based on the defined scenario dependencies; the dependencies we handle are sequential and parallel execution of multiple scenarios. This process iteratively continues through the scenario hierarchy until finally obtaining the system reliability estimate. Our evaluations performed on real-world specifications indicate that SHARP is (a) almost as accurate as a traditional non-hierarchical method, and (b) more scalable than other existing techniques.

show abstract

Section: Prior Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Architecture-level reliability prediction of concurrent systems

Cheung

Krka

Golubchik

et al. 2012

Proceedings of the 3rd ACM/SPEC International Conference on Performance Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…In [14]- [16], the authors applied dynamic Bayesian networks to build a stochastic reliability model that relies on standard models of software architecture and does not require implementation-level artifacts. However, the above mentioned approaches build global behavior models of the system based on flat construction of scenarios [17], which in the large systems introduce state space explosion problem.…”

Section: Related Workmentioning

confidence: 99%

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Hou

Chen

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYSystem scenarios that derived from system design specification play an important role in the reliability engineering of componentbased software systems. Several scenario-based approaches have been proposed to predict the reliability of a system at the design time, most of them adopt flat construction of scenarios, which doesn't conform to software design specifications and is subject to introduce state space explosion problem in the large systems. This paper identifies various challenges related to scenario modeling at the early design stages based on software architecture specification. A novel scenario-based reliability modeling and prediction approach is introduced. The approach adopts hierarchical scenario specification to model software reliability to avoid state space explosion and reduce computational complexity. Finally, the evaluation experiment shows the potential of the approach.

show abstract

“…Encryption Non-repudiation ( Figure 1) TYPE OF SECURITY REQUIREMENTS Security requirements attribute or security attribute can be defined as any piece of information that may be associated with a controlled implicit entity or user for the purpose of implementing a security policy that is not necessarily implemented directly in data structures [5]. It provides a behavioral attributes such as reliability, availability, safety, confidentiality and exclusivity or more accurately to security and dependability related attributes [6][7] [8].…”

Section: Authentication Authorizationmentioning

confidence: 99%

Meeting Real Challenges in Eliciting Security Attributes for Mobile Application Development

Yusop¹,

Kamalrudin²,

Yusof³

et al. 2016

Journal of Internet Computing and Services

View full text Add to dashboard Cite

There has been a rapid growth in the development of mobile application resulting from its wide usage for online transaction, data storage and exchange of information. However, an important issue that has been overlooked is the lack of emphasis on the security issues at the early stage of the development. In fact, security issues have been kept until the later stage of the implementation of mobile apps. Requirements engineers frequently ignore and incorrectly elicit security-related requirements at the early stage of mobile application development. This scenario has led to the failure of developing secure and safe mobile application based on the needs of the users. As such, this paper intends to provide further understanding of the real challenges in extracting security attributes for mobile application faced by novice requirements engineers. For this purpose, two experiments on eliciting security attributes requirements of textual requirements scenario were conducted. The performance related to the correctness and time taken to elicit the security attributes were measured and recorded. It was found that the process of eliciting correct security attributes for mobile application requires effort, knowledge and skills. The findings indicate that an automated tool for correct elicitation security attributes requirement could help to overcome the challenges in eliciting security attributes requirements, especially among novice requirements engineers.☞ keyword : Security requirement, security attribute, mobile application development

show abstract

A Comprehensive Exploration of Challenges in Architecture-Based Reliability Estimation

Cited by 16 publications

References 39 publications

Architecture-level reliability prediction of concurrent systems

Architecture-level reliability prediction of concurrent systems

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Meeting Real Challenges in Eliciting Security Attributes for Mobile Application Development

Contact Info

Product

Resources

About