Class design question
- From: "sundeep" <sundeeps@xxxxxxxxx>
- Date: 26 Apr 2006 03:03:02 -0700
Hi,
Let me first describe the requirement. I have to design a small system
that should be able to manage websites on a hosting environments. The
tasks that i need to do are
- CreateWebSIte
- DeleteWebSite
- ModifyWebSite
- ChangeIPAdress
Now, I have two options to design the Biz functionlity.
Option 1-
Create a class WebSite as following
Class WebSite
Attributes:
Name
CustomerId
PackageType
......
Functions
- CreateWebSite
- DeleteWebSite
- ModifyWebSite
- ChangeIPAdress
Option 1-
Create a class WebSite
Class WebSite
Attributes:
Name
CustomerId
PackageType
......
Functions
SomeFunctions....
and one class for each reques implementing a common interface
Class RequestCreateWebSite
Functions
....
....
Class RequestDeleteWebSite
Functions
....
....
and so on.
What i want to know is the difference in two options i mentioned,
merits and demerits, recomended approach as per OO design principles.
regards,
Sundeep
.
- Follow-Ups:
- Re: Class design question
- From: Daniel T.
- Re: Class design question
- From: Laurent Bossavit
- Re: Class design question
- From: H. S. Lahman
- Re: Class design question
- Prev by Date: Re: abstract factory -- a doubt ?
- Next by Date: how to represent multiobject in Rational Software Architect
- Previous by thread: OMG's Real-time and Embedded Workshop, July 10-13, 2006, Arlington, VA
- Next by thread: Re: Class design question
- Index(es):
Relevant Pages
|