This document summarizes research on factors that contribute to the success of software projects. It discusses functional requirements, operational quality, and usability. The introduction provides background on the importance of quality management and identifies requirements, quality, reliability, performance, and user satisfaction as key success factors. The literature review then summarizes several studies that have examined the impact of reliability, response time, balancing functionality and usability, and measuring customer satisfaction on project outcomes. Overall, the document outlines research establishing that addressing requirements, quality, usability, reliability, and customer satisfaction is critical for software project success.
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.
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.
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
Although there has been an extensive study over delivering, increasing and maintaining software quality, there has not been enough aide- mémoire on ‘Rating a Software‘s Quality’. This study would project the literature review thus far and also sculpt the scope and need for the evolution of a rating system of software quality for the future.
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
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.
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.
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
Although there has been an extensive study over delivering, increasing and maintaining software quality, there has not been enough aide- mémoire on ‘Rating a Software‘s Quality’. This study would project the literature review thus far and also sculpt the scope and need for the evolution of a rating system of software quality for the future.
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
In the software measurement validations, assessing the validation of software metrics in software
engineering is a very difficult task due to lack of theoretical methodology and empirical methodology [41,
44, 45]. During recent years, there have been a number of researchers addressing the issue of validating
software metrics. At present, software metrics are validated theoretically using properties of measures.
Further, software measurement plays an important role in understanding and controlling software
development practices and products. The major requirement in software measurement is that the measures
must represent accurately those attributes they purport to quantify and validation is critical to the success
of software measurement. Normally, validation is a collection of analysis and testing activities across the
full life cycle and complements the efforts of other quality engineering functions and validation is a critical
task in any engineering project. Further, validation objective is to discover defects in a system and assess
whether or not the system is useful and usable in operational situation. In the case of software engineering,
validation is one of the software engineering disciplines that help build quality into software. The major
objective of software validation process is to determine that the software performs its intended functions
correctly and provides information about its quality and reliability. This paper discusses the validation
methodology, techniques and different properties of measures that are used for software metrics validation.
In most cases, theoretical and empirical validations are conducted for software metrics validations in
software engineering [1-50].
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.
HYBRID PRACTICES IN GLOBAL SOFTWARE DEVELOPMENT: A SYSTEMATIC LITERATURE REVIEWijseajournal
Although agile methods in their purest way fit several companies, it has been a challenge to perform them in environments with distributed teams developing large software applications. Contractual items, for projects under development for external organizations, introduce additional complexities for pure agilebased approaches. The majority of global teams and companies use hybrid development practices that combine different development methods and frameworks. This research provides results from an empirical field study on how the hybrids practices are adopted in Global Software Development (GSD) projects. A systematic literature review was conducted to capture the status of combining agile with plan-driven in GSD projects. The results were limited to peer-reviewed conference papers or journal articles, published between 2001 and 2020. The present study selected 37 papers from five different bibliographic databases. In the end, 16 practices were summarized and described as hybrid by GSD projects. Based on the findings of this study, the authors can conclude that the contribution of this study is not only limited to identifying how hybrid development practices are applied in GSD but also allowing that practitioners can have a basis for adapting their development methods.
A PROCESS QUALITY IMPROVEMENT MECHANISM FOR REDUCING THE RISK OF CI ENVIRONMENTijcsit
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.
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
SOFTWARE COST ESTIMATION USING FUZZY NUMBER AND PARTICLE SWARM OPTIMIZATIONIJCI JOURNAL
Software cost estimation is a process to calculate effort, time and cost of a project, and assist in better
decision making about the feasibility or viability of project. Accurate cost prediction is required to
effectively organize the project development tasks and to make economical and strategic planning, project
management. There are several known and unknown factors affect this process, so cost estimation is a very
difficult process. Software size is a very important factor that impacts the process of cost estimation.
Accuracy of cost estimation is directly proportional to the accuracy of the size estimation.
Failure of Software projects has always been an important area of focus for the Software Industry.
Implementation phase is not the only phase for Software projects to fail, instead planning and estimation
steps are the most crucial ones, which lead to their failure. More than 50% of the total projects fail which
go beyond the estimated time and cost. The Standish group‘s CHAOS reports failure rate of 70% for the
software projects. This paper presents the existing algorithms for software estimation and the relevant
concepts of Fuzzy Theory and PSO. Also explains the proposed algorithm with experimental results.
The Impact of Software Complexity on Cost and Quality - A Comparative Analysi...ijseajournal
Early prediction of software quality is important for better software planning and controlling. In early
development phases, design complexity metrics are considered as useful indicators of software testing
effort and some quality attributes. Although many studies investigate the relationship between design
complexity and cost and quality, it is unclear what we have learned beyond the scope of individual studies.
This paper presented a systematic review on the influence of software complexity metrics on quality
attributes. We aggregated Spearman correlation coefficients from 59 different data sets from 57 primary
studies by a tailored meta-analysis approach. We found that fault proneness and maintainability are most
frequently investigated attributes. Chidamber & Kemerer metric suite is most frequently used but not all of
them are good quality attribute indicators. Moreover, the impact of these metrics is not different in
proprietary and open source projects. The result provides some implications for building quality model
across project type.
Comparison between Test-Driven Development and Conventional Development: A Ca...IJERA Editor
In Software Engineering, different techniques and approaches are being used nowadays to produce reliable
software. The software quality relies heavily on the software testing. However, not all developers are concerned
with the testing stage of a software. This has affected the software quality and has increased the cost as well. To
avoid these issues, researchers paid a lot of effort on finding the best technique that guarantee the software
quality. In this paper we aim to explore the effectiveness of building test cases using Test-Driven Development
(TDD) technique compared with the conventional technique (Test-last). The comparison measures the
effectiveness of test cases with regard to number of defects, code coverage and test cases development duration
between TDD and Test-Last. The results has been analyzes and presented to support the best technique. On an
average, the effectiveness of test cases with regards to the selected quality factors in Test-Driven Development
(TDD) was better than the conventional technique (Test-last). TDD and conventional testing had nearly the
same percentage as result in code coverage. Moreover, the number of defects found and the test cases
development duration spent in TDD are high compared with Test-Last. The results led to suggest some
contributions and achievement that could be gained from applying TDD technique in software industry. As
using TDD as development technique in young companies can produce high quality software in less time.
How software size influence productivity and project durationIJECEIAES
To make a perfect project plan, the software size of the order from the customer is the most important factor. The biggest challenge for the project manager is to estimate the project end date in the beginning of the project i.e. in project planning phase with realistic accuracy. Apart from other major inputs to estimate the project end date, expected team capability (productivity) and estimated software size are the major inputs that may influence the project end date. Software size is one of the most significant independent metric available in the planning phase and project manager has to estimate the other metrics based on the initial estimated software size. There is no direct relationship available between software size and project duration or software size and team productivity, however, there are industry data published by Quantitative Software Management and ISBSG that shows how these metrics influence each other. In this paper, using the data published by ISBSG and Quantitative Software Management, we try to statistically establish how productivity and project duration are influenced by software size. We have done linear regression analysis by generating the secondary data based on the data published by ISBSG and Quantitative Software Management. Linear regression equation validated with the actual project data and experimental results suggest that that productivity is significantly dependent on software size, however, project duration does not significantly depend on software size but may also be dependent on other metrics like team size, apart from software size.
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
One of the core quality assurance feature which combines fault prevention and fault detection, is often known as testability approach also. There are many assessment techniques and quantification method evolved for software testability prediction which actually identifies testability weakness or factors to further help reduce test effort. This paper examines all those measurement techniques that are being proposed for software testability assessment at various phases of object oriented software development life cycle. The aim is to find the best metrics suit for software quality improvisation through software testability support. The ultimate objective is to establish the ground work for finding ways reduce the testing effort by improvising software testability and its assessment using well planned guidelines for object-oriented software development with the help of suitable metrics.
Agile software processes, such as extreme programming (XP), Scrum, Lean, etc., rely on best
practices that are considered to improve software development quality. It can be said that best
practices aim to induce software quality assurance (SQA) into the project at hand. Some
researchers of agile methods claim that because of the very nature of such methods,
quality in agile software projects should be a natural outcome of the applied method.
As a consequence, agile quality is expected to be more or less embedded in the agile software
processes. Many reports support and evangelize the advantages of agile methods with respect to
quality assurance, Is it so ?
An ambitious goal of this paper is to present work done to understand how quality is or should
be handled. This paper as all survey papers attempt to summarize and organizes research
results in the field of software engineering, precisely for the topic of agile methods related to
software quality.
A Review of Agile Software Effort Estimation MethodsEditor IJCATR
Software cost estimation is an essential aspect of software project management and therefore the success or failure of a software
project depends on accuracy in estimating effort, time and cost. Software cost estimation is a scientific activity that requires knowledge of a
number of relevant attributes that will determine which estimation method to use in a given situation. Over the years various studies were done
to evaluate software effort estimation methods however due to introduction of new software development methods, the reviews have not
captured new software development methods. Agile software development method is one of the recent popular methods that were not taken
into account in previous cost estimation reviews. The main aim of this paper is to review existing software effort estimation methods
exhaustively by exploring estimation methods suitable for new software development methods.
In the software measurement validations, assessing the validation of software metrics in software
engineering is a very difficult task due to lack of theoretical methodology and empirical methodology [41,
44, 45]. During recent years, there have been a number of researchers addressing the issue of validating
software metrics. At present, software metrics are validated theoretically using properties of measures.
Further, software measurement plays an important role in understanding and controlling software
development practices and products. The major requirement in software measurement is that the measures
must represent accurately those attributes they purport to quantify and validation is critical to the success
of software measurement. Normally, validation is a collection of analysis and testing activities across the
full life cycle and complements the efforts of other quality engineering functions and validation is a critical
task in any engineering project. Further, validation objective is to discover defects in a system and assess
whether or not the system is useful and usable in operational situation. In the case of software engineering,
validation is one of the software engineering disciplines that help build quality into software. The major
objective of software validation process is to determine that the software performs its intended functions
correctly and provides information about its quality and reliability. This paper discusses the validation
methodology, techniques and different properties of measures that are used for software metrics validation.
In most cases, theoretical and empirical validations are conducted for software metrics validations in
software engineering [1-50].
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.
HYBRID PRACTICES IN GLOBAL SOFTWARE DEVELOPMENT: A SYSTEMATIC LITERATURE REVIEWijseajournal
Although agile methods in their purest way fit several companies, it has been a challenge to perform them in environments with distributed teams developing large software applications. Contractual items, for projects under development for external organizations, introduce additional complexities for pure agilebased approaches. The majority of global teams and companies use hybrid development practices that combine different development methods and frameworks. This research provides results from an empirical field study on how the hybrids practices are adopted in Global Software Development (GSD) projects. A systematic literature review was conducted to capture the status of combining agile with plan-driven in GSD projects. The results were limited to peer-reviewed conference papers or journal articles, published between 2001 and 2020. The present study selected 37 papers from five different bibliographic databases. In the end, 16 practices were summarized and described as hybrid by GSD projects. Based on the findings of this study, the authors can conclude that the contribution of this study is not only limited to identifying how hybrid development practices are applied in GSD but also allowing that practitioners can have a basis for adapting their development methods.
A PROCESS QUALITY IMPROVEMENT MECHANISM FOR REDUCING THE RISK OF CI ENVIRONMENTijcsit
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.
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
SOFTWARE COST ESTIMATION USING FUZZY NUMBER AND PARTICLE SWARM OPTIMIZATIONIJCI JOURNAL
Software cost estimation is a process to calculate effort, time and cost of a project, and assist in better
decision making about the feasibility or viability of project. Accurate cost prediction is required to
effectively organize the project development tasks and to make economical and strategic planning, project
management. There are several known and unknown factors affect this process, so cost estimation is a very
difficult process. Software size is a very important factor that impacts the process of cost estimation.
Accuracy of cost estimation is directly proportional to the accuracy of the size estimation.
Failure of Software projects has always been an important area of focus for the Software Industry.
Implementation phase is not the only phase for Software projects to fail, instead planning and estimation
steps are the most crucial ones, which lead to their failure. More than 50% of the total projects fail which
go beyond the estimated time and cost. The Standish group‘s CHAOS reports failure rate of 70% for the
software projects. This paper presents the existing algorithms for software estimation and the relevant
concepts of Fuzzy Theory and PSO. Also explains the proposed algorithm with experimental results.
The Impact of Software Complexity on Cost and Quality - A Comparative Analysi...ijseajournal
Early prediction of software quality is important for better software planning and controlling. In early
development phases, design complexity metrics are considered as useful indicators of software testing
effort and some quality attributes. Although many studies investigate the relationship between design
complexity and cost and quality, it is unclear what we have learned beyond the scope of individual studies.
This paper presented a systematic review on the influence of software complexity metrics on quality
attributes. We aggregated Spearman correlation coefficients from 59 different data sets from 57 primary
studies by a tailored meta-analysis approach. We found that fault proneness and maintainability are most
frequently investigated attributes. Chidamber & Kemerer metric suite is most frequently used but not all of
them are good quality attribute indicators. Moreover, the impact of these metrics is not different in
proprietary and open source projects. The result provides some implications for building quality model
across project type.
Comparison between Test-Driven Development and Conventional Development: A Ca...IJERA Editor
In Software Engineering, different techniques and approaches are being used nowadays to produce reliable
software. The software quality relies heavily on the software testing. However, not all developers are concerned
with the testing stage of a software. This has affected the software quality and has increased the cost as well. To
avoid these issues, researchers paid a lot of effort on finding the best technique that guarantee the software
quality. In this paper we aim to explore the effectiveness of building test cases using Test-Driven Development
(TDD) technique compared with the conventional technique (Test-last). The comparison measures the
effectiveness of test cases with regard to number of defects, code coverage and test cases development duration
between TDD and Test-Last. The results has been analyzes and presented to support the best technique. On an
average, the effectiveness of test cases with regards to the selected quality factors in Test-Driven Development
(TDD) was better than the conventional technique (Test-last). TDD and conventional testing had nearly the
same percentage as result in code coverage. Moreover, the number of defects found and the test cases
development duration spent in TDD are high compared with Test-Last. The results led to suggest some
contributions and achievement that could be gained from applying TDD technique in software industry. As
using TDD as development technique in young companies can produce high quality software in less time.
How software size influence productivity and project durationIJECEIAES
To make a perfect project plan, the software size of the order from the customer is the most important factor. The biggest challenge for the project manager is to estimate the project end date in the beginning of the project i.e. in project planning phase with realistic accuracy. Apart from other major inputs to estimate the project end date, expected team capability (productivity) and estimated software size are the major inputs that may influence the project end date. Software size is one of the most significant independent metric available in the planning phase and project manager has to estimate the other metrics based on the initial estimated software size. There is no direct relationship available between software size and project duration or software size and team productivity, however, there are industry data published by Quantitative Software Management and ISBSG that shows how these metrics influence each other. In this paper, using the data published by ISBSG and Quantitative Software Management, we try to statistically establish how productivity and project duration are influenced by software size. We have done linear regression analysis by generating the secondary data based on the data published by ISBSG and Quantitative Software Management. Linear regression equation validated with the actual project data and experimental results suggest that that productivity is significantly dependent on software size, however, project duration does not significantly depend on software size but may also be dependent on other metrics like team size, apart from software size.
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
One of the core quality assurance feature which combines fault prevention and fault detection, is often known as testability approach also. There are many assessment techniques and quantification method evolved for software testability prediction which actually identifies testability weakness or factors to further help reduce test effort. This paper examines all those measurement techniques that are being proposed for software testability assessment at various phases of object oriented software development life cycle. The aim is to find the best metrics suit for software quality improvisation through software testability support. The ultimate objective is to establish the ground work for finding ways reduce the testing effort by improvising software testability and its assessment using well planned guidelines for object-oriented software development with the help of suitable metrics.
Agile software processes, such as extreme programming (XP), Scrum, Lean, etc., rely on best
practices that are considered to improve software development quality. It can be said that best
practices aim to induce software quality assurance (SQA) into the project at hand. Some
researchers of agile methods claim that because of the very nature of such methods,
quality in agile software projects should be a natural outcome of the applied method.
As a consequence, agile quality is expected to be more or less embedded in the agile software
processes. Many reports support and evangelize the advantages of agile methods with respect to
quality assurance, Is it so ?
An ambitious goal of this paper is to present work done to understand how quality is or should
be handled. This paper as all survey papers attempt to summarize and organizes research
results in the field of software engineering, precisely for the topic of agile methods related to
software quality.
A Review of Agile Software Effort Estimation MethodsEditor IJCATR
Software cost estimation is an essential aspect of software project management and therefore the success or failure of a software
project depends on accuracy in estimating effort, time and cost. Software cost estimation is a scientific activity that requires knowledge of a
number of relevant attributes that will determine which estimation method to use in a given situation. Over the years various studies were done
to evaluate software effort estimation methods however due to introduction of new software development methods, the reviews have not
captured new software development methods. Agile software development method is one of the recent popular methods that were not taken
into account in previous cost estimation reviews. The main aim of this paper is to review existing software effort estimation methods
exhaustively by exploring estimation methods suitable for new software development methods.
Neste conteúdo explico de forma prática e cheia de exemplos os sistemas de organização, navegação, rotulação e busca utilizados na Arquitetura de Informação para interface de sites. Aproveite!
Mini-seminários da disciplina de Teste Formal de Usabilidade, Pós-graduação em Ergodesign de Interfaces da PUC-Rio / Laboratório de Ergonomia e Usabilidade de Interfaces / LEUI. Prof. Luiz Agner, 2010.
A survey of predicting software reliability using machine learning methodsIAESIJAI
In light of technical and technological progress, software has become an urgent need in every aspect of human life, including the medicine sector and industrial control. Therefore, it is imperative that the software always works flawlessly. The information technology sector has witnessed a rapid expansion in recent years, as software companies can no longer rely only on cost advantages to stay competitive in the market, but programmers must provide reliable and high-quality software, and in order to estimate and predict software reliability using machine learning and deep learning, it was introduced A brief overview of the important scientific contributions to the subject of software reliability, and the researchers' findings of highly efficient methods and techniques for predicting software reliability.
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
In this paper a correlation between the major attributes of object oriented design and changeability has been ascertained. A changeability evaluation model using multiple linear regression has been proposed for object oriented design. The validation of the proposed changeability evaluation model is made known by means of experimental tests and the results show that the model is highly significant.
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
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.
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 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.
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.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
Software quality model based on development team characteristicsIJECEIAES
Many factors have a significant impact on producing high-quality software products. Development team members are among the most important factors. Paying attention to the quality from this perspective will be a good innovation in the software development industry. Given that team members play a very important role in software products, this study tries to focus specifically on team characteristics in software product quality and provide a qualitative model based on this. The required data were collected through observations and interviews with project managers and development team members in several companies under study. Then, data were analyzed through hierarchical analysis. According to the results, the use of this model led to the improvement of the software development process so that the team members were satisfied with it. Also, time management was improved, and the customer expressed his satisfaction with the use of this model. Finally, data analysis showed that this model may lead to faster product delivery.
Contributors to Reduce Maintainability Cost at the Software Implementation PhaseWaqas Tariq
Software maintenance is important and difficult to measure. The cost of maintenance is the most ever during the phases of software development. One of the most critical processes in software development is the reduction of software maintainability cost based on the quality of source code during design step, however, a lack of quality models and measures can help asses the quality attributes of software maintainability process. Software maintainability suffers from a number of challenges such as lack source code understanding, quality of software code, and adherence to programming standards in maintenance. This work describes model based-factors to assess the software maintenance, explains the steps followed to obtain and validate them. Such a method can be used to eliminate the software maintenance cost. The research results will enhance the quality of the source code. It will increase software understandability, eliminate maintenance time, cost, and give confidence for software reusability.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
On applications of Soft Computing Assisted Analysis for Software ReliabilityAM Publications
Developing high quality reliable software is one of the main challenges in software industry. Software
Reliability is a key concern of many users and developers of software. Demand for software reliability requires robust
modeling techniques for software quality prediction. Software reliability models are very useful to estimate the
probability of failure of software along with the time. In this study we review the available literature on software
reliability. We have also elicited the current trends, existing problems, specific difficulties, future directions and open
areas for research.
Requirement engineering is a key ingredient for software development to be effective. Apart from the
traditional software requirement which is not much appropriate for new emerging software such as smart
handheld device based software. In many perspectives of requirement engineering, traditional and new
emerging software are not similar. Whereas requirement engineering of traditional software needs more
research, it is obvious that new emerging software needs methodically and in-depth research for improved
productivity, quality, risk management and validity. In particular, the result of this paper shows that how
effective requirement engineering can improve in project negotiation, project planning, managing feature
creep, testing, defect, rework and product quality. This paper also shows a new methodology which is
focused on users work process applicable for eliciting the requirement of traditional software and any new
type software of smart handheld device such as iPad. As an example, the paper shows how the methodology
will be applied as a software requirement of iPad-based software for play-group students.
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.
Majority of agile projects currently involve interactive user interface designs, which can only be possible by following UCD in agile software model. But the integration of UCD is not clear in the current agile models. Both Agile models and UCD have iterative nature but agile models focus on coding and development of software; whereas, UCD focuses on user interface of the software. Similarly, both of them have testing features where the agile model involves automated tested code while UCD involves an expert or a user to test the user interface. In this paper, a new agile usability model is presented and tested in companies and are presented. Key results from these projects clearly shows: the proposed agile model incorporates usability evaluation methods, improve the relationship between usability experts to work with agile software experts; in addition, allows agile developers to incorporate the result from UCD into subsequent interactions.
EVALUATION OF SOFTWARE DEGRADATION AND FORECASTING FUTURE DEVELOPMENT NEEDS I...ijseajournal
This article is an extended version of a previously published conference paper. In this research, JHotDraw (JHD), a well-tested and widely used open source Java-based graphics framework developed with the best software engineering practice was selected as a test suite. Six versions of this software were profiled, and data collected dynamically, from which four metrics namely (1) entropy (2) software maturity index, COCOMO effort and duration metrics were used to analyze software degradation, maturity level and use
the obtained results as input to time series analysis in order to predict effort and duration period that may
be needed for the development of future versions. The novel idea is that, historical evolution data is used to
project, predict and forecast resource requirements for future developments. The technique presented in
this paper will empower software development decision makers with a viable tool for planning and decision
making.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Key Trends Shaping the Future of Infrastructure.pdf
F0262036041
1. International Journal of Engineering Science Invention
ISSN (Online): 2319 – 6734, ISSN (Print): 2319 – 6726
www.ijesi.org Volume 2 Issue 6 ǁ June. 2013 ǁ PP.36-41
www.ijesi.org 36 | Page
The Role of Functional Requirements, Operational Quality and
Usability In The Success Story Of Software Projects
1,
Tuhin Chattopadhyay , 2,
Nidhi Natrajan
1,
Associate Professor, Fortune Institute of International Business, New Delhi.
2,
Assistant Professor, Galgotias Business School, Greater Noida.
ABSTRACT : The Role of Functional Requirements, Operational Quality and Usability in the Success Story of
Software Projects
I. INTRODUCTION
The development of high quality software is important for the successful implementation of a software
project. But to develop a bug free software is definitely a challenge. As per report of National Institute of
Standards and Technology (2003), software errors cost approximately $60 billion per year in terms of lost
productivity, increased time to market costs, higher market transaction costs, etc.Study of project management
and project management success is relevant even today inspite of project management usage from 1960’s, as
large number of failure of software projects have been reported (Riley, 2006; Hass, 2007; Xia &.Lyu,
2007).Projects fail due to number of reasons; it may be bad system design, improper process, unclear
requirements, poor quality etc. good quality management is an important factor to implement a successful
software project (Jones, 2006; Leveson, 2004; Hosalkar & Bowonder, 2000; Markus, 2000; Glass, 1999).
Quality attributes are the overall factors that affect run-time behavior, system design, and user experience.
Managing quality is critical because it is very difficult to improve or adjoin quality to the software once it is
developed, even the rectification have its overheads in terms of time and budget. According to Reel (1999), it is
desirable to establish procedures and benchmarks for high quality before beginning the development process,
which may require hiring expert developers. Success of quality can be measured through conformance to
functional requirements specified by the customer and other technical specifications (Morris & Hough, 2004;
Boehm &Turner, 2003).
Other quality features like performance/ response time, reliability and usability are factor’s which lead
to a success full project. Role of software is evident in all fields, which indicates the growing complexity and
diversification of information system. Complex softwares are associated with reliability problem (Zheng, Xu,
2008).It is important for a system to remain operational over time. Reliability is measured as the probability that
a system will not fail to perform its intended functions over a specified time interval.Functionality and usability
are critical factors of project success (Bayraktaroglu, Calisir & Gumussoy, 2009; Juristo, Moreno & Sanchez-
Segura, 2007). Usability defines how well the application meets the requirements of the user and consumer by
being intuitive, easy to localize and globalize, providing good access for disabled users, and resulting in a good
overall user experience. Performance is an indication of the responsiveness of a system to execute any action
within a given time interval. It can be measured in terms of latency or throughput. Latency is the time taken to
respond to any event. Throughput is the number of events that take place within a given amount of time. Good
response time or the real time response affects the success of a software project (Fujiki & Hasegawa, 1992;
Pekilis & Seviora, 1997; Alander, Mantere, Moghadampour & Matila, 1997). Customer satisfaction is essential
for success if a software project. (Howard, 1992;Narayanan, Balasubramanian&Swaminathan, 2011).Customer
satisfaction was initially not considered while measuring quality of software and only technical aspects and
process improvement were included, specifically it is very important for customized software to be of good
design and match the user requirement (Macaulay, Sloan, Jiang, Forbes, Loynton, Swedlow, andGregor, 2009;
Schlossberg, 1992; Anonymous, 2001). They also emphasized on the preparation of proper user manual to
enhance the usability of the software. Satisfaction of stakeholders including customer satisfaction has also been
highlighted by Meister (2008)for the project success.
As per Bayraktaroglu, Calisir & Gumussoy (2009) user centric software is an indicator of quality it is
important to balance out between the functional requirement of the user and usability of the software. According
to James Johnson (2001) chairman of Standish Group International, user satisfaction is one of the best practices
that an Information technology project management should involve. Meeting the requirements of customer
creates a value for them, and this finally leads to success of a project. Watts S. Humphrey, a Fellow of the
2. The Role Of Functional Requirements, Operational…
www.ijesi.org 37 | Page
Carnegie Mellon Software Engineering Institute and Former Director of Software Quality and Process
for IBM (2003) indicated that even experienced developers can write ten percent defective code. But if best
development practices are followed it can be lowered down by fifty percent. Although importance of quality,
functional requirement, usability and ratability has been emphasized for more than a decade not much empirical
work has been done to understand their impact together.
II. LITERATURE REVIEW
Musaand Everett (1990) highlighted that software development has reached the stage based on
reliability, starting from function oriented; schedule oriented and then cost oriented stages. Djambazov & Popov
(1995) conducted an experimental study, to find out the effect of testing on reliability, considering the impact of
reliability on the project success. Simulator was used for understanding the effect of fault in design on
behavioral modeling of software. Result of the experiment established that failure was caused due to interplay
between design faults.Huang, Lin, and Sue (2004) gave a stochastic reliability model for software failure based
on Software Reliability Growth Model (SRGM) and NHPP model. Reliability model was useful during testing
phase to remove errors, which increases project success rate. Xia & Lyu (2007) emphasized on measurement of
failure data from various stages; preprocessing of data, analysis of data, model structure identification and
parameter estimation, reliability model solution and analysis of models. This was necessary to appropriately
estimate and predict ratability of software systems. Gayen (2009) also professed the analysis of error-based
model for predicting minimum reliability of a software. The model is based on the concept that reliability is a
function of number of errors reported by the software for a given duration. In another study conducted by
Aljahdali&Sheta (2011) have proposed use of Fuzzy logic for predicting reliability of a software. Data were
obtained from Bell Telephone Laboratories; the dataset consists of software fault data on sixteen projects. Fuzzy
Model Identification Toolbox was run on data, where seventy percent data was for training and thirty percent for
testing. As a result a fuzzy nonlinear regression models were developed for predicting the total fault of software
applications. Fujiki, Hasegawa, Wongwarawipat & Ishizuka (1992), emphasized on the importance of response
time for good software quality, with reference to virtual reality applications. The result of the study was a
proposed solution, which was combination of hardware and software algorithm. Importance of response time for
real time software was also highlighted by Pekilis & Seviora (1997). Black box testing technique is suggested to
detect degradation in software quality and response time failure. Alander, Mantere, Moghadampour & Matila
(1997) through their study established the use of genetic algorithm for measuring response time of the software,
which will help in improving it. Use of software transactional memory (STM) is suggested by Fahmy,
Ravindran & Jensen (2009) to improve the response time for multiprocessor environment. They conducted
experimental study and proposed an algorithm which was validated using simulation.
Functional and usable software products are more popular among users. It is critical to balance out both
the factors i.e. functionality and usability. According to Bayraktaroglu, Calisir, Gumussoy (2009) this balancing
can be taken care during the design phase. And to do this perception of project mangers regarding user’s
expectation must match. This study compared the project managers’ and potential users’ evaluations of the
relative importance of usability and functionality factors in a software design project. (ANP) was used to
analyze the relative importance of the factors. Analytical Network Process is helpful in solving decision making
problems when factors involved are interrelated. A study was conducted by Macaulay, Sloan, Jiang, Forbes,
Loynton, Swedlow, and Gregor (2009) to understand the usability and customer centric image project. The
study showed that it was challenging for the scientific developers to work around user centric projects. And in
order to increase the number of potential users of the software, barriers to adoption of new software must be
reduced. Design ethnography was used as methodology to do the research. Proper user guide and user tutorial
including web based tutorial movies were prepared.The sample size of the survey was forty four of scientists
working with microscopy images at Dundee.
Project performance and customer satisfaction were established as important factor for the project
success by Narayanan, Balasubramanian & Swaminathan (2010). They conducted this study for outsourced
software projects by using a proprietary panel dataset. Eight hundred twenty two customers from hundred eighty
two projects responded. Five point likert scale was used to measure customer satisfaction and regression
analysis was applied to understand the impact of overall satisfaction on project performance. Although there are
few studies to understand the implication of customer satisfaction on project success but factors like reliability,
response time are not being empirically tested. Through this paper we propose to take data from developers and
project managers on usability, operational quality and whether customer requirement were met. Novelty of the
study is to empirically establish the impact of all three quality factors on project performance/ success, by
applying regression analysis.
3. The Role Of Functional Requirements, Operational…
www.ijesi.org 38 | Page
III. HYPOTHESIS
H1: There is a significant positive relationship between the success of the software project and conformance to
functional requirement (functionality) of the software.
H2: There is a significant positive relationship between the success of the software project and operational
quality of the software.
H3: There is a significant positive relationship between the success of the software project and usability of the
software.
IV. RESEARCH DESIGN
The present research is causal in nature, trying to figure out the impact of process guidance by the tool,
integration of task and information, work flow, transparency of information, visualization of analyzed
information on the success of automated software projects.
4.1.Sampling Design
The research was carried out in the software organization of India. We have taken the sample of
software professionals by dint of stratified random sampling resulting into total sample of one hundred and fifty.
Respondents were given the questionnaire over electronic-mail and were required to rate the questions on a
seven-point Likert scale. Thirty questionnaires were sent to each IT organization and the final respondent
participated in the study by returning the self-administered questionnaire was 150.
4.2.Data Collection Design
The data were collected from five leading software companies of India through a questionnaire where each item
was measured in Likert scale. The operational quality, functionality and usability are measured through a
composite score of ten items.
4.3.Statistical Design
Multiple regression was used to assess the impact of functional requirement, operational quality and
usability on success of software project, where success of software project is the dependent variable and
functional requirement, operational quality & usability are the independent variable.
4.4.Model and Variable Definitions
The following model is used for testing hypotheses:
Success of the Project = β0 + β1operational quality + β2functionality + β3Usability. The variables are explained
as following:
4.5.Success of the software project
Successful software projects are often defined as meeting business objectives, deliver on time and
within budget, and meeting requirements (Nasir&Sahibuddin, 2011).
Operational quality
1. The degree to which a system, component, or process meets specified requirements.
2. The degree to which a system, component, or process meets customer or user needs or expectations.(
Pressman, Scott (2005), Software Engineering: A Practitioner's Approach (Sixth, International ed.),
McGraw-Hill Education Pressman, p. 388)
4.6.Functionality
Functionality estimates the extent the software operates in the way it is structured and is expectedto
perform as user’s desire. Usability Usability assesses the extent a software facilitates users utilize the offered
functions easily and appropriately.
4.7.EMPIRICAL RESULTS
Correlation Matrix
The correlation between variables indicates that how much of variables changes is explained by other variables
which is between 1 and -1. The correlation between variables is shown in Table 1.
4. The Role Of Functional Requirements, Operational…
www.ijesi.org 39 | Page
Table 1 Correlation matrix
Operational Quality of the
software
Functional requirement Usability of the
software
Success of the software project Pearson Correlation .781**
.855**
.507**
Sig. (2-tailed) .000 .000 .000
N 150 150 150
The results provided in Table 1 reveal that the correlation coefficient between success of software project and
functional requirement is .855, operational quality is .781 & usability is .507 and the correlation is significant (p
< .05).The dependent variable shows a high & significant correlation with the independent variables operational
quality, functionality and usability, which shows that we have selected fairly good set of independent variables.
Table 2
Coefficientsa
Model
Unstandardized Coefficients
Standardized
Coefficients
t Sig.B Std. Error Beta
1 (Constant) .211 .294 .716 .475
Operational Quality of the software .228 .077 .218 2.972 .003
Functional requirement .639 .078 .622 8.211 .000
Usability of the software .118 .053 .105 2.243 .026
a. Dependent Variable: Success of the software project
Table 2 reveals that Functional requirement(t = 8.211, p < .05), operational quality(t = 2.972, p < .05)
andusability(t = 2.243, p < .05) all the three independent variables leaves a statistically significant impact on the
success of the software projects. All hypotheses got accepted and all the three variables leave an impact on the
success of the software project separately.The relationship between functional requirement, operational quality
& usability and the success of the software projects is as follows:All the three variables taken together make a
statistically significant impact on the success of the software project.
Table 3
ANOVAb
Model Sum of Squares df Mean Square F Sig.
1 Regression 193.160 3 64.387 150.940 .000a
Residual 62.280 146 .427
Total 255.440 149
a. Predictors: (Constant), Usability, Operation Quality, Functional Requirement
b. Dependent Variable: Project Success
Table 3 shows that the model is statistically significant (F= 150.940, p < .05)
Table 4
Model Summary
Model R R Square Adjusted R Square
Std. Error of the
Estimate
1 .870a
.756 .751 .653
a. Predictors: (Constant), Usability, Operation Quality, Functional Requirement
Table 4 reveals that a significant regression was achieved with adjusted R2
of 75.1% which shows that the
relationship between Software project success and operational quality, functionality & usability. 75.1% of the
variation of success of software project is explained by operational quality, functionality & usability. Since each
of the variables considered in this study are significant as shown by the result of t-test, the model is significant
as per the result of ANOVA and the variation explained by all the independent variables on the dependent
variables is 75.1%, hence we can form the regression equation from the Table 3 as follows: Success of the
Software Project = .211+. .228operational quality + .639 functionality + .118usability
5. The Role Of Functional Requirements, Operational…
www.ijesi.org 40 | Page
V. DISCUSSION
Customer satisfaction is achieved by delivering software which conform to the quality assurance,
conform to the functional requirements and is usable. Lack of all these features lead to rework, lost time and
eventually unhappy customers i.e. project failure. The result of this research highlights the importance of
operational quality, functionality and usability of the software for the successful implementation of the project
success. The result further reveals that the functional conformance leaves highest impact on the software project
success. The basic and most important attribute of a software product—or any other product, for that matter—is
that it delivers its specified functionality accurately. Second highest impact on software project success is of
operational quality. Quality attributes are the overall factors that affect run-time behavior, system design, and
user experience. They represent areas of concern that have the potential for application wide impact across
layers and tiers. Some of these attributes are related to the overall system design, while others are specific to run
time, design time, or user centric issues. Functional quality means that the software correctly performs the tasks
it’s intended to do for its user. Quality is vital for a software project to be successful. It is a complex concept and
it is related to business goals, good software leads to good business. Establishing a quality-oriented mindset is a
top management responsibility, but it is up to the software development organization to adopt and execute on
that mindset. IT must embrace the right process and tools, and seek the right guidance or training to produce the
results that management, customers, and end-users are seeking. Though among the three factors usability is
having least weightage as per the result, but definitely leaves an impact on the success of the project. With
higher usability users require to spend less time learning the system and are more likely to achieve their goals,
they have a satisfying experience, increasing the likelihood of future use and recommendation to others and will
be able to develop trust and use the system with greater confidence. It is very clear that the core requirement is
to deliver software with all the functional aspects, with good quality and the one which is usable, to make the
customer satisfied and software project a success.
VI. CONCLUSION
Customer satisfaction is a key to success for a software project. The customer is satisfied if the
software conform to the functional conformance, is of high quality and usable. It is extremely important to
understand the requirement of the customer/ end user in order to deliver fully functional product. The best way
to do this is to deliver in phases and get it approved by the customer, so that efforts of redoing the whole thing
are minimized. Quality, error-free work holds down costs Quality assurance provides the mechanisms for
paying close attention to details so that tasks are completed correctly and accurately every step of the way. A
quality assurance role should be established for all projects. Users tend to use functional and usable products
more frequently. The navigation facility, reports generated by the software etc. must be easy to learn and logical.
The documentation should also be proper to make the software product usable. This research helps in
understanding the importance of functionality, operational quality and usability on the success of the software
project. The uniqueness of this study is to explain the impact of all these three factors taken together. The
research considered the sample of hundred and fifty software professionals in India, which could be enhanced
in terms of a bigger sample and expanded geographic coverage.
REFERENCES:
[1] Alander J. T, Mantere,M. Moghadampour, G. &Matila,J.( 1997) ―Searching Protection Relay Response Time Extremes using
Genetic Algorithm - Software Quality by
[2] Optimization‖, Proceedings of the 4th International Conference on Advances in Power System Control, Operation and
Management, APSCOM-97, Hong Kong, November 1997.
[3] Aljahdali, S.&Sheta, A.F. (2011), Predicting the Reliability of Software Systems Using Fuzzy Logic, 2011 Eighth International
Conference on Information Technology: New Generations
[4] Atlee, J. and Wieringa, R. (2006). ‖RE 05: Engineering Successful Products‖. IEEE
[5] Software, 23, pp. 16 –18.
[6] Baccarini D., Salm G. & Love E. D. Peter (2004). ―Management of Risks in Information Technology Projects‖.Ind. Manag. Data
Syst., 104(4): 286-295.
[7] Bayraktaroglu, A. E. Calisir, F. &Gumussoy, C. A. (2009). Usability and Functionality: A Comparison of Project Managers’
and Potential Users’ Evaluations, , Proceedings of the 2009 IEEE IEEM
[8] Bertot, J.C, Snead, J.T., Jaeger, P.T. & McClure, C.R. (2006).―Functionality, usability and accessibility,‖ Performance
Measurement and Metrics, vol.7, no. 1, pp. 17-28, 2006.
[9] Boehm B (1981). ―Software Engineering Economics‖, Prentice-Hall, p. 117.
[10] Boehm, B. and R. Turner (2003). Balancing Agility and Discipline: A Guide for the
[11] Perplexed. Boston, MA, Addison Wesley.
[12] Customer satisfaction top measure of success, Anonymous, Construction Equipment; May 2001; 103, 5; ABI/INFORM Global,
pg. 14
[13] Djambazov, K. & Popov, P. (1995) The Effect of Testing on the Reliability of Single Version
[14] and 1-out-of-2 Software Systems, IEEE
[15] Dyba, T. &Dingsøyr, T. (2008) ‖ Empirical studies of agile software development: A systematic review‖, Inform.Softw.
Technol., doi:10.1016/j.infsof.2008.01.006