In the age of fast evolution, software development project must accept many challenges of unpredicted requirements change and new technology environment. Software development processes should have adjustable and extendable features to meet the multifaceted needs of the users. Iterative and Incremental Development (IID) is a practical approach to overcome the various challenges of software development.
However, continuous testing and building new versions need to spend more time and human resources that is a major obstacle of IID. The other, the iterative operations must have a sound communication skills. Lack of standard version control and intercommunication manner often lead to failure of software project. High quality Continuous Integration (CI) environment can effectively make up the defects of IID. In this paper, CI environment and advantages are deeply surveyed. In order to overcome the defects of IID, CI environment needs combine the perfect procedures and qualified tools, and concretely enhance the quality of CI environment. Based on the process quality measurement model, this paper proposes the Process
Quality Improvement Mechanism (PQIM). Applying PQIM, in software development, the processes problems and the CI environment quality defects can identify timely and indeed revise to reduce the risk of CI environment.
A maintainability enhancement procedureijseajournal
In mobile communications age, environment changes rapidly, the requirements change is the software
project must face challenge. Able to overcome the impact of requirements change, software development
risk can be effectively decreased. In order to reduce software requirements change risk, the paper
investigates the major software development models and recommends the adaptable requirements change
software development. Agile development applied the Iterative and Incremental Development (IID)
approach, focuses on workable software and client communication. In software development, agile
development is a very suitable approach to handle the requirements change. However, agile development
maintenance existed many defects that include development documents control, user story inspection and
CM system. The maintenance defects of agile development should be improved. Analysing and collecting
the critical quality factors of agile development maintainability, in this paper proposes the Agile
Development Maintainability Measurement (ADMM) model. Based on ADMM model, the Agile
Development Maintainability Enhancement (ADME) procedure can be defined and deployed for reducing
the risk of requirements change.
STRATEGIES TO REDUCE REWORK IN SOFTWARE DEVELOPMENT ON AN ORGANISATION IN MAU...ijseajournal
Rework is a known vicious circle in software development since it plays a central role in the generation of
delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative
impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth
with the notion of rework in software development as it occurs in practice by analysing a development
process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce
rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best
strategy that is software configuration management to reduce the rework problem in software development
Flexibility a key factor to testability ijseajournal
Testability is an important software quality factor that is ineffective if it is not available at an early stage in
the development life-cycle. It becomes more essential in the case of object oriented design. Flexibility is an
important key factor to testability analysis and measurement for delivering high class testable and
maintainable software. Flexibility is a criterion of crucial significance to software developers, designers
and the quality controllers. It constantly guides and supports to avoid wastage of resources as well as
enable the designers for continuous improvement in the development process. Flexibility is concerned with
building high quality and reliable software within the constraints of cost and time. It greatly influences
cost, quality and reliability at software evolution process. Despite the fact flexibility is vital and highly
significant aspect for software development processes, it is poorly managed. This paper focuses the need
and importance of flexibility early at design phase. A model has been proposed for flexibility measurement
of object oriented design by establishing multiple linear regression. Finally the proposed model has been
validated using experimental tryout.
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into
subsystems, functional modules and basis components. Finally, all tested components have to integrate to
be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development
model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is
an IID implementation concept which can effectively reduce software development risk. Web app with high
change characteristic is suitable to use agile development model as the development and maintenance
methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept
can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration
operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase
stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into subsystems, functional modules and basis components. Finally, all tested components have to integrate to be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is an IID implementation concept which can effectively reduce software development risk. Web app with high change characteristic is suitable to use agile development model as the development and maintenance methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
International Journal of Business and Management Invention (IJBMI)inventionjournals
International Journal of Business and Management Invention (IJBMI) is an international journal intended for professionals and researchers in all fields of Business and Management. IJBMI publishes research articles and reviews within the whole field Business and Management, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online
A maintainability enhancement procedureijseajournal
In mobile communications age, environment changes rapidly, the requirements change is the software
project must face challenge. Able to overcome the impact of requirements change, software development
risk can be effectively decreased. In order to reduce software requirements change risk, the paper
investigates the major software development models and recommends the adaptable requirements change
software development. Agile development applied the Iterative and Incremental Development (IID)
approach, focuses on workable software and client communication. In software development, agile
development is a very suitable approach to handle the requirements change. However, agile development
maintenance existed many defects that include development documents control, user story inspection and
CM system. The maintenance defects of agile development should be improved. Analysing and collecting
the critical quality factors of agile development maintainability, in this paper proposes the Agile
Development Maintainability Measurement (ADMM) model. Based on ADMM model, the Agile
Development Maintainability Enhancement (ADME) procedure can be defined and deployed for reducing
the risk of requirements change.
STRATEGIES TO REDUCE REWORK IN SOFTWARE DEVELOPMENT ON AN ORGANISATION IN MAU...ijseajournal
Rework is a known vicious circle in software development since it plays a central role in the generation of
delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative
impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth
with the notion of rework in software development as it occurs in practice by analysing a development
process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce
rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best
strategy that is software configuration management to reduce the rework problem in software development
Flexibility a key factor to testability ijseajournal
Testability is an important software quality factor that is ineffective if it is not available at an early stage in
the development life-cycle. It becomes more essential in the case of object oriented design. Flexibility is an
important key factor to testability analysis and measurement for delivering high class testable and
maintainable software. Flexibility is a criterion of crucial significance to software developers, designers
and the quality controllers. It constantly guides and supports to avoid wastage of resources as well as
enable the designers for continuous improvement in the development process. Flexibility is concerned with
building high quality and reliable software within the constraints of cost and time. It greatly influences
cost, quality and reliability at software evolution process. Despite the fact flexibility is vital and highly
significant aspect for software development processes, it is poorly managed. This paper focuses the need
and importance of flexibility early at design phase. A model has been proposed for flexibility measurement
of object oriented design by establishing multiple linear regression. Finally the proposed model has been
validated using experimental tryout.
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into
subsystems, functional modules and basis components. Finally, all tested components have to integrate to
be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development
model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is
an IID implementation concept which can effectively reduce software development risk. Web app with high
change characteristic is suitable to use agile development model as the development and maintenance
methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept
can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration
operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase
stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into subsystems, functional modules and basis components. Finally, all tested components have to integrate to be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is an IID implementation concept which can effectively reduce software development risk. Web app with high change characteristic is suitable to use agile development model as the development and maintenance methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
International Journal of Business and Management Invention (IJBMI)inventionjournals
International Journal of Business and Management Invention (IJBMI) is an international journal intended for professionals and researchers in all fields of Business and Management. IJBMI publishes research articles and reviews within the whole field Business and Management, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online
A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR MOBILE APPLICATIONS DEVELOPMENT ijseajournal
With the increasing in mobile application systems and a high competition between companies, that led to
increase in the number of mobile application projects.
Mobile software development is a group of process for creating software for mobile devices with limited
resources like small screen, low-power. The development of mobile applications is a big challenging
because of rapidly changing business requirements and technical constraints for mobile systems. So,
developers faced the challenge of a dynamic environment and the Changing of mobile application
requirements. Moreover, Mobile applications should adapt appropriate software development methods that
act in response efficiently to these challenges.
However, at the moment, there is limited knowledge about the suitability of different software practices for
the development of mobile applications. According to many researchers ,Agile methodologies was found to
be most suitable for mobile development projects as they are short time, require flexibility, reduces waste
and time to market.
Finally, in this research we are looking for a suitable process model that conforms to the requirement of
mobile application, we are going to investigate agile development methods to find a way, making the
development of mobile application easy and compatible with mobile device features.
FISHBONE ANALYSIS ON WASTES IN SOFTWARE DEVELOPMENT USING THE LEAN I.T. PRINC...ecij
The transformative global economy posed challenges to businesses in service management. In this computing age, the perceptual and operational edge of a certain business or organization manifested on the kind of technology it offers in the Service Management. Organizations have long recognized the
importance of managing key resources such as people and information. Information has now moved to its rightful place as a key resource in the organization and therefore management of the same can be instituted by employing methodology. To keep their brand promise, technology has been used;The number of new entrants to every sectors of economy has grown significantly in recent years, and each firm strives to make their daily operation efficient in which demand for business software or application software getting higher and businesses or organizations opted to build or buy this software. Because of
new entrants, it had offered opportunity to software developers to translate business processes into systems. This study investigates waste in the software development by application of Lean principles. Like any conventional projects, software becomes buggy and oftentimes it fails. Software failure is always attributed to the software engineering, not the incompetence of project managers, inadequacy of the
people on the project, or lack of clear goal. The researchers’ contentions are there wastes in the software development and serve as mechanism and evidence to why software fails. Software failure is not attributed to the software itself, it includes however the acceptance of the clients and end-users. Descriptive secondary data analysis, participant observation and Fishbone Analysis were the methodology used in the study. Wastes include unfinished or partially done work, extra features,
relearning, handoffs, delays, task switching, and defects.
AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITION...ijseajournal
This paper presents the result of software requirements practices survey among software practitioners, a study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the successful of a software development project, it becomes interesting to investigate the current software requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements engineering practices over the entire Kingdom of Saudi Arabia software industry.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
The Impact of In-House Software Development Practices on System Usability in ...IJMIT JOURNAL
In-house software development is a critical phenomenon for the production of efficient and effective
software in generating requisite job output. A few studies have devoted efforts towards establishing the
impact of in-house software development on software. Therefore, this paper is an effort towards
establishing the impact of in-house software development practices on system usability. In pursuit of this
paper, a sample of a sample size of 169, at 95% confidence level, with margin error of 5% was drawn from
bold software users, i.e. 300 employees who used the all software including those dealing with the main
stream activities. A total of 102 respondents actually responded to the questionnaires. The Online Sample
Calculator was used to draw the sample. Quantitative data were collected using semi-structured
questionnaires and processed using the SPSS. Descriptive statistics were applied in the analysis. Findings
of the study indicate that software development practices, specifically usability test and user involvement in
software designing and development had an impact on determining software usability for in-house
software. The paper concludes that software development practices shape the design of the software; hence
influence usability of the software produced. Recommended is therefore that software usability test and
user involvement in software designing and development be promoted for effective software production
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
EMPIRICALLY VALIDATED SIMPLICITY EVALUATION MODEL FOR OBJECT ORIENTED SOFTWAREijseajournal
Software program developers need to go from beginning to ending and understand source code of the program and other software attributes. The software complexities and length of the program exceedingly affects many design level quality attributes, specifically Simplicity, Testability and software
Maintainability. Incomplete design of any software generally leads to misunderstanding and ambiguities
and therefore to gives faulty design and development results. This is mainly seeming and appears owing to
the absence of it’s an appropriate observation, design and development control. However, high level design
and program simplicity are very necessary and one of the vital attributes of the system development cycle.This research paper highlights the impact and significance of design level software simplicity in common and as a one of the most useful key factor or index of software quality assurance and testing. In this research work principally there are three major efforts are made. As a first contribution, a valuable
relationship between software design quality factor simplicity and related object oriented design
properties, this has been set up. In the second contribution, using design level corresponding metrics a
simplicity evaluation model for object oriented software is developed. Subsequently, the developed
simplicity model has been rationally authenticated by means of experimental data try-out.
A sustainable procedural method of software design process improvementsnooriasukmaningtyas
In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is a guideline procedure with detailed steps for software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion, this paper proposed a method to improve the design process for different kinds of the software systems using a templatebased implementation to reduce the cost, effort and time needed in the implementation phase in small companies. The scientific implication behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.
A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR MOBILE APPLICATIONS DEVELOPMENT ijseajournal
With the increasing in mobile application systems and a high competition between companies, that led to
increase in the number of mobile application projects.
Mobile software development is a group of process for creating software for mobile devices with limited
resources like small screen, low-power. The development of mobile applications is a big challenging
because of rapidly changing business requirements and technical constraints for mobile systems. So,
developers faced the challenge of a dynamic environment and the Changing of mobile application
requirements. Moreover, Mobile applications should adapt appropriate software development methods that
act in response efficiently to these challenges.
However, at the moment, there is limited knowledge about the suitability of different software practices for
the development of mobile applications. According to many researchers ,Agile methodologies was found to
be most suitable for mobile development projects as they are short time, require flexibility, reduces waste
and time to market.
Finally, in this research we are looking for a suitable process model that conforms to the requirement of
mobile application, we are going to investigate agile development methods to find a way, making the
development of mobile application easy and compatible with mobile device features.
FISHBONE ANALYSIS ON WASTES IN SOFTWARE DEVELOPMENT USING THE LEAN I.T. PRINC...ecij
The transformative global economy posed challenges to businesses in service management. In this computing age, the perceptual and operational edge of a certain business or organization manifested on the kind of technology it offers in the Service Management. Organizations have long recognized the
importance of managing key resources such as people and information. Information has now moved to its rightful place as a key resource in the organization and therefore management of the same can be instituted by employing methodology. To keep their brand promise, technology has been used;The number of new entrants to every sectors of economy has grown significantly in recent years, and each firm strives to make their daily operation efficient in which demand for business software or application software getting higher and businesses or organizations opted to build or buy this software. Because of
new entrants, it had offered opportunity to software developers to translate business processes into systems. This study investigates waste in the software development by application of Lean principles. Like any conventional projects, software becomes buggy and oftentimes it fails. Software failure is always attributed to the software engineering, not the incompetence of project managers, inadequacy of the
people on the project, or lack of clear goal. The researchers’ contentions are there wastes in the software development and serve as mechanism and evidence to why software fails. Software failure is not attributed to the software itself, it includes however the acceptance of the clients and end-users. Descriptive secondary data analysis, participant observation and Fishbone Analysis were the methodology used in the study. Wastes include unfinished or partially done work, extra features,
relearning, handoffs, delays, task switching, and defects.
AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITION...ijseajournal
This paper presents the result of software requirements practices survey among software practitioners, a study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the successful of a software development project, it becomes interesting to investigate the current software requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements engineering practices over the entire Kingdom of Saudi Arabia software industry.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
The Impact of In-House Software Development Practices on System Usability in ...IJMIT JOURNAL
In-house software development is a critical phenomenon for the production of efficient and effective
software in generating requisite job output. A few studies have devoted efforts towards establishing the
impact of in-house software development on software. Therefore, this paper is an effort towards
establishing the impact of in-house software development practices on system usability. In pursuit of this
paper, a sample of a sample size of 169, at 95% confidence level, with margin error of 5% was drawn from
bold software users, i.e. 300 employees who used the all software including those dealing with the main
stream activities. A total of 102 respondents actually responded to the questionnaires. The Online Sample
Calculator was used to draw the sample. Quantitative data were collected using semi-structured
questionnaires and processed using the SPSS. Descriptive statistics were applied in the analysis. Findings
of the study indicate that software development practices, specifically usability test and user involvement in
software designing and development had an impact on determining software usability for in-house
software. The paper concludes that software development practices shape the design of the software; hence
influence usability of the software produced. Recommended is therefore that software usability test and
user involvement in software designing and development be promoted for effective software production
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
EMPIRICALLY VALIDATED SIMPLICITY EVALUATION MODEL FOR OBJECT ORIENTED SOFTWAREijseajournal
Software program developers need to go from beginning to ending and understand source code of the program and other software attributes. The software complexities and length of the program exceedingly affects many design level quality attributes, specifically Simplicity, Testability and software
Maintainability. Incomplete design of any software generally leads to misunderstanding and ambiguities
and therefore to gives faulty design and development results. This is mainly seeming and appears owing to
the absence of it’s an appropriate observation, design and development control. However, high level design
and program simplicity are very necessary and one of the vital attributes of the system development cycle.This research paper highlights the impact and significance of design level software simplicity in common and as a one of the most useful key factor or index of software quality assurance and testing. In this research work principally there are three major efforts are made. As a first contribution, a valuable
relationship between software design quality factor simplicity and related object oriented design
properties, this has been set up. In the second contribution, using design level corresponding metrics a
simplicity evaluation model for object oriented software is developed. Subsequently, the developed
simplicity model has been rationally authenticated by means of experimental data try-out.
A sustainable procedural method of software design process improvementsnooriasukmaningtyas
In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is a guideline procedure with detailed steps for software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion, this paper proposed a method to improve the design process for different kinds of the software systems using a templatebased implementation to reduce the cost, effort and time needed in the implementation phase in small companies. The scientific implication behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.
Efficient Indicators to Evaluate the Status of Software Development Effort Es...IJMIT JOURNAL
Development effort is an undeniable part of the project management which considerably influences the
success of project. Inaccurate and unreliable estimation of effort can easily lead to the failure of project.
Due to the special specifications, accurate estimation of effort in the software projects is a vital
management activity that must be carefully done to avoid from the unforeseen results. However numerous
effort estimation methods have been proposed in this field, the accuracy of estimates is not satisfying and
the attempts continue to improve the performance of estimation methods. Prior researches conducted in
this area have focused on numerical and quantitative approaches and there are a few research works that
investigate the root problems and issues behind the inaccurate effort estimation of software development
effort. In this paper, a framework is proposed to evaluate and investigate the situation of an organization in
terms of effort estimation. The proposed framework includes various indicators which cover the critical
issues in field of software development effort estimation. Since the capabilities and shortages of
organizations for effort estimation are not the same, the proposed indicators can lead to have a systematic
approach in which the strengths and weaknesses of organizations in field of effort estimation are
discovered
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
The software industry has had significant progress
in recent years. The entire life of software includes two phases:
Production and Maintenance. Software maintenance cost is
increasingly growing and estimates showed that about 90%, if
software life cost is related to its maintenance phase. Extraction
and considering the factors affecting software maintenance cost
help to estimate the cost and reduce it by controlling the factors.
Cost estimation of maintenance phase is necessary to predict the
reliability, improve the productivity, project planning, controlling
and adaptability of the software. Though there are various models
to estimate the maintenance cost of traditional software like
COCOMO, SLIM, Function Point etc., but till now there is no
such model to estimate the maintenance cost using fourth
generation language environment. Software maintenance will
continue to exist in the fourth generation environment, as systems
will still be required to evolve. In this kind of situation there is
needed to develop a model to estimate the maintenance cost using
fourth generation environment. We propose a systematic
approach and development for software maintenance cost
estimation model using fourth generation language environment
on the basis of COCOMO II. This model is based on three
parameters: SMCE with Fourth Generation Language
Environment, ACT (Annual Change Traffic), Technical and NonTechnical
factors which affect the maintenance cost. The
favorable results closely matching and it can be achieved by using
model implementation.
The software industry has had significant progress
in recent years. The entire life of software includes two phases:
Production and Maintenance. Software maintenance cost is
increasingly growing and estimates showed that about 90%, if
software life cost is related to its maintenance phase. Extraction
and considering the factors affecting software maintenance cost
help to estimate the cost and reduce it by controlling the factors.
Cost estimation of maintenance phase is necessary to predict the
reliability, improve the productivity, project planning, controlling
and adaptability of the software. Though there are various models
to estimate the maintenance cost of traditional software like
COCOMO, SLIM, Function Point etc., but till now there is no
such model to estimate the maintenance cost using fourth
generation language environment. Software maintenance will
continue to exist in the fourth generation environment, as systems
will still be required to evolve. In this kind of situation there is
needed to develop a model to estimate the maintenance cost using
fourth generation environment. We propose a systematic
approach and development for software maintenance cost
estimation model using fourth generation language environment
on the basis of COCOMO II. This model is based on three
parameters: SMCE with Fourth Generation Language
Environment, ACT (Annual Change Traffic), Technical and NonTechnical
factors which affect the maintenance cost. The
favorable results closely matching and it can be achieved by using
model implementation.
Testability measurement model for object oriented design (tmmood)ijcsit
Measuring testability early in the development life cycle especially at design phase is a criterion of crucial importance to software designers, developers, quality controllers and practitioners. However, most of the
mechanism available for testability measurement may be used in the later phases of development life cycle.
Early estimation of testability, absolutely at design phase helps designers to improve their designs before
the coding starts. Practitioners regularly advocate that testability should be planned early in design phase.
Testability measurement early in design phase is greatly emphasized in this study; hence, considered significant for the delivery of quality software. As a result, it extensively reduces rework during and after implementation, as well as facilitate for design effective test plans, better project and resource planning in a practical manner, with a focus on the design phase. An effort has been put forth in this paper to recognize the key factors contributing in testability measurement at design phase. Additionally, testability
measurement model is developed to quantify software testability at design phase. Furthermore, the relationship of Testability with these factors has been tested and justified with the help of statistical measures. The developed model has been validated using experimental tryout. Finally, it incorporates the empirical validation of the testability measurement model as the author’s most important contribution.
A novel risk management model in the Scrum and extreme programming hybrid me...IJECEIAES
Risk management in software development has always been one of the necessities of software project management. The logical nature of software projects and products has caused several challenges and risks in these projects. On the other hand, with the emergence of agile methodologies, especially Scrum, and extreme programming (XP) methodologies, in recent years, this issue has become more serious. This is mainly because emphasizing limited documentation in these methodologies has caused these methods to pay little attention to some aspects of project management, particularly risk management. Concentrating on this challenge, the current study has proposed a risk management model in the hybrid methodology, combining Scrum and XP. Using this model in a case study shows this model's success in achieving risk management purposes. The results of this study indicate an appropriate reduction in the number of reworks, change requests, identified risks, and occurred risks. Moreover, the number of eliminated risks and team productivity have increased.
The impact of user involvement in software development processnooriasukmaningtyas
In software development process, user can take part in any phase of the process, depending on what model is being applied. Lack of user involvement can result in a poorly designed solution, or even a solution that conflicts with user’s needs. This review paper presents the impact of user involvement in software development process. In this study, different software development processes will be reviewed, show where the user usually gets involved in different models such as: structural (waterfall, Vmodel) and incremental (scrum-extreme programming XP). As each model differs from the other, each of them has a different perspective of where user should take part and where they should not. This can be an asset that helps project managers, and leaders to develop suitable strategies to follow in their projects.
Comparative Analysis of Agile Software Development Methodologies-A ReviewIJERA Editor
Software development methodology consists of dividing the software development process or work into different
phases in order to achieve better planning and management. As the software development proceeds, factors such
as requirements, needs, priorities, underlying technology may change. Thus development process must be highly
dynamic and a good software development methodology must adapt to these evolving and changing
requirements. Traditional software development models are unable to handle such dynamic requirements. To
cope up with such dynamic requirements a set of software development methodologies referred as „Agile
Software development methodologies‟ are used. Comparison between different Agile software development
methods will help in the selection of appropriate development model given a particular scenario.
Risk management framework in Agile software development methodologyIJECEIAES
In software projects that use the Agile methodology, the focus is on development in small iterations to allow both frequent changes and client involvement. This methodology affects the risks that may happen in Agile software projects. Hence, these projects need a clear risk management process to reduce risks and address the problems before they arise. Most software production methodologies must use a framework for risk management, but currently, there is no such framework for the Agile methodology. Therefore, we present a risk management framework for projects that use the Agile methodology to help the software development process and increase the likelihood of the project’s success. The proposed framework states the necessary measures for risk management according to the ISO31000 standard at each stage of the Agile methodology. We evaluated the proposed framework in two running software projects with an Agile methodology by a number of expert experts. The results show that using our proposed framework increases the average positive risk reaction score by 49%.
Proposed an Integrated Model to Detect The Defect in Software Development Pro...Waqas Tariq
Currently, software quality assurance does not apply completely on the development of software industry and this leads to some challenges in the industry of software, specially, concerning cost and time consuming. While, the success of software development project depends on the application quality assurance standards, which starts by the pre-project and continue through the project till it reaches the user at the end. The aim of this model is the challenge to produce not only the software development project without defects but also the customer’s acceptance and satisfaction of the software. Thus to prevent software development project failure, this defect should be detected at an early stage.This study will deal with; the quality assurance inspection and testing, in the whole stages of software development projects. Then proposing the quality assurance inspection and testing model for the software development projects process, which known as “Integrated Model”.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
QUALITY ASSURANCE AND INTEGRATION TESTING ASPECTS IN WEB BASED APPLICATIONSIJCSEA Journal
Integration testing is one the important phase in software testing life cycle (STLC). With the fast growth of internet and web services, web-based applications are also growing rapidly and their importance and complexity is also increasing. Heterogeneous and diverse nature of distributed components, applications, along with their multi-platform support and cooperativeness make these applications more complex and swiftly increasing in their size. Quality assurance of these applications is becoming more crucial and important. Testing is one of the key processes to achieve and ensure the quality of these software or Webbased products. There are many testing challenges involved in Web-based applications. But most importantly integration is the most critical testing associated with Web-based applications. There are number of challenging factors involved in integration testing efforts. These factors have almost 70 percent to 80 percent impact on overall quality of Web-based applications. In software industry different kind of testing approaches are used by practitioners to solve the issues associated with integration which are due
to ever increasing complexities of Web-based applications.
Similar to A PROCESS QUALITY IMPROVEMENT MECHANISM FOR REDUCING THE RISK OF CI ENVIRONMENT (20)
Water scarcity is the lack of fresh water resources to meet the standard water demand. There are two type of water scarcity. One is physical. The other is economic water scarcity.
Vaccine management system project report documentation..pdfKamal Acharya
The Division of Vaccine and Immunization is facing increasing difficulty monitoring vaccines and other commodities distribution once they have been distributed from the national stores. With the introduction of new vaccines, more challenges have been anticipated with this additions posing serious threat to the already over strained vaccine supply chain system in Kenya.
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptxR&R Consult
CFD analysis is incredibly effective at solving mysteries and improving the performance of complex systems!
Here's a great example: At a large natural gas-fired power plant, where they use waste heat to generate steam and energy, they were puzzled that their boiler wasn't producing as much steam as expected.
R&R and Tetra Engineering Group Inc. were asked to solve the issue with reduced steam production.
An inspection had shown that a significant amount of hot flue gas was bypassing the boiler tubes, where the heat was supposed to be transferred.
R&R Consult conducted a CFD analysis, which revealed that 6.3% of the flue gas was bypassing the boiler tubes without transferring heat. The analysis also showed that the flue gas was instead being directed along the sides of the boiler and between the modules that were supposed to capture the heat. This was the cause of the reduced performance.
Based on our results, Tetra Engineering installed covering plates to reduce the bypass flow. This improved the boiler's performance and increased electricity production.
It is always satisfying when we can help solve complex challenges like this. Do your systems also need a check-up or optimization? Give us a call!
Work done in cooperation with James Malloy and David Moelling from Tetra Engineering.
More examples of our work https://www.r-r-consult.dk/en/cases-en/
Final project report on grocery store management system..pdfKamal Acharya
In today’s fast-changing business environment, it’s extremely important to be able to respond to client needs in the most effective and timely manner. If your customers wish to see your business online and have instant access to your products or services.
Online Grocery Store is an e-commerce website, which retails various grocery products. This project allows viewing various products available enables registered users to purchase desired products instantly using Paytm, UPI payment processor (Instant Pay) and also can place order by using Cash on Delivery (Pay Later) option. This project provides an easy access to Administrators and Managers to view orders placed using Pay Later and Instant Pay options.
In order to develop an e-commerce website, a number of Technologies must be studied and understood. These include multi-tiered architecture, server and client-side scripting techniques, implementation technologies, programming language (such as PHP, HTML, CSS, JavaScript) and MySQL relational databases. This is a project with the objective to develop a basic website where a consumer is provided with a shopping cart website and also to know about the technologies used to develop such a website.
This document will discuss each of the underlying technologies to create and implement an e- commerce website.
Student information management system project report ii.pdfKamal Acharya
Our project explains about the student management. This project mainly explains the various actions related to student details. This project shows some ease in adding, editing and deleting the student details. It also provides a less time consuming process for viewing, adding, editing and deleting the marks of the students.
Overview of the fundamental roles in Hydropower generation and the components involved in wider Electrical Engineering.
This paper presents the design and construction of hydroelectric dams from the hydrologist’s survey of the valley before construction, all aspects and involved disciplines, fluid dynamics, structural engineering, generation and mains frequency regulation to the very transmission of power through the network in the United Kingdom.
Author: Robbie Edward Sayers
Collaborators and co editors: Charlie Sims and Connor Healey.
(C) 2024 Robbie E. Sayers
NO1 Uk best vashikaran specialist in delhi vashikaran baba near me online vas...Amil Baba Dawood bangali
Contact with Dawood Bhai Just call on +92322-6382012 and we'll help you. We'll solve all your problems within 12 to 24 hours and with 101% guarantee and with astrology systematic. If you want to take any personal or professional advice then also you can call us on +92322-6382012 , ONLINE LOVE PROBLEM & Other all types of Daily Life Problem's.Then CALL or WHATSAPP us on +92322-6382012 and Get all these problems solutions here by Amil Baba DAWOOD BANGALI
#vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore#blackmagicformarriage #aamilbaba #kalajadu #kalailam #taweez #wazifaexpert #jadumantar #vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore #blackmagicforlove #blackmagicformarriage #aamilbaba #kalajadu #kalailam #taweez #wazifaexpert #jadumantar #vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore #Amilbabainuk #amilbabainspain #amilbabaindubai #Amilbabainnorway #amilbabainkrachi #amilbabainlahore #amilbabaingujranwalan #amilbabainislamabad
Quality defects in TMT Bars, Possible causes and Potential Solutions.PrashantGoswami42
Maintaining high-quality standards in the production of TMT bars is crucial for ensuring structural integrity in construction. Addressing common defects through careful monitoring, standardized processes, and advanced technology can significantly improve the quality of TMT bars. Continuous training and adherence to quality control measures will also play a pivotal role in minimizing these defects.
Immunizing Image Classifiers Against Localized Adversary Attacksgerogepatton
This paper addresses the vulnerability of deep learning models, particularly convolutional neural networks
(CNN)s, to adversarial attacks and presents a proactive training technique designed to counter them. We
introduce a novel volumization algorithm, which transforms 2D images into 3D volumetric representations.
When combined with 3D convolution and deep curriculum learning optimization (CLO), itsignificantly improves
the immunity of models against localized universal attacks by up to 40%. We evaluate our proposed approach
using contemporary CNN architectures and the modified Canadian Institute for Advanced Research (CIFAR-10
and CIFAR-100) and ImageNet Large Scale Visual Recognition Challenge (ILSVRC12) datasets, showcasing
accuracy improvements over previous techniques. The results indicate that the combination of the volumetric
input and curriculum learning holds significant promise for mitigating adversarial attacks without necessitating
adversary training.
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
A PROCESS QUALITY IMPROVEMENT MECHANISM FOR REDUCING THE RISK OF CI ENVIRONMENT
1. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
DOI:10.5121/ijcsit.2017.93010 117
A PROCESS QUALITY IMPROVEMENT MECHANISM
FOR REDUCING THE RISK OF CI ENVIRONMENT
Sen-Tarng Lai
Dept. of Information Technology and Management, Shih Chien University,
Taipei, 104, Taiwan
ABSTRACT
In the age of fast evolution, software development project must accept many challenges of unpredicted
requirements change and new technology environment. Software development processes should have
adjustable and extendable features to meet the multifaceted needs of the users. Iterative and Incremental
Development (IID) is a practical approach to overcome the various challenges of software development.
However, continuous testing and building new versions need to spend more time and human resources that
is a major obstacle of IID. The other, the iterative operations must have a sound communication skills.
Lack of standard version control and intercommunication manner often lead to failure of software project.
High quality Continuous Integration (CI) environment can effectively make up the defects of IID. In this
paper, CI environment and advantages are deeply surveyed. In order to overcome the defects of IID, CI
environment needs combine the perfect procedures and qualified tools, and concretely enhance the quality
of CI environment. Based on the process quality measurement model, this paper proposes the Process
Quality Improvement Mechanism (PQIM). Applying PQIM, in software development, the processes
problems and the CI environment quality defects can identify timely and indeed revise to reduce the risk of
CI environment.
KEYWORDS
Continuous Integration, IID, development risk, CI environment, quality improvement
1. INTRODUCTION
According to the Standish Group software project survey report in 2009, only 32% belong to the
successful software projects that budget and requirement quality almost fully met the project
planning. In development process, 24% projects were cancelled and the rest 44% owing to
development time delay, over budget and quality unsatisfied the requirement situations were
regarded as the failure projects [1]. In 2014, the latest research report of the Standish Group
further pointed out that 31.1% of software projects are cancelled, the development cost of 52.7%
cancelled projects exceed 189% of the original budget. Investigating the major cause of software
project failure is over plan change frequency. In software development process, many unexpected
events will occur successively to impact the software development activities. Forcing the software
project plan must continue to change. Project plan modification often is not able to effectively
and timely reflect to the important sub plans that include budget planning, development time,
quality management and resource allocation. Therefore, project plan changes make expansive gap
between plan items and the software development work, gradually leading to the project plan
completely unable to control the budget execution, development time, quality management and
resource allocation. Finally, software project becomes a failure project of budget overruns,
schedule delays and poor quality [2, 3]. Therefore, in order to handle high changeable software
project, software development process must have high adjustability and changeability to reduce
the function extension and requirement change risks.
2. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
118
Internet widespread age, the pursuit of a variety of high efficiency and high effective trading
activity must be combined with the network technologies. In order to overcome the ever changing
hardware facilities, advanced IT technology, services requirement change and continuous
expansion functions, software projects should cautiously select the appropriate development
model. Agile development model uses IID (Iterative and Incremental Development) process, each
repeated development work required to complete a workable version, immediately test and
evaluate the new version, early detection the processes problems and product defects, assist
timely improvement measures, reduce the software development risk [3, 4, 5]. IID mode
gradually by the software engineer attention, many of the software development models have
combined with IID. Among which the continuous integration (CI) with agile development model
is cited and discussed in [6, 7, 8]. CI is a software implementation concept that was proposed in
1998. CI have combined testing tools, integration tools, software version management system and
other aspects of technology and become an important member of the agile development method.
The advantages of CI can identify software development problems and product quality defects in
software initial development stage to reduce the software development risk [3, 6, 7, 8, 9].
Rapidly changing technology and environment makes software project must have the flexible and
changeable features. Therefore, software development process is very suitable to use IID
methodology and apply CI practical concept. In early development phase, coding errors and
quality defects can be quickly identified, corrected and revised that make the risk of software
project can be greatly reduced. However, version integration test need expend more manpower
and resource that is major obstacle of IID. In addition, IID must have well intercommunication
capability. Lacking formal version control system and stakeholder communication channel often
led the software project failure. High quality Continuous Integration (CI) environment can
effectively make up the defects of IID. In this paper, CI environment and advantages are deeply
surveyed. In order to overcome the defects of IID, CI environment needs combine the perfect
procedures and qualified tools, and concretely enhance the quality of CI environment. Based on
the process quality measurement model, this paper proposes the Process Quality Improvement
Mechanism (PQIM). Applying PQIM, in software development, the processes problems and the
CI environment quality defects can be identified timely and indeed revised to reduce the risk of
CI environment. In section II, software project failure factors and software development risks
management are discussed. In section III, advantages of IID method and major features of CI are
investigated. In section IV, based on the process quality measurement model, this section
proposes the Process Quality Improvement Mechanism (PQIM). In Section V, plans the CI-based
IID process and evaluates the benefits of CI-IID. In Section VI, emphasizes the importance of CI
environment processes quality and IID to reduce the software development risk and does the
paper conclusion.
2. SOFTWARE DEVELOPMENT RISKS
In this section, software project failure factors and software development risks management are
discussed.
2.1. MAJOR FAILURE FACTORS OF SOFTWARE PROJECT
According to the Standish Group survey report of large scale software project, software project
success ratio is under 30%. And 80% of failure projects are time delay, over budget and quality
not satisfied the requirements [1]. Many papers have discussed the causes of software project
failure [10, 11, 12]. Development time delay, over budget and quality unsatisfied the
requirements etc. three situations always cause to software project with high development risk.
The reasons of the high risk is high relationship with the following four key events:
3. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
119
˙ In beginning of development, system and requirement analyst collect and analysis
incomplete data to cause system requirement specifications and user requests existed
incorrect, incomplete and inconsistent defects. The defects can’t be revised immediately. It
must cause development time delay, over budget and product quality unsatisfied the
requirements.
˙ In software development process, new technology or development environment evolution
makes the project plan must to be adjusted to match new technology and development
environment. Before planning items unable be re-vised immediately, the follow
development operations will be affected.
˙ In initial development stage, user submits many kinds of requirements. These requirements
often are requested to expand, modify, or remove in software development process. These
requirements changes become the major impaction for the follow phase development.
˙ Each software development phase need involve difference resource that include developers,
computer hardware, software tools, and development environment. Resource allocation
defects may cause the project plan resource management need to readjustment and
allocation. Imperfect and unchangeable resource management often makes the high
development risk of software project.
Four key events of software project risk can summarize as incomplete requirement analysis,
evolution technology and environment, user requested requirements change, and changes of
resources allocation. In software development process, these high risk events almost cannot be
avoided or excluded. In order to effectively reduce the risk of software development project. Only
way is to overcome the challenges of these risk events.
2.2. SOFTWARE DEVELOPMENT RISKS MANAGEMENT
In order to reduce project failure risk, software development process must have high flexibility
and changeability. According to the situations encountered, development operations should
timely adjust and effectively change, until software projects can overcome existed risk. Four
software project change factors and the affected project planning and response measures are
discussed as follows:
Incomplete requirements analysis: generally occurs that software requirements are not clear
or missing. For this, the project plan need to give the additional cost and resource, delay the
development time, and adjust the requirement items and quality assurance mechanism. In
order to reduce the impact of incomplete requirements analysis of software project, firstly,
user can pick and choose the major and clear requirement and postpone the unclear or
ambiguous requirements.
Evolution technology and environment: introducing new development technologies or new
operating environment need to take an additional acquisition cost and staff training costs.
For adjusting the software project plan, it may affect the cost estimation, schedule and
resource management, and increase development risks. Incremental development approach
can gradually introduce new technologies and the environment to avoid the extra cost,
schedule and resource impaction and reduce the software project risks.
User requirements change: in software development process, user requirement changes are
the unavoidable challenge. However, the unexpected requirement changes is bound to affect
the project plans and the completed phase documents. Frequent user requirements change
not only may impact the development cost, schedule, product quality and other planning
projects, but also cause the software project failure risks. In order to reduce the impact of
requirement changes, iterative development can be used to gradually adjust for the
requirement changes.
4. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
120
Resources allocation changes: personnel high mobility, organizational downsizing,
development equipment late delivery, major equipment repairing or updating are bound to
affect the software development process and schedule. In order to avoid the impacts of
development schedule, the part of requirements should consider to shift to the next version.
Based on the above four items, IID is an appropriate development method to reduce the software
development risk.
3. AGILE DEVELOPMENT AND CONTINUOUS INTEGRATION
3.1 AGILE SOFTWARE DEVELOPMENT AND IID
In recent twenty years, the growth of information technology, operational environment and user
requirements, software development methodologies continuously progress. Most of software
development models have high relationship with user requirements. Waterfall model defines clear
phase mission and very concerns the phase documents. The quality of requirement documents
can't reach correctness, completeness and consistency, development process will be denied to
enter the following phase. Recently proposed development models have modified requirement
specification style. The requirement items are allowed to propose by incremental manner, not
necessary to decision at same time. Using iterative development model, user can incrementally
provide the requirement items. Software development risks can be greatly reduced. Each
development model should has the adjustment strategy to handle the change of user requirements.
The adjustment strategy can't effectively apply to reduce software development risks, then may
impact success ratio of software project.
In 2001, seventeen software developers met at the Utah of USA and produced the Manifesto of
the agile software development. Many of participants had previously authored their own software
development methodologies, including Extreme programming, Crystal, and Scrum [5, 13, 14].
Agile software development proposes several critical viewpoints:
˙ In development process, does not concern analysis and design phase operations and
documents.
˙ As soon as possible to enter programming phase, workable software is more practical than
development document.
˙ Support and provide high changeability software system.
˙ Enhance the cooperative relationship between developer and user, user can fully attend the
development team.
Agile software development neglects the formal analysis and design phases, uses non-document
oriented development, and doesn’t pay attention to follow-up maintenance operations that are
major drawbacks (shown as Figure 1). For effectively reducing the software development risks,
the drawbacks of agile model should be concretely improved or enhanced. However, agile
software development uses IID to reduce the requirement complexity, refactoring to increase the
requirement modified flexibility, and non-document oriented can reduce the cost of requirements
change [15]. Requested software project must release a workable version during two or three
weeks. Letting the client can detailed test, validate requirement items of new version and clearly
understand the development progress. In each day, a fifteen minutes stand up meeting is held to
effectively reach full intercommunication between client and developers. In development change
impacts, IID greatly decreases schedule delay, cost over budget and quality unsatisfied user
requirement situations, software development change risk can be effectively reduced. However,
version integration test need expend more manpower and resource that is major drawback of IID.
5. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
121
3.2 ADVANTAGES OF CONTINUOUS INTEGRATION
CI is a software engineering practice that the functions of add or change are immediately tested
and verified before committing to a source repository. The goal of CI is to quickly identify the
coding errors and quality defects, and to make the errors and defects can be corrected and revised
as soon as possible. In 1994, Grady Booch mentioned the CI phase in his book of Object-Oriented
Analysis and Design with Applications [16]. In 1997, Kent Beck and Ron Jeffries proposed XP
which included CI concept [6], [17]. In 1998, Kent published a paper of CI which valued and
supported the importance of directly communication technology [18]. Based on IID mechanism,
agile development combines XP, TDD (Test Driven Development) and BDD (Behaviours Driven
Development) methods, and makes CI to become a main stream and important trend of software
development. Focus on the automatic and repeat process are the major characteristics of CI.
Therefore, integrated with related automated development tools is first mission of CI
environment.
Figure 1. A schematic diagram of agile process advantages and drawbacks
In software development process, software project management applies modularization to enable
teamwork development and make complex system manageable. Modularization decomposes the
complex software system into many manageable program units. Each program unit just handle a
specific function, therefore the program units have to work together and integrate into a module
function, subsystem and system. CI through more times integration and testing makes the errors
and defects can be identified quickly. Errors correction and defects revision can be timely handled
and effectively avoid to errors and defects to transfer to the follow phases. Summarize five major
advantages of CI and discuss as follows (shown as Figure 2):
High efficiency:CI combines many automated tools and procedures can increase the development
and operation efficiency.
Reduce development risks: According to development requests, CI can more times integrate in a
day to reduce software project development risks.
Smooth communication: CM system [19], source repository and workable software can assist
build common understanding among stakeholder.
Improvement quality: CI follows the systematic procedures and combines useful automated tools
to improve software development quality.
Increased morale: CI increases communication frequency, dramatically reducing communication
barriers and software development risks. The development team confidence can be established
and morale can be increased.
6. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
122
Figure 2. Five major advantages of CI
4. QUALITY MEASUREMENT MODEL
4.1 FIVE PROCESSES OF CI ENVIRONMENT
CI pays attention to increase software development productivity and quality, concretely reduce
development risk and continuously monitor coding errors and integration defects. CI environment
must suitably combine qualified CASE tools and perfect control procedures to reduce human
resources expense and manual operation defects. This section applies the CM environment to IID
software development project. CI environment is divided into five process items to describe as
follows:
(1) CM Process: Development documents and source code, passed review activity, must have a
storage and management mechanism. Based on the Work Breakdown Structure, CM system
and version control tools can effectively manage and control the documents and source code
check-in and check-out. In incremental development, CM system is a necessary process
which can assist to record and control continuous development process problems and defects.
Version control tools can detailed record documents and source code modification time,
personnel, causes and difference between the versions.
(2) Unit Testing Process: Unit program is the primitive element of software system. Complete
and correct unit testing can increase the follow development efficiency and quality. Unit
testing conforms the test criteria and passes the review activity, the source code and test cases
can commit for the CM system. In order to increase the efficiency and quality of unit testing,
the norm of program language related unit testing tool should be defined to assist unit testing
automation.
(3) Integrated Testing Process: Test phase should cover function, integration and system testing
steps. However, before testing, each test steps must complete test cases design and planning.
Selecting the suitable test approaches (ex. Equivalence partition, cause effect graph, symbolic
execution and mutation) and assistant tools can quickly generate high efficiency and quality
test cases. With suitable test approach, integration interface errors and design defects can be
identified in time.
(4) Build and acceptable testing Process: Modularization design decomposes the system into
several program units. Using make and make-file tools can handle tens or hundreds of unit
programs and modules to clearly and quickly define the relationships between unit programs
and modules. Based on the produced or modified time of files, the make and make-file tools
can judge the source code whether recompile or relink to be a new image file. Effectively
reduce human possible misses.
(5) Deployment and validation process: passed acceptance testing activity, According to the user
requirements and assigned environment, new version software must execute deployment and
7. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
123
validation activities. Using batch process command on specific operation platform can
quickly accomplish automatic system deployment. Finally, the deployed system should
execute verification and validation activities by the stakeholder.
CI environment combining five process items includes CM and VC system, automatic unit
testing, repository management, automatic integration testing, automatic deployment, and errors
and defects identification etc. five major elements (shown as Figure 3).
Figure 3. CI environment and five development processes
4.2 QUALITY FACTORS OF PROCESSES
CI environment quality is important critical factor to affect IID software project success. In order
to ensure high quality of CI environment, in this section use check lists to collect quality factors
of CI environment. The meta-process of CI environment should measure perfect procedure,
qualified CASE tools and process interoperability three quality metrics to assure CI environment
quality. Five processes (shown as Figure 4) are instanced from meta-process and described as
follows:
Figure 4. Meta-process and five instanced processes
(1) CM and VC Process (CMP) quality factors:
8. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
124
Does CMP have the complete and correct control procedure to manage and control
development documents?
Does CMP use the suitable CM assistant tools and integrated with version control system?
Does CMP consider the interoperability between the other processes?
(2) Unit Testing Process (UTP) quality factors:
Does UTP have the complete and correct unit testing operations procedure?
Does UTP use the suitable automated unit testing assistant tools?
Does UTP consider the interoperability between the other processes?
(3) Integration Testing Process (ITP) quality factors:
Does ITP have the complete and correct integration testing operations procedure?
Does ITP use the suitable automated integration testing assistant tools?
Does ITP consider the interoperability between the other processes?
(4) Build & Acceptance testing Process (BAP) quality factors:
Does BAP have the complete and correct operations procedure of build and acceptance
testing?
Does BAP use the suitable automated build assistant tools?
Does BAP consider the interoperability between the other processes?
(5) Deployment & Validation Process (DVP) quality factors:
Does DVP have the complete and correct operations procedure of deployment and
validation?
Does DVP use the suitable automated deployment and validation assistant tools?
Does DVP consider the interoperability between and other processes?
4.3 PROCESS QUALITY MEASUREMENT MODEL
For collecting useful quality factors, it is necessary to develop a set of complete and clear
inspection checklists to conduct the CI environment items audit. Checklists can collect the
quantified quality of CI environment items. Checklists discussion and implementation can help
collect the completeness, correctness, and usability and interaction degree quality factors of CI
environment. However, individual factor or measurement can only measure or evaluate the
specific quality characteristic. In order to effectively monitor and assess the CI environment
quality defects, individual measurements should make the appropriate combination [20], [21],
[22]. Two kind of metric combination models are Linear Combination Model (LCM) [20], [21],
and Non-Linear Combination Model (NLCM) [21], [22]. NLCM has higher accuracy
measurement than LCM. However, LCM has high flexibility, more extensible and easy
formulation than NLCM. For this, in this paper, LCM is applied to CI environment quality
measurement. The different level development activities have different quality metrics be shown.
Therefore, before applying the linear combination model, the quality factors must be normalized.
The normalized value is between 0 and 1. The best quality quantified value approaches to 1 and
the worst quality approaches to 0.
CI environment should consider three quantified quality that include basic, usability and
interaction degree quality. Using the LCM, related quality factors can be combined into the
primitive metric, and then the related primitive metrics can be combined into the quality
measurements. Finally, combines with three critical quality measurements and generates a CI
environment quality indicator. The formulas described as follows:
Each one Process Quality Measurement need combine the operation procedure quality, the tools
applicability and the processes interoperability three metrics. The combination formula is shown
as Equation (1):
9. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
125
PQM: Process Quality Measurement
POP: Process Operation Procedures Metric W1: Weight of CMPQ
PTA: Process Tools Applicability Metric W2: Weight of CMTU
PI: Processes Interoperability Metric W3: Weight of CMPI
PQM= W1* POP + W2* PTA + W3*PI W1+ W2 + W3 =1 (1)
Based Equation (1), five process quality measurements (CMP, UTP, ITP, BAP and DVP) can be
sequentially generated. Finally, combining CMP, UTP, ITP, BAP and DVP quality measurements
into a CI Environment Quality Indictor (CIEQI). The combination formula is shown as Equation
(2):
CIEQI: CI Environment Quality Indictor
CMPQM: CMP Quality Measurement Wcm: Weight of CMPQM
UTPQM: UTP Quality Measurement Wut: Weight of UTPQM
ITPQM: ITP Quality Measurement Wit: Weight of ITPQM
BAPQM: BAP Quality Measurement Wba: Weight of BAPQM
DVPQM: DVP Quality Measurement Wdv: Weight of DVPQM
CIEQI = Wcm* CMPQM + Wut* UTPQM+ Wit* ITPQM + Wba* BAPQM+ Wdv* DVPQM
Wcm+Wut+Wit+Wba+Wdv = 1 (2)
IID process of agile development model, CI environment quality is the major cause to effect
software project development results. For measuring and improving the quality of CI
environment, the major quality factors of each CI sub-processes were collected and divided into 3
groups. In first layer, three groups basic quality factor are combined into three quality metrics. In
second layer, three quality metrics are combined into a process quality measurements. In third
layer, five process quality measurements are combined into a CI Environment Quality Indictor
(CIEQI). With three layer combination formulas to generate a CIEQI, the process is called a
Process Quality Measurement (PQM) model. The PQM model architecture is shown as Figure 5.
Figure 5. The architecture of process quality measurement model
10. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
126
CIEQI is a relative judgment mechanism and the basis to identify quality defects of CI
environment. In CIEQM model, basic quality factors are combined into high layer quality
measurements. High layer quality measurements are combined into a CIEQI. Therefore, if the
CIEQI does not satisfy quality criterion, it represents CI environment existed some process
quality defects. According to the combination formulas, the process tasks problems and quality
defects can be timely identified. For improving CI environment quality, the related activities of
poor quality should be rigorously inspected to identify the problem or defect and propose the
corrective action.
5. CI-BASED IID PROCESS AND BENEFIT EVALUATION
5.1 IID OPERATION PROCEDURE WITH CI ENVIRONMENT
Iterative processes of IID still use the waterfall development model. Therefore, IID should refer to
the major development phases of waterfall model. However, in order to combine CI environment
with IID, IID not only must deploy high quality CI environment but also need combine with CM
system and CASE tools to enhance IID phase activities quality. Based on the PQIM, the paper
defines and plans the CI-IID operation procedure. CI-IID operation procedure divided into six
phases (shown as Figure 6). The completed documents of each phase need pass quality assurance
activities and conform to the CM and version control system and submit the documents to the
repository, to build the documents traceability. The detailed phase activity are describes as follows:
11. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
127
Figure 6. CI-IID operation procedure
(1) Requirement Analysis phase: Analysing user stories and generating a next version
requirement, and based on the version requirement accomplish requirement specification
assurance.
(2) Interface and detailed design phase: this phase decomposes into two sub-phases as follows:
˙ Integrated interface design: based on the repository requirement specification, design the
integrated interface and pass review activities.
˙ Program unit design: based on the repository interface design and program unit
specification, develop unit program test cases and module detailed design and pass
review activities.
(3) Coding & unit testing: based on test cases and module detailed design, implement the
module source code and pass automatic module unit testing. Passed unit testing, the test
cases and source code should submit to the repository.
(4) Integrated testing: based on integrated interface design and test cases, handle automatic
integrated test and pass integrated testing criteria.
(5) Build and acceptance testing: based on acceptance criteria, launch automatic system build
and acceptance testing and pass the acceptance testing review activities.
(6) Deployment and validation: more times continuous integration, the development focuses on
system deployment. Therefore, the user should be the important attendees of system
verification and validation. User rapidly contacts new function and new version, progress of
project and current situation can be fully controlled and understand.
(7) Continuous improvement: IID accomplished the new version requirement of user, and
passed to system verification and validation activities. In this time, IID is necessary to work
for next incremental development and more frequently. In IID process, for reducing the CI-
IID operation problems and defects, data collection, problems identification and defects
assertion must be persisted to revise the problems and defects of CI-IID operation procedure
continuously.
5.2 CI-BASED IID BENEFIT EVALUATION
Software development model has tight relationship with user requirements. Waterfall
development model clearly defines the phase mission and pays attention to the quality of phase
documents. Phase documents cannot satisfy correctness, completeness and consistency, then
process activities should be adjusted, phase documents need be revised and development flow
cannot allow to enter next phase. In recently, the development model substantially adjusted the
requirements generation methods. Based on IID, user requirements are unnecessary to confirm at
one time, but can gradually submit new requirements. Agile model uses IID methodology.
According to the environment and requirement change, user can dynamic submit new
requirements or revise the requirement service items to effectively reduce the software
development risk. Introducing into a new development model should collocate the suitable
procedure. Lacking a suitable operation procedure often hard to effectively control process
efficiency and quality. About process problems and quality defects cannot timely take adjustment
operations and remedial measures. In this paper, applying CIEQM model optimize CI
environment quality, and based on CI environment drafts IID operation procedure to norm the
software development operations. Process efficiency and product quality can concretely control,
and the operation procedure can be adjusted by continuous improvement phase. Making CI-based
IID operation procedure has continuous improvement feature. Five advantages of CI-based IID
operation procedure are evaluated as follows (shown as Table I):
12. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
128
(1) Process problems and quality defects identification: Automation tools and norm procedures
are applied on each phase of CI-based IID. CI with continuous testing and integration makes
process problems and quality defects to be identified in time and to be revised quickly.
Process problems and quality defects can be avoided to affect and extend to the follow
development phases.
(2) Intercommunication efficiency and developer morale: In agile software development, IID
cares user involvement, sharable development documents and source code, frequently
meeting, and using CM and version control procedure. IID and quality activities concretely
increase the intercommunication efficiency and developer morale.
(3) Automation environment: In order to increase integration frequency, CI environment uses
automatic tools to reduce human resource involvement. Automated unit test, functional
module, subsystem and system quick automatic integrated, and assistance deployment and
validation makes the development efficiency and system quality can be enhanced.
(4) Integration frequency: Traditional development is difficult to handle continuous integration.
It is because of traditional development executes integration task only in the testing phase. It
is too late to identify the process problems and quality defects and cannot be early identified
and revised. Software project of traditional development existed high risk.
(5) Development quality and productivity: CI makes process problems and quality defects to be
identified in time and to be revised quickly. Avoid problems and defects propagation and
expansion that can effectively.
Table 1. Comparison between traditional and CI-based IID model
6.CONCLUSION
In the information network age, everything requests the achievement of fast. Software project
must overcome the changing requirements and to withstand environmental challenges that
continued to introduce new technology. Therefore, development process should have the
modification and adjustment ability to meet the diversified needs of the users. However, software
project failure rate as high as over 60%, how to effectively reduce the risk of software
development project, is a topic worthy of further exploration. In order to effectively reduce the
requirement change to cause software development risks, IID has recognized as the very
important and practical development methods in current stage. Many software development
methods and models have been taken IID to reduce the risk of requirement changes.
The iterative integration testing can effectively identify the process problems and products quality
defects. However, it need consume more time and human resources which is a critical challenge
of IID. Applying high quality CI environment can effectively overcome the challenge of IID. In
13. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
129
this paper, the operation environment and advantages of CI are discussed. Analysis CI
environment should have key processes and quality characteristics, high quality CI environment
to make up the IID defects. Based on process quality measurement model, this paper proposes the
Process Quality Improvement Mechanism (PQIM). Applying PQIM, in software development,
the processes problems and the CI environment quality defects can be identified timely and
indeed revised to reduce the risk of CI environment. Applying the high quality CI environment
develops the CI-based IID operation procedure to assist automated unit and integration testing in
software development. New version software can be effectively deployed, stakeholder
intercommunication channels increase, and staff morale enhancement. CI-based IID software
developers can achieve four results:
Users can quickly use the new or updated workable version.
Improving the major drawback of IID that version integration test need expend more
manpower and resource.
The process problems and software quality defects can be timely identified and quickly use the
suitable improvement measures.
In the frequent changes, effectively reduce software project development risks.
ACKNOWLEDGEMENTS
The research was supported by Ministry of Science and Technology research project funds
(Project No.: MOST 105-2221-E-158-002)
REFERENCES
[1] Eveleens J. L. and Verhoef, C. (2010) “The Rise and Fall of the Chaos Report Figures, IEEE
Software,” vol. 27, no. 1, pp30-36
[2] Boehm, B. W. (1991) “Software risk management: Principles and practices,” IEEE Software, vol. 8,
no. 1, pp32-41.
[3] Schach S. R. (2011) Object-Oriented and Classical Software Engineering, Eighth Edition, McGraw-
Hill, New York.
[4] Larman C. and Basili, V. R. (2004) Iterative and Incremental Development: A Brief History,
Computer, IEEE CS Press, pp47-56.
[5] Martin, R. C. (2002) Agile Software Development, Principles, Practices and Patterns, Prentice Hall,
[6] Martin Fowler, (2006) “Continuous Integration,” martinfowler.com,
http://www.martinfowler.com/articles/continuousIntegration.html
[7] Duvall, P.: Continuous Integration Servers and Tools, DZone Refcardz. (2015)
https://dzone.com/refcardz/continuous-integration-servers#, (accessed Auguest 9, 2015)
[8] Duvall, P. and Matyas, S. and Glover, A. (2007) Continuous Integration: Improving Software Quality
and Reducing Risk, Pearson Education, Inc.
[9] Saff, D. and Erns,M. D. (2003) Reducing Wasted Development Time via Continuous Testing,
Proceeding of IEEE International Symposium on Software Reliability Engineering (ISSRE), pp281-
292
[10] Hornstein, H. A. (2015) “The integration of project management and organizational change
management is now a necessity,” International Journal of Project Management, vol. 33, no. 2, pp291-
298.
[11] STEWART J. (2015) Top 10 Reasons Why Projects Fail, http://project-management.com/top-10-
reasons-why-projects-fail/.
[12] Symonds M. (2011) 15 CAUSES OF PROJECT FAILURE, https://www.projectsmart.co.uk/15-
causes-of-project-failure.php.
[13] Szalvay, V. (2004) An Introduction to Agile Software Development,” CollabNet, Inc.
[14] Hoda, Rashina, et al. (2017) “Systematic literature reviews in agile software development: A tertiary
study,” Information and Software Technology 85 pp60-70.
14. International Journal of Computer Science & Information Technology (IJCSIT) Vol 9, No 3, June 2017
130
[15] Santos, M. A., et al. (2013) “Improving the Management of Cost and Scope in Software Projects
Using Agile Practices,” International Journal of Computer Science & Information Technology
(IJCSIT) 5(1).
[16] Booch, G. (1994) Object-Oriented Analysis and Design with applications 2nd edition, Addison
Wesley Longman.
[17] Beck, K. (2003) Test-Driven Development: By Example, Addison-Wesley.
[18] Beck, K. (2004) Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series)
2nd Edition
[19] Leon, A. (2015) Software Configuration Management Handbook, Third Edition, Artech House Inc.
[20] Fenton, N. E. (1991) Software Metrics - A Rigorous Approach, Chapman & Hall.
[21] Galin, D. (2004) Software Quality Assurance – From theory to implementation, Pearson Education
Limited, England .
[22] Boehm, B.W. (1981) Software Engineering Economics, Prentice-Hall, New Jersey.
AUTHOR
Sen-Tarng Lai was born in Taiwan in 1959. He received his BS from Soochow University, Taiwan in
1982, master from National Chiao Tung University, Taiwan in 1984 and PhD from National Taiwan
University of Science and Technology, Taiwan in 1997. His research interests include software security,
software project management, and software quality. He is currently an assistant professor in the Department
of Information Technology and Management at Shin Chien University, Taipei, Taiwan.