Scribd
Upload
8K views

Noun Phrase Approach

The document describes a noun phrase approach for identifying classes in object-oriented analysis. It involves identifying nouns and noun phrases from use cases and requirements, categorizing them as relevant, fuzzy, or irrelevant classes, and selecting the final classes. Guidelines are provided such as choosing class names that make sense in the domain and avoiding implementation-specific classes. As an example, the document analyzes noun phrases from a bank ATM system and identifies the final classes as ATM machine, ATM card, Bank client, Bank, Account, Checking Account, Savings Account, and Transaction.

Uploaded by

Shabeer Ac
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
8K views

Noun Phrase Approach

The document describes a noun phrase approach for identifying classes in object-oriented analysis. It involves identifying nouns and noun phrases from use cases and requirements, categorizing them as relevant, fuzzy, or irrelevant classes, and selecting the final classes. Guidelines are provided such as choosing class names that make sense in the domain and avoiding implementation-specific classes. As an example, the document analyzes noun phrases from a bank ATM system and identifies the final classes as ATM machine, ATM card, Bank client, Bank, Account, Checking Account, Savings Account, and Transaction.

Uploaded by

Shabeer Ac
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

 

           Noun phrase approach:


Nouns in the textual description are considered to be classes and verbs to be methods of the
classes. All plurals are changed to singular, the nouns are listed and the list divided into relevant
classes, fuzzy classes and irrelevant class.
Look for the noun phrases through the use cases.

 Three categories:

 Relevant classes.
 Fuzzy classes.
 Irrelevant classes.

 Identifying tentative classes.

 Look for noun phrases and nouns in the use cases.


 Some classes are implicit or taken from general knowledge.
 All classes must make sense in the application domain.
 Carefully choose and define class names.

 Selecting classes from the relevant and fuzzy classes.

 Redundant classes.
 Adjective classes.
 Attribute classes.
 Irrelevant classes.

Guide lines for selecting classes in all application:

 Carefully choose and define class names.


 All classes must make sense in the application domain, avoid computer implementation
classes – defer there to the design stage.
 Look for nouns and noun-phrases in the use cases.
 Some classes are implicit or taken from general knowledge.

Example: Bank ATM system: Identifying classes by using noun phrase approach:
Initial list of Noun phrases candidate classes

o Account
o Account Balance
o Amount
o Approval process
o ATM card
o ATM machine
o Bank
o Bank client
o Card
o Cash
o Check
o Checking
o Checking Account
o Client
o Client’s Account
o Currency
o Dollar
o Envelope
o Four digits
o Fund
o Savings
o Savings Account
o Step
o System
o Transaction
o Transaction history
o Invalid PIN
o Message
o Money
o Password
o PIN
o Pin Code
o Record

            The following irrelevant classes are removed from the above list:

 Envelope  
 Four Digits
 Step

            Reviewing the Redundant classes and Building a common vocabulary:


            Client, Bank client                 à Bank client
            Account, Client’s Account    à Account
            PIN, PIN code                     à PIN
            Checking, Checking Accountà Checking Account
            Savings, Savings Account     à Savings Account
            Fund, Money                        à Fund
            ATM card, card                   à ATM card
            Reviewing the classes containing adjectives
                        In this example, we have no classes containing adjectives that we can eliminate.
            Reviewing the Possible Attribute
            Amount                à A value not a class
            Account Balance  à An attribute of the Account class
            Invalid PIN           à It is only a value, not class
            Password              à An attribute for Bank client class
            Transaction history à An attribute of transaction class
            PIN                       à An attribute of Bank client class
            Reviewing the class purpose
            The final candidate classes are:

o ATM machine class


o ATM card class
o Bank client
o Bank class
o Account class
o Checking Account class
o Savings Account class
o Transaction class

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy