Prev: learning OOD with C++, good idea ?
Next: Practices for avoiding tight coupling?
From: sri on 2 Mar 2007 04:14
IACtx
|
|
----------------------------------------------------
| |
IACtxCart IACtxStruct
| |
| |
------------------------------
------------------------------------
| | | |
XACtxCart YACtxCart XACtxStruct
YACtxStruct

what could be the best alternative design for the above design.

Regards,
sri

From: sri on 2 Mar 2007 04:42
On Mar 2, 2:14 pm, "sri" <srinivasarao_mot...(a)yahoo.com> wrote:
> IACtx
> |
> |
> ----------------------------------------------------
> | |
> IACtxCart IACtxStruct
> | |
> | |
> ------------------------------
> ------------------------------------
> | | | |
> XACtxCart YACtxCart XACtxStruct
> YACtxStruct
>
> what could be the best alternativedesignfor the abovedesign.
>
> Regards,
> sri

sorry, the diagram is cluttered after posting. below is the C++ code
for the diagram

class IACtx //abstract class
{
}

class IACtxCart : public IACtx //abstract class
{
}

class IACtxStruct : public IACtx //abstract class
{
}

class XACtxCart : public IACtxCart //concrete class
{
}

class YACtxCart : public IACtxCart //concrete class
{
}

class XACtxStruct : public IACtxStruct //concrete class
{
}

class YACtxStruct : public IACtxStruct //concrete class
{
}

Regards,
sri

From: H. S. Lahman on 2 Mar 2007 13:00
Responding to Sri...

> IACtx
> |
> |
> ----------------------------------------------------
> | |
> IACtxCart IACtxStruct
> | |
> | |
> ------------------------------
> ------------------------------------
> | | | |
> XACtxCart YACtxCart XACtxStruct
> YACtxStruct

A few tips for drawing text diagrams in eMails.

(1) Never use tabs

(2) Make sure you use a fixed font.

(3) Tell you mailer to use a plain text and a fixed font. If you use a
mailer like Outlook that insists on converting to its own HTML format,
bracket the diagram with "<pre>" and "</pre>". (You may also have to
define the font inside the pre brackets with markups as well.)

(4) Keep the line width to well under 80 characters to avoid wrapping
for typical window widths whenever possible. Most people view eMail with
windows in the 60-70 character range. More important, USENET plain text
readers often automatically wrap lines at 72 characters when they
convert from HTML.

> what could be the best alternative design for the above design.

To provide an alternative one needs to know what the problem is that
your design is supposed to be solving.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl(a)pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info(a)pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH



From: Nick Malik [Microsoft] on 3 Mar 2007 17:49
There is no word in the English language that is spelled 'IActx'. In fact,
none of your classes are named after anything I can recognize. While this
is not "bad," from a design standpoint, those names are the only words in
your post that describe any part of the problem.

So given a problem that is described as a heirarchy of words that you
invented with no context whatsoever, I'm having a hard time guessing at how
to help you.

Take a look at the system you have and decide which part of that system you
want help with. Then, for that part:
Please provide a brief but complete description of its *responsibilities*
Please describe the logical data and process *elements* that the part will
consume or express
Please tell us what *forces* are acting on that part of the system
Please tell us how you expect that part to *behave* in a runtime
environment.

Responsibilities, Elements, Forces, and Behavior
(REFaB)

If you don't know all, tell us what you can.

Then, I'm sure that many folks would be happy to work with you to uncover
some ideas about how you can represent the solution.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"sri" <srinivasarao_moturu(a)yahoo.com> wrote in message
news:1172828544.730133.127130(a)p10g2000cwp.googlegroups.com...
> On Mar 2, 2:14 pm, "sri" <srinivasarao_mot...(a)yahoo.com> wrote:
>> IACtx
>> |
>> |
>> ----------------------------------------------------
>> | |
>> IACtxCart IACtxStruct
>> | |
>> | |
>> ------------------------------
>> ------------------------------------
>> | | | |
>> XACtxCart YACtxCart XACtxStruct
>> YACtxStruct
>>
>> what could be the best alternativedesignfor the abovedesign.
>>
>> Regards,
>> sri
>
> sorry, the diagram is cluttered after posting. below is the C++ code
> for the diagram
>
> class IACtx //abstract class
> {
> }
>
> class IACtxCart : public IACtx //abstract class
> {
> }
>
> class IACtxStruct : public IACtx //abstract class
> {
> }
>
> class XACtxCart : public IACtxCart //concrete class
> {
> }
>
> class YACtxCart : public IACtxCart //concrete class
> {
> }
>
> class XACtxStruct : public IACtxStruct //concrete class
> {
> }
>
> class YACtxStruct : public IACtxStruct //concrete class
> {
> }
>
> Regards,
> sri
>


 | 
Pages: 1
Prev: learning OOD with C++, good idea ?
Next: Practices for avoiding tight coupling?