Beyond ATAM: Architecture Analysis in the Development of Large Scale Software Systems

2007 ◽  
pp. 92-105 ◽  
Author(s):  
Andrzej Zalewski
Keyword(s):  
Large Scale ◽  
Software Systems ◽  
Architecture Analysis

scholarly journals Adapting Behavior Driven Development (BDD) for large-scale software systems

2021 ◽  
Vol 177 ◽  
pp. 110944
Author(s):  
Mohsin Irshad ◽  
Ricardo Britto ◽  
Kai Petersen
Keyword(s):  
Large Scale ◽  
Software Systems

scholarly journals Multi-purpose, multi-level feature modeling of large-scale industrial software systems

2016 ◽  
Vol 17 (3) ◽  
pp. 913-938 ◽  
Author(s):  
Daniela Rabiser ◽  
Herbert Prähofer ◽  
Paul Grünbacher ◽  
Michael Petruzelka ◽  
Klaus Eder ◽  
...  
Keyword(s):  
Large Scale ◽  
Feature Modeling ◽  
Software Systems ◽  
Multi Level ◽  
Industrial Software

scholarly journals Algorithmic Transparency of Large-Scale *AIDA Programs

2020 ◽  
Vol 30 (09) ◽  
pp. 1263-1288
Author(s):  
Yutaka Watanobe ◽  
Nikolay Mirenkov
Keyword(s):  
Data Structures ◽  
Large Scale ◽  
Software Systems ◽  
Computational Algorithms ◽  
Computer Language ◽  
Algorithms And Data Structures ◽  
Application Methods ◽  
Analysis System ◽  
Computational Comparison

Programming in pictures is an approach where pictures and moving pictures are used as super-characters to represent the features of computational algorithms and data structures, as well as for explaining the models and application methods involved. *AIDA is a computer language that supports programming in pictures. This language and its environment have been developed and promoted as a testbed for various innovations in information technology (IT) research and implementation, including exploring the compactness of the programs and their adaptive software systems, and obtaining better understanding of information resources. In this paper, new features of the environment and methods of their implementation are presented. They are considered within a case study of a large-scale module of a nuclear safety analysis system to demonstrate that *AIDA language is appropriate for developing efficient codes of serious applications and for providing support, based on folding/unfolding techniques, enhancing the readability, maintainability and algorithmic transparency of programs. Features of this support and the code efficiency are presented through the results of a computational comparison with a FORTRAN equivalent.

scholarly journals An analysis of software aging in cloud environment

2020 ◽  
Vol 10 (6) ◽  
pp. 5985
Author(s):  
Shruthi P. ◽  
Nagaraj G. Cholli
Keyword(s):  
Cloud Computing ◽  
Large Scale ◽  
Virtual Machines ◽  
Cloud Service ◽  
Software Systems ◽  
System Failure ◽  
Dynamic Nature ◽  
Software Aging ◽  
Software Rejuvenation ◽  
The Impact

Cloud Computing is the environment in which several virtual machines (VM) run concurrently on physical machines. The cloud computing infrastructure hosts multiple cloud service segments that communicate with each other using the interfaces. This creates distributed computing environment. During operation, the software systems accumulate errors or garbage that leads to system failure and other hazardous consequences. This status is called software aging. Software aging happens because of memory fragmentation, resource consumption in large scale and accumulation of numerical error. Software aging degrads the performance that may result in system failure. This happens because of premature resource exhaustion. This issue cannot be determined during software testing phase because of the dynamic nature of operation. The errors that cause software aging are of special types. These errors do not disturb the software functionality but target the response time and its environment. This issue is to be resolved only during run time as it occurs because of the dynamic nature of the problem. To alleviate the impact of software aging, software rejuvenation technique is being used. Rejuvenation process reboots the system or re-initiates the softwares. This avoids faults or failure. Software rejuvenation removes accumulated error conditions, frees up deadlocks and defragments operating system resources like memory. Hence, it avoids future failures of system that may happen due to software aging. As service availability is crucial, software rejuvenation is to be carried out at defined schedules without disrupting the service. The presence of Software rejuvenation techniques can make software systems more trustworthy. Software designers are using this concept to improve the quality and reliability of the software. Software aging and rejuvenation has generated a lot of research interest in recent years. This work reviews some of the research works related to detection of software aging and identifies research gaps.

Requirements Engineering for Software Systems: A Systematic Literature Review

2021 ◽  
Vol 12 (7) ◽  
pp. 339-349
Author(s):  
A. A. Kodubets ◽  
◽  
I. L. Artemieva ◽  
Keyword(s):  
Literature Review ◽  
Requirements Engineering ◽  
Language Processing ◽  
Systematic Literature Review ◽  
Large Scale ◽  
Development Process ◽  
Research Question ◽  
Software Systems ◽  
Software System ◽  
Requirements Development

This article contains a systematic literature review of requirements engineering for software systems. The literature published within last 5 years was included into the review. A research question was defined as requirements development process of large scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that large-scale software system requirements process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constrains, and thus, the interaction between them seriously slows down the overall requirements development process than writing the requirements specification itself. The research papers were classified by several research directions: Natural Language Processing for Requirements Engineering (NLP4RE), Requirement Prioritization, Requirements Traceability, Quality of Software Requirements, Non-functional Requirements and Requirements Elicitation. Motivation and intensity of each direction was described. Each direction was structured and represented with the key references. A contribution of each research direction into the research question was analyzed and summarized including potential further steps. It was identified that some researchers had met a part of the described problem in different forms during their researches. At the end, other researches were described additionally in a short overview. To approach the research question further potential direction was described.

Lifecycles

2019 ◽  
pp. 1-32
Keyword(s):  
Large Scale ◽  
Software Systems ◽  
Software Products ◽  
Product Success ◽  
Product Features ◽  
Lifecycle Model ◽  
Software Product ◽  
Project Risks ◽  
Mission Critical ◽  
Common Understanding

This chapter discusses lifecycle model application for software development. It compares the benefits and shortcomings of different models. The authors argue that there is no universal lifecycle model. For agility, this chapter recommends combining prototyping with the other models. The authors suggest this to achieve a common understanding of the key product features and to reduce project risks. The lifecycle model choice determines project economics and time to market. The model also influences product quality and overall project success. However, product success essentially depends on human factors. The authors analyze the applicability of the lifecycle models to large-scale, mission-critical software systems. Finally, this chapter introduces a methodology. It includes a spiral-like lifecycle and a set of formal models and visual tools for software product development. This methodology helps to optimize the software product lifecycle. It fits large-scale, complex heterogeneous software products.

Architecture-Centered Integrated Verification

2012 ◽  
pp. 201-222
Author(s):  
Yujian Fu ◽  
Zhijang Dong ◽  
Xudong He
Keyword(s):  
Petri Nets ◽  
Software Architecture ◽  
Large Scale ◽  
Future Research ◽  
Software Systems ◽  
Compositional Verification ◽  
Software Product ◽  
Implementation Level ◽  
High Level ◽  
Florida International University

The approach aims at solving the above problems by including the analysis and verification of two different levels of software development process–design level and implementation level-and bridging the gap between software architecture analysis and verification and the software product. In the architecture design level, to make sure the design correctness and attack the large scale of complex systems, the compositional verification is used by dividing and verifying each component individually and synthesizing them based on the driving theory. Then for those properties that cannot be verified on the design level, the design model is translated to implementation and runtime verification technique is adapted to the program. This approach can highly reduce the work on the design verification and avoid the state-explosion problem using model checking. Moreover, this approach can ensure both design and implementation correctness, and can further provide a high confident final software product. This approach is based on Software Architecture Model (SAM) that was proposed by Florida International University in 1999. SAM is a formal specification and built on the pair of component-connector with two formalisms – Petri nets and temporal logic. The ACV approach places strong demands on an organization to articulate those quality attributes of primary importance. It also requires a selection of benchmark combination points with which to verify integrated properties. The purpose of the ACV is not to commend particular architectures, but to provide a method for verification and analysis of large scale software systems in architecture level. The future research works fall in two directions. In the compositional verification of SAM model, it is possible that there is circular waiting of certain data among different component and connectors. This problem was not discussed in the current work. The translation of SAM to implementation is based on the restricted Petri nets due to the undecidable issue of high level Petri nets. In the runtime analysis of implementation, extraction of the execution trace of the program is still needed to get a white box view, and further analysis of execution can provide more information of the product correctness.

Sign in / Sign up

Export Citation Format

Share Document