Tuesday, February 15, 2005
Sun ONE Studio 5 update 1 running the CDShopCart application. (Pointbase and Sun ONE Application Server minimized) 
Friday, January 28, 2005
1. Abstraction
"With object-oriented programming, programmers focus on the commonalities among objects in the system, rather than on the special cases. This process is called abstraction."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
2. Inheritance
Inheritance "is a form of software reuse in which classes are created by absorbing an existing class's data (attributes) and methods (behaviors) and embellishing them with new or modified capabilities." Subclasses have an is a relationship to their superclass.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
3. Polymorphism
"Polymorphism enables us to 'program in the general' rather than 'program in the specific'."
"With polymorphism, it is possible to design and implement systems that are easily extensible. New classes can be added with little or no modification to the generic portions of the program, as long as those classes are part of the inheritance hierarchy that the program processes generically."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 438, 439.
"With polymorphism, it is possible to design and implement systems that are easily extensible. New classes can be added with little or no modification to the generic portions of the program, as long as those classes are part of the inheritance hierarchy that the program processes generically."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 438, 439.
4. Encapsulation
"Object orientation uses objects to encapsulate (i.e., wrap together) data (attributes) and methods (behaviors)."
"Encapsulation enables objects to hide their implementation from other objects--aprinciple called information hiding."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 342, 343.
"Encapsulation enables objects to hide their implementation from other objects--aprinciple called information hiding."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 342, 343.
5. Association
"When classes are connected together conceptually, that connection is called an association."
(from Week2UML.ppt)
(from Week2UML.ppt)
6. Multiplicity
"Multiplicity denotes the number of objects of one class that can relate to one object of an associated class."
(from Week2UML.ppt)
(from Week2UML.ppt)
7. Qualified Associations
"When an association’s multiplicity is one-to-many, a particular challenge often arises: lookup. When an object from one class has to choose a particular object of another in order to fulfill a role in an association, the first class has to rely on a specific attribute to find the right object. That attribute is typically an identifier, such as an ID number." That identifier acts a qualifier.
(from Week2UML.ppt)
(from Week2UML.ppt)
8. Reflexive Associations
"Sometimes, a class is in an association with itself. This can happen when a class has objects that can play a variety of roles."
(from Week2UML.ppt)
(from Week2UML.ppt)
9. Inheritance and Generalizations
Inheritance "is a form of software reuse in which classes are created by absorbing an existing class's data (attributes) and methods (behaviors) and embellishing them with new or modified capabilities." Subclasses have an is a relationship to their superclass.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 401.
10. Aggregations
Aggregation is the gathering of component classes into one whole. The whole has a "has a" relationship with each component. For example, a computer system has a CPU, disk drive(s), memory module(s), etc. In aggregate, these components form the whole computer.
(example taken from Week3UML.ppt)
(example taken from Week3UML.ppt)
11. Composites
"A composite is a strong type of aggregation. Each component in a composite can belong to just one whole. "
(from Week3UML.ppt)
(from Week3UML.ppt)
12. Contexts
Contexts show the classes in a system in a way that makes clear their relationship to other classes and to the system as a whole. In other words, they show how each class "fits in." For example, if one were modeling a "clothing" system there might be a classes Wardrobe, Outfit, Slacks and Shirt. A context diagram might show that Wardrobe has a 1-to-many relationship with Slacks and Shirt, but that Outfit only has a 1-to-1 relationship with each.
(example based on Week3UML.ppt)
(example based on Week3UML.ppt)
13. Interfaces and Realizations
"An interface describes a set of methods that can be called on an object. Programmers can declare classes that implement one or more interfaces. Each interface method must be declared in the class that implements the interface."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 439.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 439.
14. Use Case Diagrams
"Use Case diagrams represent the interaction between the user and [ the ] system (i.e., all actions the user may perform on the system)."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
15. Class Diagrams
"Class diagrams [ . . . ] model the classes, or 'building blocks,' used in a system. Each entity in the problem statement is a candidate to be a class in the system [ . . . ]."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 68.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 68.
16. Object Diagrams
"Object diagrams model a 'snapshot' of the system by modeling a system's objects and their relationships at a specific point in time. Each object represents an instance of a class from the class diagram [ . . . ], and there may be several objects created from one class [ . . . ]."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
17. State Diagrams
"Statechart diagrams [ . . . ] model how an object changes state (i.e., the condition of an object at a specific time). When an object changes state, that object may behave differently in the system."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
18. Sequence Diagrams
"Sequence diagrams [ . . . ] model the interactions among objects in a system [ with an emphasis on ] when interactions occur."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
19. Activity Diagrams
"Activity diagrams [ . . . ] model an object's activity--the object's workflow during program execution. An activity diagram is a flowchart that models the actions the object will perform and in what order."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
20. Collaboration Diagrams
"Collaboration diagrams model the interactions among objects in a system with an emphasis on what interactions occur."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
21. Component Diagrams
"Component Diagrams [ . . . ] model the artifacts and components--resources (which include graphics, audio and source files) and packages (which are groups of classes)--that make up the system."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
22. Deployment Diagrams
"Deployment diagrams model the runtime requirements of the system (such as the computer or computers on which the system will reside), memory requirements for the system, or other devices the system requires during execution."
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
H.M. Deitel and P.J. Deitel, Java: How to Program, 5th Ed. (New Jersey: Prentice Hall, 2003) 69.
Sunday, January 23, 2005
netBeans 3.6 observations
I've noticed that the VP-SDE will work fairly well in netBeans 3.6 if I follow a simple procedure:
- Open netBeans by itself, without VP-SDE.
- Open a project (or create a new one) and mount it.
- Close netBeans.
- Reopen netBeans, but this time use the "SDE for NetBeans-Sun ONE 2.0" icon to do it, which will load netBeans and the VP-SDE with the previously opened project ready.
The problem I was having, following the instructions in the VP documentation, was that after step 2 they say to load the VP-SDE from within netBeans, which resulted in an exception and no result every time.
Fig. 4.18 from textbook created with VP-SDE in netBeans 3.6 (click image for full size)
Saturday, January 22, 2005
My rendition of Fig. 3.19 from textbook, created with VP-UML (click image for full size).
Spoke too soon :-(
Although the Visual Paradigm SDE appeared to work with netBeans at first, it didn't last long. I started getting exceptions every time I would try to load it.
The standalone Visual Paradigm UML tool was working though, and since I was tired of fooling with the other and was eager to get on with actually learning some UML, I set out to review the "Thinking About Objects" sections in our textbook. After reading a few sections I decided to use VP-UML to re-create Fig. 3.19 from the textbook (page 112), a class diagram for the Deitel's "Elevator" project.
It was a little frustrating at first, but with some practice it was no problem. I'm going to upload my first diagram to the blog (if I can figure out how to do it).
The standalone Visual Paradigm UML tool was working though, and since I was tired of fooling with the other and was eager to get on with actually learning some UML, I set out to review the "Thinking About Objects" sections in our textbook. After reading a few sections I decided to use VP-UML to re-create Fig. 3.19 from the textbook (page 112), a class diagram for the Deitel's "Elevator" project.
It was a little frustrating at first, but with some practice it was no problem. I'm going to upload my first diagram to the blog (if I can figure out how to do it).
It works with netBeans 3.6 anyway ;-)
I never got Visual Paradigm SDE to work properly with Sun One Studio 5 (U1), but it installed perfectly with netBeans 3.6
Thursday, January 20, 2005
Problems with Sun One and Visual Paradigm SDE
Click the title link to see a problem I'm having, posted to the VP forums. No replies over there as of this writing. If anyone in class has any insight, I'm all ears.
Links...
Added a couple links.
Wednesday, January 19, 2005
Initial Post
Welcome to my blog!
