Change Requests | ScienceGate

An extensive literature review shows that Information Systems (IS) are changed and eventually replaced by substitutes under the influence of productivity, popularity, and specialisation of IS along with associated available support facilities, maintenance activities, failures, and user feedback. This chapter compiles those factors emerged from software engineering, IS, software quality assurance measurements, and computer science literature. A final product is a proposed model bringing those factors together as they are suspected to raise a need for taking the decision of evaluating change requests that may lead to a further maintenance or replace the IS. While keeping in mind that limitations on advanced testing exist, an expected service of such a model may help decision makers to explain maintenance/replacement decision of IS/component in a more itemized manner, hence diminish overburden pressure of experience responsibility on them.

Download Full-text

Agile Scrum Issues at Large-Scale Distributed Projects

10.4018/978-1-6684-3702-5.ch019 ◽

2022 ◽

pp. 388-398

Author(s):

Ayesha Khalid ◽

Shariq Aziz Butt ◽

Tauseef Jamal ◽

Saikat Gochhait

Keyword(s):

Software Development ◽

Large Scale ◽

Software Industry ◽

Small Scale ◽

Project Organization ◽

Distinctive Features ◽

Main Components ◽

Change Requests ◽

Agile Model ◽

Large Scale Project

The agile model is a very vast and popular model in use in the software industry currently. It changes the way software is developed. It was introduced in 2001 to overcome deficiencies of software development in a workshop arranged by researchers and practitioners who were involved with the agile concept. They introduced the complete agile manifesto. The agile model has main components that make it more viable for use in well-organized software development. One of these is scrum methodology. The reason for the agile-scrum popularity is its use for small-scale projects, making small teams and allows change requests at any stage of a project from the client. It works for client satisfaction. Instead of so much popularity and distinctive features, agile-scrum also has some limitations when used for large scale projects development that makes it less efficient for development. This article discusses the agile-scrum methodology and its limitations when using for large-scale project organization.

Download Full-text

Software Requirements Risk and Maintainability

Encyclopedia of Information Science and Technology, First Edition ◽

10.4018/978-1-59140-553-5.ch454 ◽

2005 ◽

pp. 2562-2566

Author(s):

Norman F. Schneidewind

Keyword(s):

Risk Factors ◽

Life Cycle ◽

Software Metrics ◽

Space Shuttle ◽

Software Requirements ◽

Requirements Specifications ◽

Requirements Change ◽

Code Metrics ◽

Change Requests

In order to continue to make progress in software measurement, as it pertains to reliability and maintainability, there must be a shift in emphasis from design and code metrics to metrics that characterize the risk of making requirements changes. By doing so, the quality of delivered software can be improved because defects related to problems in requirements specifications will be identified early in the life cycle. An approach is described for identifying requirements change risk factors as predictors of reliability and maintainability problems. This approach can be generalized to other applications with numerical results that would vary according to application. An example is provided that consists of 24 space shuttle change requests, 19 risk factors, and the associated failures and software metrics.

Download Full-text

Systematic Decision Support for Engineering Change Management in PLM

Volume 3: 25th Computers and Information in Engineering Conference, Parts A and B ◽

10.1115/detc2005-85267 ◽

2005 ◽

Cited By ~ 3

Author(s):

Nikhil Joshi ◽

Farhad Ameri ◽

Debasish Dutta

Keyword(s):

Change Management ◽

Lead Times ◽

Change Orders ◽

Engineering Change ◽

Engineering Change Management ◽

Industry Standard ◽

Downstream Effects ◽

Engineering Changes ◽

Automated Tools ◽

Change Requests

Engineering Change Management (ECM) is an important component of PLM. ECM modules in current PLM solutions conform to the industry-standard CMII closed-loop change model. They provide customised forms and pre-defined workflows for creating and processing change requests, change orders, etc. Evaluating the effects of the proposed Engineering Change on manufacturing processes, BOM, lead times, inventory, etc., usually form tasks in this generic workflow. However, each change has different downstream effects, which themselves lead to further changes that may not be evident. Identifying these impacts requires considerable experience and expertise. This paper addresses the need for automated tools to assist this process. The approach involves dynamic creation of workflow tasks for evaluating cascaded effects of any change using a predefined industry specific knowledge base. The process is further enhanced by prioritising the evaluation of effects based on experience generated by past engineering changes.

Download Full-text

A Multidomain Engineering Change Propagation Model to Support Uncertainty Reduction and Risk Management in Design

Journal of Mechanical Design ◽

10.1115/1.4007397 ◽

2012 ◽

Vol 134 (10) ◽

Cited By ~ 38

Author(s):

Bahram Hamraz ◽

Nicholas H. M. Caldwell ◽

P. John Clarkson

Keyword(s):

Prediction Method ◽

Propagation Model ◽

Change Propagation ◽

Levels Of Abstraction ◽

Propagation Models ◽

Engineering Change ◽

Change Requests ◽

Current Engineering ◽

Different Levels ◽

Linkage Model

Engineering change (EC) is a source of uncertainty. While the number of changes to a design can be optimized, their existence cannot be eliminated. Each change is accompanied by intended and unintended impacts both of which might propagate and cause further knock-on changes. Such change propagation causes uncertainty in design time, cost, and quality and thus needs to be predicted and controlled. Current engineering change propagation models map the product connectivity into a single-domain network and model change propagation as spread within this network. Those models miss out most dependencies from other domains and suffer from “hidden dependencies”. This paper proposes the function-behavior-structure (FBS) linkage model, a multidomain model which combines concepts of both the function-behavior-structure model from Gero and colleagues with the change prediction method (CPM) from Clarkson and colleagues. The FBS linkage model is represented in a network and a corresponding multidomain matrix of structural, behavioral, and functional elements and their links. Change propagation is described as spread in that network using principles of graph theory. The model is applied to a diesel engine. The results show that the FBS linkage model is promising and improves current methods in several ways: The model (1) accounts explicitly for all possible dependencies between product elements, (2) allows capturing and modeling of all relevant change requests, (3) improves the understanding of why and how changes propagate, (4) is scalable to different levels of decomposition, and (5) is flexible to present the results on different levels of abstraction. All these features of the FBS linkage model can help control and counteract change propagation and reduce uncertainty and risk in design.

Download Full-text