Printable View
OOT is Object Oriented Technology which uses UML, Use Case, Class Diagram, Sequence Diagram.... and etc.
Structure Approach uses Data Flow Diagram, Entity Relationship Diagram, Structure Chart...
OOP is object oriented programming (java, C++).
My question is how to choose a metholodogy(OOT vs Structure Approach) for open source project.
I studied the structured approach, DFD and ERD.
They are not very good. OOP is better. If you use C++ than learn UML. There are 9 diagrams for UML. They involve drawing relationships between classes and objects.
The OOP approach utilizes concepts like inheritance, polymorphism and encapsulation. It is hard to beat because the objects can be reused in other programs. They are complete components invoving the data members of the class and the methods that act on the data. This is all familiar to C++er's. Makes programming more fun too.
Okay.. Thank you for reply. I have another question.
Is that any project can use both Structred approach and OOT? It seems OOT foucs on class & objects. But what if I do not have class and resuable objects? My project develops an GUI interface for some existing programs run in console (eg. a GUI to use SQL instead of using command line). I have read a book about UML, it said UML can be used to model many system (including designing hardware products).
Not quite. With the structured approach you are required to analyse the logic of the whole program, the analytical model and the physical model. With OOT you are only analysing objects and classes, or in other words distinct pieces of the logic that are separate but together form the entire logic of the system. That is what distinguishes them. Note I said system, not program. Yes a sytem involves not only the implimentation, but also the business feasability analyis.Quote:
Is that any project can use both Structred approach and OOT?
Both methodologies are the same though in the sense that they go through the stages of the systems development life cycle: planning/analysis/design/implimentation
Actually you can get programs that help you design a system such as Rational Rose by Rational software, or Microsoft Project.
Sorry, I am still frustrated.
My project develops an GUI interface for some existing programs run in console (eg. a GUI to use SQL instead of using command line). I am still learning OOT now. I think my project is quite straightforward and I would choose Structure Approach.
Are you going to use an OOP language such as C++ or C#? If so than use OOT, otherwise use structured approach. The systems analyses basically just makes it so that you can clearly design the project by being aware of the dataflow to and from processes and file stores, which would include data bases. If you did not use classes to furthur modularize your code than the structured approach is the answer because you have to analyse and design the whole system together as a whole due to the fact that there is no encapsulation.
I don't know your project so I can't say what to use, but I would think that you would have to use either one or the other and not combine the two. To use OOT you would have to convert the program so that it used classes and inheritance hierarchies.
I see.
My project is a Linux application which provides GUI to manipulate firewall rules. It uses Qt(C++). Only the GUI part is OO. Other modules of the programs invloves parser, system/network programming.