ooad applied

[Jesus Angeles]

Hello teachers/fellow learners,

I am a new j2ee developer (6 months into it).

After my first project, I found some of my weaknesses: ooad, and testing.

I am working on my 'testing' weakness already; reading junit, xp, tdd, etc.

However, I am at lost on how to be a good analyst/designer for oo systems.

I want to be able to:

>>>design systems, e.g. properly identify what classes i must create, etc.

Eventually, from small systems, I will go to huge j2ee designs.

For now, I didnt know how to design a simple 1 servlet/5 jsp/ 10 class system (doing mq and jdbc). I just proceeded using common sense.

There were: huge methods, huge try-catch blocks, etc. on my design.

Any advice? (advice, books, comments, anything)

I hope you know what I mean: I dont know what to do in between, requirements gathering, and coding/testing.

I will appreciate any comments.

[Ilja Preuss]

I can recommend a book: "Agile Software Development - Principles, Patterns and Practices" by Robert C. Martin. Or start by watching his recent video at http://www.infoq.com/presentations/principles-agile-oo-design

[Pauline McNamara]

Great link Ilja

[Jesus Angeles]

Originally posted by Ilja Preuss:
I can recommend a book: "Agile Software Development - Principles, Patterns and Practices" by Robert C. Martin. Or start by watching his recent video at http://www.infoq.com/presentations/principles-agile-oo-design

Nice presentation. Thanks.