Not bad!
The collaboration/communication diagram is UML1.? not UML2.
And I don't see any use cases! Just bubbles in a use case diagram. A
use case is a textual artifact.
I disagree with conclusions. The to techniques are complementary not
competitors.
SAD is more about how the enterprise works but
OOAD is focussed on the software components in the enterprise.
Example: SAD helps you choose hardware. OOAD assumes you've got it
already!
IMHO.
On May 13, 3:35 am, "Motaz K. Saad" <
motaz.s...@gmail.com> wrote:
> Hello,
>
> I am preparing a presentation about "structured vs object oriented
> analysis and design"
>
> it is available at:
>
>
http://www.slideshare.net/mksaad/structure-vs-object-oriented-analysi...