hw2_sol

hw2_sol - 2.1. Use Case Diagram Sequence Diagram 2.2. Class...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
2.1. Use Case Diagram
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Sequence Diagram
Background image of page 2
2.2. Class Diagram
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2.3. Design Patterns 2.3.1 Strategy Have a chessManager class that has both chessboard and strategy. Provide the strategy on the current board setting to the chess manager, and it takes care of implementing the strategy on chessboard. Pseudo-code: public class ChessManager { Chessboard board; Strategy movePicker; // other members makeMove() { Move = movePicker.suggest(board); . . . } // other methods ChessManager(Strategy s) { movePicker = s; } }
Background image of page 4
2.3.2. composite The composite pattern would work best for this music program because the program breaks a song down into subgroups with a hierarchical design. A song is created from verses, which are made up of melodies, which are made up of notes. The user can do whatever is needed with each group of notes, melodies, or verses to compose a song. Pseudo-code: //a song is made of verses, each with subgroups of melodies, each //with a subgroup of notes public class Verse { int verse_number;
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 8

hw2_sol - 2.1. Use Case Diagram Sequence Diagram 2.2. Class...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online