Incorporate
Success Indicators in Software Change Control Model for Minimizing Change
Effects
By
Shazia parveen
Department of Computer Science, Government
College University Faisalabad,
Pakistan
Supervised by
Sami Ullah1, SohailIqbal2,
Nafees Ayub3, Dr. Ramzan Talib4, Umar Sarwar5
Department of Computer Science,
Government College University Faisalabad, Pakistan
Abstract:The software is designed for a system or to assist a system, the study
of software development process is based on the analysis phase the next phases
are design, code, and testing and after that software maintenance process
starts that continues after the delivery of software. These are the very basic
principle of engineering that we follow in software development process. The
latest trends and practices have changed the working principles of development
cycle. The study of design and implementation is increasing day by day. The
system acceptability and usability teaches people to demands more that’s way
changes occurs during the developing cycle and after the delivery of product,
so a change can affect the software other modules to reduce these problem
development team needs a effective change control model that have define set of
rules to implement change. Nearly in one decade GSM technology has a verity of
implementation that is not a single example there are many more examples like
that this indicates that new technology have new changes. So this study is
based over change indicators and their role in the general software development.
The researchers will purpose new change control model which will be based over
not only the software analysis phase but these will also consider the change
indicators as a part of this. Moreover purposed model is based on the
classification of the change. This feature will make the software more
customizable and adaptable more over increase the customer trust on the
software development team.
Keywords:Software Change, software development process, Change Control Process,
Change Impact, Effective Change Control Model, Change Indicators.
The software
changes are common problems for the software development team. The environment
and trends are changing rapidly because changes are necessary for any software
product. In the current world software core development team approach to
developing quality software in short time at low cost in this changing
situation over the last twenty years companies software development they are
using new approaches to software development according to new cultures. Still,
we have seen that the development of complex software make it harder to change
the state of the consumer market and change. The old approach to software
development is not able to meet new market demands and to complete all the
requirements considered and applied to develop can be applied immediately.
There is a better way to deal with change and be free from hazards that may be
associated with the transformation of this analysis is an integral part of the
development process should be warned. It is suggested that the two types of
threats as the primary method for predicting sensitivity analysis: the change
in design requirements unstable and where the most vulnerable areas identified
needs. Processes change impact analysis support the decision-making process and
to assess the risks of the possible effects of change is used to predict.
Change control is the heart of the software configuration phase, created by the
goods in the product life-cycle management, and control of the release of the
baseline and change. In this document the definition of software configuration
management is described and projects the effect of a specific software
development, and noted that to effectively fight the change and the
introduction of basic management through the graphic expression of the software
project basic of the most common. Then, focus on the study of change of the
field, through the graphic display cascade model change in the size and
determine exchange rates, and the change request and evaluate change, and to approve
the modification or reject the change management process (Xing, 2010). The main
problem for the software development team is software maintenance after
delivery of the software. This may include new customer requirements, software
update error correction. Maintenance management is found in products services
information technology, accounting for over 50% of the total cost of the
development budget. One of the main reasons for the high cost is software
updates and bug fixes. software development and management services in the
field of the contradictions that occur when changes inevitably lead to further
price increases, which leads to maintenance problems, confusion and
misunderstanding. information technology software product management and
configuration management software (SCM) software to improve products and
services in order to maintain consistency of approach Here, a conceptual
framework showing the relationship between the four areas SMC and software
development, including within the integrity necessary to implement the
established reference, and keep those forced interstate relations. Any kind of
development model, waterfall, rapid prototyping and spiral development is
flexible enough to apply (Ping and Jianyang, 2007). The research is based on about
global study of the process of change management software software developers
to develop software for different situations and different organizations may
have different economic cycle than the cycle can be changed after some time or
by the adoption of new strategies or change can be produced by a change in the
organizational structure there some other reason. The main focus of the
development team to satisfy the customer, the customer will be more satisfied
when he has your desired characteristic in your product. The success of the
software is not easy to measure is a clear indication in two categories first
success is the success of software that is primary (software functionality)
success and the second success is your success in the future (adaptation to
change) The main objective of this research is to handle the requirement of
change in the process of software development and after delivering software
efficiently leading the development team to implement change successfully, the
changes are evident after the first product delivery that cannot be assumed
that developed the product is the final product without further addition or
deletion of software functionality is required. Software teams have a risk in your
mind before implementing change that change can affect the overall performance
of the software product to reduce that risk, indication of success will be
incorporated into the model change in each step showing the level sensitivity
of change in the basis of the change will be a priority. The information
technology is currently growing faster field. Most organizations have changed
their process of manual work to computer due to data processing is faster and
less occurrence of errors in the software to the time customers is increasingly
IT literate, and who understand their needs, this customer to demand more now
before it changes one day comes more often from one side to the client during
the development process and after development. Through a mechanism of risk
control effective exchange rate can be reduced and the chances of product
failure can be minimized in projects such as space devices, transportation,
avionics defense but the medical field have more importance are used in
connection with a change because these devices have a direct effect on human
health life. Changing needs of software
development projects are the main source of risk. To minimize the impact of
change there are a number of model changes already proposed. It is suggested
that the two types of threats as the primary method for predicting sensitivity
analysis: Change in unstable design requirements and in the most vulnerable
areas identified needs. Processes change impact analysis support the
decision-making process and to assess the risks of the possible effects of
change is used to predict. The research is based on about global study of the
process of change management software developers to develop software for
different situations and different organizations may have different economic
cycle than the cycle can be changed after some time or by the adoption of new
strategies or change can be produced by a change in the organizational
structure there some other reason. The main focus of the development team to
satisfy the customer, the customer will be more satisfied when you have your
desired feature in your product. The success of the software is not easy to
measure no clear indication in two categories first success is the success of
software that is primary (software functionality) success and the second
success is your success in the future (adaptation to change). On the other
hand, many of these projects will be critical factors, therefore, they should
be. One of the ways to highlight the view of these factors through the use of
risk management practices. Moreover, processes, techniques and the use of risk
management tools recognized the importance of software development
environments. Some authors believe that project management manages risks. Most
of the failures of the project due to poor risk management on the part of the meaning
is. Risk management is one of the sections of the project, and its use will
grow in size and complexity of the growing need for software. If you are a
company considering the complexity of information technology hardly feels good
to be a project. Running simultaneously on different projects, and they have
the same environment, they are sharing resources. But relations between the
projects - the scope, cost, time and quality - therefore, there is a concern
not only for the project in each constraint. In this case, the project aims to
optimize the use of resources, environment management activities. Usually
software products to companies, it is possible, and in many cases need to
develop or survive. Similarly, products that meet their needs, according to the
software development process, cost, time, scope and quality of the product
inside are generally aligned with the business models of these companies make.
Faced with these challenges, companies that make software for their projects,
due to the lack of effective and proactive management practices under penalty
of losing their place in the market should be able to manage. Then, you can,
for example, an organizational structure that allows you to review the projects
must have increased the risk of providing better risk management-driven, and
based on the information indicating the risk of loss of control.
(Diaz et al.,
2013)To raise the level of software engineering is an important element In a
large software intensive Agile Software Development (ASD) Systems. Currently,
the software architectures Mechanism is often contacted by Software designed
and developed gradually able to of architectures. Be the lightweight design
decisions should be through the provision of a process that can be thinking of
agile knowledge to help architects Transformation. This paper presents a novel
solution Knowledge as the key engine change impacts using Graceful design. The
solution consists of Page this analysis and a set of models to help influence
Architects in graceful Page (decision -making) through the process of
retrieving the impact of architectural changes to add or change properties of
the resulting Repetition after repetition. To validate our approach, we have
developed the practice by running the solution Project management systems in
power measurement Software smart electricity networks in the factory.
Modern
iterative software development and software development team and the meetings
among stakeholders and encourage frequent interaction. This conversation
gradually or suddenly change the conditions meet the expectations of the
stakeholders to create change requests with development needs, during
development, and software developers about the status of incomplete sampling in
software change requests is to assess the impact of change is important. This
phase of software development the effect of changing the size of the estimate
(CISE) offers new perspective. In addition, this policy is to support the
implementation and evaluation of a prototype tool has been developed. To
evaluate this approach using a case study method to estimate the size of the
effect of a change in the function and accuracy of this approach is confirmed
(Asl and Kama, 2013) Maintenance costs for developers and users of software
systems are becoming a big problem. Risk of changing needs, especially in
environments where software changes are frequently coming, handling change is
an important aspect of maintenance (Ajrnal Chaumun et al., 1999). In this study author’s assumption to transform
high- level design for more than a risk to have an impact on the maintenance
and investigation has revealed that the quality characteristics. (OO) systems
and object-oriented approach to assess the variability of the types of systems
is to calculate the effects made by changes. The model describes the effects of
low -level transformation and is mapped to C + + language. Large industrial
software system to assess the practical application of the model, and its
telecommunications systems to include the effects of a change to experience
Software easily change the results may indicate that absorption, and a good
selection of traditional OO design metrics can be used as indicators of change.
Software change impact analysis ( CIA) use to determine the potential impact
occurs Due to the proposed changes , and program a graphical representation of
the most widely used application access to the CIA's analysis techniques to
determine its effects(Li et al.,
2013) . For analysis after many false positives, which would be lost, and with
the resources - they are often likely to affect a wide range of elements that
account. Moreover, these techniques do not exist in reality, the proposed
changes do not interfere between.. '' '' S natural tendency of water wave propagation
proposed by the CIA by our motivated. The process of wave -like spread of the
CIA in the process We first created by the essence of perceived changes ( to a
certain set of methods ) determined . Then we analyze the effects ripple
through the center spread of the Log In real-world software projects,
experimental evaluation of our approach and demonstrate the effectiveness of
the CIA. Consequences of changes in our CIA technique known better effect when
predicting results, and provide for practical use can provide a source that
indicated Moreover, it effectively ( chart -based advocacy ) compared to
traditional techniques the CIA at the cost of missing few false negatives can
eliminate false positives .With increasing demands on the Today program, software
developers reduce software engineering that can be changed without the risk of
software products is a must. One way to cope with changes in the program of
their causes and effects features. Software developers to change the properties
of a procedure, for example, by using various quality features that allows the
impact of change, transformation, and that needs to change type, and where
changes need to be part of the system due to. This information was then used to
describe the potential impact of change can be. In this paper the
characteristics of the software engineering literature offers a systematic
review. The results of this systematic review used a System Architecture Change
Characterization Scheme (SACCS) was creating. Software Engineering table in
this report examines the key areas involved. SACCS aim at a higher level that
will affect software engineering program is to identify replacement properties
(Williams and Carver, 2010). The flexibility and efficiency of software
projects desirable but conflicting objectives in the development of software
(Wang et al., 2008). We studied the
relationship between project performance, flexibility, and management
interventions. Specifically, we studied the flexibility of the program as a
mediator between the two management control mechanisms recommended (management
review and change control) and project performance. The evaluation model
experimentally using data collected from 212 project managers in the Project
Management Institute. Our results confirm that the level of surveillance
activities during the process of development of the system was an important
facilitator of software flexibility, which, in turn, enhance the success of the
project. Mediator of flexibility in the program means that the higher levels of
management controls could achieve higher levels of flexibility in the program
and that it was beneficial not only to the maintenance of complex applications
but also to project performance. Currently we have little theory and fewer
tools to help us manage the maintenance process.
The reason
for the difficulty is the less information stored in design phase. It produces
an increasing concern with the installation and maintenance of the code. We
provide an alternative model: make the
design the main focus of the construction process for the code as a byproduct;
make the design of a central element in the process of maintenance and
preservation of the revised access to the code as in the design of the product
before (Baxter and Pidgeon, 1997). Assess variation software systems is a major
concern for buyers of large systems found in fast-changing fields such as
telecommunications (Kabaili et al.,
2001). One way to address this problem is to study the dependence on the
diversity of the programs and their design, in order to find design
characteristics that can be used as indicators of change. In the field of
object-oriented systems, experiments were carried out shows that the coupling
between the layers such as this indicator. Dealing with dependence now points
more inevitable impact of software changes and expression analysis. Software
modifications including middleware components, such as a Web service exposes
these organizations serving the unforeseen chain reaction often leads to a
failure of the system software. The current model for analyzing the impact of
software changes not adequately address the situation. Moreover, with the
expansion of the size and complexity of software programs, give information
about your understanding of web software engineers. Preparation of the research
work analyzes the expansion of the impact analysis of changes to existing
software to be interoperable distributed applications to resolve dependencies
and to examine the three-dimensional visualization software (3D) navigation is
more efficient. Stojanov described a basic commodity must meet changes in the
software lifecycle. The main problem in managing the change process specified
by the customer requests a change after delivery processing software. Change
requests of customers using the website developer often are presented of. This
article explains that the client generates a change request to produce a new
way to help change request. Send requests generated model change includes three
views:
The path of the application, it may request the
generator Based on the change of change, and change requests, even requests
Product Model Integration model. In a specific XML format, flip the switch via
HTTP requests to the developer's site. Sheriff Williams verification and
validation methods and often reported various types of software development
artifacts. Safe and validation errors in the records of the files show how the
change in response to change and do not see them together build. By adjusting
the value of the unit as a result of the changes we have to analyze the
recording of the new system was proposed to determine the capabilities of the
software. Based on this approach by the groups, the error in the direction of
history and allows you to change the failure of the library code. Five systems,
open source software, we then conducted a case study of this process. We have
to attack the source of updates of our strategies, make it small, are not
always effective in identifying stakeholders and recognize the changes in the
file system developers. We also compare the results of our technical analysis
methods and the other two; We will provide the same results in our technology,
but also to ensure that it can be affected by the changes in the files to see
other than the source.
Mayhew, though a bit more, they are widely used in
Worsley, describes the development of the system will be discussed today. The
main reason for this situation is to control the process of iterative
development mode example of the director of the project. This paper frame
design, from common changes that occur in the control system, describes a
method based on the use of force. However, advances in English, design,
monitoring and evaluation of development for commercial purposes Real shipyard
to control the phases of this change.
- III.MATERIALS
AND METHODS
In these days software product accounts for more than thirty-two percent
of the software in most organizations. Although the executives tracking and
analysis of dependency supported actually analyze the impact of the programs in
the past, they do not adequately address in this direction. As software systems
grow in size and complexity, networks, adoption of information also extends
beyond the ability of most software engineers to understand (Bohner, 2002).
Researcher describes a method to quantify the precise impact of technology to
change the program without trouble. Method is used to measure small variations
of the software to determine the impact of technology. Researcher illustrate this approach in a detailed case
study on the impact of the use of two technologies, including source code
editor and copy sensitive environment field application engineering product in
telecommunications. In both cases, the change has been reduced effort.
Methodology can be measured accurately and cost savings in change efforts,
simple and inexpensive because it depends on the information that is collected
automatically by the version control systems (Atkins et al., 2000).Continuous availability is a key requirement for a
large class of software systems. For these systems, the evolution of the system
can reduce run-time costs and risks associated with the shut down and restart
the system to update. Provide structure on the basis of the evolution of
software runtime and the emphasis on the role of support programs and links
approach to implementing the change.
At the end of this phase, and offer a better understanding of the
definition, the information is classified.
Found that the categorization of information as a
result of the mapping of risk indicators, ad hoc review of the literature and
the establishment of indicators as a basis for the SEI risk taxonomy was used
for definition. Finally, risk indicators and risk management in the field of
project management software qualitatively through questionnaires sent to
experts, with the aim of identifying areas for improvement were evaluated, and
the research methodology adopted to evaluate the risk of losses.
Risk Management in Multiple Projects Environments
Project management situations, it can be argued
that all the projects have risks. Before the project, the project itself is a
risky decision, so in order to identify the various internal and external
environmental factors, an analysis of the feasibility of the project is
necessary. Control and monitoring of risks in the project life cycle to enable
more effective decision-making, the main critical success factors is a way to
perform better visualization. Projects in the field of risk management
environments because of its inherent existence of the projects have been
studied in recent years, academics and industry experts.
Therefore, the scope of risk management, cost, time
and quality, particularly focused on issues related to project management in
all phases of the expansion. In other words, the property managed; there are
several factors that contribute to the failure of the project. An institutional
environment, it is important to realize that there are many projects running
simultaneously. In this sense alone, only need to analyze the critical success
factors. Projects to share resources and people, and existing projects, because
the company is linked to the strategic objectives and successful because they
have not been optimized to take into account, according to the context, the barriers
between each project and projects, it is necessary to simultaneously manage
several projects.
There is a consensus on risk management activities
in general. These are:
i)
Planning Risk Management:
The objective of this activity is to define the
strategy of risk management, the necessary resources and the timetable for
carrying out the process of risk management. According to PMBOK this activity
generates an artifact called Risk Management Plan, describing policies, costs,
liabilities, calendar and all activities necessary to implement Risk
Management.
ii) Risk
Assessment:
This activity consists of two processes: Hazard
Identification and Risk Analysis. The first aims to increase the possibilities
and existing events on a project or organization, while the second
characterizes and gives priority to the risks identified in order to assist in
decision-making. To identify the risks of the following techniques can be used:
brainstorming, work breakdown analysis, risk breakdown structure, checklists,
among others. Risk analysis characterizes the most important aspects of risks,
with the aim of exploring the best mitigation strategies. In view of the risk
identification deepens. In this process, the risks are generally classified and
prioritized according to some specific criteria in order to focus on risk
management in major risk factors. It also determines risk drivers and makes
estimates, commonly through the analysis of probability - - probability and
impact - consequences of an event.
iii)
Planning risk:
This activity aims to manage the risks identified
according to their analysis. We assume that an organization or a single project
cannot cope with all the risks identified in the same time, therefore, risk of
planning activity selects the risks to be managed. In addition to these risks,
contingency plans and action plans (to minimize or avoid) are made
iv) Risk
control:
Risk Control is responsible for monitoring and
tracking of risks and to check whether the risk management activities have been
effective. With this activity, you can update mitigation strategies and to
reorganize the risk priority, once during the project life cycle new risks may
arise and other risks may have their priorities reduced.
v) Risk
communication:
This activity is a critical component to successful
risk management because risk communication enables the exchange of information
among stakeholders in the project, contributing to the collective effort and
integration of activities in the risk management process.
Multiple Project Risk Management
Companies often manage risks of each project
separately, and do not observe the influence of risk on the level of
organization among projects.
The
proposed indicators Applications
Indicators are primarily decision support,
knowledge and tools for the control of measured companies and properties. The
project is the use of indicators in the environment a better understanding of
matters relating to the environment, especially in the processes, products
(software and related artifacts), which allows resources and projects. The
collection of information identified in the environmental risk, and at the same
time allowing the analysis and definition of strategies for the appropriate
risk factors, the risk level is defined by the - planned accidents. Another point
to note is that it allows the project life cycle analysis of the impact of
actions through the use of indicators in this sense, there is a risk control
facilities. A reasonable range of application of the proposed indicators at
different levels of management, are. In addition, depending on the preferences
of the company to focus on the structural indicators, some of the risk factors
that allows the assignment of responsibilities. This is due to the
classification of software projects committed to the environment, and the risks
of expansion and adaptation indicators provide insight into the well. It
collected information from indicators, properly structured, project risks,
provides a historical view is noteworthy that enable the organization to execute
the benchmark. Therefore, the collection of experiences increases the chances
of success of new and ongoing projects will help to create a better knowledge
of the company. In addition, the indicators, along with other identification
techniques and the use of risk analysis give a complementary view. In view of
this, indicators of view, multi-project environment, risk management aims to
improve the risk assessment of the activities of the main existing models of
risk management software projects additional tool from the consensus. In the
software industry, the introduction of new methods of software development is
growing rapidly. Initially, development organizations collocated software, but
eventually moved on the world market.. Low labor costs, expert contacts,
proximity to markets and customers access to the latest technology by GSD
software industries are some of the reasons. Similarly, geographical distance,
time difference, like the difference between social and cultural challenges of
communication, collaboration, knowledge management and knowledge sharing issues
that result. Requirements engineering is a branch of engineering software,
which is subdivided into two phases.
First phase is called phase of development
requirement and the second phase is called phase requirements management. Phase
development is required activities requirement collection, analysis,
documentation and validation. The purpose of the requirement development is the
creation and analysis of customer needs. Requirement change management is a
difficult task and it became more difficult in software development worldwide.
The team members are geographically distributed in any other country in the
world where the cost of software development is reduced. Software companies
that are in high-cost countries are trying to reduce development costs by
hiring programmer decade low cost countries worldwide. Global software
development process, the cost of labor has decreased due to its many
advantages, twenty-four hours of development time, at any place at any time of
the availability of people with the skills of a great importance of the
software industry, the rapid communication, increased access to the customer
and the market and new technology to know how. Other technologies, such as the
software development process, the cultural and linguistic differences, there
are some risks, as well as background knowledge can cause the failure of the
project, a variety of factors, etc., are in different time zones. A decade ago,
the world of software developers faced the problem of the failure of the market
for the project. With the passage of time and the best technology, the world of
software development problems is minimized. However, the need for change
management, communication, face to face at any time they can communicate with
each other and because of the distribution of more than collocated team work
between team members is a challenge. Lack of understanding of the needs of the
team members and the world face the problem are in the process of software
development, technical and non-technical risks involved. Technology, strategy
and systems, a lack of coordination among the problems faced with the need to
change the management plan. Therefore,
knowledge of the software development lifecycle structural changes taking place
in at any time to deal with all the dispersed team members involved should be
shared. Changes often, consistent product quality and the technical team and
the business carried out by the impact of disappointing results. Change management
is a crucial part of the requirement in the software process engineering
requirements. It plays a key role in the production of any software
development. Software change request, in the traditional process. In this
process, the change request and a note by the client, the change request
manager who is responsible for preparing the request for change, to be started
later. Then give priority to the demand and to determine the effect of the
change, the next step is to solve the conflicts between the need. This research proposes a model of RCM. GSD
they need to respect the environment and maintaining the structural change in
the draft in order to demonstrate its effectiveness refers to how software
development should be incorporated into the frame. GSD environment so that
developers have to deal with the problems and have the ability to determine a
common understanding of the diversity policy, the development of a new
framework is essential to the current time, scattered throughout the world.
Using knowledge management system requirements for the models, our goal is to
define the exchange of knowledge and mutual understanding among the various
stakeholders. It also solves the problems of ambiguity in the requirements so
that the model explains the need.
Traditional Requirement Change Request Process
Model
Architectural view of Proposed Requirement Change
Management Model
- IV.RESULTS
AND DISCUSSION
In recent requirement different models change
management year for software development worldwide have been proposed. Some of
these models have been studied. The brief description of these models is
presented in detail, for example, and proposes a framework used to manage
changes in requirements for technical, industrial and business application. All
changes were analyzed before being approved by the Exchange Control Board after
analyzing the impact of change and regulation of the process of change. The
full evaluation report is recorded with all changes and report also documents
the individual assessment of changes in the process lifecycle software
development. The parameters evaluation report, impact analysis, change control,
change log, check for changes by changes of control table, update document,
dashboard changes are identified. The proposal authors focus is on
process-oriented information is used to manage customer needs through
innovative approach to information management framework use system. The ERIM
framework requirements means the company in Information Management and the cost
and time of construction project throughout the project life cycle is reduced.
Authors described controlled version of the application and registration of all
changes in the new version of the system in a database. Version control
minimizes the impact of changes in the system requirements. Chua and Vemer
determined effort estimation of the resumption of changes in the requirements.
The framework reduces the risks in estimating the effort to return to work and
control changes. The frame estimated the cost of rework and the impact of
changes in requirements are analyzed. Changing forms approved inspection
requirement apply the change, then the relationship between change and the need
to return to work in change management is described. In Smite the concept of
social mediation between the end user and the developer is applied. Mediation
of a partner helps in buying software and developer support during development.
Following problems have occurred during his work as a difference in
terminology, lack of language skills, lack of consistency in working practices,
customers, the unwillingness of employees to collaborate and lack of version
control. The authors have proposed a model that can be adopted by all types of
software organizations. One of the main challenges is managing dispersed teams
and is trying to respond to user expectations in case of problems. Development
team does not adjust the project to the client when the client application is
completely meaningless. Most require the co management model is used for
software projects and accurately distributed software projects to have
sufficient capacity to accommodate the needs. Therefore, changes in the
distribution of software for project management are needed to find new models.
This model to improve its software products for global software development has
been designed. Based on the facts collected by literature and expert opinion,
it is being applied this model.
The investigation began with a
detailed literature review, journal articles, conference proceedings, books,
research reports. A questionnaire will be prepared for a survey consisting of
three basic categories technical, non-technical and attitudes (personal and
behavioral) skills that are affected requirement change management in the
process of global software development. The scale is used to design a
questionnaire for the survey. Statistical analysis was carried out on the
management requirements paradigm shift in the global development of software to
test the effectiveness of the proposed model. GSD is following an environment
that is difficult to follow a normal process of change management. We apply our
framework of the organization and take expert opinion. expert opinion process
is used to take the opinion of RCM for customer satisfaction and easy to learn.
The panel of experts with a team leader fifteen years experience three software
engineers from where you have an experience of ten years and two have managers
experience of three projects eight years with three, five and seven years of
experience, respectively two RE engineers who have six years of experience, and
two members of quality assurance with five years of experience Our model would
be helpful for the software industry in general, in the opinion of experts.
Experts who have used other models found that our framework was giving better
results. However, according to some experts, our model is needed to evaluate
further studies to obtain the best results in the GSD to implement software
industries on a large scale. The results of our assessment are the opinion of
several experts who agreed partially agreed and disagreed, shown in Table The
expert opinion of a graph of our model is also shown. And the difference in
performance between RCM processes and clearly shown that the proposed model is
perfect for organizations. Based on the initial assessment, experts understand
the needs of the management model are changing and requirements change
management and may think that. However, other companies to meet the
requirements of change management may need to use.
It is said that questionnaires can
be used to reach a wider group of participants, it takes less time to
administer, and can be analyzed more rigorously. It can also be administered at
several points in the design process, even during tasks requirements capture,
analysis and evaluation, in order to obtain information on the needs,
preferences and user experience. Given that the evaluator is not likely to be
directly involved in carrying out the questionnaire, it is vital that is well
designed. The first thing the evaluator must establish is the purpose of the
questionnaire: what information is sought? It is also useful to decide at this
stage how the questionnaire responses will be analyzed. There are a number of
styles of questions that can be included in the questionnaire. As a rule they
are multiple choice open, close or finished, scale, composition qualified. This
section presents the results and conclusions of change control model already
presented and weaknesses of these models have made the author are presented.
The questionnaire method was used to collect information for evaluation
purposes.
The
main objective of this research was the introduction of an effective model of
change control software. This research is expected to be helpful in decision
making so that users who are in the field of software development could take
advantage of that model and research. For this purpose has been studied most of
the previous model and discussed with experts. This research concluded that the
above Software Change Models has some shortcomings as a process is too long to
implement the change, the change is not handled properly creates a lot of
obstacles to the confidence level of the development team and users is also
effects with attitude the development team when their demands or requirements
below rejected on small businesses do not have adequate equipment for analysis
of change due to lack of resources. Most developers do not get satisfactory
response by using older models. This is leading to dissatisfaction of this
ancient change control processes. After analyzing customer trends and
developers effective change model is proposed and evaluated, and the answer is
satisfactory.
Akinsola,
A.O., Potts, K.F., Ndekugri, I., Variations on construction projects: A review
of empirical studies, Building Research & Information 22 (5) (1994)
269-271.
Arain,
F.M., IT-based approach for effective management of project changes: A change
management system (CMS), Advanced Engineering Informatics 22 (4) (2008)
457-472.
Arain,
F.M., Pheng, L.S., Modeling for management of variations in building projects,
Engineering, Construction and Architectural Management 14 (5) (2007) 420-433.
Arain,
F.M., Pheng, L.S., The potential effects of variation orders on institutional
building projects, Facilities 23 (11/12) (2005) 496-510.
B.
Kitchenham, T. Dybå, M. Jørgensen, “Evidence-based Software Engineering”, 26th
International. Conference on Software Engineering, (2004) 273-281
Bohner, S.A. Software change impacts-an
evolving perspective. in Software Maintenance, 2002. Proceedings. International
Conference on. 2002. IEEE.
Bower,
D., A systematic approach to the evaluation of indirect costs of contract
variations, Construction
Breech, B., M. Tegtmeyer, and L. Pollock. A
comparison of online and dynamic impact analysis algorithms. in Software
Maintenance and Reengineering, 2005. CSMR 2005. Ninth European Conference on.
2005. IEEE
Charoenngam,
C., Coquinco, S.T., Hadikusumo, B.H.W., Web-based application for managing
change orders in construction projects, Construction Innovation: Information,
Process, Management 3 (2003) 197-215.
Chui Wu, “Exploring impacts of software
development process maturity on project risk,” 2008 IEEE International
Conference on Industrial Engineering and Engineering Management, pp. 1033-1037,
Dec.
Construction
Engineering and Management 131 (11) (2005) 1219-1223.
D. Izquierdo-cortazar et al., “Using Software
Archaeology To Measure Knowledge Loss in Software Projects Due To Developer
Turnover ∗,” System, pp. 1-10, 2009.
D. W. Karolak, “Software Engineering Risk Management”,
IEEE, Washington, DC, USA, 1996.A. Hosseingholizadeh, “A source-based risk
analysis approach for software test optimization,” 2010 2nd
International Conference on Computer Engineering and Technology, pp.
V2-601-V2-604, 2010.
E. Souza, C. Gusmão, K. Alves, J. Venâncio, and R. Melo,
“Measurement and control for risk-based test cases
and
activities,”. LATW’09. 10th Latin American Test Workshop, 2009.Neumann, P.,
Computer-Related Risks. 1995. Reading: Addison-Wesley, 1995.
G. P. Kulk, R. J. Peters, and C. Verhoef, “Quantifying
IT estimation risks,” Science of Computer Programming, vol. 74, no. 11-12, pp.
900-933, Nov. 2009.
Hanna,
A., Camlic, R., Peterson, P., Nordheim, E., Quantitative Definition of Projects
Impacted by Change Orders, Journal of Construction Engineering and Management
128 (1) (2002) 57-64.
Hao,
Q., Shen, W., Neelamkavil, J., Thomas, R., Change management in construction
projects, Institute for Research in Construction, National Research Council
Canada, London, Ontario, Canada, 2008.
Ibbs,
C., Quantitative Impacts of Project Change: Size Issues, Journal of
Construction Engineering and Management 123 (3) (1997) 308-311.
Ibbs,
C.W., Wong, C.K., Young Hoon, K., Project change management system, Journal of
Management in Engineering 17 (3) (2001) 159.
Ibbs,
W., Impact of Change’s Timing on Labor Productivity, Journal of
Ibbs,
W., Nguyen, L., Lee, S., Quantified Impacts of Project Change, Journal of
Professional Issues in Engineering Education and Practice 133 (1) (2007) 45-52.
Isaac,
S., Navon, R., Modeling building projects as a basis for change control,
Automation in Construction 18 (5) (2009) 656-664.
J. Biolchini, P. Mian, A. Natali and G. Travassos, Systematic
review in software engineering. Technical Report, Federal University of Rio de
Janeiro, Brazil, TR ES 679/05, 2005.
J. Kontio, Software engineering risk management: a
method, improvement framework, and empirical evaluation, Doctoral Dissertation,
Helsinki University of Technology, Finland, 2001.
J. Pajares and A. López-Paredes, “An extension of the
EVM analysis for project monitoring: The Cost Control Index and the Schedule
Control Index,” International Journal of Project Management, vol. 29, no. 5, pp.
615-621, Jul. 2011.
J.
Rong, L. Hongzhi, Y. Jiankun, S. Yafei, L. Junlin, and C. Lihua, “An Approach
to Measuring Software Development Risk Based on Information Entropy,” 2009
International Conference on Computational Intelligence and Natural Computing,
pp. 296-298, Jun. 2009.
J. S. Persson, L. Mathiassen, J. Boeg, T. S. Madsen, F.
Steinson, “Managing risks in distributed software projects: an integrative
framework”, IEEE Transactions on Engineering Management, v. 56, n. 3, p.
508-532, Aug. 2009.
Jarratt,
T.A.W., Eckert, C.M., Caldwell, N.H.M., Clarkson, P.J., Engineering change: an
overview and perspective on the literature, Research in Engineering Design 22
(2) (2011) 103-124.
K.
Emam and A. Koru, “A replicated survey of it software project failures”, IEEE
Software, p. 84-90, 2007.
Keane,
P., Sertyesilisik, B., Ross, A., Variations and Change Orders on Construction
Projects, Journal of Legal Affairs and Dispute Resolution in Engineering and
Construction 2 (2) (2010) 89-96.
L. Ribeiro, Processo ágil para gestão de riscos em
ambientes de múltiplos projetos. Master Dissertation in Computer Engineering,
Escola Politécnica de Pernambuco, Universidade de Pernambuco, Brazil, 2009.
M. Benaroch and A. Appari, “Financial Pricing of
Software Development Risk Factors,” IEEE Software, vol.
Management
and Economics 18 (3) (2000) 263-268.
Mayhew, P., C. Worsley, and P. Dearnley,
Control of software prototyping process: change classification approach.
Information and Software Technology, 2009. 31(2): p. 59-66
Mosley, V., How to assess tools efficiently
and quantitatively. Software, IEEE, 1992. 9(3): p. 29-32.
Motawa,
I., A systematic approach to modelling change processes in construction
projects, Australasian Journal of Construction Economics and Building 5 (1)
(2005) 23-31.
Motawa,
I.A., Anumba, C.J., El-Hamalawi, A., A fuzzy system for evaluating the risk of
change in construction projects, Advances in Engineering Software 37 (9) (2006)
583-591.
Motawa,
I.A., Anumba, C.J., El-Hamalawi, A., Chung, P.W.H., Yeoh, M., An innovative
approach to the assessment of change implementation in construction projects,
2nd International Conference on Innovation in Architecture, Engineering and
Construction, Loughborough University, Loughborough, U.K., 2003, pp. 729-740.
Motawa,
I.A., Anumba, C.J., Lee, S., Peña-Mora, F., An integrated system for change
management in construction, Automation in Construction 16 (3) (2007)
368-377.
N.
Mustafa, “Software Risk Assessment Visualization Tool Design Using
Probabilistic Inference Models,” Journal of Management, pp. 1-3, 2010.
O. Perminova, M. Gustafsson and K. Wikstrom, “Defining
uncertainty in projects – a new perspective”. International Journal of Project
Management, v. 26, n. 1, p. 73-79, Jan 2008.
Runeson, P. and M. Höst, Guidelines for conducting and reporting
case study research in software engineering. Empirical software engineering,
2009. 14(2): p. 131-164.
S. Lopes, Análise e definição de métricas para o
processo de gerência de riscos para projetos de software. Graduation Work in
Computer Science, Centro de Informática, Universidade Federal de Pernambuco,
Brazil,
Serag,
E., Oloufa, A., Malone, L., Radwan, E., Model for Quantifying the Impact of
Change Orders on Project Cost for U.S. Roadwork Construction, Journal of
Construction Engineering and Management 136 (9) (2010)
1015-1027.
Sun,
M., Fleming, A., Senaratne, S., Motawa, I., Yeoh, M.L., A Change Management
Toolkit for Construction Projects, Architectural Engineering and Design
Management 2 (4) (2006) 261-271.
Sun,
M., Meng, X., Taxonomy for change causes and effects in construction projects,
International Journal of Project Management 27
V. Holzmann, I. Spiegler, “Developing risk breakdown
structure for information technology organizations”, International Journal of
Project Management, v. 29, n. 5, p. 537-546, Jul. 2011.
Points: 90000
Reviews: 1085
Donate