learning the object oriented way

this is what i understand or i don't understand about object oriented programming
non computer geeks need not go further

what do we want from a system?
that it takes a given input and gives a output that is what a system is..
system : it must exist in time, space (don't know what einstein would say about that) well defined interface with rest of the universe

now a system may have other subsystems ...
now these subsystems interact among themselves in a well defined way.
good things we wantfrom a software

- satisfies all requirements quite broad for a defination
- should be usable and useul
- maintanence
-relaible
portable / scalable

problem is that a s/w system can never really model a real life system exactly
we can only come close to it
modular is a term used for procedural programming

we want cohesion to be maximum and interaction b/w systems mininmum


so we started with the feasibilty analysis


requirement nalysis
access permission read write etcwe require to demarcate who is reponsible for what work
goals are long term
objectives how to do it
keep taking notes during the interval
prepare a formal document get he document ratified
find what information is required what requires further elaboration
system development life cycle (SDLC)

.- feasibilty analysis
.- requirement analysis
.- specification details
.- design
.- code it
.- testing
.- deployment
models
waterfall - freeze each stage
spiral - limiited number of functionalties
coding design testing
add other functionalties

prototype - working small prototyp
polymorphism
20% code is comments


UML
unified modelling language
model - a list of must have
dialog functions of the systems
actors classes normally

amusing

lets study english grammar

noun can used as classes
noun can be describe by candidate classes
- relevant
- irrelevant
- fuzzy
... assumes that the correct document is complete and correct

a name of person place animal or thing
though it i does not work everywhere
but
ok
verb used it as function

what do we do about adjectives adverbs etc ......... is the question i have on my mind

nothing strict just a guideline

types of classes
parametrized class
interface classes
utility classes

we can ideify classes by other ways too
like using patterns
crc cards
use case driven
hash all of these


well this summary of my course
better blogging when my minors get over