Objects by Design Forums Here you can view your subscribed threads, work with private messages and edit your profile and preferences Registration is free! Calendar Find other members Frequently Asked Questions Search Home  
Objects by Design Forums : Powered by vBulletin version 2.3.5 Objects by Design Forums > Main Forums > Object-Oriented Calculator > UML Diagrams
  Last Thread   Next Thread
Author
Thread Post New Thread    Post A Reply
littlejohn
Junior Member

Registered: Apr 2002
Location: Amsterdam
Posts: 3

UML Diagrams

Hi,

If the purpose of this exercise is to 'serve the developer community as a tutorial for both the UML as well as the principles of object-oriented design', I think it should follow the 'right' order of development process. I know it is only a beginning, but I see only class diagrams and some implementation. It is not the right way to start for a tutorial. The first diags explained should the 'Use Cases' with some scenarios.

Cheers,

Stephane.

Report this post to a moderator | IP: Logged

Old Post 04-24-2002 07:12 AM
littlejohn is offline Click Here to See the Profile for littlejohn Click here to Send littlejohn a Private Message Find more posts by littlejohn Add littlejohn to your buddy list Edit/Delete Message Reply w/Quote
SZ
Administrator

Registered: Apr 2001
Location: New York
Posts: 492

Yes, you are absolutely right. That's why this is a preview and not yet fully published. More is coming.

Also, remember that this is a project, not a product, so it is meant to be under development. And this is open-source, so contributions are always welcome...

Report this post to a moderator | IP: Logged

Old Post 04-24-2002 11:26 AM
SZ is offline Click Here to See the Profile for SZ Click here to Send SZ a Private Message Visit SZ's homepage! Find more posts by SZ Add SZ to your buddy list Edit/Delete Message Reply w/Quote
kckc
Junior Member

Registered: Jul 2002
Location: Stuttgart/Germany
Posts: 1

Teaching OOAD

Hi,

at the moment, I'm thinking about, to teach the OO in a different way. Why to beginn like an real OO-developer (with the use case first)? Isn't it better to go the opposit way, to begin with the OO-Fundamentals (object, class, relation, inheritance) and end with the use case?

I think, in the teaching area it is better to show the details first and the global things last (in opposite to the normal development process).

Walter

Report this post to a moderator | IP: Logged

Old Post 07-16-2002 05:26 PM
kckc is offline Click Here to See the Profile for kckc Click here to Send kckc a Private Message Find more posts by kckc Add kckc to your buddy list Edit/Delete Message Reply w/Quote
SZ
Administrator

Registered: Apr 2001
Location: New York
Posts: 492

Walter, you have an interesting perspective. There is a lot of value to what you say. This is especially true because new programmers like to learn from the low-level up.

There are many new approaches to software development, such as eXtreme Programming (XP) for example, which advocate getting closer to the code.

Your suggestion, starting with the code and then working up to the design, could be developed as a new and different approach to teaching OO design and programming. Any more ideas you have about this would be welcome.

Report this post to a moderator | IP: Logged

Old Post 07-17-2002 04:11 AM
SZ is offline Click Here to See the Profile for SZ Click here to Send SZ a Private Message Visit SZ's homepage! Find more posts by SZ Add SZ to your buddy list Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 11:16 PM. Post New Thread    Post A Reply
  Last Thread   Next Thread
Show Printable Version | Email this Page | Subscribe to this Thread

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 

< Contact Us - Objects by Design >

Powered by: vBulletin Version 2.3.5
Copyright ©2000 - 2014, Jelsoft Enterprises Limited.
Copyright 1999-2005, Objects by Design, Inc.