Efang: Many people are now using OO development tools, but often mostly in process development software. These two thinking is difficult to distinguish. Where is the heroes pointing for one or two.
SPIDE: The demand is a variable, and the design is relatively stable (therefore, because the adaptation range is completely opposite, even if the "pure decomposition needs design model" is feasible, it is also the direct cause of the "ivory tower". When the demand changes, it cannot be broken or rewritten. It has been written, the test is good, and the mechanism should be used to use the mechanism of the component to temporarily retain the original code and extend the system (only "override" or "upgrade" partial flow). Almost no longer need to repeat the test whether the application system based on the original code is still based on new components. Object-oriented designers, always give priority to how each component is "future" is reused and enhanced, and more is more accustomed to the milestone, agile development. The process-oriented designer, I like "big and complete" doesn't like "small and fine", because I don't recognize some of the active development techniques (mainly in design, and the development language and running platforms) However, it is impossible to consider it in the future, and it is not bad to implement the current system functionality.
Efang: Object-oriented thinking ability is really difficult to form, the design of the object is often very no boundary. After the system's database design is successful, it is very no effect on the design object. Can you use OOA - OOD - OOP project success case?
frankwoo:. that is a funny question actually, people usually say object-oriented design, instead of process :) process belongs to softwareengineer, in essense, there is no object-oriented process or procedure-oriented process, but since some amigoes like to Nudge UML INTO A Process, So Does It :) I Think People Much More Like to Fond Of Object-Oriented Design Uml, with The Process of Rup /, ...., XP, .... etc :)
smilemac: you misunderstood the term process for it is PROCEDURE-oriented rather than PROCESS-oriented normally the procedure-oriented is named functional programming (abr fp.), which was popular before the oop took over it as main-stream technology... Oo Think The World Is Made Up of Objects, But The FP Think It Is Procedure. I Think They Are All Wrong. :)
By the way: Sometimes, We Also Say "Object-orientied Software Engineer". --------------------------------- --------------------------------------------- It's now Different Viewing from high level. But SEPECIAL DETAILS LIE IN The Concrete Process.
