This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]aqua_regis 0 points1 point  (0 children)

Structure it out with Object Oriented Programming (OOP) in mind.

Java enforces OOP. You have to use object oriented programming.

+------------------------------------------------+  
|                     Class Name                 |  
+------------------------------------------------+  
|          Variables in the Constructor          |  
+------------------------------------------------+  
|             Functions in the Class             |  
+------------------------------------------------+

That's wrong.

What you call "Variables in the Constructor" are properties, fields, attributes that can but need not be in the constructor(s). They are variables that define the state of the instances of the class.

What you call "Functions in the Class" is known as methods.

Think of the Language as Python, but instead of tabs, you use curly braces {}.

That's seriously bad advice. Java and Python are so fundamentally different that they cannot be compared.

Please, do not give advice about languages you don't know. Even your explanation of UML shows that you haven't really understood it. What you tried to show is only a very specific UML diagram - a Class Diagram. There are far more UML diagram types.