Requirements For Software Development Research Articles

Definition of the requirements architecture for IT solution as a business analytics product

The subject of research in the article is approaches to understanding and interpreting the concept of the architecture of requirements for an IT solution. The purpose of the work is to define the architecture of software requirements for a better understanding and further implementation of this concept in the practice of software development. The article addresses the following tasks: analyze approaches to the classification of requirements to determine common and distinctive characteristics and their impact on the definition of the architecture of requirements; examine requirements engineering standards to find the definition and any relationship to the requirements architecture; consider approaches to building a set of requirements and using templates to describe them to identify optimal strategies for business analytical processes and their impact on the architecture of requirements. The following methods are used: comparative analysis, including comparison and generalization of different classifications of requirements taking into account their impact on the definition of requirements architecture, review of literature and standards related to requirements engineering, as well as analysis of their impact on the process of formation of requirements architecture, analysis of documentation with the aim identifying optimal strategies for building the requirements architecture, as well as analyzing the use of templates for describing requirements and their importance in defining the requirements architecture. In addition, the requirements quality criteria analysis results were interpolated to identify relationships between the quality of requirements and their architecture, which made it possible to determine the optimal approaches to building the architecture of requirements that meet the requirements of software quality. The following results were obtained: approaches to understanding requirements in software development were investigated, generally accepted classifications of requirements and characteristics of quality requirements were given, and links of the chain "requirements – quality of requirements – approaches to description of requirements – standards – architecture of requirements" were analyzed with further logical interpolation of the studied context on the architecture of requirements, the author's definition of the concept of architecture of requirements is proposed. Conclusions. Requirements architecture can be based on different architectural frameworks and depends on software development methodologies, but at the same time, it can vary depending on industry standards and the needs of a specific project. Also, requirements architecture can use certain document templates, but it is not limited to them.

Reprocolla: Requirements Prioritisation Model with Collaboration Perspectives Based on Cost-Value Approach

The process of ranking requirements in software development is made up of various criteria and numerous stakeholders, which are properly selected for the effective prioritisation of software requirements. These requirements have encountered several challenges, including lack of scalability, complexity of pairwise comparisons and biases due to the cognitive load on stakeholders. Therefore, this research aimed to investigate and find solutions to improve the software prioritisation process using the Reprocolla model. The model was built by weighing the criteria in terms of benefits, opportunities, costs, and risks (BOCR) classification, which were then calculated using the fuzzy analytic hierarchy process (FAHP) method. Furthermore, the selection of alternatives was computed using the fuzzy technique for order preference using the similarity to an ideal solution (FTOPSIS) method. The success of Reprocolla was evaluated using seven datasets based on real projects and compared with the two existing methods for prioritising requirements, FAHP and FTOPSIS. The experiment results used inferential and descriptive statistics approaches with three indicators: accuracy, time consumption, and ease of use. Based on the three indicators mentioned above, the inferential statistics showed no significant difference between the perspectives of clients and developers. Whereas, descriptive statistics found that Reprocolla is more accurate, consumes less time, and has the highest ease of use percentage. The result showed that as stakeholders’ satisfaction level increases, the software development process becomes more accurate, thereby leading to a decrease in time consumption and a rise in ease ofusage. The result also showed that the development of the Reprocolla tool, a collaboration between humans and machines, enhanced the effectiveness of the requirements prioritisation process.

Modern Software Development for JUNO offline software

The Jiangmen Underground Neutrino Observatory (JUNO), under construction in South China, primarily aims to determine the neutrino mass hierarchy and to precise measure the neutrino oscillation parameters. The data-taking is expected to start in 2024 and the detector plans to run for more than 20 years. The development of the JUNO offline software (JUNOSW) started in 2012, and it is quite challenging to maintain the JUNOSW for such a long time. In the last ten years, tools such as Subversion, Trac, and CMT had been adopted for software development. However, new stringent requirements came out, such as how to reduce the building time for the whole project, how to deploy offline algorithms to an online environment, and how to improve the code quality with code review and continuous integration. To meet the further requirements of software development, modern development tools are evaluated for JUNOSW, such as Git, GitLab, CMake, Docker, and Kubernetes. This contribution will present the software development system based on these modern tools for JUNOSW and the functionalities achieved: CMake macros are developed to simplify the build instructions for users; CMake generator expressions are used to control the build flags for the online and offline environments; a tool named git-junoenv is developed to help users partially checkout and build the software; a script is used to build and deploy the software on the CVMFS server; a Docker image with CVMFS client installed is created for continuous integration; a GitLab agent is set up to manage GitLab runners in Kubernetes with all the configurations in a GitLab repository.

Using Artificial Intelligence in Software Development

The AI use is also heavily influencing software development. The demands on software are many, including its continuous update and ever-shorter development cycles. There is a growing need for shorter development cycles, flexibility and meeting requirements without compromising software quality. AI can help meet these requirements in software development. AI supports these goals. AI tools aid software development by supporting almost all development activities. It aids testing by making it faster and more efficient. The main possibilities to support activities in the different phases of software production are presented, based on tools that are available on the market and prototypes exploring the possible AI applications. The research purpose is to study the modern capabilities of AI in the domain of software production, its application limitations and to determine its role and place in software production

Specifying Requirements for Modern Software Development: A Test-Oriented Methodology

Most modern computer systems operate in distributed environments. To develop and test such applications, services, and systems, it is necessary to consider the physical devices, architectures, communication, security and deployment mechanisms involved. However, the requirements’ specification process still replicates that of traditional applications: details remain implicit and are hidden in the description. As a result, specifications are difficult to identify and, ultimately, tests are designed in the traditional way: they overlook constraints and fail to achieve the desired effects. Our objective is to design a methodology for specifying requirements in both traditional software and applications deployed in distributed environments. We present an iterative and incremental requirements specification methodology. This methodology allows us to describe functional requirements and incorporate non-functional or quality constraints, which is the main contribution of this proposal. To ensure that quality requirements are specified during the design phase, the methodology proposes a series of phases, stages and artefacts that ensure the discovery and consideration of these requirements. In order to find out the strengths and weaknesses of our methodology, we have carried out a comparative study with other similar proposals in the literature. To this end, evaluation criteria were defined by considering standards and good practices in Requirements Engineering. The results of the comparative study show that our methodology constitutes a solid procedure for a detailed requirements specification from the beginning of the software development cycle. This represents an advance over the rest of the proposals studied. Our methodology contributes to the simplification of the design and execution phases of software testing, enabling traceability between the specified requirements and the designed test cases.

Redesigning Graphical User Interface of Open-Source Geospatial Software in a Community-Driven Way: A Case Study of GRASS GIS

Learning to use geographic information system (GIS) software effectively may be intimidating due to the extensive range of features it offers. The GRASS GIS software, in particular, presents additional challenges for first-time users in terms of its complex startup procedure and unique terminology associated with its data structure. On the other hand, a substantial part of the GRASS user community including us as developers recognized and embraced the advantages of the current approach. Given the controversial nature of the whole issue, we decided to actively involve regular users by conducting several formal surveys and by performing usability testing. Throughout this process, we discovered that resolving specific software issues through pure user-centered design is not always feasible, particularly in the context of open-source scientific software where the boundary between users and developers is very fuzzy. To address this challenge, we adopted the user-centered methodology tailored to the requirements of open-source scientific software development, which we refer to as community-driven design. This paper describes the community-driven redesigning process on the GRASS GIS case study and sets a foundation for applying community-driven design in other open-source scientific projects by providing insights into effective software development practices driven by the needs and input of the project’s community.

Data security in smart devices: Advancement, constraints and future recommendations

AbstractNetwork security protocols are implemented to address network security challenges. Computer networks and applications have advanced and developed significantly in recent years, but consumers ‘excitement for network technology and high‐tech devices has been dampened by continual exposure to data security vulnerabilities. As of now, some individuals refuse to use smart devices due to concerns about the authenticity, confidentiality and integrity of data security leaks. This not only prompts Internet service providers to follow market protection mechanisms but also requires software developers to apply appropriate security protocols to protect computer network security. These applications’ dependability and integrity are dependent not just on the effectiveness of cryptographic algorithms, but also on key management protocols. Understanding network security protocols and implementing high‐quality standards to govern the transmission of data in the network are critical components of guaranteeing network security. The article explores data security, primarily at the application layer, various attack methods for different network security protocols and highlights the potential security implications. The study also looks at the corresponding, practical security measures and future research prospects for certain kinds of attacks. Finally, some technical challenges that remain unsolved at the time of writing are summarised, and future trends in cybersecurity are discussed.

Cloud-Based Software Development Lifecycle: A Simplified Algorithm for Cloud Service Provider Evaluation with Metric Analysis

At present, hundreds of cloud vendors in the global market provide various services based on a customer's requirements. All cloud vendors are not the same in terms of the number of services, infrastructure availability, security strategies, cost per customer, and reputation in the market. Thus, software developers and organizations face a dilemma when choosing a suitable cloud vendor for their developmental activities. Thus, there is a need to evaluate various cloud service providers (CSPs) and platforms before choosing a suitable vendor. Already existing solutions are either based on simulation tools as per the requirements or evaluated concerning the quality of service attributes. However, they require more time to collect data, simulate and evaluate the vendor. The proposed work compares various CSPs in terms of major metrics, such as establishment, services, infrastructure, tools, pricing models, market share, etc., based on the comparison, parameter ranking, and weightage allocated. Furthermore, the parameters are categorized depending on the priority level. The weighted average is calculated for each CSP, after which the values are sorted in descending order. The experimental results show the unbiased selection of CSPs based on the chosen parameters. The proposed parameter-ranking priority level weightage (PRPLW) algorithm simplifies the selection of the best-suited cloud vendor in accordance with the requirements of software development.

A systematic review of non-functional requirements mapping into architectural styles

Fortunately, the software attracted enough businesses to the market, allowing them to earn money in less time with less work and more accurate results. Software development life cycle (SDLC) is used for software development as it is responsible for system functionality, efficiency, maintainability, and any other non-functional system requirements. Each stage of the SDLC process is critical. However, software requirements and software architecture are both fundamental activities that play a vital role in all other SDLC stages. Non-functional requirements are critical to the success of any software because they explain all system quality attributes such as complexity, reliability, security, and maintainability, among others. The architectural styles assist you in determining which architecture may be best for your project requirements. This paper discusses several of the most important architectural styles that are best suited for mapping desired non-functional requirements for software development, as well as their comparison based on various quality attributes (non-functional requirements).

A hybrid technique using minimal spanning tree and analytic hierarchical process to prioritize functional requirements for parallel software development

A hybrid technique using minimal spanning tree and analytic hierarchical process to prioritize functional requirements for parallel software development

Improving Software Development Effort Estimation with a Novel Design Pattern Model

A U.S. Midwestern Fortune 500 financial services firm develops software capabilities in-house and requires predictions of project needs for efficient resource allocation decisions across the many projects operating simultaneously. The company develops a novel prediction tool based on the projects’ required software development tasks as described by firm-specific design patterns. The firm provides these predictions within a set of estimates based on industry standard function count methods as well as firm-specific predictive models based on function points and on initial labor assignments. Company management is thus equipped with predictions from multiple methodologies and multiple information sources, enhancing the firm’s ability to predict project needs. Managers aggregate the forecasts, with prediction performance estimated to improve by 35%–49%, measured relative to estimates of the absolute percentage error of the prior method. The improved predictions provide a significant advantage to planning decisions and efficient internal operations. Insights to how managers aggregate the set of forecasts and insights to how the models contribute to the scaled value of information are discussed and further illustrate the benefits of the approach.

Development of Android-Based 3d Animation Learning Applications to Support Distance Learning for the D4 Animation Study Program, Udinus Semarang

The existence of the COVID-19 pandemic has become a big problem in practicum courses, especially the 3D1 Animation course at the Dian Nuswantoro University animation study program, Semarang. Lecturers cannot guide students directly when experiencing obstacles in the learning process such as during face-to-face learning. The purpose of this research is to create an android application for learning media 3d1 animation. In this application there are several menus including the semester learning plan menu, video tutorials, task collection, consultation with lecturers, remote desktop requests and othersRemote desktop features to make it easier for lecturers to guide students remotely. This study uses the waterfall method, namely software requirements analysis, design, development, testing, and maintenance with testing using the black box method. The test results show that each aspect has results that can be concluded as successful and feasible. This research succeeded in developing android-based 3d1 animation learning media.

The effect of advice network connectedness on problem-solving competence among software developers

Software development requires software developers to share knowledge and solve problems together. Although researchers have considered the business and technical knowledge germane to performing software development tasks, empirical studies investigating business and technical advice networks on problem-solving competence is scarce. Using social network theory, we argue that software developers must be embedded for knowledge brokering within and across business and technical advice connectedness for improving problem-solving competence. Moreover, we argue that contact quality matters in increasing or decreasing individual problem-solving competence. We present data collected via an online survey from 153 respondents in a professional software organisation. Our findings suggest that software developers who engage in knowledge brokering in business and technical advice connectedness will increase problem-solving competence in the software development effort. Our findings also reveal no significant effect of contact quality between these advice networks and problem-solving competence. We discuss our findings’ implications for theory and practice.

Aplikasi Pengenalan Nama Benda dalam Bahasa Jepang dengan Metode GDLC Berbasis Android

The development of information and communication technology in the field of education can turn abstract learning into concrete through android-based learning media. The development of learning media requires software development methods, one of which is the Game Development Life Cycle (GDLC) method. Game Development Life Cycle (GDLC) is a method that handles game development from start to finish. This educational game contains elements of text, images, audio and 3D animation that are designed as attractive as possible to increase the attraction for beginners in learning Japanese. In making this educational game using Adobe Photoshop and Unity 3D software. The purpose of this study is to help beginners learn to know more about recognizing object names in Japanese with an attractive appearance and provide a different atmosphere and learning method.

General Roadmap and Core Steps for the Development of AI Tools in Digital Pathology.

Integrating artificial intelligence (AI) tools in the tissue diagnostic workflow will benefit the pathologist and, ultimately, the patient. The generation of such AI tools has two parallel and yet interconnected processes, namely the definition of the pathologist’s task to be delivered in silico, and the software development requirements. In this review paper, we demystify this process, from a viewpoint that joins experienced pathologists and data scientists, by proposing a general pathway and describing the core steps to build an AI digital pathology tool. In doing so, we highlight the importance of the collaboration between AI scientists and pathologists, from the initial formulation of the hypothesis to the final, ready-to-use product.

Design and implementation of the whole process collaborative system for software development

With the increasingly urgent and arduous task of software development, software engineering development tools that can efficiently respond to the continuous changes in software requirements, rationally plan the software development process, and control the development cost will be widely used in software engineering. In response to actual needs, the supporting tool is designed to meet the system requirements, software requirements and software design and development. First, we use visualization modeling optimization technology of structured analysis and design method to build demand analysis models and system design models; Secondly, the dynamic verification technology of data model logical consistency is adopted to verify the logical consistency of data model in evolution; finally, the verification of the system model is achieved through hierarchical flow diagrams, fully expanded flow diagrams and statistical views. The vehicle cruise control system is selected for application verification, and the tool meets the requirements of software development and improves the software quality.

Smart automotive technology adherence to the law: (de)constructing road rules for autonomous system development, verification and safety

Abstract Driving is an intuitive task that requires skill, constant alertness and vigilance for unexpected events. The driving task also requires long concentration spans, focusing on the entire task for prolonged periods, and sophisticated negotiation skills with other road users including wild animals. Modern motor vehicles include an array of smart assistive and autonomous driving systems capable of subsuming some, most, or in limited cases, all of the driving task. Building these smart automotive systems requires software developers with highly technical software engineering skills, and now a lawyer’s in-depth knowledge of traffic legislation as well. This article presents an approach for deconstructing the complicated legalese of traffic law and representing its requirements and flow. Our approach (de)constructs road rules in legal terminology and specifies them in ‘structured English logic’ that is expressed as ‘Boolean logic’ for automation and ‘Lawmaps’ for visualization. We demonstrate an example using these tools leading to the construction and validation of a ‘Bayesian Network model’. We strongly believe these tools to be approachable by programmers and the general public, useful in development of Artificial Intelligence to underpin motor vehicle smart systems, and in validation to ensure these systems are considerate of the law when making decisions.

The use of WEB-oriented technologies in the process of WEB-programming teaching for technical universities students

The realities of the XXI century - informatization, digital transformation, high technologies, WEB-technologies in particular - put Ukraine state in front of global challenges of creating a digital state. It is the implementation of a number of digital projects which form the digital space of the state, in particular those coordinated by the Ministry of Digital Transformation of Ukraine. The development of a significant number of applications requires the state to constantly update them, maintain them working, which requires qualified programmers. The task of technical universities is to train competitive specialists in the IT field. This study analyzes the results of a survey of students of NTUU "Kyiv Polytechnic Institute. Igor Sikorsky ”, the purpose of which was to find out what integrated development environments and programming languages ​​senior students independently choose when developing programs within the educational and professional programs of the faculty, and which correlate with software used by programmers in the implementation of large IT-enterprises, in particular WEB-programming languages. The results of the study showed as well that the rating of programming languages and the use of integrated development environments meet modern requirements for software development. 76.7% of graduates, while being students, are already employed in IT companies as full-time employees. The high percentage of employment suggests that graduate students of the Faculty of Informatics and Computer Engineering of Igor Sikorsky NTUU KPI are competitive in the modern IT labor market.

Design and Practice of Software Architecture in Agile Development

Software architecture design is a very critical part of the software development process. In order to be able to respond to changes in user requirements in software development in a timely manner, a convenient and lightweight development model should be adopted. Agile development adopts a human-oriented, step-by-step development process that can quickly respond to changes in software requirements, adjust the design of software architecture in a timely manner and adapt to software development in a dynamic environment. Based on the analysis and comparison of traditional development process and agile development process, this paper analyzes the key technologies in agile architecture design and proposes a software architecture design method based on agile development mode.

Managing non‐functional requirements in agile software development

Non-functional requirements define qualities of the software system that ensure effectiveness while embedding any constraints and restrictions on the design. A challenge rises with agile implementation in handling non-function requirements in regulated environments. Thus, a practitioner's perceptions of agile method tailoring are described in relation to inter-team boundaries and non-functional requirements. The research comprises 18 practitioner interviews from two multinational agile software development companies. Interviews were recorded, transcribed, and analysed using an approach informed by grounded theory and information flow models were used to compare and contrast interactions of processes. It was discovered that one of the case study companies managed non-functional requirements as artefacts in their agile methodology, while the other company reverts to conventional plan-based software development practices of documentation, timeline estimations, and safety critical requirements. This research creates a detailed comparison of these contrasting approaches. The main contribution of this study is a set of proposed recommendations to deal with non-functional requirements in a regulated environment using agile techniques. The introduction of two new artefacts, Documentation Work Item and Safety Critical Work Item, is recommended and it is accompanied with an illustrative example, to transform the handling of documentation and safety critical requirements in a more agile way.