A Software Development Approach for Robotics Control Systems

Safe Comp 95 ◽  
1995 ◽  
pp. 317-330
Author(s):  
Emilio Ruiz Morales
Keyword(s):  
Software Development ◽  
Control Systems ◽  
Development Approach

scholarly journals Methodology of software development for artificial microclimate control systems

2020 ◽  
pp. 21-31
Author(s):  
Ihor Golinko ◽  
Pavlo Gikalo
Keyword(s):  
Control System ◽  
Software Development ◽  
Control Systems ◽  
Mass Exchange ◽  
Air Conditioning ◽  
Block Diagram ◽  
Dew Point ◽  
Program Logic ◽  
Air Conditioners ◽  
Exchange Processes

The specificity of accelerated software development for microcontrollers is considered. The software development technique for a program-logic controller is presented on the example of an algorithm for controlling the industrial premises microclimate. The method of “dew point” for the control system of industrial air conditioning. The analysis of the functioning of the control system of industrial air conditioning according to the “dew point” method has been carried out and a block diagram of the control system of an artificial microclimate has been proposed. Structurally, the mathematical description of an artificial microclimate system is presented, which takes into account the nonlinearity of mass-exchange processes of air preparation. It can be used by specialists to implement computer-integrated technologies and to analyze and adjust the parameters of the control system of industrial air conditioners.

scholarly journals Systematic Literature Review: Causes of Rework in GSD

2022 ◽  
Author(s):  
Shiza Nawaz ◽  
Anam Zai ◽  
Salma Imtiaz ◽  
Humaira Ashraf
Keyword(s):  
Literature Review ◽  
Software Development ◽  
Systematic Literature Review ◽  
Empirical Literature ◽  
Global Software Development ◽  
Time Zones ◽  
Multiple Challenges ◽  
Development Approach ◽  
Different Cultures ◽  
Geographical Locations

Global Software Development (GSD) involves multiple sites which comprise of different cultures and time zones apart from geographical locations. It is a common software development approach adopted to achieve competitiveness. However, due to multiple challenges it can result in misunderstandings and rework. Rework raises the chance of project failure by delaying the project and increasing the estimated budget. The aim of this study is to identify and categorize the rework causes to reduce its frequency in GSD. To identify the empirical literature related to causes of rework, we performed a Systematic Literature Review (SLR). A total of 23 studies are included as a result of final inclusion. The empirical literature from the year 2009 to 2020 is searched. The overall identified causes of rework in GSD are categorized into 6 major categories which are communication, Requirement Management (RM), roles of stakeholders, product development/integration issues, documentation issues, and differences among stakeholders. The most reported rework causes are related to the category of communication & coordination and RM. Moreover, an industrial survey is conducted to validate the identified rework causes and their mitigation practices from practitioners. This study will help practitioners and researchers in addressing the identified causes and therefore reduce the chances of rework.

Agile Software Engineering

2010 ◽  
pp. 28-37
Author(s):  
Ernest Mnkandla
Keyword(s):  
Software Development ◽  
Production Process ◽  
Software Products ◽  
Agile Methodologies ◽  
Software Productivity ◽  
Software Production ◽  
Agile Software Engineering ◽  
Development Approach ◽  
Agile Software ◽  
Traditional Approaches

This chapter aims to reveal agile techniques that have been applied to software development and have resulted in meaningful improvements in software productivity. Available literature generally state some claims on the gains associated with the use of particular agile methodologies in software development. What lacks however, is a comprehensive analysis of how the application of agile techniques as a family will lead to improvement in software productivity. This chapter therefore provides such details. Software productivity techniques provide ways of measuring three things in order to determine the productivity of software; software products, software production processes and structures, and software production setting. Agile methodologies improve software productivity by focusing on the software production process and structures. The fundamental concern of this chapter is to show that agile methodologies measure the production process activities in a different but effective way from the more traditional approaches. For example, time-to-market is reduced by use of an iterative incremental development approach.

The Table to Tablet (T2T) therapy software development approach

2015 ◽  
Author(s):  
Luis M. T. Jesus ◽  
Joaquim Santos ◽  
Joana Martinez ◽  
Marisa Lousada ◽  
Daniel Pape
Keyword(s):  
Software Development ◽  
Development Approach
Sign in / Sign up

Export Citation Format

Share Document