title: UML class diagram for restaurant and Analysis to Design..
body: <p>I'm studying for a reexam in OOAD and doing some old exam questions. I'm trying to develop an analysis class model that may be used to manage a restaurant's menus. Here are the requirements:</p>
  
  <p>Several different menus (breakfast,lunch,dinner)<br />
  Dishes may exists in several different menus<br />
  The restaurant also provides catering<br />
  Dishes should keep information which is relevant for guests with special requests (vegetarian,allergies etc..) Special menus may be created using this information as search criteria.</p>
  
  <p>How I should model the catering? Should there be a Menu class and then breakfast,lunch,dinner and special as specialization classes or should I just have one Menu class? Should there be specialization classes for vegetarian,gluten free..etc dishes?</p>
  
  <p>Then I have this question which confuses me a bit..<br />
  "What are 4 tasks that must be addressed when you transform this analysis class model into a design model?"</p>
  
  <p>What is meant by this? Are there 4 general tasks/steps that always should be done when translating an analysis model into a design model or is it 4 specific tasks specifically for this analysis class model?</p>
  
  <p>I've looked thorugh the presentations and the book (OOAD with applications) and the only thing I found related to these 4 steps/tasks was in a case study:</p>
  
  <p>■ Identify the architectural elements at the given level of abstraction to further establish the problem boundaries and begin the object-oriented decomposition.<br />
  ■ Identify the semantics of the elements, that is, establish their behavior and attributes.<br />
  ■ Identify the relationships among the elements to solidify their boundaries and collaborators.<br />
  ■ Specify the interface of the elements and then their refinement in preparation for analysis at the next level of abstraction.</p>
  
  <p>Regards</p>