As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
A Comparative Study of Software Requirement, Elicitation, Prioritization and ...IJERA Editor
The failure of many software systems are mainly due to the lack of the requirement engineering. Where
software requirement play a very vital role in the field of software engineering. The main task of the
requirement engineering are eliciting the requirements from the customer and to prioritize those requirements to
make decisions in the software design. Prioritization of the software requirement is very much useful in giving
priority within the set of requirements. Requirement prioritization is very much important when there are strict
constraints on schedule and the resources, then the software engineer must take some decisions on neglecting or
to give prioritization to some of the requirements that are to be added to the project which makes it successful.
This paper is the frame work of comparison of various techniques and to propose a most competent method
among them.
Contributors to Reduce Maintainability Cost at the Software Implementation PhaseWaqas Tariq
Software maintenance is important and difficult to measure. The cost of maintenance is the most ever during the phases of software development. One of the most critical processes in software development is the reduction of software maintainability cost based on the quality of source code during design step, however, a lack of quality models and measures can help asses the quality attributes of software maintainability process. Software maintainability suffers from a number of challenges such as lack source code understanding, quality of software code, and adherence to programming standards in maintenance. This work describes model based-factors to assess the software maintenance, explains the steps followed to obtain and validate them. Such a method can be used to eliminate the software maintenance cost. The research results will enhance the quality of the source code. It will increase software understandability, eliminate maintenance time, cost, and give confidence for software reusability.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
An Elite Model for COTS Component Selection ProcessIJEACS
Component-based software development (CBD) promises development of high-quality trustworthy software systems within specified budget and deadline. The selection of the most appropriate component based on specific requirement plays a vital role for high-quality software product. Multi-Agent software (MAS) engineering approach played a crucial role for selection of the most appropriate component based on a specific requirement in a distributed environment. In this paper, multi agent technique is used for component selection. A semi-automated solution to COTS component selection is proposed. It is evident from the result that (MAS) plays an essential role and is suitable for component selection in a distributed environment keeping in view of the system design and testing strategies.
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
A Comparative Study of Software Requirement, Elicitation, Prioritization and ...IJERA Editor
The failure of many software systems are mainly due to the lack of the requirement engineering. Where
software requirement play a very vital role in the field of software engineering. The main task of the
requirement engineering are eliciting the requirements from the customer and to prioritize those requirements to
make decisions in the software design. Prioritization of the software requirement is very much useful in giving
priority within the set of requirements. Requirement prioritization is very much important when there are strict
constraints on schedule and the resources, then the software engineer must take some decisions on neglecting or
to give prioritization to some of the requirements that are to be added to the project which makes it successful.
This paper is the frame work of comparison of various techniques and to propose a most competent method
among them.
Contributors to Reduce Maintainability Cost at the Software Implementation PhaseWaqas Tariq
Software maintenance is important and difficult to measure. The cost of maintenance is the most ever during the phases of software development. One of the most critical processes in software development is the reduction of software maintainability cost based on the quality of source code during design step, however, a lack of quality models and measures can help asses the quality attributes of software maintainability process. Software maintainability suffers from a number of challenges such as lack source code understanding, quality of software code, and adherence to programming standards in maintenance. This work describes model based-factors to assess the software maintenance, explains the steps followed to obtain and validate them. Such a method can be used to eliminate the software maintenance cost. The research results will enhance the quality of the source code. It will increase software understandability, eliminate maintenance time, cost, and give confidence for software reusability.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
An Elite Model for COTS Component Selection ProcessIJEACS
Component-based software development (CBD) promises development of high-quality trustworthy software systems within specified budget and deadline. The selection of the most appropriate component based on specific requirement plays a vital role for high-quality software product. Multi-Agent software (MAS) engineering approach played a crucial role for selection of the most appropriate component based on a specific requirement in a distributed environment. In this paper, multi agent technique is used for component selection. A semi-automated solution to COTS component selection is proposed. It is evident from the result that (MAS) plays an essential role and is suitable for component selection in a distributed environment keeping in view of the system design and testing strategies.
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
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.
AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITION...ijseajournal
This paper presents the result of software requirements practices survey among software practitioners, a study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the successful of a software development project, it becomes interesting to investigate the current software requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements engineering practices over the entire Kingdom of Saudi Arabia software industry.
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.
Evaluation of the software architecture styles from maintainability viewpointcsandit
In the process of software architecture design, different decisions are made that have systemwide
impact. An important decision of design stage is the selection of a suitable software
architecture style. Lack of investigation on the quantitative impact of architecture styles on
software quality attributes is the main problem in using such styles. So, the use of architecture
styles in designing is based on the intuition of software developers. The aim of this research is
to quantify the impacts of architecture styles on software maintainability. In this study,
architecture styles are evaluated based on coupling, complexity and cohesion metrics and
ranked by analytic hierarchy process from maintainability viewpoint. The main contribution of
this paper is quantification and ranking of software architecture styles from the perspective of
maintainability quality attribute at stage of architectural style selection.
A Review on Quality Assurance of Component- Based Software Systemiosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
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.
THE USABILITY METRICS FOR USER EXPERIENCE was innovatively created by Google engineers and it is ready for production in record time. The success of Google is to attributed the efficient search algorithm, and also to the underlying commodity hardware. As Google run number of application then Google’s goal became to build a vast storage network out of inexpensive commodity hardware. So Google create its own file system, named as THE USABILITY METRICS FOR USER EXPERIENCE that is GFS. THE USABILITY METRICS FOR USER EXPERIENCE is one of the largest file system in operation. Generally THE USABILITY METRICS FOR USER EXPERIENCE is a scalable distributed file system of large distributed data intensive apps. In the design phase of THE USABILITY METRICS FOR USER EXPERIENCE, in which the given stress includes component failures , files are huge and files are mutated by appending data. The entire file system is organized hierarchically in directories and identified by pathnames. The architecture comprises of multiple chunk servers, multiple clients and a single master. Files are divided into chunks, and that is the key design parameter. THE USABILITY METRICS FOR USER EXPERIENCE also uses leases and mutation order in their design to achieve atomicity and consistency. As of there fault tolerance, THE USABILITY METRICS FOR USER EXPERIENCE is highly available, replicas of chunk servers and master exists.
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.
This paper presents findings from the evaluation study carried out to review the UAE national ID card software. The paper consults the relevant literature to explain many of the concepts and frameworks explained herein. The findings of the evaluation work that was primarily based on the ISO 9126 standard for system quality measurement highlighted many practical areas that if taken into account is argued to more likely increase the success chances of similar system implementation projects.
Ijartes v2-i1-001Evaluation of Changeability Indicator in Component Based Sof...IJARTES
The maintaining of software system is a major
cost concern. The maintaining of a software system depends
on how the changes made to it. The maintainability of a system
depending on the folw of software, its design pattern and
CBSS. In Maintainability phase of a sotware system there are
4 parts, like analyzing, testing, stability, and changes made to
it. In some side areas, these systems emerged very rapidly.
There are many companies which purchase software instead
of developing it .These companies do not have any interst in
the testing of the system but wants to like smoothness in the
flow of the system during changes.
Changeability is one of the characteristics of maintainability.
Software changeability is associated with refactoring which
makes code simpler and easier to maintain (enable all
programmers to improve their code).Factors that affect
changeability include coupling between the modules, lack of
code comments, naming of functions and variables.
Basically,”changeabilty” is the ability of a product or software
to be able to change the structure of the program. It is the rate
the product allows the modification to its components.
In this paper changeability based cost estimation is done.
Initially we take four components; these components are
evaluated based on the coupling, cohesion and Interface
metrix. Next some changes are made to the existing
components and than again these components are evaluated.
Now, on the basis of these two evaluations some conclusion is
made for changeability cost.
A reliability estimation framework for OO design complexity perspective has been developed inthis paper. The proposed framework correlates the object oriented design constructs with complexity and also correlates complexity with reliability. No such framework has been available in the literature that estimates software reliability of OO design by taking complexity into consideration. The framework bridges the gap between object oriented design constructs, complexity and reliability. Framework measures and minimizes the complexity of software design at the early stage of software development life cycle leading to a reliable end product. Reliability and complexity estimation models have been proposed by following the proposed framework. Complexity estimation model has been developed which takes OO design constructs into consideration and proposed reliability estimation models take complexity in consideration for estimating reliability of OO design.
A Review of Agile Software Effort Estimation MethodsEditor IJCATR
Software cost estimation is an essential aspect of software project management and therefore the success or failure of a software
project depends on accuracy in estimating effort, time and cost. Software cost estimation is a scientific activity that requires knowledge of a
number of relevant attributes that will determine which estimation method to use in a given situation. Over the years various studies were done
to evaluate software effort estimation methods however due to introduction of new software development methods, the reviews have not
captured new software development methods. Agile software development method is one of the recent popular methods that were not taken
into account in previous cost estimation reviews. The main aim of this paper is to review existing software effort estimation methods
exhaustively by exploring estimation methods suitable for new software development methods.
A novel defect detection method for software requirements inspections IJECEIAES
The requirements form the basis for all software products. Apparently, the requirements are imprecisely stated when scattered between development teams. Therefore, software applications released with some bugs, missing functionalities, or loosely implemented requirements. In literature, a limited number of related works have been developed as a tool for software requirements inspections. This paper presents a methodology to verify that the system design fulfilled all functional requirements. The proposed approach contains three phases: requirements collection, facts collection, and matching algorithm. The feedback results provided enable analysist and developer to make a decision about the initial application release while taking on consideration missing requirements or over-designed requirements.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
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.
AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITION...ijseajournal
This paper presents the result of software requirements practices survey among software practitioners, a study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the successful of a software development project, it becomes interesting to investigate the current software requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements engineering practices over the entire Kingdom of Saudi Arabia software industry.
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.
Evaluation of the software architecture styles from maintainability viewpointcsandit
In the process of software architecture design, different decisions are made that have systemwide
impact. An important decision of design stage is the selection of a suitable software
architecture style. Lack of investigation on the quantitative impact of architecture styles on
software quality attributes is the main problem in using such styles. So, the use of architecture
styles in designing is based on the intuition of software developers. The aim of this research is
to quantify the impacts of architecture styles on software maintainability. In this study,
architecture styles are evaluated based on coupling, complexity and cohesion metrics and
ranked by analytic hierarchy process from maintainability viewpoint. The main contribution of
this paper is quantification and ranking of software architecture styles from the perspective of
maintainability quality attribute at stage of architectural style selection.
A Review on Quality Assurance of Component- Based Software Systemiosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
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.
THE USABILITY METRICS FOR USER EXPERIENCE was innovatively created by Google engineers and it is ready for production in record time. The success of Google is to attributed the efficient search algorithm, and also to the underlying commodity hardware. As Google run number of application then Google’s goal became to build a vast storage network out of inexpensive commodity hardware. So Google create its own file system, named as THE USABILITY METRICS FOR USER EXPERIENCE that is GFS. THE USABILITY METRICS FOR USER EXPERIENCE is one of the largest file system in operation. Generally THE USABILITY METRICS FOR USER EXPERIENCE is a scalable distributed file system of large distributed data intensive apps. In the design phase of THE USABILITY METRICS FOR USER EXPERIENCE, in which the given stress includes component failures , files are huge and files are mutated by appending data. The entire file system is organized hierarchically in directories and identified by pathnames. The architecture comprises of multiple chunk servers, multiple clients and a single master. Files are divided into chunks, and that is the key design parameter. THE USABILITY METRICS FOR USER EXPERIENCE also uses leases and mutation order in their design to achieve atomicity and consistency. As of there fault tolerance, THE USABILITY METRICS FOR USER EXPERIENCE is highly available, replicas of chunk servers and master exists.
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.
This paper presents findings from the evaluation study carried out to review the UAE national ID card software. The paper consults the relevant literature to explain many of the concepts and frameworks explained herein. The findings of the evaluation work that was primarily based on the ISO 9126 standard for system quality measurement highlighted many practical areas that if taken into account is argued to more likely increase the success chances of similar system implementation projects.
Ijartes v2-i1-001Evaluation of Changeability Indicator in Component Based Sof...IJARTES
The maintaining of software system is a major
cost concern. The maintaining of a software system depends
on how the changes made to it. The maintainability of a system
depending on the folw of software, its design pattern and
CBSS. In Maintainability phase of a sotware system there are
4 parts, like analyzing, testing, stability, and changes made to
it. In some side areas, these systems emerged very rapidly.
There are many companies which purchase software instead
of developing it .These companies do not have any interst in
the testing of the system but wants to like smoothness in the
flow of the system during changes.
Changeability is one of the characteristics of maintainability.
Software changeability is associated with refactoring which
makes code simpler and easier to maintain (enable all
programmers to improve their code).Factors that affect
changeability include coupling between the modules, lack of
code comments, naming of functions and variables.
Basically,”changeabilty” is the ability of a product or software
to be able to change the structure of the program. It is the rate
the product allows the modification to its components.
In this paper changeability based cost estimation is done.
Initially we take four components; these components are
evaluated based on the coupling, cohesion and Interface
metrix. Next some changes are made to the existing
components and than again these components are evaluated.
Now, on the basis of these two evaluations some conclusion is
made for changeability cost.
A reliability estimation framework for OO design complexity perspective has been developed inthis paper. The proposed framework correlates the object oriented design constructs with complexity and also correlates complexity with reliability. No such framework has been available in the literature that estimates software reliability of OO design by taking complexity into consideration. The framework bridges the gap between object oriented design constructs, complexity and reliability. Framework measures and minimizes the complexity of software design at the early stage of software development life cycle leading to a reliable end product. Reliability and complexity estimation models have been proposed by following the proposed framework. Complexity estimation model has been developed which takes OO design constructs into consideration and proposed reliability estimation models take complexity in consideration for estimating reliability of OO design.
A Review of Agile Software Effort Estimation MethodsEditor IJCATR
Software cost estimation is an essential aspect of software project management and therefore the success or failure of a software
project depends on accuracy in estimating effort, time and cost. Software cost estimation is a scientific activity that requires knowledge of a
number of relevant attributes that will determine which estimation method to use in a given situation. Over the years various studies were done
to evaluate software effort estimation methods however due to introduction of new software development methods, the reviews have not
captured new software development methods. Agile software development method is one of the recent popular methods that were not taken
into account in previous cost estimation reviews. The main aim of this paper is to review existing software effort estimation methods
exhaustively by exploring estimation methods suitable for new software development methods.
A novel defect detection method for software requirements inspections IJECEIAES
The requirements form the basis for all software products. Apparently, the requirements are imprecisely stated when scattered between development teams. Therefore, software applications released with some bugs, missing functionalities, or loosely implemented requirements. In literature, a limited number of related works have been developed as a tool for software requirements inspections. This paper presents a methodology to verify that the system design fulfilled all functional requirements. The proposed approach contains three phases: requirements collection, facts collection, and matching algorithm. The feedback results provided enable analysist and developer to make a decision about the initial application release while taking on consideration missing requirements or over-designed requirements.
Requirement engineering is a key ingredient for software development to be effective. Apart from the
traditional software requirement which is not much appropriate for new emerging software such as smart
handheld device based software. In many perspectives of requirement engineering, traditional and new
emerging software are not similar. Whereas requirement engineering of traditional software needs more
research, it is obvious that new emerging software needs methodically and in-depth research for improved
productivity, quality, risk management and validity. In particular, the result of this paper shows that how
effective requirement engineering can improve in project negotiation, project planning, managing feature
creep, testing, defect, rework and product quality. This paper also shows a new methodology which is
focused on users work process applicable for eliciting the requirement of traditional software and any new
type software of smart handheld device such as iPad. As an example, the paper shows how the methodology
will be applied as a software requirement of iPad-based software for play-group students.
Analytical Hierarchy Process Based Framework for Modelling Preferences and Priorities in
Requirements....................................................................................................................................1
R.Subha and S.Palaniswami
Unstructured Data Integration through Automata-Driven Information Extraction ...............................1
Maroun Abi Assaf, Kablan Barbar, Youakim Badr and Mahmoud Rammal
Wireless Solution for Water Saving In Agriculture Using Embedded System.........................................1
Venkata Narayana Eluri, K. Madhusudhana Rao and A. Srinag
Upcoming Trends of Virtual Experiments for Laboratories...................................................................1
Bhaskar Y. Kathane, Pradeep B. Dahikar and Satish J. Sharma
Negotiation Based Resource Allocation for Distributed Environments.................................................1
Krishnamoorthy M. and Senthil Murugan B.
Wireless Solution for Water Saving In Agriculture Using Embedded System ........................................1
Venkata Narayana Eluri, K. Madhusudhana Rao and A. Srinag
Digital Image Tamper Detection Techniques - A Comprehensive Study ...............................................1
Minati Mishra and Flt. Lt. Dr. M. C. Adhikary
A Multi-parametric based W-PAC Mechanism in Ad Hoc Network using IPv6 and IPv4 Address............1
S. Thirumurugan and Dr. E. George Dharma Prakash Raj
A New Online XML Document Clustering Based on XCLS++..................................................................1
Ahmad Khodayar E Qaramaleki and Ahmad Khodayar E Qaramaleki
Integrating goals after prioritization andijseajournal
Decision support system in Requirements engineering plays an important role in software development life
cycle. The relationship between functional and non-functional requirements often plays a crucial role in
resolving conflicts or arriving at decisions in requirements engineering phase. Goal-Oriented
Requirements Engineering (GORE) methods make a good attempt of addressing these aspects which are
helpful in decision support. We propose a GORE method - Integrating goals after prioritization and
evaluation (IGAPE). The method is semi-formal in nature thereby ensuring active stakeholder
participation. In this paper we elaborate the various steps of IGAPE method. The output of IGAPE is then
given as input to a decision support system which makes use of Analytic Hierarchy Process (AHP) and
Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS). Integration of IGAPE with
AHP and TOPSIS will clearly provide a rationale for various decisions which are arrived at during the
requirements engineering phase. The method is illustrated for an e-commerce application and is validated
by expert analysis approach.
Distributed Software Development Process, Initiatives and Key Factors: A Syst...zillesubhan
Geographically Distributed Software Development (GSD) process differs from Collocated Software Development (CSD) process in various technical aspects. It is empirically proven that renowned process improvement initiatives applicable to CSD are not very effective for GSD. The objective of this research is to review the existing literature (both academia and industrial) to identify initiatives and key factors which play key role in the improvement and maturity of a GSD process, to achieve this goal we planned a Systematic Literature Review (SLR) following a standard protocol. Three highly respected sources are selected to search for the relevant literature which resulted in a large number of TOIs (Title of Interest). An inter-author custom protocol is outlined and followed to shortlist most relevant articles for review. The data is extracted from this set of finally selected articles. We have performed both qualitative and quantitative analysis of the extracted data to obtain the results. The concluded results identify several initiatives and key factors involved in GSD and answer each research question posed by the SLR.
Abstract In Software Engineering (SE) process Requirement Engineering (RE) is considered as an important part in Software Development Life Cycle (SDLC). Requirement Prioritization is very useful for making good decisions about product plan but most of the times it is ignored. In many cases it is seem that the product fails to meet its core objectives because lack of proper prioritization. Increased emphasis on requirement prioritization and high changing requirements makes management of composite services time consuming and a complicated task. When a project has tight schedule, restricted resources and high customer expectations, it becomes necessary to deploy the most critical and important features as early as possible. The problem can be solved by prioritizing the requirements. In Software Engineering process numbers of requirement prioritization methods are already present. This paper shows the comparison of some of these techniques and based on its advantages and disadvantages a new technique ‘Adaptive Fuzzy Hierarchical Cumulative Voting’ is proposed. Fuzzy logic is used with adaptation mechanism, to target the situations where composite service behaviour can be deviated from customer expectations and to also deal with uncertainty and ambiguity. The proposed Adaptive Fuzzy Hierarchical Cumulative Voting includes the analysis of different self-adaptive properties such as self-heal, self-configure, self-optimize, self-protect and the addition to Fuzzy HCV, in order to increase the coverage of events that can occur at runtime. It may be useful to prioritize the requirements at run time. Keywords: Requirement prioritization, Fuzzy system, Fuzzy adaptation, HCV, Fuzzy HCV
Appendix AProof of effectiveness of some of the agile methods us.docxarmitageclaire49
Appendix A
Proof of effectiveness of some of the agile methods used to develop systems requirements
In all software development methodologies, the process of collecting, understanding and managing all requirements for a system is a crucial process in software development. Similar to all this other methods, agile methods are not exceptional. Most agile method handle requirements in order to implement them as much accurately as possible to satisfy all the customer demands. This is usually achieved by maintaining a continuous interaction with the customers to address their needs according to priority and functionalities. In this appendix, we shall be focusing on continuous process of improving the development process.
Some agile methods include the following
1. eXtreme Programming (XP) – it improves a software project in communication, simplicity, feedback and courage.
2. scrum- this is an agile, iterative and incremental method which takes care of all changes that may come across in the life-cycle of the project. Basically, it adds energy, focus and clarity to development teams. Its major aim is ot see the whole system being a successful product.
3. Dynamic system, development method (DSDM)
4. Adaptive software development (ASD)- this is a development process that is a product of rapid application development. It has four phases of communication and planning, analysis, testing & deployment and design and deployment.
5. the crystal family
Due to availability of these various methods, the potential adopters may experience a challenge of determining what to apply on its own and therefore there was need to define a document containing all the necessary values and common qualities to be used across all agile methods. This document is the Agile Manifesto and focuses mainly on human interactivity and processes management.
1. Individual and interaction over various processes and tasks. Usually the agile process will focus more on people and their interactivity but not on the structural processes and tools.
2. Working software and documentation. Main objective of the developers is actually delivering a functional code which will always add value to our users. Well documented code is always self-documented.
3. Responding to change over planning. Here developers are required to respond very fast to the requirements variations. Time used in planning is minimal compared to what our users actually requires.
4. Customer collaboration over contracts. The mutual relationship of the developers and susers of our system is monitored and regulated through engaging the customer in the development process.
The figure below shows the steps in agile methodologies which focus on an iteration and adaptable change.
5.
Tools needed for requirement management in agile methods of system development.
1. The most popular tools in agile methods include paper, pencil a drawing pin board. If we consider eXtreme programming requirements are obtained from user stories which ar.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
With the massive growth of the organizations files, the needs for archiving system become a must. A lot of time is consumed in collecting requirements from the organization to build an archiving system. Sometimes the system does not meet the organization needs. This paper proposes a domain-based requirement engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed during analyzing and designing the archiving systems decreased significantly. The proposed methodology also reduces the system errors that may happen at the early stages of the development of the system.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
With the massive growth of the organizations files, the needs for archiving system become a must. A lot of
time is consumed in collecting requirements from the organization to build an archiving system. Sometimes
the system does not meet the organization needs. This paper proposes a domain-based requirement
engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and
SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed
during analyzing and designing the archiving systems decreased significantly. The proposed methodology
also reduces the system errors that may happen at the early stages of the development of the system.
Working software measures the progress. Basically, Agile method involves interleaving the specification, implementation, design and testing. Series of versions are developed with the involvement of and evaluation by the stake holders in each version. Agile methods aim at reducing the software process overheads (like documentation) and concentrate more on code rather than the design. Customer involvement, incremental delivery, freedom of developers to evolve new working methods, change management, and last but not the least simplicity is the basic essence of Agile development. Agile methodologies are well suited for small as well as medium sized projects.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
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
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
Changeability has a direct relation to software maintainability and has a major role in providing high quality maintainable and trustworthy software. The concept of Changeability is a major factor when we design and develop software and its constituents. Developing programs and its constituent components with good changeability continually improves and simplifies test operations and maintenance during and after implementation. It encourages and supports improvement in software quality at design stage in the development of software. The research here highlights the importance of changeability broadly and also as an important aspect of software quality.
In this paper a correlation between the major attributes of object oriented design and changeability has been ascertained. A changeability evaluation model using multiple linear regression has been proposed for object oriented design. The validation of the proposed changeability evaluation model is made known by means of experimental tests and the results show that the model is highly significant.
Insights on Research Techniques towards Cost Estimation in Software Design IJECEIAES
Software cost estimation is of the most challenging task in project management in order to ensuring smoother development operation and target achievement. There has been evolution of various standards tools and techniques for cost estimation practiced in the industry at present times. However, it was never investigated about the overall picturization of effectiveness of such techniques till date. This paper initiates its contribution by presenting taxonomies of conventional cost-estimation techniques and then investigates the research trends towards frequently addressed problems in it. The paper also reviews the existing techniques in well-structured manner in order to highlight the problems addressed, techniques used, advantages associated and limitation explored from literatures. Finally, we also brief the explored open research issues as an added contribution to this manuscript.
ENHANCING ENGLISH WRITING SKILLS THROUGH INTERNET-PLUS TOOLS IN THE PERSPECTI...ijfcstjournal
This investigation delves into incorporating a hybridized memetic strategy within the framework of English
composition pedagogy, leveraging Internet Plus resources. The study aims to provide an in-depth analysis
of how this method influences students’ writing competence, their perceptions of writing, and their
enthusiasm for English acquisition. Employing an explanatory research design that combines qualitative
and quantitative methods, the study collects data through surveys, interviews, and observations of students’
writing performance before and after the intervention. Findings demonstrate a beneficial impact of
integrating the memetic approach alongside Internet Plus tools on the writing aptitude of English as a
Foreign Language (EFL) learners. Students reported increased engagement with writing, attributing it to
the use of Internet plus tools. They also expressed that the memetic approach facilitated a deeper
understanding of cultural and social contexts in writing. Furthermore, the findings highlight a significant
improvement in students’ writing skills following the intervention. This study provides significant insights
into the practical implementation of the memetic approach within English writing education, highlighting
the beneficial contribution of Internet Plus tools in enriching students' learning journeys.
A SURVEY TO REAL-TIME MESSAGE-ROUTING NETWORK SYSTEM WITH KLA MODELLINGijfcstjournal
Messages routing over a network is one of the most fundamental concept in communication which requires
simultaneous transmission of messages from a source to a destination. In terms of Real-Time Routing, it
refers to the addition of a timing constraint in which messages should be received within a specified time
delay. This study involves Scheduling, Algorithm Design and Graph Theory which are essential parts of
the Computer Science (CS) discipline. Our goal is to investigate an innovative and efficient way to present
these concepts in the context of CS Education. In this paper, we will explore the fundamental modelling of
routing real-time messages on networks. We study whether it is possible to have an optimal on-line
algorithm for the Arbitrary Directed Graph network topology. In addition, we will examine the message
routing’s algorithmic complexity by breaking down the complex mathematical proofs into concrete, visual
examples. Next, we explore the Unidirectional Ring topology in finding the transmission’s
“makespan”.Lastly, we propose the same network modelling through the technique of Kinesthetic Learning
Activity (KLA). We will analyse the data collected and present the results in a case study to evaluate the
effectiveness of the KLA approach compared to the traditional teaching method.
A COMPARATIVE ANALYSIS ON SOFTWARE ARCHITECTURE STYLESijfcstjournal
Software architecture is the structural solution that achieves the overall technical and operational
requirements for software developments. Software engineers applied software architectures for their
software system developments; however, they worry the basic benchmarks in order to select software
architecture styles, possible components, integration methods (connectors) and the exact application of
each style.
The objective of this research work was a comparative analysis of software architecture styles by its
weakness and benefits in order to select by the programmer during their design time. Finally, in this study,
the researcher has been identified architectural styles, weakness, and Strength and application areas with
its component, connector and Interface for the selected architectural styles.
SYSTEM ANALYSIS AND DESIGN FOR A BUSINESS DEVELOPMENT MANAGEMENT SYSTEM BASED...ijfcstjournal
A design of a sales system for professional services requires a comprehensive understanding of the
dynamics of sale cycles and how key knowledge for completing sales is managed. This research describes
a design model of a business development (sales) system for professional service firms based on the Saudi
Arabian commercial market, which takes into account the new advances in technology while preserving
unique or cultural practices that are an important part of the Saudi Arabian commercial market. The
design model has combined a number of key technologies, such as cloud computing and mobility, as an
integral part of the proposed system. An adaptive development process has also been used in implementing
the proposed design model.
AN ALGORITHM FOR SOLVING LINEAR OPTIMIZATION PROBLEMS SUBJECTED TO THE INTERS...ijfcstjournal
Frank t-norms are parametric family of continuous Archimedean t-norms whose members are also strict
functions. Very often, this family of t-norms is also called the family of fundamental t-norms because of the
role it plays in several applications. In this paper, optimization of a linear objective function with fuzzy
relational inequality constraints is investigated. The feasible region is formed as the intersection of two
inequality fuzzy systems defined by frank family of t-norms is considered as fuzzy composition. First, the
resolution of the feasible solutions set is studied where the two fuzzy inequality systems are defined with
max-Frank composition. Second, some related basic and theoretical properties are derived. Then, a
necessary and sufficient condition and three other necessary conditions are presented to conceptualize the
feasibility of the problem. Subsequently, it is shown that a lower bound is always attainable for the optimal
objective value. Also, it is proved that the optimal solution of the problem is always resulted from the
unique maximum solution and a minimal solution of the feasible region. Finally, an algorithm is presented
to solve the problem and an example is described to illustrate the algorithm. Additionally, a method is
proposed to generate random feasible max-Frank fuzzy relational inequalities. By this method, we can
easily generate a feasible test problem and employ our algorithm to it.
LBRP: A RESILIENT ENERGY HARVESTING NOISE AWARE ROUTING PROTOCOL FOR UNDER WA...ijfcstjournal
Underwater detector network is one amongst the foremost difficult and fascinating analysis arenas that
open the door of pleasing plenty of researchers during this field of study. In several under water based
sensor applications, nodes are square measured and through this the energy is affected. Thus, the mobility
of each sensor nodes are measured through the water atmosphere from the water flow for sensor based
protocol formations. Researchers have developed many routing protocols. However, those lost their charm
with the time. This can be the demand of the age to supply associate degree upon energy-efficient and
ascendable strong routing protocol for under water actuator networks. During this work, the authors tend
to propose a customary routing protocol named level primarily based routing protocol (LBRP), reaching to
offer strong, ascendable and energy economical routing. LBRP conjointly guarantees the most effective use
of total energy consumption and ensures packet transmission which redirects as an additional reliability in
compare to different routing protocols. In this work, the authors have used the level of forwarding node,
residual energy and distance from the forwarding node to the causing node as a proof in multicasting
technique comparisons. Throughout this work, the authors have got a recognition result concerning about
86.35% on the average in node multicasting performances. Simulation has been experienced each in a
wheezy and quiet atmosphere which represents the endorsement of higher performance for the planned
protocol.
STRUCTURAL DYNAMICS AND EVOLUTION OF CAPSULE ENDOSCOPY (PILL CAMERA) TECHNOLO...ijfcstjournal
This research paper examined and re-evaluates the technological innovation, theory, structural dynamics
and evolution of Pill Camera(Capsule Endoscopy) technology in redirecting the response manner of small
bowel (intestine) examination in human. The Pill Camera (Endoscopy Capsule) is made up of sealed
biocompatible material to withstand acid, enzymes and other antibody chemicals in the stomach is a
technology that helps the medical practitioners especially the general physicians and the
gastroenterologists to examine and re-examine the intestine for possible bleeding or infection. Before the
advent of the Pill camera (Endoscopy Capsule) the colonoscopy was the local method used but research
showed that some parts (bowel) of the intestine can’t be reach by mere traditional method hence the need
for Pill Camera. Countless number of deaths from stomach disease such as polyps, inflammatory bowel
(Crohn”s diseases), Cancers, Ulcer, anaemia and tumours of small intestines which ordinary would have
been detected by sophisticated technology like Pill Camera has become norm in the developing nations.
Nevertheless, not only will this paper examine and re-evaluate the Pill Camera Innovation, theory,
Structural dynamics and evolution it unravelled and aimed to create awareness for both medical
practitioners and the public.
AN OPTIMIZED HYBRID APPROACH FOR PATH FINDINGijfcstjournal
Path finding algorithm addresses problem of finding shortest path from source to destination avoiding
obstacles. There exist various search algorithms namely A*, Dijkstra's and ant colony optimization. Unlike
most path finding algorithms which require destination co-ordinates to compute path, the proposed
algorithm comprises of a new method which finds path using backtracking without requiring destination
co-ordinates. Moreover, in existing path finding algorithm, the number of iterations required to find path is
large. Hence, to overcome this, an algorithm is proposed which reduces number of iterations required to
traverse the path. The proposed algorithm is hybrid of backtracking and a new technique(modified 8-
neighbor approach). The proposed algorithm can become essential part in location based, network, gaming
applications. grid traversal, navigation, gaming applications, mobile robot and Artificial Intelligence.
EAGRO CROP MARKETING FOR FARMING COMMUNITYijfcstjournal
The Major Occupation in India is the Agriculture; the people involved in the Agriculture belong to the poor
class and category. The people of the farming community are unaware of the new techniques and Agromachines, which would direct the world to greater heights in the field of agriculture. Though the farmers
work hard, they are cheated by agents in today’s market. This serves as a opportunity to solve
all the problems that farmers face in the current world. The eAgro crop marketing will serve as a better
way for the farmers to sell their products within the country with some mediocre knowledge about using
the website. This would provide information to the farmers about current market rate of agro-products,
their sale history and profits earned in a sale. This site will also help the farmers to know about the market
information and to view agricultural schemes of the Government provided to farmers.
EDGE-TENACITY IN CYCLES AND COMPLETE GRAPHSijfcstjournal
It is well known that the tenacity is a proper measure for studying vulnerability and reliability in graphs.
Here, a modified edge-tenacity of a graph is introduced based on the classical definition of tenacity.
Properties and bounds for this measure are introduced; meanwhile edge-tenacity is calculated for cycle
graphs and also for complete graphs.
COMPARATIVE STUDY OF DIFFERENT ALGORITHMS TO SOLVE N QUEENS PROBLEMijfcstjournal
This Paper provides a brief description of the Genetic Algorithm (GA), the Simulated Annealing (SA)
Algorithm, the Backtracking (BT) Algorithm and the Brute Force (BF) Search Algorithm and attempts to
explain the way as how the Proposed Genetic Algorithm (GA), the Proposed Simulated Annealing (SA)
Algorithm using GA, the Backtracking (BT) Algorithm and the Brute Force (BF) Search Algorithm can be
employed in finding the best solution of N Queens Problem and also, makes a comparison between these
four algorithms. It is entirely a review based work. The four algorithms were written as well as
implemented. From the Results, it was found that, the Proposed Genetic Algorithm (GA) performed better
than the Proposed Simulated Annealing (SA) Algorithm using GA, the Backtracking (BT) Algorithm and
the Brute Force (BF) Search Algorithm and it also provided better fitness value (solution) than the
Proposed Simulated Annealing Algorithm (SA) using GA, the Backtracking (BT) Algorithm and the Brute
Force (BF) Search Algorithm, for different N values. Also, it was noticed that, the Proposed GA took more
time to provide result than the Proposed SA using GA.
PSTECEQL: A NOVEL EVENT QUERY LANGUAGE FOR VANET’S UNCERTAIN EVENT STREAMSijfcstjournal
In recent years, the complex event processing technology has been used to process the VANET’s temporal
and spatial event streams. However, we usually cannot get the accurate data because the device sensing
accuracy limitations of the system. We only can get the uncertain data from the complex and limited
environment of the VANET. Because the VANET’s event streams are consist of the uncertain data, so they
are also uncertain. How effective to express and process these uncertain event streams has become the core
issue for the VANET system. To solve this problem, we propose a novel complex event query language
PSTeCEQL (probabilistic spatio-temporal constraint event query language). Firstly, we give the definition
of the possible world model of VANET’s uncertain event streams. Secondly, we propose an event query
language PSTeCEQL and give the syntax and the operational semantics of the language. Finally, we
illustrate the validity of the PSTeCEQL by an example.
CLUSTBIGFIM-FREQUENT ITEMSET MINING OF BIG DATA USING PRE-PROCESSING BASED ON...ijfcstjournal
Now a day enormous amount of data is getting explored through Internet of Things (IoT) as technologies
are advancing and people uses these technologies in day to day activities, this data is termed as Big Data
having its characteristics and challenges. Frequent Itemset Mining algorithms are aimed to disclose
frequent itemsets from transactional database but as the dataset size increases, it cannot be handled by
traditional frequent itemset mining. MapReduce programming model solves the problem of large datasets
but it has large communication cost which reduces execution efficiency. This proposed new pre-processed
k-means technique applied on BigFIM algorithm. ClustBigFIM uses hybrid approach, clustering using kmeans algorithm to generate Clusters from huge datasets and Apriori and Eclat to mine frequent itemsets
from generated clusters using MapReduce programming model. Results shown that execution efficiency of
ClustBigFIM algorithm is increased by applying k-means clustering algorithm before BigFIM algorithm as
one of the pre-processing technique.
A MUTATION TESTING ANALYSIS AND REGRESSION TESTINGijfcstjournal
Software testing is a testing which conducted a test to provide information to client about the quality of the
product under test. Software testing can also provide an objective, independent view of the software to
allow the business to appreciate and understand the risks of software implementation. In this paper we
focused on two main software testing –mutation testing and mutation testing. Mutation testing is a
procedural testing method, i.e. we use the structure of the code to guide the test program, A mutation is a
little change in a program. Such changes are applied to model low level defects that obtain in the process
of coding systems. Ideally mutations should model low-level defect creation. Mutation testing is a process
of testing in which code is modified then mutated code is tested against test suites. The mutations used in
source code are planned to include in common programming errors. A good unit test typically detects the
program mutations and fails automatically. Mutation testing is used on many different platforms, including
Java, C++, C# and Ruby. Regression testing is a type of software testing that seeks to uncover
new software bugs, or regressions, in existing functional and non-functional areas of a system after
changes such as enhancements, patches or configuration changes, have been made to them. When defects
are found during testing, the defect got fixed and that part of the software started working as needed. But
there may be a case that the defects that fixed have introduced or uncovered a different defect in the
software. The way to detect these unexpected bugs and to fix them used regression testing. The main focus
of regression testing is to verify that changes in the software or program have not made any adverse side
effects and that the software still meets its need. Regression tests are done when there are any changes
made on software, because of modified functions.
GREEN WSN- OPTIMIZATION OF ENERGY USE THROUGH REDUCTION IN COMMUNICATION WORK...ijfcstjournal
Advances in micro fabrication and communication techniques have led to unimaginable proliferation of
WSN applications. Research is focussed on reduction of setup operational energy costs. Bulk of operational
energy costs are linked to communication activities of WSN. Any progress towards energy efficiency has a
potential of huge savings globally. Therefore, every energy efficient step is an endeavour to cut costs and
‘Go Green’. In this paper, we have proposed a framework to reduce communication workload through: Innetwork compression and multiple query synthesis at the base-station and modification of query syntax
through introduction of Static Variables. These approaches are general approaches which can be used in
any WSN irrespective of application.
A NEW MODEL FOR SOFTWARE COSTESTIMATION USING HARMONY SEARCHijfcstjournal
Accurate and realistic estimation is always considered to be a great challenge in software industry.
Software Cost Estimation (SCE) is the standard application used to manage software projects. Determining
the amount of estimation in the initial stages of the project depends on planning other activities of the
project. In fact, the estimation is confronted with a number of uncertainties and barriers’, yet assessing the
previous projects is essential to solve this problem. Several models have been developed for the analysis of
software projects. But the classical reference method is the COCOMO model, there are other methods
which are also applied such as Function Point (FP), Line of Code(LOC); meanwhile, the expert`s opinions
matter in this regard. In recent years, the growth and the combination of meta-heuristic algorithms with
high accuracy have brought about a great achievement in software engineering. Meta-heuristic algorithms
which can analyze data from multiple dimensions and identify the optimum solution between them are
analytical tools for the analysis of data. In this paper, we have used the Harmony Search (HS)algorithm for
SCE. The proposed model which is a collection of 60 standard projects from Dataset NASA60 has been
assessed.The experimental results show that HS algorithm is a good way for determining the weight
similarity measures factors of software effort, and reducing the error of MRE.
AGENT ENABLED MINING OF DISTRIBUTED PROTEIN DATA BANKSijfcstjournal
Mining biological data is an emergent area at the intersection between bioinformatics and data mining
(DM). The intelligent agent based model is a popular approach in constructing Distributed Data Mining
(DDM) systems to address scalable mining over large scale distributed data. The nature of associations
between different amino acids in proteins has also been a subject of great anxiety. There is a strong need to
develop new models and exploit and analyze the available distributed biological data sources. In this study,
we have designed and implemented a multi-agent system (MAS) called Agent enriched Quantitative
Association Rules Mining for Amino Acids in distributed Protein Data Banks (AeQARM-AAPDB). Such
globally strong association rules enhance understanding of protein composition and are desirable for
synthesis of artificial proteins. A real protein data bank is used to validate the system.
International Journal on Foundations of Computer Science & Technology (IJFCST)ijfcstjournal
International Journal on Foundations of Computer Science & Technology (IJFCST) is a Bi-monthly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Foundations of Computer Science & Technology. Over the last decade, there has been an explosion in the field of computer science to solve various problems from mathematics to engineering. This journal aims to provide a platform for exchanging ideas in new emerging trends that needs more focus and exposure and will attempt to publish proposals that strengthen our goals. Topics of interest include, but are not limited to the following:
Because the technology is used largely in the last decades; cybercrimes have become a significant
international issue as a result of the huge damage that it causes to the business and even to the ordinary
users of technology. The main aims of this paper is to shed light on digital crimes and gives overview about
what a person who is related to computer science has to know about this new type of crimes. The paper has
three sections: Introduction to Digital Crime which gives fundamental information about digital crimes,
Digital Crime Investigation which presents different investigation models and the third section is about
Cybercrime Law.
DISTRIBUTION OF MAXIMAL CLIQUE SIZE UNDER THE WATTS-STROGATZ MODEL OF EVOLUTI...ijfcstjournal
In this paper, we analyze the evolution of a small-world network and its subsequent transformation to a
random network using the idea of link rewiring under the well-known Watts-Strogatz model for complex
networks. Every link u-v in the regular network is considered for rewiring with a certain probability and if
chosen for rewiring, the link u-v is removed from the network and the node u is connected to a randomly
chosen node w (other than nodes u and v). Our objective in this paper is to analyze the distribution of the
maximal clique size per node by varying the probability of link rewiring and the degree per node (number
of links incident on a node) in the initial regular network. For a given probability of rewiring and initial
number of links per node, we observe the distribution of the maximal clique per node to follow a Poisson
distribution. We also observe the maximal clique size per node in the small-world network to be very close
to that of the average value and close to that of the maximal clique size in a regular network. There is no
appreciable decrease in the maximal clique size per node when the network transforms from a regular
network to a small-world network. On the other hand, when the network transforms from a small-world
network to a random network, the average maximal clique size value decreases significantly
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
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.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
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.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
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.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
An interactive approach to requirements prioritization using quality factors
1. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
An Interactive Approach to Requirements
Prioritization Using Quality Factors
Dinesh Singh1 and Aman Jatain2
1
2
Department of Computer Science, M.D.University, Rohtak
Department of Computer Science and Information Technology, ITM University,
Gurgaon
ABSTRACT
As the prevalence of software increases, so does the complexity and the number of requirements associated
to the software project. This presents a dilemma for the developers to clearly identify and prioritize the
most important requirements in order to deliver the project in given amount of resources and time. A
number of prioritization methods have been proposed which provide consistent results, but they are very
difficult and complex to implement in practical scenarios as well as lack proper structure to analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text based
story form and use case form. Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in this paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly analyzed
and ranked the requirements on the basis of quality attributes in the first level, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement value
associated with each user sequence in order to find out the final priority sequence.
KEYWORDS
Requirement, Prioritization, Requirements Engineering, Quality attributes, Desirability, Disagreement,
AHP, Genetic Algorithm.
1. INTRODUCTION
Software engineering decision support plays an important role in developing valuable software as
it is important to make right decisions for the development of right product. Requirement
engineering is one of the most important activity carried out in the requirement engineering stage
that supports this decision making process [1]. A requirement can be defined as a feature that the
system must have or a constraint that it must satisfy for it to be accepted by the client or
customer. Requirement Prioritization facilitates the requirement engineering process that helps in
making crucial decisions about requirements associated with the development process of a
software system [2]. Requirement Prioritization can be defined as the process of selecting the
most important requirements that are crucial for customer satisfaction in a software application as
the order in which requirements are implemented in a system affects the value of the software
delivered [15]. With the growing need of software in our day to day life, the complexity of the
software is increasing as well and also the number of requirements associated to the modern
software projects [10]. So, in order to overcome the increasing demands and the pressure on the
DOI:10.5121/ijfcst.2013.3603
25
2. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
software engineers and program managers to deliver the software to the customers on time and in
given budget, there is a huge need to identify the most important requirements and establish their
relative importance for implementation according to certain criteria [15]. The existing techniques
for requirement prioritization although provide consistent results but are difficult to use and
implement [8].Whereas some existing techniques that are easy to apply lack structure to analyze
the complex requirements. Moreover the available techniques lack user friendliness in the
prioritization process. So in order to overcome these issues or problems, a hybrid approach of two
available techniques is proposed. The proposed technique provides two mechanisms in which the
gathered requirements can be fed into the prioritization tool i.e. 1.Text Based Story Form where
the gathered requirements can be inputted by simply typing them in the text box provided or by
simply browse the text file containing the user’s requirements and, 2. Use Case Form where a
graphics editor is provided containing user-defined graphical use-case controls which follows
simple drag and drop mechanism. Once the gathered requirements are fed into the tool, the two
levels of prioritization takes place.
2. RELATED WORK
While delivering a market-driven software product development, there is a requirement overload
situation as there are a large number of requirements, even more than what can be dealt with.
Even in bespoke software development, the numbers of requirements are usually more than that
of the available resources to fulfill them. So, there are always questions like what requirements to
choose and prioritize as well as what features should be included in the product. This scenario is
when requirements prioritization comes in. There are a lot of techniques which have been
researched upon in order to prioritize requirements. Berander and Aurum [ ] have listed various
techniques like numerical assignment where the prioritization is based on grouping the
requirements into different categories, where three groups used in [R. Wiegers, Software
Requirements. Redmond: Microsoft Press, 1999] are high, medium and low.; ranking which
means the most important requirements are ranked first, and the less important requirements are
ranked last, on an ordinal scale, ; top-ten requirements; Analytical Hierarchy Process technique in
which the pairs of requirements are compared according to their importance and these
comparisons provide an understanding of each requirements share of the total value[2], and
Cumulative Voting or the 100$-method [8] in which the stakeholders participating in the
prioritization are given a number of imaginary units like 100 dollars, 1000 points, etc. which are
distributed among the requirements that are to be prioritized. A number of units that are assigned
to a requirement represent its priority. The results of the prioritization are represented on a ratio
scale that gives the information of how much a requirement is more/less important than other.
Various other researchers have worked in the field of requirements prioritization.
Carlos, Erica et al [1] proposed a Quality-Based Requirement Prioritization approach for
evaluating the quality of requirements in software projects based on multiple quality evaluation
criteria. Specifically, it presents a methodology that uses the concept of “Desirability Functions”
that acts as a unified measurement to represent how well requirements meet the quality attributes
and how important the quality attributes are for the project. These quality attributes are applied to
individual requirements based on the knowledge of the requirements analysts. The selected
quality attributes for the requirements form a metric for evaluating the importance of
requirements and based on the values calculated by the formula proposed in this paper,
requirements are ranked accordingly with relative importance for a particular software project. By
26
3. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
modifying the parameters of the desirability functions, quality and priority of requirements can be
evaluated. Overall, the approach presented proved to be a feasible technique for efficiently
evaluating the quality and priority of requirements in software projects and also can be extended
to include additional quality attributes.
Paolo , Angelo[2] have proposed an interactive genetic algorithm that exploits the user
knowledge to prioritize requirements. They performed a pair wise comparison on the information
useful to prioritize the requirements for a software system. They have applied the proposed
algorithm to a real case study, consisting of a non-trivial number of requirements, whereas AHP
is hardly applicable due to a system with large number of requirements. This approach scaled to
the size of the considered case study and produced a result that outperforms GA (i.e., a genetic
algorithm which optimizes satisfaction of the initial constraints, without gathering further
constraints from the user). Specifically, by eliciting between 50 and 100 pair wise comparisons
from the user it was possible to obtain a substantially better ordering of the prioritized
requirements.
Azeem Ahmad, Aamir Shahzad et al [3] considered various attributes that can affect requirements
prioritization while dealing with geographically distributed Stakeholders. They analyzed that
people related to a software product make their contribution to SDLC (Software Development
Life cycle) either by staying at a particular place or by being geographically distributed at
different locations. The term Globally Distributed Stakeholders refers to those stakeholders, who
are related to a project but are distributed in different locations all over the world. These
distributed locations can be within same area or in a continent. These distributions can also be
located all over the world where each stakeholder can have his/her own perception about the
software requirements as well as requirements expectations for a software project. This paper
provides a framework that can be used to identify those requirements that can play an essential
role in a product success during distributed development.
Joseph and Charlotte[] discussed various techniques for that are used for the process of
requirements elicitation. Requirements elicitation is an essential mechanism that tells the
developer what customers really need from the product that is to be delivered to them. Once the
requirements are gathered, the developers identify the properties that must be included in the
software in order to meet the customer requirements. This paper discussed various techniques of
gathering the knowledge from the user’s requirements along with their advantages and
limitations. The techniques discussed in this paper include Introspection that is the most common
source of information; but experiences indicate that it can be very misleading. Interviews and
questionnaires are other types of techniques that are widely used to gather user requirement data,
and sometimes protocol analysis is also used. All the techniques are good to use but this paper
suggests that techniques like interaction, conversation and discourse analyses are detailed and
more accurate to use. Ravi Prakash Verma, Alok Joshi et al [] proposed an algorithm using BTree for reduction in number of comparisons required for requirement prioritization. Large
software projects have large number of requirements and moreover these requirements keep on
changing. So, there is immense pressure on the developers to deliver the software on time as well
as manage the changing requirements. In order to resolve these issues, requirements are
prioritized relative to each other. Most of the requirement prioritization approaches use pair wise
comparison to achieve relative prioritization among the set of requirements but its disadvantage is
that it consumes a lot of resources because a large number of comparisons are if there are changes
in requirements. This paper proposed an algorithm using B-tree which effectively reduced the
27
4. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
number of comparisons required to prioritize the requirements. This method prioritized n
requirements in just log2t * log t(n) comparisons where prioritize the requirement, which when
compared with the complexity of AHP comparisons comes out to be less.
Muhammad Atif Iqbal , Athar Mohsin Zaidi and Dr. Saeed Murtaza presented a new model
based on AHP to prioritise requirements in a market driven software development where a large
number of requirements coming from different users, customers and competitors imposes a
burden on the requirement engineering process. So it is necessary for the product management to
analyze and select those requirements that are aligned with the overall business goals and dispose
of the other unimportant ones as soon as possible. This paper presents a MDRPM (Market Driven
Requirement Prioritization Model) based on Analytic Hierarchy Process in a sequential stepwise
manner which effectively produced the required results and reduced the number of comparisons
required to prioritize the requirements as compared to traditional AHP.
3 PROPOSED TECHNIQUE
The proposed technique can be considered as a hybrid approach to requirements prioritization
where the first level of prioritization takes place at developer level and the second level of
prioritization incorporates the role of user in order to add interactivity to the prioritization
process. Before the prioritization process begins, the developer needs to gather requirements from
the users. The proposed technique provides two mechanisms in which the gathered requirements
can be fed into the prioritization tool i.e. 1.Text Based Story Form where the gathered
requirements can be inputted by simply typing them in the text box provided or by simply browse
the text file containing the user’s requirements and, 2. Use Case Form where a graphics editor is
provided containing user-defined graphical use-case controls which follows simple drag and drop
mechanism. Once the gathered requirements are fed into the tool, the two levels of prioritization
takes place.
This work has been developed using C# (C-sharp.NET) technology with SQL Server 2008 as the
back-end database. The application executes on Visual Studio 2010 IDE. This application has
been developed on the principles of object-oriented techniques wherein we define our own
classes for performing any specific function, import some existing, pre-defined, inbuilt classes for
including their properties in the project. We have defined the architecture in such a manner so
that every class performs functions which are cleanly separated from the functions of the other
class. We have used the database interface layer provided by the .NET technology in the form of
LINQ2SQL. LINQ to SQL is a component of .NET Framework version 3.5 which provides a runtime infrastructure to manage relational data as objects. LINQ to SQL maps the data model of
a relational database to an object model expressed in the programming language of the developer
using .NET technology. When the application runs, LINQ to SQL translates into SQL the
language-integrated queries in the object model and sends them to the database for
execution. When the database returns the results, LINQ to SQL translates them back to objects
that you can work with in your own programming language. Developers using Visual
Studio typically use the Object Relational Designer, which provides a user interface for
implementing many of the features of LINQ to SQL. Moreover, a graphical editor has been built
up that enables the user to furnish the requirements in the form of use-cases. The graphical editor
contains user-defined controls which we have coded and compiled in separate C# files and then
integrated or mapped them within our project through addition of their references. The resources
28
5. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
used within the application have been kept in a separate folder in order to include them from their
designated paths. In this way, the applications consist of user-defined classes which inherit the
inbuilt classes and use their objects to call functions for performing specific operations. The
extraction of requirements from the use case uses the custom logic of distance between pixels of
actors, arrows and oval symbols with respect to their adjoining diagrams. The requirements are
parsed and extracted on the basis of this pixel distance between various symbols.
3.1 Requirement Gathering and Selection of Quality Attributes
Firstly, the requirements are gathered from the users associated with the software product in a two
very effective and user friendly manner. The users can submit their requirements in simple text
based story form or also can provide a text file (.txt file) that lists the requirements, and the
second way is graphical form where the user can exhibit their requirements by drawing use case
diagrams on a customized graphical editor through user control toolbox that is available to the
customer.
After the requirements are gathered from the users, the developer can select the valid set of
requirements out of the user supplied requirements.
Once the valid set if requirements are identified by the developer, he can perform the first level
prioritization of the requirements by applying certain quality attributes and sub attributes on the
valid requirements and calculate the desirability values associated with each requirement. The
quality attributes [1] used are:
1. Type: This attributes describes the type of requirement and thus have 3 sub attributes i.e.
Functional, Imposed, and Product.
2. Scope: This quality attribute deals with the impact of a particular requirement on the
overall system. So, the requirements that affect more number of (or all)subsystems are
determined to be of higher priority than
a. Requirements that affect minimal number of subsystems.
b. Scope attribute is defined with the following sub attributes: Subsystem 1 (S1),
Subsystem 2 (S2), and Subsystem 2 (S3)… Subsystem n (Sn).
3. Customer Satisfaction: Customer satisfaction plays an important quality attribute of a
system. The more the number of customers satisfied by a requirement, the greater is the
desirability of the requirement. So, the sub attributes for this quality attributes are
Customer 1 (C1), Customer 2 (C2), Customer 3 (C3)… Customer n (Cn).
4. Perceived Impact (PMF): This quality attribute is based on expert opinion. It considers all
the leads which can be software, hardware, systems and asks them that if the particular
requirement is perceived as a major functionality. Thus, the sub attributes of PMF are
Lead 1(L1), Lead 2(L2), Lead 3(L3)….Lead n (Ln).
5. Application-Specific: Depending on the type application domain, the attributes that are
important to a specific software application act as the sub attributes to this quality
attribute. The sub attributes taken this research are: Usability (U), Performance (P),
Safety (S), Security (S), Reliability, and Interoperability (I).
6. Penalties: Various types of penalties are associated with software requirements. This
attributes analyses if a particular requirement has any penalty associated to it. These
penalties are: Costly (C), Risky (R), and Complex (Cx).
29
6. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
One important point to note here is that for each of the requirement, at least one sub attribute
of the applied quality attributes must be selected. Figure 3.1 shows the shows the interaction
of the developer with the proposed tool. The developer acts as the actor who performs various
functions shown in the ellipses.
Figure 3.1: Developer Interaction with Proposed Tool
The first level of prioritization results in a requirement priority sequence based on the quality
attributes that are selected to be applied on the valid requirements as per the knowledge of the
requirement analyst or the software developer. The selected attributes are ticked and they act as
binary value input 1 and the non-selected ones are binary value input 0.
Then the second level of prioritization takes place where the developer gathers the opinions of
five distinct users about what should be the priority sequence as per their choices.
As per the gathered user’s priority sequence, the developer calculates the degree of disagreement
for each user elicited sequence with respect to the requirements prioritization sequence obtained
by the developer in the first level after applying quality attributes. After the disagreement factor
for each user is calculated, the developer selects that user elicited sequence as the final priority
sequence whose disagreement value comes out to be minimum. One important point here is
fixation of threshold value i.e. maximum value of the disagreement. If the disagreement value
exceeds the threshold value i.e. 5 in our case for any of the five users, crossover and mutation
operations are applied to the overall population which means all the five priority sequences till
the disagreement value becomes less than threshold value.
This makes the prioritization process more user friendly and is also easy to implement and
moreover this process resolves the case of ties that was occurring in [2] due to insufficient
knowledge about relationship between the requirements and thus eliminates the need of user
intervention which in itself was a conflicting issue.
5. RESULTS
The entire approach for the requirements prioritization can be presented in a series of sequential
steps that are mentioned below:
30
7. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
STEP 1
First step is requirement elicitation phase. In this phase, the developer interacts with the users to
whom the software product is to be delivered in order to gather the requirements from different
users.
STEP 2
Once the developer has obtained the user’s requirements, he needs to input them to the
requirements prioritization tool. This process is automated here. The developer has two ways to
feed in the gathered requirements:
a) Text Based Story Form
b) Use Case Form
The developer enters the home screen of the prioritization tool and enters the project name. The
developer can then select the mode in which the requirements are to be fed into the project i.e.
Text based story form or Use case form.
Fig.4.1.Home Screen
If the developer selects the Story form, he/she will be leaded to the next page where one of the
two options can be followed to input the requirements in text form:
1. Either the requirements can be typed in the text box provided or,
2. Developer can click on the browse text file button and can select any text file which
could have been provided by the users to whom the project is to be delivered. This text
file can contain the user requirements in text form separated by full stops (.).
31
8. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Fig.4.2.Developer types the requirements in textbox
Fig.4.2 shows the case when the developer types in the requirements into the text box. In case
when the developer has a text file containing the requirements as shown in Fig.4.3, he/she can
simply click on the browse text file button.
Fig.4.3.Text File containing user requirements
Once the developer clicks the browse text file button, a dialog box open up where the user can
browse through the system and select the requirement document text file from the appropriate
location.
Fig.4.4.Browsing the user requirements text file
After the text file is selected, and open button is clicked in the dialog box, the contents of the text
file is copied into the text box provided on the requirement elicitation page.
32
9. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Fig.4.5.Contents of text file copied to the text box
STEP 3
Once the gathered requirements are presented to the tool, the tool parses the text and extracts the
requirements by splitting and tokenization of text wherever a full-stop (.) occurs in the text-based
sentence. As the developer clicks on the get requirements button the requirements present in the
text box splits wherever the full stop (.) occurs in the text and are listed automatically on the same
page in the space provided below the text box.
Once the requirements are extracted, the developer or the requirement analyst possesses the
relevant knowledge to judge the valid set of requirements from the requirements that are obtained
from different users. Based on his/her knowledge the requirement analysts for the project can
select the valid requirements among all the extracted requirements by simply checking the check
box against each valid requirement. The selected valid requirements are then saved by clicking on
the save requirements button. When the save requirements in clicked, the finalized requirements
i.e. the set of developer selected valid requirements are inputted to the first level of the
requirements prioritization. For ex: in the Fig.4.6 below the developer selects REQ 1, REQ 3,
REQ 4, REQ 5, REQ 6, REQ 7, REQ 8 as the valid set of requirements leaving REQ 2. So, all the
selected requirements i.e. except REQ 2 will go through the two prioritization levels.
Fig.4.6.Selection of valid requirements
But if the developer selects the Use Case form as in Fig.4.7:
33
10. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Fig.4.7.Home screen when Use Case Form is selected
The developer will see a graphical editor where he can simply drag and drop the functionality
provided in the toolbox on right hand side and show the interactions or relationship between
various users and their requirements in graphical form.
Fig.4.8.Use Case graphics editor
After graphically drawing the relationship between the user and their requirements, developer
simply clicks the get requirement button and the requirement description along with the
concerned user name is displayed in the space provided below on the same page. There can be
multiple actors with the same name in order to incorporate the large no. of requirements of a
single user. The requirements are extracted on the basis of distance between pixels of actors,
arrows and oval symbols with respect to their adjoining diagrams. Once the developer gets the
extracted requirements from the use case diagram, he can simply select the valid set of
requirements among them using his own knowledge in a similar way as he did in case of Story
form elicitation. The developer after ticking the checkboxes in front of the valid requirements
clicks on the Save Requirements Button in order to process and prioritize the selected
requirements.
Fig.4.9.Selecting valid requirements in case of Use case Form of requirements elicitation
34
11. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
STEP 4: After the valid requirements are chosen by the developer, the first level of requirement
prioritisation takes place. The valid requirements are fed to the quality attributes [2] as shown in
fig.4.10.The developer then selects the quality attributes that must be applied to a particular
requirement based on the relevant knowledge. Sub attributes of each attributes are listed; the
developer can simply select the appropriate ones as per each requirement based on his
knowledge.
Fig.4.10.Applying quality attributes on the valid requirements
One important point to be noted here is that for each quality attribute for a particular requirement,
at least one sub attribute must be selected. Otherwise, an error message appear indicating which
quality attribute for which particular requirement is missing. This is shown in fig.4.10 above. If
the quality attributes for each requirement is furnished properly without missing any attribute, the
developer clicks on the Save Requirement attributes button and the disagreement value for each
requirement is calculated first for each attribute and then the overall desirability value. The
formula [1] used to calculate the desirability value for first five quality attributes is:
And for the last quality attribute (penalty), formula [1] used is:
35
12. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Fig.4.11.Calculation of Desirability value
CALCULATION OF DISERABILITY VALUE:
The value that the developer selects acts as binary input 1. The calculation desirability value for
REQ 1 is done in the following manner. For REQ1:
For QA1 as per values in Table.3.2 [1];
Y ij = 1/3 =.667 (the no. of sub attributes selected/ total no. of sub attributes)
After calculating this value, the formula [1] mentioned above is applied where:
L=0, T=100, U=100 and r=1.
This gives the desirability value of REQ 1 for QA1.Similarly the desirability value for each
quality attribute is calculated depending upon the sub attributes ticked by the developer and the
values in Table.3.2.After desirability values for each attribute is calculated, the overall
desirability is calculated as the geometric mean of desirability values of all the quality attributes
for a particular requirement. Once the desirability value for each requirement is calculated, they
are arranged in descending order to get the requirements priority sequence which is displayed in
the message box that prompts when save requirement
Fig.4.13.Taking user’s opinion and displaying the best priority sequence
If the minimum disagreement value is greater than the threshold value, then crossover and
mutation operation of the genetic algorithm is applied on the entire population i.e. the entire 6
user’s priority sequence in order to decrease the disagreement values.
36
13. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
MUTATION OPERATION: The mutation process [2] uses requirement-pair-swap operator,
which selects two requirements and swap their position in the mutated individual. The selection
of two requirements to be swapped is done randomly.
CROSSOVER OPERATION: The crossover Process [2] uses the cut-head/fill-in-tail and the
cut tail /fill-in-head operators, which selects a cut point randomly in the chromosome /sequence
of the first individual, keep either the head or the tail, and fill-in the tail (head) with the missing
requirements, ordered according to the order found in the second individual/ sequence to be
crossed over. These mutation and crossover operations are applied iteratively to the entire
population i.e. 6 users priority sequence till the minimum disagreement value becomes less than
the threshold value or the maximum limit till these operations can be applied is reached(
whichever comes first). This case is shown in fig.4.14 below, where the min value of
disagreement is 7
Fig.4.14.Disagreement value greater than threshold value
So, as the user clicks the get final prioritization button, he is prompted with the message box
saying “Mutation and Crossover will be applied.”
Fig.4.15.Mutation and Crossover message box appears
37
14. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Fig.4.16.After Mutation and Crossover is applied
After the mutation and crossover operations are applied, the revised disagreement values are
reflected in fig.4.16.But the minimum value now comes out to be 11 which is still greater than the
threshold value. So, when the get final Prioritization Sequence button is clicked same message is
prompted: “Mutation and Crossover will be applied.”
Fig.4.17.Mutation and Crossover message box appears again
So, mutation and crossover is applied again on the entire 6 sequences and the result is shown in
fig.4.18 where the minimum disagreement value now comes out to be 4 which is less than
threshold.
Fig.4.18.Mutation and Crossover applied
38
15. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
Now when Get final Prioritization Sequence button is clicked, the final sequence is displayed i.e.
the one with minimum disagreement value: R7, R5, R4, R1, R2, R6, R3.
Fig4.19.Final requirement priority Sequence
After the mutation and crossover are applied, again the disagreement values are calculated and
the final priority sequence is displayed i.e. the one having minimum disagreement value. Using
this technique does not require any human input whenever the ties occur as in [2] because the ties
were occurring in 2 due to incomplete relationship between the requirements, whereas in the
proposed approach the input to the second level of prioritization is a complete sequence in itself;
so whenever the pairs are formed there is a relationship between each requirement.
6. CONCLUSION AND FUTURE SCOPE
The order in which requirements are implemented in a system affects the value of the software
that is to be delivered. So, it is important to identify the important requirements and rank them as
per their significance. The proposed approach performs a two level requirement prioritization
where the first level is performed by the developer after gathering the requirements from different
users. The second level prioritization involves the opinion of the customers or the users about the
requirements associated with the particular product. This is an effective and easy to implement
technique that considers various quality attributes to prioritize requirements by measuring the
quality of each requirement and also is user friendly as their opinion is given importance while
deciding the final prioritization sequence. The approach is simple to use and implement and can
be extended to include additional attributes as well as the number of user’s whose opinions are
taken. Moreover, it can be further enhanced to work on private cloud environment where several
users are furnishing their requirements from several different locations. In future, it may also
include the principles of other software engineering techniques like the estimation of different
software metrics like Effort, Time, People, Cost etc apart from quality attributes.
REFERENCES
[1]
[2]
P. Berander and A. Aurum, Engineering and Managing Software Requirements. Berlin Germany:
Springer Verlag,2005, ch. Requirements Prioritisation, pp. 69–94.
Berntsson-Svensson R., Gorschek T., Regnell B., Torkar R., Shahrokni A., Feldt R.,“Quality
Requirements in Industrial Practice – an extended interview study at eleven companies”, IEEE
Transactions on Software Engineering, vol. 38 no. 4, pp. 923-935, 2012.
39
16. International Journal in Foundations of Computer Science & Technology (IJFCST), Vol. 3, No.6, November 2013
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]
[16]
[17]
[18]
[19]
[20]
[21]
Carlos E. Otero, Erica Dell, Abrar Qureshi, Luis D. Otero, “A Quality-Based Requirement
Prioritization Framework Using Binary Inputs“ 2010 Fourth Asia International Conference on
Mathematical/Analytical Modeling and Computer Simulation.
Paolo Tonella, Angelo Susi,Francis Palma, “Using Interactive GA for Requirements Prioritization”
2nd International Symposium on Search Based Software Engineering.
Azeem Ahmad, Aamir Shahzad, V. Kumar Padmanabhuni, Ali Mansoor, Sushma Joseph, Zaki
Arshad “Requirements Prioritization with Respect to Geographically Distributed Stakeholders” 2011
IEEE International Advance Computing Conference
Anil Jadhav, Rajendra Sonar “Analytic Hierarchy Process (AHP), Weighted Scoring Method (WSM),
and Hybrid Knowledge Based System (HKBS) for Software Selection: A Comparative Study”
Second International Conference on Emerging Trends in Engineering and Technology, ICETET-09
Muhammad Atif Iqbal, Athar Mohsin Zaidi, Dr. Saeed Murtaza “A New Requirement Prioritization
Model for Market Driven Products Using
Analytical Hierarchical Process” 2010 International
Conference on Data Storage and Data Engineering
Md. Rizwan Beg, Ravi Prakash Verma, Alok Joshi”Reduction in number of comparisons for
requirement prioritization using B- Tree” 2009 IEEE International Advance Computing Conference.
Martin S. Feather, Steven L. Cornford, and Kenneth A. Hicks, James D. Kiper, Tim Menzies, “A
Broad, Quantitative Model for Making Early Requirements Decisions” 2008 IEEE.
Md. Rizwan Beg, Qamar Abbas , Ravi Prakash Verma“An Approach for Requirement Prioritization
using B-Tree” 2008 IEEE.
Kevin Logue and Kevin McDaid “Handling Uncertainty in Agile Requirement Prioritization and
Scheduling Using Statistical Simulation” Agile 2008 Conference.
Steven K. Sherman “Algorithms for Timing Requirement Analysis and Generation” 2008 IEEE.
Nancy R. Mead “Requirements Prioritization Case Study Using AHP” 2008 Carnegie Mellon
University.
Goguen, J.A. and Linde, C.” Techniques for Requirements Elicitation” Proceedings IEEE
International Symposium on Requirements Engineering, IEEE CS Press, San Diego, CA, 1993.
Karlsson, J., Wohlin, C., &Regnell, B. (1998). An evaluation of methods for prioritizing software
requirements. Information and Software Technology, 39(14-15), 939-947.
T.L. Saaty, The Analytic Hierarchy Process, McGraw-Hill, Inc. (1980).
Ritu and Dr. Nasib Singh Gill,”A Comparison among Various Techniques to Prioritize the
Requirements”. IJCSMS International Journal of Computer Science & Management Studies, Vol. 12,
Issue 03, Sept 2012 ISSN (Online): 2231 –5268.
Andrea Herrmann, Maya Daneva,” Requirements Prioritization Based on Benefit and Cost Prediction:
An Agenda for Future Research”, 16th IEEE International Requirements Engineering Conference
2008.
http://en.wikipedia.org/wiki/Agile_software_development
Mikko Vestola,” A Comparison of Nine Basic Techniques for Requirements Prioritization”, Helsinki
University of Technology.
R.
Wiegers,
Software
Requirements.
Redmond:
Microsoft
Press,
1999
40