2004-10-22 15:24:47 Ryanoriginally, WE Describe The Problem as "What to Do First, Then What To Do Next ...", SO A Problem is described as a sequence of operations. This is caled "procedural" Way of Solving Problem
2004-10-22 15:25:55 Ryanthe "Procedural" way of solving problem is focusing on the sequences of operations needed to resolve the problem. But on the other hand, "data" is described "as needed for operations". They Are not focused.
2004-10-22 15:27:40 RyanLater, when real world gets more comprehensive, people has found that it's hard (even not possible) to simply describe problems as a sequence of operations: solutions to problems is no longer straight-forward. SO Some Clever Men Has Turned There Eyes from Operations To Data-Objects.
2004-10-22 15:29:30 RyanObject-oriented way of solving problems, differed from the good-old procedural way, is that people no longer describe the problem as simply a sequence of operations, but trying to break up the problem into Different Objects, That IS, Entities with Own Data And Operations.
.
2004-10-22 15:37:11 RyanObject-oriented is mostly represented in analysis and design phases. Newer languages like C , Java or C # have added language-level support to Object-oriented programmings, like "class", "inheritence" And So Forth, But You CAN Still Use C to Write Code That IMPLEments An Oo-Design.
