Scribd
Upload
375 views

Guidelines::Selecting Classes From Relevant and Fuzzy Category

The document provides guidelines for selecting relevant classes and establishing a common vocabulary when developing a class model. It describes removing redundant, irrelevant, and adjective classes. Attribute classes should be used instead of classes only representing values. The document then applies these guidelines to the initial list of noun classes for a bank system, removing irrelevant classes, consolidating redundant names, and identifying the purpose of remaining classes to determine which should be included in the final class model.

Uploaded by

smassys
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
375 views

Guidelines::Selecting Classes From Relevant and Fuzzy Category

The document provides guidelines for selecting relevant classes and establishing a common vocabulary when developing a class model. It describes removing redundant, irrelevant, and adjective classes. Attribute classes should be used instead of classes only representing values. The document then applies these guidelines to the initial list of noun classes for a bank system, removing irrelevant classes, consolidating redundant names, and identifying the purpose of remaining classes to determine which should be included in the final class model.

Uploaded by

smassys
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Guidelines :Selecting classes from relevant and fuzzy category

Redundant classes
Avoid Choose more meaningful name and name used by user

Adjective classes
Adjective can suggest
Different kind of object Different use of same object Utterly irrelevant

eg: adult member and youth member

Attribute classes
Objects used only as value can be treated as attribute instead of classes

Irrelevant classes
Relevant class have statement of purpose. Irrelevant classes - have no statement of purpose

Initial list of noun classes : in vianet bank


Account Account balance Amount Approval process Atm card Atm machine Bank Bank client Card Cash Check Checking Checking account Client Clients account Currency Dollar Envelope Four digits Fund Invalid pin Message Money Password PIN Pin code Record Savings Savings account Step System Transaction transaction history

Removing irrelevant classes


Account Account balance Amount Approval process Atm card Atm machine Bank Bank client Card Cash Check Checking Checking account Client Clients account Currency Dollar Envelope Four digits Fund Invalid pin Message Money Password PIN Pin code Record Savings Savings account Step System Transaction transaction history
They donot belong to problem statement

Removing redundant classe and building common vocabulary


Account Account balance Amount Approval process Atm card Atm machine Bank Bank client Card Cash Check Checking Checking account Client Clients account Currency Dollar Envelope Four digits Fund Invalid pin Message Money Password PIN Pin code Record Savings Savings account Step System Transaction transaction history

Reviewing the classes containing adjectives


When class represented by noun behaves differently when adjective is applied to it, then separate class has to be created In this ex no such classes

Reviewing possible attributes


Account Account balance Amount Approval process Atm card Atm machine Bank Bank client Card Cash Check Checking Checking account Client Clients account Currency Dollar Envelope Four digits Fund Invalid pin Message Money Password PIN Pin code Record Savings Savings account Step System Transaction transaction history

Reviewing the class purpose


Include classes with
Purpose Clear definition Necessary in achieving system goal

Eliminate classes with no purpose Ex: Candidate class with purpose are
ATM machine class ATM card class Bankclient class Bank class Account class Checking account class Saving account class Transaction class

Common class pattern approach


Based on knowledge base of the common classes , proposed by researchers like shlaer and mellor Patterns for finding class and object
Concept class
Particular idea or understanding
Ex: performance

Event class
Are points in time tat must be recorded Ex : account, request, order

Organization class
Collection of people, resources, facilities or groups to which the user belongs Ex : account dept,bank

People class
Represents different roles user plays in interacting with the system. Ex : bank client

Places class
Physical location that the system must keep inform about Ex :

Tangible things and devices


Includes physical objects or group of objects Ex : atmmachine

You might also like