Processing Requirements by Software Configuration Management (original) (raw)

Requirement Design for Software Configuration and System Modeling

Intelligent Automation & Soft Computing, 2022

Software Configuration Management (SCM) aims to control the development of complex software systems. Traditional SCM systems treat text files as central artifacts, so they are mainly developed for source code. Such a system is not suitable for model-based software development with model-centric artifacts. When applying traditional systems to model-based software development, new challenges such as model mapping, differentiation, and merging arise. Many existing methods mainly use UML or domain-specific languages to determine model differences. However, as far as we know, there is no such technology for System Modeling Language (SysML) models. SysML covers the entire development life cycle of various complex systems, covering information, processes, hardware and software. SysML contains nine types of diagrams for system modeling. One of them is the SysML requirement diagram, which is used to capture the functional requirements of the system. We propose a differentiation method for the SysML demand model. We recommend to create a SysML requirement model in the CASE tool first, and then export the SysML model in the form of XMI. Then, we parse the XMI representation through difference calculations. Finally, we summarize the results in annotated form. We implemented our method in a satellite system case study and demonstrated the experimental use of the method.

Towards a Dynamic Model for Requirements Handling in Software Architecture Configuration Management

Lecture Notes on Software Engineering, 2016

Nowadays the role of software architecture is obvious. Both complex requirements and non-deterministic chang ing environments lead software architecture to face with problems for coverage of requirements and environments. Consequently, the configuration of the software architec ture is faced with challenges even in run-time. Being able to deal with such problems requires new techniques to be used. In spite of variety of related works performed in this domain, improvements are required in some aspects such as consideration of overlap and contradictory require ments and also effects in dynamic environments. In this paper, a dynamic model is presented for handling chang ing requirements which makes use of the configuration management concepts such as versioning, composition, consistency, construction, and selection; hence the possibility of configuring software architecture in overlapped and contradictory requirements and dynamic environ ments has been provided in the proposed model. The model includes change management and versioning activities for software architecture and its artefacts. The results of performing the proposed model on a case are reported in this paper.

Requirement Change Management Techniques in Software Systems

2019

During software development requirement gathering is an important phase. Requirements are the basis of software development. The success or failure of any software depends upon level of understanding developed in requirements. During software development requirements keeps on changing due to different reasons. Hence requirements are such a critical phase that leads to the total project failure. So, to understand the impacts and to identify the conflicts with existing requirements, it is important to manage and analyze the requirements well. Requirement change management is the interest of this paper. Different requirement change management techniques has been discussed in this paper and analyzed them well and finally conclude the results accordingly.

Supporting requirements model evolution throughout the system life-cycle

2008

Abstract Requirements models are essential not just during system implementation, but also to manage system changes post-implementation. Such models should be supported by a requirements model management framework that allows users to create, manage and evolve models of domains, requirements, code and other design-time artifacts along with traceability links between their elements.

Software Configuration Management and Change Management

2009

Nowadays, as the use of computers is rapidly spreading to our life, software is getting more and more complex and large in computer systems. Therefore, the software configuration management (SCM) is playing an increasingly important role in the software development process. One of its significant activities is change management, which has an outstanding role in dealing with the continued and concurrent change requirements during the system development and use.

Requirements-driven configuration of software systems

2005

Reverse engineering aims at extracting many kinds of information from existing software, such as requirements specifications, design documents, and system artifacts, and using this information in system renovation and program understanding [WCRE].

Configuration Management for Designs of Software Systems

Configuration management systems are traditionally concerned only with source code. However in large-scale projects, capturing the evolution of design artifacts is crucial to the success of the software products. This paper presents a novel tool to provide version control and configuration management supports for design artifacts as well as specifications and documentations produced during a software life cycle. The tool is distinguished itself from existing ones by its ability to manage the evolution of the semantic relationships between design objects and implementation source code. This paper also describes the use of that tool in the software concordance integrated development environment to manage the evolution of software projects.

Change requirement management issues for a large software development projects

2013

There are no major organizations that are free from the challenges of initiating, developing and implementing effective software changes management. Only few project managers got the ability to manage the change efficiently. As a result, software practitioners recognize that strategic change is not temporary issues but it is continued process. Software Change requirement management approach is required for constantly evolving systems to support the comprehension, implementation, and evaluation of changes. A lot of research efforts have been spent on this subject over the last twenty years, and many approaches were published likewise. But, there has not been an extensive attempt made to develop an approach that can support current software change requirement management in practice. Therefore, this paper examines issues of software change requirement management approach and investigates and compares current practice issues of a software change requirement management approach, examining their strengths and weaknesses. It also reviews existing popular tools and models of software change requirement management and how it supports to the current software change managements. Finally, it will identify existing issues of current processes and suggests the need of proper approach that can support to the current practice.

A Customized Data Model for an Integrated Process of Requirements and Configuration Management

Journal of Aerospace Technology and Management

This work aims to propose a customized, open-source data model for supporting an integrated process of Requirements and Configuration Management that allows for keeping track of which requirement originated each part, subsystem and systemand vice versa-, over their entire life cycle. That model might prospectively contribute to the processes of Aeronautical Engineering design and Continued Airworthiness in organizations that do not want either to invest in complex existing commercial, proprietary software packages or to train their professionals for that purpose. The complete source code of the model is provided in Python and SQL languages.

Review of Requirements Management Issues in Software Development

A requirement is a capability to which a product or service should conform to. A meticulous consideration to requirements engineering acts as a backbone of software projects. Ambiguous and unrealistic requirements are major source of failure in the software-intensive systems. Requirements engineering processes are complex as most of the requirements engineering documentation is written in natural languages which are less formal and often distract the designers and developers. Requirements management is a continuous process throughout the project life cycle and relates to documenting, analyzing, tracing and prioritizing requirements and then finally controlling changes. The main issues related to requirements management are usually social, political and cultural. Software requirement engineers who gather the requirements generally consider that such issues are beyond the scope of their profession as they deem them within the project management ambit. In this study, we highlight the management issues that arise in the requirements engineering process and explore the possibilities to tackle them amicably. The study is supplemented with a critical review of the existing methodologies for resolving and managing software requirements.