2. What is fuzzy logic ?
Crisp Statement.
Fuzzy Statement
CHAPTER 1 INTRODUCTION
How can we represent that expert knowledge that uses
indefinite character or meaning and words having more than
one meaning in a computer? With the same level of
understanding and intelligence as knowledgeable a human
being in that particular domain. A fuzzy system can produce
agreeable but definite output in response to incomplete,
multiple meaning words, distorted or inaccurate input. Fuzzy
logic is an idea that resembles human ideas. The approach of
Fuzzy Logic is to copy the way of decision making by humans
that can meet all the possibility between yes or no.
4. Software requirement
Software requirement is define as expectation of user from the software
based on the particular domain. Also its features and functionalities are
the goal of software on that domain.
Requirement prioritization
Due to increase in competition of globalization and attract people with
fast technological improvements industries demand quality with the
product. Means we need to make different decisions about the product
release such as milestones available resources, serious disagreement or
argument of stake holders, also we have to check the opportunity, risks,
product strategies and costs need for release and also for future release.
Usually all requirements are not full filled or implemented in the first
release. Hence we need to prioritize the all the user requirements so that
we can implement important requirement according to resources, dead
line, budget, and to meet the expectation of client regarding to quality.
5. AHP
The Analytical Hierarchy Process was introduced by
Thomas L. Saaty in 1980. In AHP candidates
requirements are compared pairwise in order to know
which requirement is more important. it is easy for
developer’s team to identify important and less
important requirements when there is a single stack
holder, but in case of multiple stack holder it is difficult
to priorities, because different stack holders have
different perception regarding to requirements.
6. 1.1 MOTIVATION
While studying and calculating AHP using pairwise
comparison matrix we found that it’s tough to calculate
priority of a requirement, also there are no any pre-defined
pattern that one can understand that the given priority to
requirements are correct or not.
After that we found our interest in AHP to introduce a pattern
on which requirements are priorities with their correct values.
7. 1.2 BACKGROUND
A. Numerical Assignment Technique (NAT)
In this technique requirements are assigned a symbol
representation according to their priority. There are multiple
variants in this technique. A straightforward approach of this
technique is introduced by Brackett, he suggested that the
requirements should be classified as mandatory, desirable, or
inessential. According to finer requirements are assigned a
number on a scale ranging from 1 to 5, where the numbers
represent:
Different method of prioritization
8. 1.2 BACKGROUND
B. Value Oriented prioritization (VAT)
This technique proved a framework to requirement engineers for
foundation for prioritizing and making decision about
requirements. The framework is use to identify the business core
values and relative relationships among the stakeholder, and their
prioritize requirements. Company executives take the core
business value and use a simple ordinal scale to evaluate them
according to their importance for organization.
9. 1.2 BACKGROUND
C. Cumulative Voting
This method is introduced by Leffingwell and Widrig. It is also
called 100-point method or Hundred-Dollar test. In this method
all stakeholders are given a constant amount of imaginary units,
to vote in the favor of most important requirement as per there
perception towards that requirement. In this way the amount of
money represents the priority of that requirement in relation
with other requirement. The points can be distributed in any way
that the stakeholder wants. Stakeholder is free to give all the
amount in favor of one requirement.
10. What is AHP ?
Analytical Hierarchy Process (AHP)
The Analytical Hierarchy Process was introduced by Thomas L.
Saaty in 1980. In AHP candidates requirements are compared
pairwise in order to know which requirement is more important.
In AHP, first of all requirements are identified then criteria are
identified in order to prioritize requirements against them. user
will assign importance on the scale which is from 1 to 9. Now
AHP changes the customer consideration to numeric values and
numeric values are assign to cross ponding requirement.
Consistency ratio is must exist in order to value of CR
(consistency ratio) not exceed 10%.
CHAPTER 2 WHAT AND WHY ?
11. Due to increase in competition of globalization and attract people
with fast technological improvements industries demand quality
with the product. Means we need to make different decisions
about the product release such as milestones available resources,
serious disagreement or argument of stake holders, also we have
to check the opportunity, risks, product strategies and costs need
for release and also for future release. Usually all requirements
are not full filled or implemented in the next release. Hence we
need to prioritize the all the user requirements so that we can
implement important requirement according to resources, dead
line, budget, and to meet the expectation of client regarding to
quality.
Why AHP?
12. it is easy for developer’s team to identify important and less
important requirements when there is a single stack holder, but in
case of multiple stack holder it is difficult to priorities, because
different stack holders have different perception regarding to
requirements. Requirements prioritization method helps to
remove ambiguities among multiple stack holders. Once we
prioritize our requirement we can easily assigned our resources to
requirement, which may decrease the cost of project (somehow).
13. AHP is good prioritization methods instead of other methods
when we have multiple stakeholder and their requirement.
14.
15. THANK YOU
• Md. Aouwsaf Nawaz
• Alamgir Sheikh
Diploma in computer engineering, Jamia Millia
Islamia, New Delhi.
Under the super vision
Mr. Mohd. Sadiq Idris
Assistant Professor and Section In-Charge of computer
engineering, University Polytechnic, JMI