title: UML class diagram questions
body: <p>If i have a system for organising a schedule for pilots and the plane they fly for a job. And a manager for organising the schedule. But the manager is also a pilot. Do i need two seperate child classes of <strong>user</strong> as pilot + manager. Or would it be more practical to just use an attribute of isManager in the pilot class for example? Or would the manager be a child of pilot?</p>
  
  <p>And if the schdule class is a composition to <strong>system</strong>, would the method for creating a new schedule have to be in the system class?</p>