I have a methodology question, regarding oop, and other stuff. I want to know what the top level is.?

Question

I started playing around with programming 15 years ago. For many different reasons I got good, but not quite good enough to actually finish anything serious. When I started to learn about different programming languages, C, Pascal, Basic and so on, I picked them up quite quickly. Tried to program, but never finished anything other than small stuff. Then I learned all about structured programming, eventually I learned modular programming, and eventually OOP. At each stage I tried and tried again only to find that I still cannot complete any sort of sizeable program. Yet I know it is not a limitation in the method, (Structured, Modular, OOP ect), or the language (Basic, C, C++, Pascal ect), because many others developed using those methods and languages long before OOP ever became serious. Later, upon studying OOP, I learned that there are different methodologies, but I cant find any really detailed resourses on them. If I study methodologies, will I later have to learn something else.

Thanks so much for the detailed answers so far. That is great but not quite what I mean. What I mean is, after studying different languages, I found there were different "styles" or "methods" of programming, then after studying the structured style, I found there was a moduler style, after studying that, I found there was an OOP style, and after studying that I have now found there is something called a methology which covers the overall rules behind developing software as opposed to the code itself. For example, OOP deals with classes, and objects and stuff, mostly that is code, but a methodology deals with the different phases of design, developement, and testing, and so on. I want to learn about this, but I am afraid that if I learn about this will there be another thing that I have to learn about afterward, or will learning this allow me to now develop my software to completion. What am I missing that is preventing me from completing a full accounting, or payroll system.

Answer 1

I would assume the top level is the computer system's operating system. There is nothing higher. It did cross my mind that a network of systems is higher, but then a network is considered a structure within the system. When designing a top-down model, the highest and top-most design is always the whole system, paper, computer or whatever. However, as concepts and operating systems develop, I'd assume the application is the highest, with accessible operating system objects a structure withing the application. The reason being the operating system treats each application as a stand-alone program with its own memory space and so on. Should anything crash, it is this protected enclosure of a sandbox land that is effected, not the system as a whole.

Answer 2

There are two paths you could go to find the "top level". Both are valid and deserve consideration, and may even be related.

One is the methodology of how to proceed with a project as a whole, how the whole flow of work on a product will go, regardless of what programming language is in use, and how the individuals involved in the project, programmers, testers, management, and clients, all interact. All of these are covered in one of my favorites, Extreme Programming (XP). Also worthy of exploration is something called Agile software development.

The other consideration is more software oriented. The language you use and the effectiveness of the editing and debugging environment is only one part of it. Is there a version control system in use? CVS, or perhaps Microsoft Visual SourceSafe or StarTeam? What is the procedure for signing code in and out? Does this relate in any way to rigorous Unit Testing (one of the principles of Extreme Programming). What system is in place for testers and clients to report bugs and other functionality issues, and how are these resolved in the work-flow.

These are all real-world, commercial programming project issues, and even when working on hobbyist-type projects, they are well worth a look. Did you ever have a project grow to the point where it gave you a headache trying to figure out what's going on, and in what file and on what line?

Answer 3

methodologies include such things as extreme programming, or rapid application development. they just represent steps or stages in a project and how to achieve these stages.

for instance, i use this way of developing software:

1. i create some scenarios
2. identify classes
3. then some use cases.
4. then i expand on the use cases by creating interaction diagrams or activity diagrams
5. do some coding


i iterate these steps to finally come up with a running solution.

this is only one way, and it is my way but what i believe you could do is study the different methodologies: RAD, Agile development, use-case based development, eXtreme Programming, make a search on the internet, you find lots of tutorials and a list of these methodologies...i guess that would be a very good introduction.


if you have more specific questions, i'll be happy to (try to) answer them

Answer 4

used to love pascal and cobal (even though cobal used to be a pain in the **** sometimes - but it was structured well)

i do prefer C++

have a look at http://en.wikipedia.org/wiki/Object-oriented_programming
for a overview - has a few good links on it

also try

http://sepwww.stanford.edu/sep/josman/oop/oop1.htm
quite amusing !!