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.
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.
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.
SRGM Analyzers Tool of SDLC for Software Improving QualityIJERA Editor
Software Reliability Growth Models (SRGM) have been developed to estimate software reliability measures such as
software failure rate, number of remaining faults and software reliability. In this paper, the software analyzers tool proposed
for deriving several software reliability growth models based on Enhanced Non-homogeneous Poisson Process (ENHPP) in
the presence of imperfect debugging and error generation. The proposed models are initially formulated for the case when
there is no differentiation between failure observation and fault removal testing processes and then this extended for the case
when there is a clear differentiation between failure observation and fault removal testing processes. Many Software
Reliability Growth Models (SRGM) have been developed to describe software failures as a random process and can be used
to measure the development status during testing. With SRGM software consultants can easily measure (or evaluate) the
software reliability (or quality) and plot software reliability growth charts.
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.
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
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.
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.
SRGM Analyzers Tool of SDLC for Software Improving QualityIJERA Editor
Software Reliability Growth Models (SRGM) have been developed to estimate software reliability measures such as
software failure rate, number of remaining faults and software reliability. In this paper, the software analyzers tool proposed
for deriving several software reliability growth models based on Enhanced Non-homogeneous Poisson Process (ENHPP) in
the presence of imperfect debugging and error generation. The proposed models are initially formulated for the case when
there is no differentiation between failure observation and fault removal testing processes and then this extended for the case
when there is a clear differentiation between failure observation and fault removal testing processes. Many Software
Reliability Growth Models (SRGM) have been developed to describe software failures as a random process and can be used
to measure the development status during testing. With SRGM software consultants can easily measure (or evaluate) the
software reliability (or quality) and plot software reliability growth charts.
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.
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
Introduction to Investigation And Utilizing Lean Test Metrics In Agile Softwa...IJERA Editor
The growth of the software development industry approaches the new development methodologies to deliver the
error free software to its end-user fulfilling the business values to product. The growth of tools and technology
has brought the automation in the development and software testing process, it has also increased the demand of
the fast testing and delivery of the software to end customers. Traditional software development methodologies
to trending agile software development trend have brought new philosophy, dimensions, and processes having
invested new tools to make process easy. The Agile development (Scrum, XP, FDD, BDD, ATDD, ASD,
DSDM, Kanban, Crystal and Lean) process also faces the software testing model crises because of the fast
development of life cycles, fast delivery to end users without having appropriate test metrics which make the
software testing process slow as well as increase the risk. The analysis of the testing metrics in the software
testing process and setting the right lean test metrics help to improve the software quality effectively in agile
process.
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.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
A maintainability enhancement procedureijseajournal
In mobile communications age, environment changes rapidly, the requirements change is the software
project must face challenge. Able to overcome the impact of requirements change, software development
risk can be effectively decreased. In order to reduce software requirements change risk, the paper
investigates the major software development models and recommends the adaptable requirements change
software development. Agile development applied the Iterative and Incremental Development (IID)
approach, focuses on workable software and client communication. In software development, agile
development is a very suitable approach to handle the requirements change. However, agile development
maintenance existed many defects that include development documents control, user story inspection and
CM system. The maintenance defects of agile development should be improved. Analysing and collecting
the critical quality factors of agile development maintainability, in this paper proposes the Agile
Development Maintainability Measurement (ADMM) model. Based on ADMM model, the Agile
Development Maintainability Enhancement (ADME) procedure can be defined and deployed for reducing
the risk of requirements change.
The modern business environment requires organizations to be flexible and open to change if they are to gain and retain their competitive age. Competitive business environment needs to modernize existing legacy system in to self-adaptive ones. Reengineering presents an approach to transfer a legacy system towards an evolvable system. Software reengineering is a leading system evolution technique which helps in effective cost control, quality improvements and time and risk reduction. However successful improvement of legacy system through reengineering requires portfolio analysis of legacy application around various quality and functional parameters some of which includes reliability and modularity of the functions, level of usability and maintainability as well as policy and standards of software architecture and availability of required documents. Portfolio analysis around these parameters will help to examine the legacy application on quality and functional gaps within the application [1].
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.
DETECTION AND REFACTORING OF BAD SMELL CAUSED BY LARGE SCALEijseajournal
Bad smells are signs of potential problems in code. Detecting bad smells, however, remains time
consuming for software engineers despite proposals on bad smell detection and refactoring tools. Large
Class is a kind of bad smells caused by large scale, and the detection is hard to achieve automatically. In
this paper, a Large Class bad smell detection approach based on class length distribution model and
cohesion metrics is proposed. In programs, the lengths of classes are confirmed according to the certain
distributions. The class length distribution model is generalized to detect programs after grouping.
Meanwhile, cohesion metrics are analyzed for bad smell detection. The bad smell detection experiments of
open source programs show that Large Class bad smell can be detected effectively and accurately with this
approach, and refactoring scheme can be proposed for design quality improvements of programs.
Management of time uncertainty in agileijseajournal
The rise of the use of mobile technologies in the world, such as smartphones and tablets, connected to
mobile networks is changing old habits and creating new ways for the society to access information and
interact with computer systems. Thus, traditional information systems are undergoing a process of
adaptation to this new computing context. However, it is important to note that the characteristics of this
new context are different. There are new features and, thereafter, new possibilities, as well as restrictions
that did not exist before. Finally, the systems developed for this environment have different requirements
and characteristics than the traditional information systems. For this reason, there is the need to reassess
the current knowledge about the processes of planning and building for the development of systems in this
new environment. One area in particular that demands such adaptation is software estimation. The
estimation processes, in general, are based on characteristics of the systems, trying to quantify the
complexity of implementing them. Hence, the main objective of this paper is to present a proposal for an
estimation model for mobile applications, as well as discuss the applicability of traditional estimation
models for the purpose of developing systems in the context of mobile computing. Hence, the main objective
of this paper is to present an effort estimation model for mobile applications.
FAST TRANSIENT RESPONSE LOW DROPOUT VOLTAGE REGULATORijseajournal
This paper presents the design of Low Drop-Out (LDO) voltage regulator has fast transient response and which exploits a few current else low quiescent current in the operational amplifier PMOS type. We use band-gap reference for eliminate the temperature dependence. The proposed LDO voltage regulator implemented in 0.18-μm CMOS technology, we use Folded cascode CMOS amplifiers high performance in the stability , provide fast transient response which explains a fast settling, the LDO itself should provide in the output regulator voltages at t equal 2ps with transient variation of the voltage less than 170mV. High accuracy in the DC response terms, the simulation results show that the accuracy of the output regulator voltages is 1.54±0.009V, and power consumption of 1.51 mW.
A model for run time software architecture adaptationijseajournal
Since the global demand for software systems and constantly changing environments and systems is
increasing, the adaptability of software systems is of significant importance. Due to the architecture of
software system is a high-level view of the system and makes the modifiability possible at an overall level,
the adaptability of the software can be considered an effective approach to adapt software systems by
changing architecture configuration. In this study, the architecture configuration is modified through xADL
language which is a software architecture description language with a high flexibility. Software
architecture reconfiguration is done based on existing rules of rule-based system, which are written with
respect to three strategies of load balancing, fixed bandwidth and fixed latency. The proposed model of the
study is simulated based on samples of client-server system, video conferencing system and students’
grading system. The proposed model can be used in all types of architecture, include Client Server
Architecture, Service Oriented Architecture and etc.
Secured cloud support for global softwareijseajournal
This paper presents core problem solution to security of Global Software Development Requirement
Information. Currently the major issue deals with hacking of sensitive client information which may lead to
major financial as well as social loss. To avoid this system provides cloud security by encryption of data as
well as deployment of tool over the cloud will provide significant security to whole global content
management system. The core findings are presented in terms of how hacker hacks such systems and what
counter steps need to follow. Our algorithmic development provide random information storage at various
cloud nodes to secure our client requirement data files.
A novel approach for clone group mappingijseajournal
Clone group mapping has a very important significance in the evolution of code clone. The topic modeling
techniques were applied into code clone firstly and a new clone group mapping method was proposed. The
method is very effective for not only Type-1 and Type-2 clone but also Type-3 clone .By making full use of
the source text and structure information, topic modeling techniques transform the mapping problem of
high-dimensional code space into a low-dimensional topic space, the goal of clone group mapping was
indirectly reached by mapping clone group topics. Experiments on four open source software show that the
recall and precision are up to 0.99, thus the method can effectively and accurately reach the goal of clone
group mapping.
Introduction to Investigation And Utilizing Lean Test Metrics In Agile Softwa...IJERA Editor
The growth of the software development industry approaches the new development methodologies to deliver the
error free software to its end-user fulfilling the business values to product. The growth of tools and technology
has brought the automation in the development and software testing process, it has also increased the demand of
the fast testing and delivery of the software to end customers. Traditional software development methodologies
to trending agile software development trend have brought new philosophy, dimensions, and processes having
invested new tools to make process easy. The Agile development (Scrum, XP, FDD, BDD, ATDD, ASD,
DSDM, Kanban, Crystal and Lean) process also faces the software testing model crises because of the fast
development of life cycles, fast delivery to end users without having appropriate test metrics which make the
software testing process slow as well as increase the risk. The analysis of the testing metrics in the software
testing process and setting the right lean test metrics help to improve the software quality effectively in agile
process.
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.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
A maintainability enhancement procedureijseajournal
In mobile communications age, environment changes rapidly, the requirements change is the software
project must face challenge. Able to overcome the impact of requirements change, software development
risk can be effectively decreased. In order to reduce software requirements change risk, the paper
investigates the major software development models and recommends the adaptable requirements change
software development. Agile development applied the Iterative and Incremental Development (IID)
approach, focuses on workable software and client communication. In software development, agile
development is a very suitable approach to handle the requirements change. However, agile development
maintenance existed many defects that include development documents control, user story inspection and
CM system. The maintenance defects of agile development should be improved. Analysing and collecting
the critical quality factors of agile development maintainability, in this paper proposes the Agile
Development Maintainability Measurement (ADMM) model. Based on ADMM model, the Agile
Development Maintainability Enhancement (ADME) procedure can be defined and deployed for reducing
the risk of requirements change.
The modern business environment requires organizations to be flexible and open to change if they are to gain and retain their competitive age. Competitive business environment needs to modernize existing legacy system in to self-adaptive ones. Reengineering presents an approach to transfer a legacy system towards an evolvable system. Software reengineering is a leading system evolution technique which helps in effective cost control, quality improvements and time and risk reduction. However successful improvement of legacy system through reengineering requires portfolio analysis of legacy application around various quality and functional parameters some of which includes reliability and modularity of the functions, level of usability and maintainability as well as policy and standards of software architecture and availability of required documents. Portfolio analysis around these parameters will help to examine the legacy application on quality and functional gaps within the application [1].
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.
DETECTION AND REFACTORING OF BAD SMELL CAUSED BY LARGE SCALEijseajournal
Bad smells are signs of potential problems in code. Detecting bad smells, however, remains time
consuming for software engineers despite proposals on bad smell detection and refactoring tools. Large
Class is a kind of bad smells caused by large scale, and the detection is hard to achieve automatically. In
this paper, a Large Class bad smell detection approach based on class length distribution model and
cohesion metrics is proposed. In programs, the lengths of classes are confirmed according to the certain
distributions. The class length distribution model is generalized to detect programs after grouping.
Meanwhile, cohesion metrics are analyzed for bad smell detection. The bad smell detection experiments of
open source programs show that Large Class bad smell can be detected effectively and accurately with this
approach, and refactoring scheme can be proposed for design quality improvements of programs.
Management of time uncertainty in agileijseajournal
The rise of the use of mobile technologies in the world, such as smartphones and tablets, connected to
mobile networks is changing old habits and creating new ways for the society to access information and
interact with computer systems. Thus, traditional information systems are undergoing a process of
adaptation to this new computing context. However, it is important to note that the characteristics of this
new context are different. There are new features and, thereafter, new possibilities, as well as restrictions
that did not exist before. Finally, the systems developed for this environment have different requirements
and characteristics than the traditional information systems. For this reason, there is the need to reassess
the current knowledge about the processes of planning and building for the development of systems in this
new environment. One area in particular that demands such adaptation is software estimation. The
estimation processes, in general, are based on characteristics of the systems, trying to quantify the
complexity of implementing them. Hence, the main objective of this paper is to present a proposal for an
estimation model for mobile applications, as well as discuss the applicability of traditional estimation
models for the purpose of developing systems in the context of mobile computing. Hence, the main objective
of this paper is to present an effort estimation model for mobile applications.
FAST TRANSIENT RESPONSE LOW DROPOUT VOLTAGE REGULATORijseajournal
This paper presents the design of Low Drop-Out (LDO) voltage regulator has fast transient response and which exploits a few current else low quiescent current in the operational amplifier PMOS type. We use band-gap reference for eliminate the temperature dependence. The proposed LDO voltage regulator implemented in 0.18-μm CMOS technology, we use Folded cascode CMOS amplifiers high performance in the stability , provide fast transient response which explains a fast settling, the LDO itself should provide in the output regulator voltages at t equal 2ps with transient variation of the voltage less than 170mV. High accuracy in the DC response terms, the simulation results show that the accuracy of the output regulator voltages is 1.54±0.009V, and power consumption of 1.51 mW.
A model for run time software architecture adaptationijseajournal
Since the global demand for software systems and constantly changing environments and systems is
increasing, the adaptability of software systems is of significant importance. Due to the architecture of
software system is a high-level view of the system and makes the modifiability possible at an overall level,
the adaptability of the software can be considered an effective approach to adapt software systems by
changing architecture configuration. In this study, the architecture configuration is modified through xADL
language which is a software architecture description language with a high flexibility. Software
architecture reconfiguration is done based on existing rules of rule-based system, which are written with
respect to three strategies of load balancing, fixed bandwidth and fixed latency. The proposed model of the
study is simulated based on samples of client-server system, video conferencing system and students’
grading system. The proposed model can be used in all types of architecture, include Client Server
Architecture, Service Oriented Architecture and etc.
Secured cloud support for global softwareijseajournal
This paper presents core problem solution to security of Global Software Development Requirement
Information. Currently the major issue deals with hacking of sensitive client information which may lead to
major financial as well as social loss. To avoid this system provides cloud security by encryption of data as
well as deployment of tool over the cloud will provide significant security to whole global content
management system. The core findings are presented in terms of how hacker hacks such systems and what
counter steps need to follow. Our algorithmic development provide random information storage at various
cloud nodes to secure our client requirement data files.
A novel approach for clone group mappingijseajournal
Clone group mapping has a very important significance in the evolution of code clone. The topic modeling
techniques were applied into code clone firstly and a new clone group mapping method was proposed. The
method is very effective for not only Type-1 and Type-2 clone but also Type-3 clone .By making full use of
the source text and structure information, topic modeling techniques transform the mapping problem of
high-dimensional code space into a low-dimensional topic space, the goal of clone group mapping was
indirectly reached by mapping clone group topics. Experiments on four open source software show that the
recall and precision are up to 0.99, thus the method can effectively and accurately reach the goal of clone
group mapping.
MULTIVIEW SOA : EXTENDING SOA USING A PRIVATE CLOUD COMPUTING AS SAAS AND DAASijseajournal
This work is based on two major areas, the Multiview Service Oriented Architecture and the combination between the computing cloud and MV-SOA. Thus, it is suggested to extend firstly the service oriented architecture (SOA) into an architecture called MV-SOA by adding two components, the Multiview service generator, whose role is to transform the classic service into Multiview service, and the data base, this component seeks to stock all of consumer service information. It is also suggested to combine the computing cloud and Multiview Service Oriented Architecture MVSOA. To reach such combination, the
MVSOA architecture was taken and we added to the client-side a private cloud in SaaS and DaaS.
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
Requirement analysis method of e commerce websites development for small-medi...ijseajournal
Along with the growth of the Internet, the trend shows that e-commerce have been growing significantly in
the last several years. This means business opportunities for small-medium enterprises (SMEs), which are
recognized as the backbone of the economy. SMEs may develop and run small to medium size of particular
e-commerce websites as the solution of specific business opportunities. Certainly, the websites should be
developed accordingly to support business success. In developing the websites, key elements of e-commerce
business model that are necessary to ensure the success should be resolved at the requirement stage of the
development. In this paper, we propose an enhancement of requirement analysis method found in
literatures such that it includes activities to resolve the key elements. The method has been applied in three
case studies based on Indonesia situations and we conclude that it is suitable to be adopted by SMEs.
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.
EMPIRICALLY VALIDATED SIMPLICITY EVALUATION MODEL FOR OBJECT ORIENTED SOFTWAREijseajournal
Software program developers need to go from beginning to ending and understand source code of the program and other software attributes. The software complexities and length of the program exceedingly affects many design level quality attributes, specifically Simplicity, Testability and software
Maintainability. Incomplete design of any software generally leads to misunderstanding and ambiguities
and therefore to gives faulty design and development results. This is mainly seeming and appears owing to
the absence of it’s an appropriate observation, design and development control. However, high level design
and program simplicity are very necessary and one of the vital attributes of the system development cycle.This research paper highlights the impact and significance of design level software simplicity in common and as a one of the most useful key factor or index of software quality assurance and testing. In this research work principally there are three major efforts are made. As a first contribution, a valuable
relationship between software design quality factor simplicity and related object oriented design
properties, this has been set up. In the second contribution, using design level corresponding metrics a
simplicity evaluation model for object oriented software is developed. Subsequently, the developed
simplicity model has been rationally authenticated by means of experimental data try-out.
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.
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.
MAKE THE QUALITY OF SOFTWARE PRODUCT IN THE VIEW OF POOR PRACTICES BY USING S...Journal For Research
In the Software Engineering, One of the most important factors to impact national and international business is quality of software and its assurance. Integral part of software development cycle is SQA, evaluation of software Quality product when compared to other industrial projects and it is very highly difficult. For developing, performance, speed, maintaining the quality, cost and efficiency of the software, SQA activities, principles and its methods are implemented in the early stages of the software engineering development phases. Where in this paper there is little visibility of lack of software Quality product in the view of poor practices. Hence we proposed a new system with best practices in software quality management to make the best quality product. This System works on Gain Better Visibility into Supplier Quality with Technology.
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
Regression Testing: Maintaining Software Integrity Over TimeUncodemy
In the ever-evolving world of software development, ensuring that your software maintains its integrity over time is paramount. As new features are added, bugs are fixed, and changes are implemented, there's always a risk of introducing new issues into your codebase.
Software testing is an activity which is aimed for evaluating quality of a program and also for improving it, by identifying defects and problems. Software testing strives for achieving its goal (both implicit and explicit) but it has certain limitations, still testing can be done more effectively if certain established principles are to be followed. In spite of having limitations, software testing continues to dominate other verification techniques like static analysis, model checking and proofs. So it is indispensable to understand the goals, principles and limitations of software testing so that the effectiveness of software testing could be maximized.
Testing Excellence_ Proven Methods for Delivering Reliable Software.pdfkhushnuma khan
As Agile testing integrates seamlessly into dynamic development cycles and user-centric approaches such as exploratory testing and feedback loops enhance user satisfaction, testing excellence emerges as the linchpin to success. The continuous learning mindset and adaptability to technological advancements ensure that testing remains not only dynamic but also an indispensable part of the software development process.
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
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.
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into
subsystems, functional modules and basis components. Finally, all tested components have to integrate to
be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development
model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is
an IID implementation concept which can effectively reduce software development risk. Web app with high
change characteristic is suitable to use agile development model as the development and maintenance
methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept
can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration
operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase
stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into subsystems, functional modules and basis components. Finally, all tested components have to integrate to be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is an IID implementation concept which can effectively reduce software development risk. Web app with high change characteristic is suitable to use agile development model as the development and maintenance methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
Quality assurance and testing _ H2kinfosys.pdfsharontims
Quality assurance and testing are integral components of the software development process, playing a pivotal role in ensuring the delivery of reliable, high-quality software products to end-users.
An empirical evaluation of impact of refactoring on internal and external mea...ijseajournal
Refactoring is the process of improving the design of existing code by changing its internal structure
without affecting its external behaviour, with the main aims of improving the quality of software product.
Therefore, there is a belief that refactoring improves quality factors such as understandability, flexibility,
and reusability. However, there is limited empirical evidence to support such assumptions.
The objective of this study is to validate/invalidate the claims that refactoring improves software quality.
The impact of selected refactoring techniques was assessed using both external and internal measures. Ten
refactoring techniques were evaluated through experiments to assess external measures: Resource
Utilization, Time Behaviour, Changeability and Analysability which are ISO external quality factors and
five internal measures: Maintainability Index, Cyclomatic Complexity, Depth of Inheritance, Class
Coupling and Lines of Code.
The result of external measures did not show any improvements in code quality after the refactoring
treatment. However, from internal measures, maintainability index indicated an improvement in code
quality of refactored code than non-refactored code and other internal measures did not indicate any
positive effect on refactored code.
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.
Similar to Flexibility a key factor to testability (20)
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
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.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
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
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
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.
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.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
Flexibility a key factor to testability
1. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
DOI : 10.5121/ijsea.2015.6108 89
FLEXIBILITY: A KEY FACTOR TO
TESTABILITY
Abdullah1
, Dr. M.H. Khan2
, Dr. Reena Srivastava3
1
Research Scholar, School of Computer Application, BBD University, Lucknow, India
2
Associate Professor, Department of C.S. E., I.E.T., Lucknow, India
3
Dean, School of Computer Application, BBD University, Lucknow, India
ABSTRACT
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.
KEYWORDS
Flexibility Measurement, Testability Estimation, Software Testability, Software Quality, Design Phase,
Object Oriented Design.
1. INTRODUCTION
Quality has become more important with our increasing dependence on software. In the last
decades the demand for quality in software products has been increasingly emphasized. Computer
industry has been delivering exponential improvement in cost, performance, but the problems
with software are not declining. Software still delivered is late, goes beyond budget and is full of
residual faults. As per the newest IBM report, 31% of the projects get cancelled prior to they are
completed, 53% over-run their cost estimates by an average of 189%, and for each 100 projects,
there are 94 restarts [1]. A key problem of software industry is its lack of ability to develop bug
free software. If software developers are asked to officially state that the developed software is
bug free, no software would have ever been released. Objective of software engineering is to
create high quality software in time and within budget. If a product is meeting its requirements,
we may say it is a superior quality product. The whole thing is measured with respect to
requirements and if it matches, product is a quality product.
2. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
90
Software has become vital to advancement in almost all areas of human endeavor. The ability of
programming only is no longer satisfactory to build large programs. There are major problems in
the cost, timeliness, maintenance and quality of many software products. Software engineering
has the goal of solving these problems by producing good quality, testable, maintainable
software, on time, inside budget [10]. According to software engineering principles, if the process
for development of any software is right, the chance of success of the software projects is greatly
increased [22]. To attain this objective, study has to focus in a disciplined manner on both the
quality of the product and on the process used to develop the product. However, due to increase in
price of testing and maintenance of software, objective is now changing to deliver quality
software. Software testing is an important and necessary activity of software development life
cycle for producing high quality software. Testing is very important and challenging task. The
time spent and effort required for software testing is very significant and consumes about 40% to
50% of the total cost for the entire development life cycle [3]. The most important problem during
testing is that before correcting a program (error/fault), the programmer must first trace and
understand it and it is possible with the help of its flexibility. For the same reason, traceability and
understandability is the two most important criteria of quality factor flexibility [4].
It is important that cost effective testing technique must be applied during development life cycle
and maintenance. The basic factor contributing to the development of these cost effective
techniques is the testability of program. Program testability is defined as a measure of the effort
required to satisfactorily test the program according to some well defined testing criteria [18]. To
a large perspective, testing depends on how difficult the error is to trace. Program testability and
error/fault traceability are two most important concepts: the more difficult an error is to trace, the
more difficult it is in order to be fixed. The more difficult it is to correct, the higher its testability
risk is [20]. The overall effort spent on testing not only depends on human factors, process issues,
test techniques, and test tools, but also on characteristics of the software development artifacts.
The degree to which a software artifact facilitates test tasks in a given test context is called
testability [5]. If we want to improve testability we have to trace those parts of a program that
lack testability. In view of the fact, it is clear that flexibility holds an important place as part of
testability and traceability is an important criterion of flexibility [4]. The tester can use testability
information to determine on what code to focus during testing [4]. Testability has been identified
as one of the major issues in the field of software engineering for producing high quality
software. It provides insights that are found to be very much valuable for the duration of software
design, coding, testing and quality assurance [12].
2. TESTABILITY FACTOR
Testability is a major quality factor for producing high quality software. Lack of testability
contributes to increased test and maintenance effort. The IEEE Standard Glossary defines
testability as the degree to which a system or component makes possible the establishment of test
criteria and performance of tests to conclude whether those criteria have been met [24]. ISO
defines it in a parallel way: an attributes of software that bear on the effort needed to validate the
software product [25]. The most well-known definition of testability is easiness of performing
testing [13, 14]. The insight provided by software testability is significant for the extent of
development life cycle, and quality promise. Design-for-testability is a very important issue in
software engineering.
Testability is one of the most important factors determining the time and effort required to test
software system [2]. A lower degree of testability outcome means increased test effort. It is
essential in the case of OO designs where control flows are normally not hierarchical; it is costly
3. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
91
to redesign a system during implementation or maintenance. An effort has been put forth to
recognize the key factors having positive impact on testability measurement at design phase. It
has been concluded that Flexibility and Modifiability are the two most important factor affecting
software testability measurement at design phase [8]. Taking into consideration the significance
of their involvement, in this paper we have proposed a model to measure software flexibility at
design phase.
3. FLEXIBILITY
In general, the objective of flexibility is to improve the quality of software systems within the
development life cycle. Flexibility is a key concern to guarantee stability between software
artifacts of succeeding phases of the development cycle. On the other hand only some works have
addressed the theme of flexibility into its design. Flexibility is a testability factor, which allows
the incorporation of changes in a design and gives an early focus to produce testable software
within time and budget. The reported experience suggests that by emphasizing flexibility as a
quality factor for testability measurement from the initial stage, the documentation will be clearer
and extra reliable [16]. Flexibility of software artifacts has been recognized as an important key
factor of testability for supporting various activities in the software system development process.
More purposely, flexibility information can be used to support the analysis of implications and
integration of changes that occurs in software systems. Flexibility enables system acceptance by
allowing users to better understand the system and contributes to clear and consistent system
documentation. Researchers and Practitioners advocated that flexibility aspect of software is
highly desirable and significant for developing quality software. Literature survey reveals that
there are various aspects of software, including flexibility factor that either directly or indirectly
influence testability of software [4], [6], [7]. Flexibility plays a central role for producing quality
software; it incorporates software quality objectives into the product and focuses on early error
detection and design flaws. Aforementioned facts reveal that flexibility is a key factor to
testability.
3.1. FLEXIBILITY QUALITY CRITERIA
Criteria are the characteristics which classify the quality factors. The criteria of the factors are the
attributes of the software product or software production process by which the factor can be
judged or characterized. The relationship between the flexibility and the quality criteria is listed
below in Table 1.
4. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
92
Table 1: Flexibility Quality Criteria
S.No. Factor Quality Criteria Mode
1
Flexibility
Structured
Augment ability
Criteria of Boehm quality
Mode
2 Generality
Independence
Self- documentation
Modularity
Software independence
Criteria of McCall quality
Mode
3 Complexity
Concision
Consistency
Generality
Modularity
Self-documentation
Expandability
Simplicity
Criteria of Ming-Chang
Lee Mode
There are following four major motivations for developing a list of criteria for flexibility:
1. Criteria provide a more absolute and real definition of factors.
2. Criteria common between factors help to show the interrelation among factors.
3. Criteria allow assessment and review metrics to be developed with greater easiness.
4. Criteria consent to identify that area of quality factors which may not be up to a predefined
acceptable standard.
4. OBJECT ORIENTED DESIGN PROPERTIES
Object oriented design is the latest approach and provides a set of methods, tools and procedures
for development of quality software. Object oriented design properties are real concepts that can
be directly judged by scrutinizing the internal and external organization, association, and
functionality of the design components, classes, attributes and methods. The feature of a design
has a very important impact on the quality of a software product; but due to the multiplicity and
complexity of design properties (e.g., coupling, encapsulation), their measurement and correlation
with external quality attributes (e.g., testability, portability) is tough. Object-oriented design
argues to continue essential software quality objectives like testability and reusability by
mechanisms similar to encapsulation of data, inheritance and dynamic binding. Object-oriented
programming is a fundamental technology that supports the above mentioned quality goals but
only knowing the language policy or concepts of the object-oriented technology is not sufficient
to produce good quality software [21]. A good quality object-oriented design wants design policy
and practices that must be known and used. Their contravention will finally have a strong impact
on the higher-level quality attributes. But as mentioned in advance, quality must be expressed in a
quantified manner [15].
The design properties of abstraction, encapsulation, coupling, cohesion, complexity and design
size are regularly used as being representative of design quality characteristics in cooperation
with procedural development as well as object oriented development. Messaging, composition,
5. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
93
inheritance, polymorphism and class hierarchies correspond to new design concepts which have
been introduced by the object oriented paradigm and are thus vital to the quality of an object
oriented design [17]. Table 2 summarizes the various design properties and their benefits.
Table 2: Object Oriented Design Properties and Their Benefits
Design
Property
Definition Benefits
Design Size A measure of the number of classes
used in a design.
Representative of design quality
characteristics of object oriented
development
Abstraction A measure of the generalization,
specialization view of the design.
Flexibility
Effectiveness
Functionality
Encapsulation Hides the implementation details. Reduces complexity
Flexibility
Understandability
Easier testing and maintenance
Coupling Defines the interdependency of an
object on other objects in a design.
Low Coupling Provides
Flexibility
Good understandability
Cohesion Assesses the relatedness of methods
and attributes in a class.
Flexibility
Inheritance Allows child classes inherit the
characteristics of existing parent
class.
Flexibility
Reusability
Eliminates redundant code
Polymorphism Ability to take more than one form.
(Extensively used in implementing
inheritance)
Provide abstraction
Extensibility
Reusability
Eliminates redundant code
Messaging A count of the number of public
methods that is available as services
to other classes. This is a measure of
the services that a class provides.
Functionality
Testability
Effectiveness
Reusability
5. OBJECT ORIENTED METRICS
Object orientation has several advantages such as lower development effort and lower
development time and better testability, flexibility and maintainability etc. It is based on objects
that constitute a system. It is more close to the real world. Object oriented approach supported
some very useful design principles like maintainability, testability, reusability and quality. Each
of the design properties identified in this paper signify an attribute or characteristics of a design
that is satisfactorily well defined to be objectively assessed by using one or more well defined
design metrics during the design stage. A review of existing design metrics [19] revealed that
there are numerous metrics that can be modified and used in the estimation of some design
properties, such as abstraction, inheritance and messaging. After a thorough review of some of the
existing object-oriented metrics those might be applied in the design phase of object-oriented
6. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
94
software systems, a set of metrics listed in [17] has been elected for measuring flexibility at
design phase.
6. RELATIONSHIP OF FLEXIBILITY WITH DESIGN PROPERTIES
Many experts tried to incorporate a variety of views as to how design properties may influence
design quality attributes and establish a strong relationship between object oriented design
properties and quality attribute flexibility. An extensive review of object oriented design and
development was conducted in order to develop a basis for relating design properties to quality
attribute flexibility [4]. It was observed that each of these properties have positive or negative
impact on the factors that influence testability of object oriented design. After an in-depth
evaluation of available literature on the topic [5] [9] [10] [11] [12] [15] [17], we established a
correlation among object oriented design properties and flexibility as shown in Figure 1.
Figure 1: Correlation among Object Oriented Design Properties and Flexibility
Table 3: Metrics Description
Metric Description
DAM Data Access Metrics
DCC Direct Class Coupling
CAM Cohesion Among Methods of Class
MFA Measure of Functional Abstraction
7. FLEXIBILITY MEASUREMENT MODEL
As discussed in the previous section, we have established the correlation among flexibility, object
oriented design properties and object oriented metrics as depicted in Figure 1. With this
correlation, this paper proposes a model for flexibility measurement. The proposed model has
been developed using multiple linear regression procedure. This regression procedure has been
widely accepted [8, 10, 26]. With the established correlation and linear regression we can say that
Flexibility= ß + A1 × Encapsulation + A2 × Coupling + A3 × Cohesion + A4 × Inheritance
Eq. (1)
We used SPSS to calculate the coefficients and the final flexibility model that we arrived at is
Flexibility= 1.051 + 2.320 × Encapsulation + 0.160 × Coupling - 2.283 × Cohesion + 11.572 ×
Inheritance Eq. (2)
7. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
95
Table 4: Coefficients
Coefficientsa
Model Unstandardized
Coefficients
Standardized
Coefficients
t Sig.
B Std. Error Beta
1 (Constant) 1.051 10.446 0.101 0.926
Encapsulation 2.320 10.433 0.275 0.222 0.838
Coupling 0.160 0.752 0.147 0.212 0.845
Cohesion -2.283 3.298 -0.846 -0.692 0.539
Inheritance 11.572 5.869 0.810 1.972 0.143
a. Dependent Variable: Flexibility
The Coefficients part of the output gives us the values that we need in order to write the
regression equation (1). The Standardized Beta Coefficients give a measure of the contribution of
each variable to the flexibility model. A big value designates that a unit change in this predictor
variable has a large effect on the criterion variable. The t and Sig (p) values give a rough
indication of the impact of each predictor variable – a big absolute T value and small p value
suggests that a predictor variable is having a large impact on the criterion variable. The
experimental evaluation of flexibility is very encouraging to obtain testability index of software
design for low cost testing and maintenance.
The data used for developing flexibility model is taken from [21] that have been collected through
large commercial object oriented systems. The index value of the expert’s rating of flexibility for
these systems is known and is termed as ‘Known Value’ in this research paper. For experimental
validation this ’Known Value’ will be compared with the calculated value; values will be
calculated with the help of the proposed model.
The descriptive statistics of the output gives the mean, standard deviation, and observation count
(N) for each of the dependent and independent variables and is shown in Table 5.
Table 5: Descriptive Statistics
Mean Std. Deviation N
Flexibility 7.1938 2.88881 8
Encapsulation 0.9013 0.34203 8
Coupling 3.0775 2.65602 8
Cohesion 0.7663 1.07103 8
Inheritance 0.4588 0.20223 8
The Model Summary table of the output is most useful when performing multiple regression.
Capital R is the multiple correlation coefficients that tell us how strongly the multiple
independent variables are related to the dependent variable. R square is very supportive as it gives
us the coefficient of determination. The Model Summary is shown in Table 6.
8. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
96
Table 6: Model Summary
Mode
l
R R Square Adjusted R
Square
Std. Error of the Estimate
1 0.903a
0.816 0.571 1.89306
a. Predictors: (Constant), Inheritance, Cohesion, Coupling, Encapsulation
8. Empirical Validation
The empirical validation is an essential stage of planned research. Empirical validation is the
correct approach and practice to justify the model acceptance. Keeping view of this fact, practical
validation of the Flexibility measurement model has been performed using sample tryouts. In
order to validate proposed flexibility measurement model the data has been taken from [21].
During experiments, flexibility value of the projects has been calculated using the developed
model, followed by the calculation of flexibility rating. These calculated ratings are then
compared with the known rating given by experts with the help of Charles Speraman’s
Coefficient of Correlation.
Table 7: Known and Calculated Flexibility Rating
Projects Known
Flexibility
Value
Known
Flexibility
Rating
Calculated
Flexibility
Value
Calculated
Flexibility
Rating
P1 8.22 11 8.36 11
P2 12.64 14 9.29 14
P3 12.94 15 9.13 13
P4 0.84 1 7.09 8
P5 1.5 2 6.53 7
P6 3.0 3 6.19 5
P7 7.2 9 4.79 3
P8 6.2 6 5.83 4
P9 4.2 4 10.79 15
P10 4.7 5 7.24 9
P11 8.2 10 8.67 12
P12 9.5 13 7.83 10
P13 8.5 12 3.56 2
P14 7.2 8 6.43 6
P15 6.7 7 1.40 1
9. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
97
Table 8: Computed Ranking, Actual Ranking and their Relation
Projects
Flexibility
Ranking
P
1
P
2
P
3
P
4
P
5
P
6
P
7
P
8
P
9
P1
0
P1
1
P1
2
P1
3
P1
4
P1
5
Computed
Ranking
1
1
14 13 8 7 5 3 4 15 9 12 10 2 6 1
Known
Ranking
1
1
14 15 1 2 3 9 6 4 5 10 13 12 8 7
∑d2
0 0 4 49 25 4 36 4 12
1
16 4 9 10
0
4 36
rs 1 1 .9
9
.9
1
.9
6
.9
9
.9
4
99 .7
8
.97 .99 .98 .82 .99 .94
rs >.6536
rs >.6536 means significant results.
Flexibility measurement model had statistically significant correlations with 15 of 15
projects.
As mentioned above, Charles Speraman’s Coefficient of Correlation (rank relation) rs was used
to check the significance of correlation between calculated values of flexibility using model and
it’s ‘Known Values’. Rank correlation is the process of determining the degree of correlation
between two variables. The ‘rs’ was calculated using the method given as under: Speraman’s
Coefficient of Correlation
‘d’ = difference between ‘Calculated values’ and ‘Known values’ of Flexibility.
n = number of projects (n=15) used in the experiment.
The correlation values between flexibility through model and known ranking are shown in table
above. Pairs of these values with correlation values rs above [±.6536] are checked in Table 8. The
correlations are up to standard with high degree of confidence, i.e. up to 99%. Therefore we can
conclude without any loss of generality that flexibility measurement model measures are really
reliable and significant.
9. Conclusion
Flexibility is one of the most significant factors for measuring testability of object oriented
software design. Study developed a flexibility measurement model that establishes the correlation
among flexibility, object oriented design properties and object oriented metrics. This paper
shows the significance of flexibility as a key factor of testability and its relationship with various
object oriented design properties. Flexibility measurement model in design phase has been
developed and validated theoretically as well as empirically using experimental try-out. For
experimental validation several large commercial projects has been used. The applied validation
on the flexibility model concludes that developed model is highly reliable, up to standard and
10. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
98
significant. Finally paper concludes there is a high corelation between flexibility and testability,
in addition statistical results shows that flexibility model is statistically very much significant and
reliable.
REFERENCES
[1] K.K. Aggarwal, Yogesh Singh. New Age International, Jan 1, 2005 - Software engineering.
[2] Nazir, Mohd, and Raees A. Khan. "Testability Estimation Model (TEMOOD)." Advances in
Computer Science and Information Technology. Computer Science and Information Technology.
Springer Berlin Heidelberg, 2012. 178-187.
[3] Jibitesh Mishra, Ashok Mohanty “Software Engineering. Page No.21, Pearson, 2012.
www.pearsoned.co.in/ jibiteshmishra
[4] Nazir, Mohd, and Raees A. Khan. "Software Design Testability Factors: A New Perspective."
Proceedings, 3rd National Conference: INDIACom-2009, Bharti Vidya Peeth Institute of Computer
Application and Management, New Delhi, Feb. 2009.
[5] Lee, Ming-Chang. "Software Quality Factors and Software Quality Metrics to Enhance Software
Quality Assurance." British Journal of Applied Science & Technology 4.21 (2014).
[6] Poston, Robin, Jignya Patel, and Jasbir Dhaliwal. "A software testing assessment to manage project
testability." (2012).
[7] S. Mouchawrab, L. C. Briand and Y. Labiche, “A Measurement Framework for Object-Oriented
Software Testability,” Information and Software Technology, Vol. 47, No. 1, 2005, pp. 979-997
[8] Jungmayr, Stefan. "Testability measurement and software dependencies." Proceedings of the 12th
International Workshop on Software Measurement. 2002.
[9] J Voas and Miller , “Improving the software development process using testability research”,
Proceedings of the 3rd international symposium on software Reliability Engineering , p. 114--121,
October, 1992, RTP, NC, Publisher: IEEE Computer Society.
[10] IEEE Press, “IEEE Standard Glossary of Software Engineering Technology,” ANSI/IEEE Standard
610.12-1990, 1990.
[11] ISO, “International standard ISO/IEC 9126. Information technology: Software product evaluation:
Quality characteristics and guidelines for their use.” 1991.
[12] Jianping, Fu, Liu Bin, and Lu Minyan. "Present and future of software testability analysis." 2010
International Conference on Computer Application and System Modeling (ICCASM 2010). Vol. 15.
2010.
[13] IEEE Standard Glossary of Software Engineering Terminology, ANSI/IEEE Standard 610.12- 1990,
IEEE Press, New York, 1990.
[14] Abdullah, Dr, Reena Srivastava, and M. H. Khan. "Testability Estimation of Object Oriented Design:
A Revisit." International Journal of Advanced Research in Computer and Communication
Engineering .Vol. 2, Issue 8, pages 3086-3090, August 2013
[15] Abdullah, Dr, Reena Srivastava, and M. H. Khan.”Modifiability: A Key Factor To Testability”,
International Journal of Advanced Information Science and Technology, Vol.26, No.26, Pages 62-71
June 2014.
[16] Antoniol, Giulio, et al. "Design‐code flexibility for object‐oriented systems." Annals of Software
Engineering 9.1-2 (2000): 35-58.
[17] J. Gao, S. Ming-Chih, “A Component Testability Model for Verification and Measurement”, In
Proceedings of the 29th Annual International Computer Software and Applications Conference, pages
211–218. IEEE Computer Society (2005).
[18] G. Jimenez, S. Taj, and J. Weaver, “Design for Testability” in the Proceedings of the 9th Annual
NCIIA Conference, 2005.
[19] R. V. Binder, “Design for Testability in Object-Oriented Systems,” Communications of the ACM,
Vol. 37, No. 9, 1994, pp. 87-101
[20] Marinescu, Radu, and Daniel Ratiu. "Quantifying the quality of object-oriented design: The factor-
strategy model." Reverse Engineering, 2004. Proceedings. 11th Working Conference on. IEEE, 2004.
[21] Bansiya, Jagdish, and Carl G. Davis. "A hierarchical model for object-oriented design quality
assessment." Software Engineering, IEEE Transactions on 28.1 (2002): 4-17.
11. International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015
99
[22] M. Bruntink and A. V. Deursen, “Predicting Class Testability Using Object-Oriented Metrics,”
Proceedings of IEEE International Workshop on Source Code Analysis and Manipulation, Chicago,
15-16 September 2004, pp. 136-145.
[23] ISO 9001:2005, Quality management system Fundamentals and vocabulary; 2005.
[24] Mulo, E. "Design for Testability in Software Systems." Master's Thesis (2007).
[25] Gupta, S. P., and M. P. Gupta. Business statistics. Sultan Chand & Sons, 1983.
[26] Abdullah, Dr, Reena Srivastava, and M. H. Khan. "Testability Measurement Framework: Design
Phase Perspective.”, International Journal of Advanced Research in Computer and Communication
Engineering Vol. 3, Issue 11, Pages 8573-8576 November 2014.
Authors
Abdullah received the MCA degree from Uttar Pradesh Technical University, Lucknow, in
2006. He is currently working as an Associate Professor, in the Department of Computer
Application, at Institute of Environment and Management, Lucknow. His research interests
Include Software testability, Software Quality Estimation. He has written various books and
study materials for (North Orissa University) Orissa, (Suresh Gyan Vihar University, Jaipur) Rajasthan,
(Bharati Vidyapeeth University, Pune) Maharashtra, NAAC Re-Accredited “A" Grade University.
Dr. Reena Srivastava is currently working as Dean, School of Computer Applications at
BBD University, Lucknow. She received her Ph.D. degree from MNNIT Allahabad, India.
Her research area includes Multi-Relational Classification, Privacy Preserving Data Mining
and Software Engineering.
Dr. M. H. Khan, Associate Professor, Department of Computer Science and Engineering at
IET Lucknow UP. He obtained his MCA degree from Aligarh Muslim University (A Central
University) in 1989. Later he did his PhD from Lucknow University. He has around 25 years
rich teaching experience at UG and PG level. His area of research is Software Engineering. Dr.
Khan published numerous articles, several papers in the National and International Journals and conference
proceedings.