object-oriented analysis the noun phrase
approach it would be a very interesting
topic so let's let us discuss this one
with further detailing the developers
having less exposure with the
application domain can make use of these
three-stage process to extract candidate
classes so it is a very vital question
for the freshers for the developers who
are not having a good exposure on a
certain domain in the application in
which they the domain in which the
application is going to get developed
that how to get the classes at what are
the classes are to be there and what
will be their respective methods and
attributes are to be included in a
certain class so that's why this
candidate classes how to get this
candidate classes is a big questions for
certain developers so first one is that
so here we are having three stage
approach the first one concise problem
definition so define the product as
briefly and concisely as possible that
means we should define the software
product or the software problem whatever
it is the problem statement should be
very much concise and must be given
briefly and preferably in a single
statement if it is possible next one
informal strategy the constraints
specified informally must be taken into
account so what are the different
constraints we have mentioned informally
that should be taken into our account
formalize the strategy that is identify
the nouns in the informal strategy
exclude those that lie outside the
problem boundary so here we are
considering the nouns and those nouns
which are outside of the problem
boundary should be excluded of the
requirement gathering is added and
formalized to identify that candidate
classes if this conception is not
cleared up to this particular discussion
so let us proceed more the guidelines
for selecting tentative classes in the
given application are
such four nouns pronouns and noun
phrases in the use cases so that is the
search for nouns pronouns and noun
phrases in the use cases so what are the
use case use concern nothing but the
functional recommend in the software in
the system nouns and noun phrases become
the objects and attributes verbs and
phrases become the operations and
associations positive phrases indicate
that noun should be attribute rather
than the objects so these are the
respective herschel cell formalities you
should maintain that is a nouns and noun
phrases become the objects and
attributes attributes of the class
attributes of the object and then pause
and power phrases become the operations
and associations operations means
methods and associations and this
positive phrases indicate that noun
should be attributes rather than the
objects so some classes are either
implicit or taken from general knowledge
all classes must make sense in the
application domain and avert computed
implementation classes and delayed them
to the design stage so that means it
indicates that we should explain we
should gather all these classes all this
candidate classes in such a way that
there should not be any redundancy and
it should cover all the aspects of our
design carefully choose and define class
names this class names and class name
and nomenclature should be done very
precisely and carefully so that from the
name event we should get the idea of
what is the purpose of the class so this
is the way to have our methods how to
have our attributes in the class to have
our class names and the respective
association between classes the
candidate classes of noun phrase
approach can be divided into three
categories such as really
classes Fuzzy's classes that is the
classes that are not sure about and the
Idul event classes that means they can
be excluded and they can be deleted from
the system therefore finding the exact
list of required classes is iterative
and incremental process so it is
iterative means inclusion of this
classes will be iterative where we are
going to revise and we are going to
retune our problem statement again and
again so that we should read our problem
statement we should read our problem
definition again and again so that these
classes whether it should be treated as
a relevant class or say fuzzy class or
irrelevant class so they are to be
categorized in a suitable way so that we
are going to make our system ready with
the relevant classes only and those
classes should have a proper name so
that from the class name event that
nomenclature should be done in such
interesting way that from the class name
event you can get the purpose of the
class so in case of redundant classes
what you should do the classes which
express the some information same
information must be avoided use the same
words to define class that is being used
by the user of the system that means
whenever you are finding that some
classes are there which are having the
same kind of functionalities so those
classes are to be are to be eliminated
adjectives classes the classes which
behave differently when the object is
represented by the noun and bewbs
differently when the adjectives are
applied to it so they are known as the
adjectives classes so let me repeat the
definition once again for your better
understanding the classes which behave
differently when the object is
represented by the noun and behaves
differently when the adjectives applied
to it that means whenever we are having
this adjective classes so whenever it is
differently behaving when it will be
treated as a noun and BA
currently when the adjectives are
applied to it I think for the better
understanding will be going for the case
studies which are there in our in the
last portion of our tutorial we're
having multiple case studies where we
have discussed and there we have used
this noun phrase filtering and how to
get the classes out of them we have
discussed that one with a real-life case
study there
please watch those videos also to have a
grip over this concept attribute classes
means the noun phrase that is the client
status is not separate class but it is
an attribute of the client class so it
indicates that let us suppose that is
one noun phrase as an example we are
having this client status so against the
client status we cannot create in a
separate class we should not create in a
separate class it will be the attribute
of a class so that is known as the
attribute classes so here we are having
this adjective classes we're having this
redundant classes so we have defined the
definition of three classes we're having
this now going for the EDL event classes
the class that is not having any purpose
is known as irrelevant class and for
each candidate class the statement of
purpose must be clearly defined and if
it is not possible eliminate the
candidate class so that means for the
relevant classes that means which are
not very much linked to this with the
system some nouns you might be finding
in the problem statement which are not
very much related to the system so those
those particular classes should not be
formed because they are the irrelevant
classes weight classes the classes that
are out of scope within the boundaries
of the problem statement are known as
the weight classes so that means we are
having some nouns where this nouns are
not related with the problem and they
are outside of the boundaries of the of
the domain so that those classes are not
to be are not to be constructed because
they are known as the vague classes so
relevant classes were having we're
having fuzzy classes and we are having
EDD living classes so now let us go for
this diagram for the baited
understanding so problem statement which
will be consisting of set of
requirements first set of candy
classes are to be formed review
irrelevant classes and review redundant
classes and then review attributes and
then review adjectives so in this way we
are going to have the identifying the
classes using noun phrase approach so in
this diagram we have shown you that what
are the different steps for this non
phrase approach so now a simplified
steps non phrase approach can also be
also be shown using this diagram that is
a requirement statement so exact nouns
we are going to found find and then
tentative object classes and exact nouns
will produce the object classes from
this respective noun phrase approach so
in this particular session we have
discussed that how to form classes how
to get the methods in a classes how to
get the attributes in a classes and
water to be eliminated what are to be
combined and water to be treated as a
outside of the boundary of the domain on
which we are making our system ready so
they are not to be considered so in this
way we are going to get our primary
classes the respective attributes and
that respective methods and operations
so it is a very tricky one and obviously
going through the case study only you
can explain it further so please work
please watch all the case studies
whatever have been discussed in this
tutorial thanks for watching this video