Components Association Mechanism Supporting Requirements Tracing

2014 ◽  
Vol 998-999 ◽  
pp. 591-596
Author(s):  
Hui Ling Wang ◽  
Li Peng ◽  
Yu Cheng Ding

Requirements Traceability has a very important role in the entire application development lifecycle. As for the problem of manual creating requirement traceability relationship time-consuming and error-prone effort problem, this paper proposed a new component-based dynamic requirement traceability model. The model incorporates the requirements specification model and component functionality tree model to format requirements documents and component library. Establish requirements traceability relationships through mutual matching between component facet functional items and requirement documents. Validate requirements traceability feasibility and efficiency through multiple systems and component requirements documents, the experimental results provided by the implemented system show that the model is valid, and efficiency and accuracy have been improved to some extent compared with the conventional information retrieval model.

2022 ◽  
pp. 819-834
Author(s):  
Nayem Rahman

Software development projects have been blamed for being behind schedule, cost overruns, and the delivery of poor quality product. This paper presents a simulation model of a data warehouse to evaluate the feasibility of different software development controls and measures to better manage a software development lifecycle, and improve the performance of the launched software. This paper attempts to address the practical issue of code defects in each stage of data warehouse application development. The author has compared the defect removal rate of their previous project to the newly proposed enhanced project development life cycle that uses code inspection and code scorecard along with other phases of software development life cycle. Simulation results show that the code inspection and code score-carding have achieved a significant code defect reduction. This has also significantly improved the software development process and allowed for a flawless production execution. The author proposes this simulation model to a data warehouse application development process to enable developers to improve their current process.


10.29007/cfm3 ◽  
2019 ◽  
Author(s):  
Salman Faizi ◽  
Shawon Rahman

Software application development must include implementation of core functionality along with secure coding to contain security vulnerabilities of applications. Considering the life cycle that a software application undergoes, application developers have many opportunities to include security starting from the very first stage of planning or requirement gathering. However, before even starting requirement gathering, the software application development team must select a framework to use for the application’s lifecycle. Based on the application and organizational characteristics, software application developers must select the best-fit framework for the lifecycle. A software application’s functionality and security start with picking the right lifecycle framework.When it comes to application development frameworks, one size does not fit all. Based on the characteristics of the application development organization such as the number of application developers involved, project budget and criticality, and the number of teams, one of the five frameworks will work better than others.Keywords: Software development lifecycle, software functionality, software security, application development, framework security


Author(s):  
Peter Torrellas ◽  
Daniel J. Paulish

This paper describes experience with developing and maintaining a requirements tracing model for a system of systems for Positive Train Control (PTC). Positive Train Control is a system of monitoring and controlling train movements to provide increased safety. A PTC system consists of four segments: locomotive, office, wayside, and communication. We have found that it is useful to describe the segments of a PTC system as a system of systems. A requirements tracing model has been developed to manage the requirements of a PTC system of systems. The tracing model provides traces from requirements, design, features, and test artifacts across the development lifecycle. Tracing models are required for safety-critical systems, and they are very useful for performing various types of impact analyses on a PTC development project. The characteristics of the tracing model are described and lessons learned with implementing the model are discussed.


2021 ◽  
Vol 11 (2) ◽  
pp. 683
Author(s):  
Juuso Autiosalo ◽  
Riku Ala-Laurinaho ◽  
Joel Mattila ◽  
Miika Valtonen ◽  
Valtteri Peltoranta ◽  
...  

Industrial Internet of Things practitioners are adopting the concept of digital twins at an accelerating pace. The features of digital twins range from simulation and analysis to real-time sensor data and system integration. Implementation examples of modeling-oriented twins are becoming commonplace in academic literature, but information management-focused twins that combine multiple systems are scarce. This study presents, analyzes, and draws recommendations from building a multi-component digital twin as an industry-university collaboration project and related smaller works. The objective of the studied project was to create a prototype implementation of an industrial digital twin for an overhead crane called “Ilmatar”, serving machine designers and maintainers in their daily tasks. Additionally, related cases focus on enhancing operation. This paper describes two tools, three frameworks, and eight proof-of-concept prototypes related to digital twin development. The experiences show that good-quality Application Programming Interfaces (APIs) are significant enablers for the development of digital twins. Hence, we recommend that traditional industrial companies start building their API portfolios. The experiences in digital twin application development led to the discovery of a novel API-based business network framework that helps organize digital twin data supply chains.


Author(s):  
Kamalendu Pal ◽  
Bill Karakostas

The adoption of agility at a large scale often requires the integration of agile and non-agile development practices into hybrid software development and delivery environment. This chapter addresses software testing related issues for Agile software application development. Currently, the umbrella of Agile methodologies (e.g. Scrum, Extreme Programming, Development and Operations – i.e., DevOps) have become the preferred tools for modern software development. These methodologies emphasize iterative and incremental development, where both the requirements and solutions evolve through the collaboration between cross-functional teams. The success of such practices relies on the quality result of each stage of development, obtained through rigorous testing. This chapter introduces the principles of software testing within the context of Scrum/DevOps based software development lifecycle.


Author(s):  
Nikos Kefalakis ◽  
John Soldatos

In recent years we have witnessed a proliferation of RFID (Radio Frequency Identification) middleware systems and projects (including several open source projects), which are extensively used to support the emerging wave of RFID applications. Some of the RFID middleware projects come with simple tools, which facilitate the application development, configuration, and deployment processes. However, these tools tend to be fragmented since they address only part of an RFID system (such as the filtering of tag streams and/or the generation of business events). In this chapter, the authors introduce an Integrated Development Environment (IDE) for RFID applications, which addresses multiple parts of an RFID application, while at the same time supporting the full application development lifecycle (i.e. design, development, deployment, and testing of RFID applications). The introduced IDE comprises a wide range of tools, which have been implemented as modular plug-ins to an Eclipse-based environment. The various tools enable application development, deployment, testing, and configurations over the middleware infrastructure established by the AspireRFID (AspireRFID Consortium, 2013), and their evaluation has proven that they can significantly ease RFID application development.


2022 ◽  
pp. 1059-1076
Author(s):  
Kamalendu Pal ◽  
Bill Karakostas

The adoption of agility at a large scale often requires the integration of agile and non-agile development practices into hybrid software development and delivery environment. This chapter addresses software testing related issues for Agile software application development. Currently, the umbrella of Agile methodologies (e.g. Scrum, Extreme Programming, Development and Operations – i.e., DevOps) have become the preferred tools for modern software development. These methodologies emphasize iterative and incremental development, where both the requirements and solutions evolve through the collaboration between cross-functional teams. The success of such practices relies on the quality result of each stage of development, obtained through rigorous testing. This chapter introduces the principles of software testing within the context of Scrum/DevOps based software development lifecycle.


2021 ◽  
Vol 13 (5) ◽  
pp. 2602
Author(s):  
Basit Shahzad ◽  
Fazal-e-Amin Fazal-e-Amin ◽  
Ahsanullah Abro ◽  
Muhammad Imran ◽  
Muhammad Shoaib

Software risks are a common phenomenon in the software development lifecycle, and risks emerge into larger problems if they are not dealt with on time. Software risk management is a strategy that focuses on the identification, management, and mitigation of the risk factors in the software development lifecycle. The management itself depends on the nature, size, and skill of the project under consideration. This paper proposes a model that deals with identifying and dealing with the risk factors by introducing different observatory and participatory project factors. It is assumed that most of the risk factors can be dealt with by doing effective business processing that in response deals with the orientation of risks and elimination or reduction of those risk factors that emerge over time. The model proposes different combinations of resource allocation that can help us conclude a software project with an extended amount of acceptability. This paper presents a Risk Reduction Model, which effectively handles the application development risks. The model can synchronize its working with medium to large-scale software projects. The reduction in software failures positively affects the software development environment, and the software failures shall reduce consequently.


This paper takes a deeper look at data breach, its causes and the linked vulnerability aspects in the application development lifecycle. Further, the Vulnerabilities are mapped to the software development life cycle (SDLC) involving requirement elicitation, design, development, testing and deployment phases. Being aware of exact SDLC life cycle where the vulnerabilities are injected, suitable security practices (countermeasures) can be adopted in delivery methodology, which can control the eventual data breaches and safeguard the application from security perspective. Our research focuses on Evolution of Vulnerabilities through the application development life cycle, and we have leveraged “Inverted Tree Structure/Attack Tree” and “Affinity Principles” to map the vulnerabilities to right Software Development Life Cycle.


Sign in / Sign up

Export Citation Format

Share Document