Help understanding OO concepts.

Question

Hi all,
I'm really struggling to get my head around OO programming. I am wanting to make a few simple programs to try and figure it out.
If I am wanting to have 2 classes and a main method class, say player and team class. It is obvious that the team class will have attributes and methods, as will a player.
Team:
Name - simple string.
Stadium - forget for now
Capacity - an int
Players - this is where my problem lies
Coach - forget for now
Manager - forget for now
Player:
Name - string
age - int
shooting - int
tackiling - int
passing - int
Now I can create a new object in my main method that will create a Player object with the above attributes. I am stuck with how to get a player object to be 'part of' the team.
I assume that I need to put the Player class into the Team constructor but am unsure how to do this. I treid looking up on the internet but am not sure what the process is called. If someone could either show me a good link on how to do something similar, or post up some sample code to demonstrate, or even better both, then I can read up on it and understand with an example.
What I really want is for the players to be held in an array within the team class, but not sure how easy this is to do for a beginner.
Thanks
Andrew

Answer 1

Hi thanks for the help. I think i will look into the
set, although it does seem a bit confusing for a
beginner. First though, regarding inheritance:
If in the Player class that extends TeamMember, if I
want to add extra attributes, how do I add these into
the constructor?
public class Player extends TeamMember
int speed;
int shooting;
int tackling;
int passing;
public Player (String name, String position, int
speed, int shooting, int tackling, int passing)
this.speed = speed;
this.shooting = shooting;
this.tackling = tackling;
this.passing = passing;
Is this how I would do it? Unfortunately at the
moment I do not have a comiler so cannot test - I am
a little confused as to how the super word was used.
Thanks
Andrewis Player really a TeamMember? I mean, it is, clearly, but is this relationship correct? I'd say that Player is a role that TeamMembers can have. what if you have a Player/Manager for instance? good OO principle: favour composition over inheritance.
using inheritance, Player would be a class, Manager would be a class, and then you'd need another class PlayerManager. not ideal. if members were composed of roles, you could simply give your Player/Manager both roles, and not need to worry about which class it extended. probably a tricky concept for you to grasp at the moment, granted, but something for you to investigate at your leisure :-)