Created May 31, 2009
Last updated August 8, 2009
[ Japanese | English ]

Why open this content

  Opened because of this content is as follows.

  1. I have studied object-oriented up to now for about four years. Therefore, I was going to arrange the content that had been studied.
  2. I thought that I became the material of HP.
  3. We associate "encapsulation", "inheritance", and "polymorphism" from the word called object-oriented. However, I thought that they were different.
  4. The new figure will be educated in the company, incidentally.

About 1.
  Thinking that I may arrange object-oriented earlier about them is usual. However, because limited knowledge had been understood for myself, I did not arrange it.
  Of course, I still have a lot of inaccurate knowledge and unknown things. For instance, I did not know the Design pattern at all when UMTP L2 was acquired, and I did not know the BCE pattern 1.   I did not know even the word of the Aspect-oriented 2.
  When the content of object-oriented is put on this page in such a state, it troubles the person who saw this page. The trust of this page is damaged.Therefore, I have not done up to now.
  But, It was thought it was already unquestionable for me, and decided to put the content of object-oriented on this page.

About 2.
  There are not so much a lot of HP written with HP related to Excel VBA about object-oriented. Then, I will do.

About 3.
  Three large elements of object-oriented are "encapsulation", "inheritance", and "polymorphism". I do not deny them.
  However, I want you to forget once about them when there is a person who studies object-oriented now.
  I want you to confirm it if the book on object-oriented is at hand now. What is the content written most first about object-oriented?
  I think that it is not any of "encapsulation", "inheritance", and "polymorphism".
  Perhaps, I think that the book does the explanation that doesn't understand well about "Class" and "Object".
  I do not have confidence to explain "Class" and "Object" well. But, if these are not understood though you read the explanation of "encapsulation", "inheritance", and "polymorphism", I think time to be useless 3.   Therefore, (Though I do not have the confidence that can be explained to our regret well.) if I explain "Class" and "Object" from the point of "Entity-relationship diaglam (ERD)" and "Module Coupling", It becomes a more comprehensible explanation, and I thought that it became possible for more people to understand object-oriented 4. And, I decided to put the content concerning object-oriented on this page.
  And, I want you to consider the reason object-oriented is used. That is not popular and good-looking but wanting the high quality. If you design the program of high quality ( Especially, Module Coupling and Cohesion ) and you consider the correspondence of the data , I think that you will design program in object-oriented.

About 4.
  Hereafter, there might be what educates the new figure and the junior in the company. At that time, if I say, "Look at this web site", the traffic of this page increase.
  This is also for the new figure, and when the content that exists in the range of setting questions about qualifications such as "Japan Information-Technology Engineers Examination" and "UMTP" is included in the page, I want to write so as much as possible.   Because, I want the junior to acquire the qualification.

1:The Design-pattern is not set in UMTP L2.
The BCE pattern is set. But, I think that we were able to solve the problem even if we do not know BCE pattern.
2:When you do not know "Aspect-oriented", I judge that Even if you know, you do not know doing of it is not possible to do by "object-oriented".
3:Though this is my prejudice, I think that As for the Class Diagram(designed by the person who did not correctly understand "Class" and "Object"), attention is not brushed off to Module Coupling and Cohesion, it relies on the Design-pattern too much, the use of "Inheritance" stands out, and the entity class doesn't exist at all.
4:May I write such outrageous?

Prev Up Next  Top

I doesn't assume the responsibility of any damage that occurs because of the use of this page.

Microsoft ,Windows ,Visual Basic and Excel are registered trademarks of Microsoft Corporation in the United States and other countries.
Visual Basic® for Applications may represent a VBA.
Mac ,Mac OS ,Mac OS X ,AppleScript are trademarks of Apple Inc., registerd in the U.S. and other countries.
Google is a registered trademark of Google Inc.
Other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such.

The author of this page and these companies do not have any relationship.