OOPS: Revisiting it for a lec-dem

Having been asked to hold a lec-dem for the freshmen of IT unit, I realize there is always a huge gain in revisiting the basics.. For records I thought I better most this here..

oops1.pdf

Think of Architectural CAD:

  Started with the  Procedural lines, circles, arcs.. ,  added the capability of blocks and finally has gone Object Oriented with walls, windows, doors et als to visually display the simile in transition from procedural to object oriented and beyond..

Fun with Objects if you understand them well..
What is OOPS and what is not OOPS..
Specifications and structure of OOPS: a lil bit of history..
Evolving  OOPS for your needs:
    –Trapping requirements
    – Designing with OOPS
Visualizing and representing OOPS
     – Writing the code
     – Debugging and testing OOP code
     – Delivering OOP code..
Practical OOPS tips.. The best way to be a Zen master at OOPS..
     –All that you should do
     –All that you should avoid…
     –Somethings you can get away with.. Occassionally..
Is OOPS the cure-all methodology.. Alternatives and their terrains..
      –The way ahead to succeed with OOPS.. And meld it with other techniques..
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: