Overview of contradictions in the presentation of the results of the stages of development of software systems

2020 ◽  
pp. 61-65
Author(s):  
Vyacheslav Lapshin ◽  
Yuri Rogozov ◽  
Sergey Kucherov ◽  
Karina Kandyba
Keyword(s):  
Development Process ◽  
System Development ◽  
New Method ◽  
Software Systems ◽  
Software System ◽  
Stages Of Development ◽  
Domain Specific

The article discusses the main contradictions that arise during the transition between the stages of the software system development process. The causes of these contradictions are analyzed. The approaches to the elimination of identified contradictions, in particular, the approach based on the construction of domain-specific models (DSM), are examined. The disadvantages of such solutions based on the DSM approach are described. The substantiation of the relevance of developing a new method for constructing software systems is given.

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.

Enabling the Interoperability of the Modelica DSL and Matlab Simulink towards the Development of Self-Adaptive Dynamic Systems

2018 ◽  
Vol 7 (4) ◽  
pp. 54-75
Author(s):  
Nikolay Tcholtchev ◽  
Grit Dudeck ◽  
Michael Wagner ◽  
Christian Hein ◽  
Arun Prakash ◽  
...  
Keyword(s):  
Development Process ◽  
System Development ◽  
Efficient Design ◽  
Matlab Simulink ◽  
Adaptive Dynamic ◽  
Domain Specific ◽  
Current Article ◽  
Cost Efficient ◽  
Self Adaptive

Domain Specific Languages (DSL) are an important concept that is used in industry, in order to enable the fast and cost-efficient design of specific functions/components, and/or to target particular aspects of the systems' development and operation. In the current article, the authors describe their experiences on the integration of the Modelica DSL into a platform that enables the integration and interoperability of model-based tools across the various phases of the system development process. Furthermore, it is illustrated how Matlab Simulink can be used in parallel in the course of the same system design undertaking. Thereby, the authors present their approach and compare different tools which were used, in order to efficiently complete the integration, and finally exemplify the outcome on a case study related to a self-adaptive dynamic system from the automotive domain.

A Method and Software Tool for Automated Gearbox Synthesis

2009 ◽  
Author(s):  
Yi-shih Lin ◽  
Kristina Shea ◽  
Aylmer Johnson ◽  
John Coultate ◽  
Jamie Pears
Keyword(s):  
Development Process ◽  
Software Tool ◽  
New Method ◽  
Analysis Tool ◽  
Test Results ◽  
Support Design ◽  
Design Synthesis ◽  
Domain Specific ◽  
Design Specifications ◽  
Generative Approach

In today’s economy, engineering companies strive to reduce product development time and costs. One approach to assisting this goal is to introduce computer-aided methods and tools earlier in the development process. This requires providing robust design automation methods and tools that can support design synthesis and the generation of alternative design configurations, in addition to automated geometric design. A new method for automated gearbox design, tailored for integration within an existing commercial gearbox analysis tool, is described in this paper. The method combines a rule-based generative approach, based on a previous parallel grammar approach for mechanical gear systems, with domain specific heuristics and stochastic search using simulated annealing. Given design specifications that include a bounding box, the number of required speeds and their target ratios, a range of valid gearbox configurations is generated from a minimal initial configuration. Initial test results show that this new method is able to generate a variety of designs which meet the design specifications. The paper concludes with a discussion of the method’s current limitations and a description of the work currently underway to improve and extend its capabilities.

scholarly journals Identifying common activities in the graphical user interface development process and their integration into the software-system development life cycle

2015 ◽  
Vol 12 (1) ◽  
pp. 323-348
Author(s):  
Laura Rodriguez-Martinez ◽  
Hector Duran-Limon ◽  
Ricardo Mendoza-González ◽  
Jaime Muñoz
Keyword(s):  
Life Cycle ◽  
Graphical User Interface ◽  
User Interfaces ◽  
Development Process ◽  
System Development ◽  
Graphical User Interfaces ◽  
Generic Model ◽  
Software System ◽  
Development Life Cycle ◽  
Definition Of

We identify a suite of activities in the development process of Graphical User Interfaces (GUI) and include them as part of an approach to a generic model for the GUI Development Process (GDP). This work contributes with: (1) the identification of common activities of previous GDPs, (2) the definition of an approach to a generic GDP limited to its phases and activities, and (3) the integration of such a generic GDP with any software-system development life cycle (SDLC), illustrated with the Spiral SDLC. We show this work is useful by a) highlighting the advantages of our proposal over other methodologies for GDP in Human-Computer Interaction (HCI), b) showing one example of the integration of the GDP into a SDLC, and c) showing the usefulness of our approach in a case example.

OPTIMAL COMPONENT SELECTION OF COTS BASED SOFTWARE SYSTEM UNDER CONSENSUS RECOVERY BLOCK SCHEME INCORPORATING EXECUTION TIME

2010 ◽  
Vol 17 (03) ◽  
pp. 209-222 ◽  
Author(s):  
P. C. JHA ◽  
P. K. KAPUR ◽  
SHIVANI BALI ◽  
U. DINESH KUMAR
Keyword(s):  
Execution Time ◽  
Fault Tolerant ◽  
System Development ◽  
Software Systems ◽  
Software System ◽  
Reliability Models ◽  
Development Costs ◽  
Software Modules ◽  
Reduce Development Time ◽  
Commercial Off The Shelf

Computer based systems have increased dramatically in scope, complexity, pervasiveness. Most industries are highly dependent on computers for their basic day to day functioning. Safe & reliable software operations are an essential requirement for many systems across different industries. The number of functions to be included in a software system is decided during the software development. Any software system must be constructed in such a way that execution can resume even after the occurrence of failure with minimal loss of data and time. Such software systems which can continue execution even in presence of faults are called fault tolerant software. When failure occurs one of the redundant software modules get executed and prevent system failure. The fault tolerant software systems are usually developed by integrating COTS (commercial off-the-shelf) software components. The motivation for using COTS components is that they will reduce overall system development costs and reduce development time. In this paper, reliability models for fault tolerant consensus recovery blocks are analyzed. In first optimization model, we formulate joint optimization problem in which reliability maximization of software system and execution time minimization for each function of software system are considered under budgetary constraint. In the second model the issue of compatibility among alternatives available for different modules, is discussed. Numerical illustrations are provided to demonstrate the developed models.

scholarly journals Requirement Elicitation issues and Challenges in Pakistan Software Industry

2018 ◽  
pp. 84-92
Keyword(s):  
Development Process ◽  
Software Industry ◽  
Software Systems ◽  
User Needs ◽  
Stages Of Development ◽  
Software Developers ◽  
Requirement Elicitation ◽  
Communication Problem ◽  
The Poor ◽  
Elicitation Process

Requirement elicitation is the actual description of the system that the software developers follow in the earlier stages of development process. It is one of the most important and primary part in developing a new application or project. It describes what a system should do and what it is capable of doing. There are some essential requirements of a system that must be met for its correct functionality. Many software systems fail due to the wrong requirement elicitation practices or poor requirement elicitation. Without the help of elicitation, it is impossible to find out the needs and the requirements of the user. In Pakistan software industry, requirement elicitation practices are not followed. In this paper, we have analyzed the issues and challenges being faced by the Pakistan software industry due to the poor requirement elicitation process. The identified issues in requirement elicitation process include a change of scope, volatility problem, change in user needs, understanding problem, uncertain requirements, communication problem, and missing requirements.

scholarly journals Investigating Fitness Functions for Search-based Requirements Prioritization

2021 ◽  
Author(s):  
Andrei Corezolla ◽  
Lincoln Costa ◽  
Francisco Carlos Souza ◽  
Alinne Correa Souza
Keyword(s):  
Genetic Algorithm ◽  
Development Process ◽  
System Development ◽  
Software System ◽  
Optimal Solutions ◽  
Requirements Prioritization ◽  
Empirical Results ◽  
Fitness Functions ◽  
Fitness Value

It can be challenging for people to select the most relevant requirementamong several software system development options.Requirements prioritization defines the ordering for executing requirementsbased on their priority or importance concerning stakeholders’viewpoints, which is a problematic task. Based on thisproblem, this study aims to present a requirements prioritizationapproach using a genetic algorithm to find optimal solutions, andit can assist in the requirements prioritization activity during thesoftware development process. In this paper, we investigated aset of criteria to create four functions GUT-D, ThS-D, ST, and LT,to assess candidate solutions, i.e., the recommended prioritizedrequirements. We examine the empirical results concerning thepractical approach’s effectiveness and cost computational two experimentsin the evaluation. We found that the 𝐺𝑈𝑇 − 𝐷 fitnessfunction achieved the best fitness value in different settings with90.51% and 98.63%. Besides that, our study demonstrates that the approachis promising to assist requirements prioritization since eachfitness function can be used individually according to companies’necessities.

scholarly journals THE MODEL FOR CALCULATING THE PRODUCTION PERIOD OF HARDWARE AND SOFTWARE SYSTEMS DESIGNED BY DEVELOPING COMPANIES

2021 ◽  
Vol 3 (65) ◽  
pp. 67-76
Author(s):  
Andrey A. Pertsev ◽  
◽  
Aleksandr N. Podobriy ◽  
Yuliya A. Radionova ◽  
◽  
...  
Keyword(s):  
System Development ◽  
Software Systems ◽  
Software System ◽  
Preliminary Assessment ◽  
Factors Influencing ◽  
Main Factors ◽  
Production Period ◽  
Hardware And Software System ◽  
Bulk Production ◽  
Duration Of Development

It is relevant for a developer of hardware and software systems to assess the duration of development in advance and determine the main factors influencing on its success. Bulk production or bulk production with little changes can be assessed based on the experience. However, when making preliminary assessment, some factors that had not a great effect before may not be considered. The article describes an approach to calculate the duration of hardware and software system development based on analogues, statistics and factors effecting the production. At the same time, it should be noted this method provides only a preliminary assessment and its usage requires additional s.

scholarly journals Prompt system redesign: Shifting to open source technology to satisfy user requirements

2010 ◽  
Vol 7 (3) ◽  
pp. 441-457 ◽  
Author(s):  
Igor Svetel ◽  
Aleksandar Djurovic ◽  
Vencislav Grabulov
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Development Process ◽  
System Development ◽  
User Needs ◽  
User Requirements ◽  
Software System ◽  
Short Period ◽  
Sustainable System ◽  
Selection Of

The paper describes a redesign project undertaken in a short period to adapt a software system to user needs. Additional goals of the project included a shift to Open Source software and the selection of technology to enable sustainable system development. The paper chronologically describes all phases of the project and provides reasons for all decisions taken during the development process. The paper concludes with a discussion of the merits of the redesign methodology.

Sign in / Sign up

Export Citation Format

Share Document