scholarly journals A Method for Considering Error Propagation in Reliability Estimation of Component-Based Software Systems

2019 ◽  
Vol 4 (3) ◽  
pp. 635-653
Author(s):  
Preeti Malik ◽  
Lata Nautiyal ◽  
Mangey Ram
Keyword(s):  
Numerical Simulation ◽  
Sensitivity Analysis ◽  
Software Engineering ◽  
Error Propagation ◽  
Reliability Estimation ◽  
Software Systems ◽  
System A ◽  
Number Of Factors ◽  
Software Product ◽  
Component Based Software Engineering

Component-based software engineering has proved itself as a strong pillar in software engineering community. Large number of factors are involved in the success of software product developed using Component-based software engineering, for instance, security, reliability, quality, safety, and testability. As the component-based software is made up of large number of components put together, therefore components’ reliability influence the reliability of the complete software. Numerous models and principles have been established to estimate the reliability of software by applying information regarding architecture, quality and security attributes of the software. Many researchers overlooked a major factor while estimating reliability of component-based software and that is error-propagation. Although it can be a case that the components are not dependent on each other and they are supplemented with the wrappers. However it is not true for many component-based applications. In this paper, a framework for reliability estimation has been proposed. In our proposal we have considered error propagation. We have analyzed the program structure and also presented how they are handled in estimation process. Further sensitivity analysis is done to identify the most sensitive component of the system. A numerical simulation is also presented for better understanding of the proposed framework.

Software Development Crisis

2017 ◽  
pp. 126-148 ◽  
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

An Approach to Formal Specification of Component-Based Software

2011 ◽  
pp. 34-42
Author(s):  
Tarek Zernadji ◽  
Raida Elmansouri ◽  
Allaoua Chaoui
Keyword(s):  
Software Engineering ◽  
Software Reuse ◽  
Formal Specification ◽  
Component Composition ◽  
Software Systems ◽  
Software Components ◽  
Design Component ◽  
Component Design ◽  
Component Based Software Engineering ◽  
Expected Benefits

Current research on software reuse in Component Based Software Engineering (CBSE) covers a variety of fields, including component design, component specification, component composition, component-based framework. CBSE is quickly becoming a mainstream approach to software development and most researchers are hoping that it will be solutions to all the problems that led to software crisis. The software engineering techniques specific to this discipline, in phases such as modeling, verification or validation of component based software systems still insufficient and need more research efforts. ECATNets (Extended Concurrent Algebraic Term Nets) are frameworks for specification, modeling and validation of concurrent and distributed systems. They are characterized by their semantics defined in terms of rewriting logic. The objective of this article is to propose a formal specification of software components by using ECATNets formalism. The expected benefits of this work are: Offer a formal notation for describing the different features of concurrent and distributed software components; Defining a formal unambiguous semantic to describe behavior of the composed system.

scholarly journals Evaluation of a Suite of Metrics for Component Based Software Engineering (CBSE)

10.28945/3379 ◽  
2009 ◽  
Author(s):  
Lakshmi Narasimhan ◽  
Prapanna Parthasarathy ◽  
Manik Lal Das
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Large Scale ◽  
Software Systems ◽  
Systematic Analysis ◽  
Rapid Production ◽  
Component Based Software Engineering ◽  
Large Software ◽  
Engineered Systems

Component-Based Software Engineering (CBSE) has shown significant prospects in rapid production of large software systems with enhanced quality, and emphasis on decomposition of the engineered systems into functional or logical components with well-defined interfaces used for communication across the components. In this paper, a series of metrics proposed by various researchers have been analyzed, evaluated and benchmarked using several large-scale publicly available software systems. A systematic analysis of the values for various metrics has been carried out and several key inferences have been drawn from them. A number of useful conclusions have been drawn from various metrics evaluations, which include inferences on complexity, reusability, testability, modularity and stability of the underlying components. The inferences are argued to be beneficial for CBSE-based software development, integration and maintenance.

scholarly journals Review of Relevant System Development Life Cycles (SDLCs) in Service-Oriented Software Engineering (SoSE)

2012 ◽  
Vol 10 (2) ◽  
Author(s):  
L. Rodríguez-Martínez ◽  
M. Mora ◽  
F. Álvarez ◽  
L. Garza ◽  
H. Durán ◽  
...  
Keyword(s):  
Software Engineering ◽  
System Development ◽  
Life Cycles ◽  
Software Systems ◽  
Computing Technology ◽  
New Paradigm ◽  
Development Life Cycle ◽  
Service Oriented ◽  
Component Based Software Engineering ◽  
Relevant Range

Service-oriented software engineering (SoSE) is a new  paradigm for building software systems, fostered by the availability of a new -but already mature- computing technology based on services.  SoSE advances the current object-oriented and the component-based software engineering paradigms. Under that new paradigm, multiple software-system development life cycle (SDLC) methodologies have been proposed; however, none of them have gained a total acceptance as the dominant SDLC in SoSE.  On this theoretical and practical situation, we believe that a research is required to reach more standardized and stabilized knowledge about SDLCs in SoSE.  Thus, this article reviews nine recent SDLCs proposed for SoSE with the aim to present a descriptive-comparative landscape of a relevant range of SDLCs for SoSE. Such description-comparison is guided by two criteria: (i) the extent of completeness of each SDLC, with respect to the proposed phases, activities and delivered artifacts, and (ii) the extent of the Boehm-Turner’s Rigor-Agility balance. Our results suggest that only three of the nine SDLCs studied already provide the best level of completeness and Rigor-Agility. Finally, we consider that the reported descriptivecomparative framework and their findings from each SDLC can be useful also for comparing and elaborating future SDLCs in SoSE.

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

Software Development Crisis

2021 ◽  
pp. 1145-1162
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

Approach of Modelization and Management on Software Components

2019 ◽  
pp. 98-126
Author(s):  
Fadoua Rehioui
Keyword(s):  
Information System ◽  
Information Systems ◽  
Software Engineering ◽  
Data Management ◽  
Added Value ◽  
Software Systems ◽  
Communication Management ◽  
Component Identification ◽  
Identification Approach ◽  
Component Based Software Engineering

The complexity of information systems leads to poor data management and therefore bad decisions. The advantage of using component-based software engineering is to divide an information system into subsystem blocks with less complexity. In fact, a component is intended to provide specific services as management of the combination and communication between the units of the system. This chapter addresses this problem by developing information systems, proposing a component identification approach and the management pattern for data management. In this work, three developed views are taken into account, which include modelization and the design to achieve the purpose of defining and building the components and how they can be assembled. A component is intended to provide specific services, as a combination and communication management between the system units, and the manager component is the important and complementary paradigm pattern and added value for the development of software systems.

Research on Heterogeneous Component Assembly Problems Based on Software Product Line

2013 ◽  
Vol 765-767 ◽  
pp. 1324-1327 ◽  
Author(s):  
Jian Li Dong
Keyword(s):  
Software Engineering ◽  
Software Product Line ◽  
Product Line ◽  
Key Technology ◽  
Software Production ◽  
Software Product ◽  
Engineering Environment ◽  
Component Based Software Engineering ◽  
Component Assembly ◽  
Integrated Software

With the research and development of software product line and component-based software engineering methodology, it has become key technology how to build component assembly environment and realize heterogeneous component assembly. Thus, a new industrialized product line based integrated software engineering environment (PL-ISEE) model is firstly proposed, and the heterogeneity problems of developed components are analyzed and discussed. For removing components heterogeneity and realizing heterogeneous components assembly, the wrapper wrapping component is studied further. These researches and ideas will play significant role in promoting the formations of component-based software engineering methodology and future industrialized software production technology.

A Literature Review Study of Software Defect Prediction using Machine Learning Techniques

2018 ◽  
Vol 6 (6) ◽  
pp. 300 ◽  
Author(s):  
Feidu Akmel ◽  
Ermiyas Birihanu ◽  
Bahir Siraj
Keyword(s):  
Machine Learning ◽  
Software Metrics ◽  
Quality Standard ◽  
Machine Learning Techniques ◽  
Software Systems ◽  
Health Care Insurance ◽  
Software Defect ◽  
Learning Techniques ◽  
Software Product

Software systems are any software product or applications that support business domains such as Manufacturing,Aviation, Health care, insurance and so on.Software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from other for this reason it is better to apply the software metrics to measure the quality of software. Attributes that we gathered from source code through software metrics can be an input for software defect predictor. Software defect are an error that are introduced by software developer and stakeholders. Finally, in this study we discovered the application of machine learning on software defect that we gathered from the previous research works.

Sign in / Sign up

Export Citation Format

Share Document