Download Using Spin Coach Software for Baseball Training: Classroom Mode and Feedback Mechanism and more Study Guides, Projects, Research Engineering in PDF only on Docsity!
Wood Product Documents SIE 554A, Fall 2006
Document 6
The Use Case Model
Revision History Revision Date Team Member Description 1 9/24/ Montealegre, Wolert, Wood Initial release. 2 11/03/2006 Blake Converted from functional decomposition to use cases. 3 11/27/2006 Blake Expanded use cases. 4 12/1/2006 Wolert Included derived requirements in use cases. 5 12/2/2006 Blake Modified use cases. 6 12/3/2006 Wolert Added requirements. Minor changes to used cases.
Wood Product Documents SIE 554A, Fall 2006 7 12/5/2006 Blake/Wolert Editorial changes. 6.1 Use Case Report 6.1.1 Use Case 1 Name: Learn Iteration: 6. Derived from: Concept of operations Brief description: The Spin Coach helps the player to learn how to predict the spin-induced movement of a ball. Players can learn to recognize the spin induced movement of each pitch type by accessing one of three learning modes: Classroom, Batting Practice, and Game. Added value: Player’s batting average will improve due to an increased ability to identify pitch type and subsequent position of the ball in the strike zone. Level: High Scope: One season for a high school baseball player. Primary actor: Player or Tester Frequency: Fifty times per season Precondition: Player has a legal copy of the Spin Coach and a personal computer. Trigger: Player inserts Spin Coach CD-ROM in CD-ROM drive. Main Success Scenario:
- System performs built-in self-test.
- The Spin Coach welcomes Player to the system.
- The Spin Coach asks Player (1) if he or she wants to start a new profile or use existing profile 5a. If player wants to start a new profile, Spin Coach allows for input of Player (1) name, (2) age, (3) years experience, (4) batting handedness, and (5) current batting average.
- System displays modes on main menu. 7a. Player chooses Classroom mode from main menu. 7b. Player chooses Batting Practice mode from main menu. 7c. Player chooses Game mode from main menu.
- System displays the chosen mode.
- System updates MyInfo Player profile (Game mode only).
- The Spin Coach shuts down and says good bye [exit use case]. Anchored Alternate Flow: 5b. If Player already has a profile, Player selects their profile.
Wood Product Documents SIE 554A, Fall 2006 N1-2: The MyInfo Player profile information shall include the following data: Player Name, Player Age, Years of Baseball Experience, Batting Handedness, Batting Average. [From step 5a, refines F1-7] N1-3: The system shall provide exit interface with ‘Esc’ key or screen selection. [From unanchored alt flow, refines F1-6.] N1-4: The Player name field shall at least 40 characters. [From step 5a, refines F1-7.] N1-5: The default value for Player name is ‘John Doe’. [From step 5a, refines F1-8.] N1-6: The Player age field shall accept integers from 1 to 150. [From step 5a, constraint on F1-7.] N1-7: The default value for Player age is ‘15’. [From step 5a, refines F1-8.] N1-8: The Player experience field shall accept integers from 1 to 150. [From step 5a, constraint on F1-7.] N1-9: The default value for Player experience shall be ‘5’. [From step 5a, refines F1-8.] N1-10: The Player batting handedness field shall allow for selection of ‘Right’, ‘Left’, or ‘Switch’. [From step 5a, constraint on F1-7] N1-11: The default value for batting handedness shall be ‘Right’. [From step 5a, refines F1-8.] N1-12: The Player batting average field shall accept three digit decimal numbers between zero and .999. [From step 5a, constraint on F1-7] N1-13: The default value for batting average shall be ‘.000’. [From step 5a, constraint on F1-8.] N1-14: MyStats shall be accessible from MyInfo. [From step 9, refines F1-12.] N1-15: The system shall not allow for multiple MyInfo profiles with the same Player name. [Refines F1-7.] N1-16: The system shall provide test interface upon receipt of ‘CNTL’, ‘T’ command. [Refines F1-13.] Authors: Blake/Wolert Last changed: 12/3/ 6.1.2 Use Case 2 (Abstract extending use case) Name: Classroom Iteration: 6. Derived from: Concept of Operations Brief description: Player uses the Classroom mode to read background information about how pitch type affects the spin and the subsequent movement
Wood Product Documents SIE 554A, Fall 2006 of the ball. Player can choose between two sections in this use case ( Textbook or Display Spin Type). The Textbook section contains basic background information about pitch type, levels in the game, and instructions for playing the game. The Display Spin Type section allows you to view a spinning four-seam fastball, two-seam fastball, curveball, or slider and see the expected spin-induced deflection of the ball from the pitcher. The flow of this use case is inserted into the Learn use case at the Display Specified Mode extension point. Added value: Player will learn basic information regarding spin-induced deflection of the ball. Level: Medium Scope: This use case allows the player to view spin types and read about spin- induced deflection. Frequency: Several times per session. Precondition: This use case is invoked from the Learn use case at the Display Specified Mode extension point if Mode = Classroom. Main Success Scenario:
- The Spin Coach asks Player if he would like to (1) read the textbook, (2) learn pitch types, or (3) exit Classroom. 2a. System displays Textbook text and figures.
- System returns to main menu upon Player request [exit use case]. Anchored Alternate Flow: 2b. System displays Pitchtype upon Player request. (Pitchtypes included are left- hand two-seam fastball, left-hand four-seam fastball, left-hand curveball, left-hand two-seam slider, left-hand four seam slider, right-hand two-seam fastball, right-hand four-seam fastball, right-hand curveball, right-hand two-seam slider, right-hand four-seam slider). [Repeat 2b until Player chooses to exit.] Unanchored Alternate Flow: This use case can be halted at any time upon Player request. Postcondition: The system exits to main menu. Extension points: Name Location Condition Display Selected Pitch System displays selected pitch. [PitchType = left-hand two-seam fastball] System displays selected pitch. [PitchType = left-hand four-seam fastball] System displays selected pitch. [PitchType = left-hand curveball] System displays selected pitch. [PitchType = left-hand slider]
Wood Product Documents SIE 554A, Fall 2006 Brief description: A random sequence of pitch types will be displayed and the user must select the area on the screen corresponding to the appropriate spin- induced deflection. The flow of this use case is inserted into the Learn use case at the Display Specified Mode extension point. Added value: Player will learn spin-induced deflection of the ball in an un-timed setting. Level: Medium Scope: This use case displays a sequence of 10 pitches. Frequency: Several times per session. Precondition: This use case is invoked from the Learn use case at the Display Specified Mode extension point if Mode = BattingPractice. Main Success Scenario:
- Player indicates ready to receive pitch.
- The System uses a random number generator to choose a PitchType.
- The System displays the selected PitchType.
- Player predicts the direction of spin-induced deflection and indicates this direction using a numeric keypad or a mouse.
- The system provides feedback to the player with extend Provide Player Feedback use case.
- System returns to step 2 until Player indicates exit Batting Practice. Unanchored Alternate Flow: This use case can be halted at any time upon player request. Postcondition: The system exits to main menu. Extension points: Name Location Condition Display Selected Pitch System displays selected pitch. [PitchType = left-hand two-seam fastball] System displays selected pitch. [PitchType = left-hand four-seam fastball] System displays selected pitch. [PitchType = left-hand curveball] System displays selected pitch. [PitchType = left-hand four-seam slider] System displays selected pitch. [PitchType = right-hand two-seam fastball] System displays selected pitch. [PitchType = right-hand four-seam fastball] System displays selected pitch. [PitchType = right-hand curveball] System displays selected pitch. [PitchType = right-hand four-seam slider]
Wood Product Documents SIE 554A, Fall 2006 System displays selected pitch. [PitchType = left-hand two-seam slider] System displays selected pitch. [PitchType = right-hand two-seam slider] Provide Player Feedback System provides player feedback. Step 5. Functional Requirements: F3-1: BattingPractice mode shall be an interactive learning mode that displays a pitch and allows Player to input spin induced deflection prediction. [From step 2 and CR-3.] F3-2: The system shall begin BattingPractice upon request of the Player. [From step 1.] F3-3: The system shall display video of spinning ball of selected PitchType until spin induced deflection is indicated by Player [From step 3, refines SR-3 ] F3-4: The system shall accept Player prediction of spin-induced deflection at anytime during display of pitch. [From step 4, refines SR-4.] Authors: Blake/Wolert Last changed: 11/24/ 6.1.4 Use Case 4 (Abstract extending use case) Name: Game Iteration: 6. Derived from: Concept of operations Brief description: The player uses the Game mode to practice identification of the spin-induced deflection after a defined display duration and response window. The flow of this use case is inserted into the Learn use case at the Display Specified Mode extension point. Added value: Player will apply the information learned in the Classroom mode in a more challenging, timed setting. Player will be able to monitor progress in MyStats. Level: Medium Scope: This use case displays a sequence of 10 pitches. Primary Actor: Player or tester. Frequency: Several times per session. Precondition: This use case is invoked from the Learn use case at the Display Specified Mode extension point if Mode = Game. Main Success Scenario:
- Player begins Game mode. The Spin Coach asks Player (1) if he wants to set new preferences or use existing preferences. 2a. Player sets DisplayDuration and ResponseWindow preferences. System stores preferences.
Wood Product Documents SIE 554A, Fall 2006 System displays selected pitch. [PitchType = right-hand two-seam slider] System displays selected pitch. [PitchType = left-hand four-seam slider] Provide Player Feedback System provides player feedback. Step 9. Functional Requirements: F4-1: The system shall begin Game upon request of the player. [From step 1.] F4-2:The system shall system shall gather and store PlayerPreferences for pitch DisplayDuration and ResponseWindow. [From step 1 and CR-1.] F4-3: The system shall set default values for Player Preferences, if values have not been specified by the Player. [From step 2b and JSI company policy.] F4-4: The system shall alert Player that pitch is about to come. [From step 5 and CR-4.] F4-5: The system shall display each pitch for the DisplayDuration in Player Preferences. [From step 6 and CR-1.] F4-6: The system shall provide a ResponseWindow for a duration specified by the Player. [From step 7 and CR-1.] F4-7 The system shall use a timer to determine pitch display duration, allowable response time and pitch delay. [From steps 5, 6, 7 and refines SR-7.] F4-8: The system shall display PitchType after alert. [From step 5, refines SR- for Game use case..] F4-9: The system shall accept Player prediction during ResponseWindow time. [Froms step 7a, CR-6 and refines SR-5 for Game use case.] F4-10: The system shall not accept Player prediction once ResponseWindow has expired. [From steps 7b1.] F4-11: The system shall notify Player if allowable response time has expired. [From step 7b3 and CR-7.] F4-12: The system shall be capable of counting pitches. [From step 10, CR-8, and CR-9.] F4-13: The system shall increment the PitchCount by one if player responds within ResponseWindow and store in MyGame. [From steps 7a,8,10 and CR-8.] F4-14: The system shall increment the TimeOut count by one if Player does not respond within Response window and store in MyGame. [From step 7b and CR-8] F4-15: The system shall increment the HitCount by one if Player correctly predicts spin-induced movement and store in MyGame. [From step 7a, 8, 10 and CR-8.]
Wood Product Documents SIE 554A, Fall 2006 F4-16: The system shall calculate the Player’s Batting Average and store in MyGame. [From step 10 and CR-8.] F4-17: The system shall display MyGame while in Game mode. [From step 10 and CR-10.] F4-18: The system shall gather cumulative MyGame session data and store in MyStats. [From step 11 and CR-2 and CR-10.] F4-19: The system shall display MyStats upon completion of each MyGame session. [From step 12.] Nonfunctional Requirements: N4-1: The system shall provide Player with display durations options of 0.2, 0.4, 0.6, 0.8, 1.0, 2.0 and 5.0 seconds. [From steps 1, 2, CR-1, refines F4-2.] N4-2: The system shall provide Player with ResponseWindow options of 0. 2, 0.4, 0.6, 0.8, 1.0, 2.0 and 5.0 seconds. [From steps 1, 2, CR-1, refines F4-2.] N4-3: The default value for DisplayDuration shall be 5.0 seconds. [From step 2b, refines F4-3.] N4-4: The default value for ResponseWindow shall be 5.0 seconds. [From step 2b, refines F4-3] N4-5: The system shall display PitchType one second after alert is complete. [From steps 5, 6, refines F4-8.] N4-6: PitchCount shall be an integer between 0 and 10. [Refines F4-13.] N4-7: TimeOut shall be an interger between 0 and 10. [Refines F4-14.] N4-8: Hit Count shall be an integer between 0 and 10. [Refines F4-15.] N4-9: Batting average shall be calculated by dividing HitCount by PitchCount. [Refines F4-16.] N4-10: Batting average shall be recorded with three significant digits. [Refined F4-16.] N4-11: The system shall display MyGame table until feedback has been received from the last pitch. [Refines F4-17.] N4-12: The system shall display MyStats for 10 seconds. [Refines F4-19.] Authors: Blake/Wolert Last changed: 12/2/ 6.1.5 Use Case 5 (Abstract extending use case) Name: Provide Player Feedback Iteration: 6. Derived from: Customer requirements, CR-7. Brief Description: The flow of this use case is inserted in the Batting Practice and Game use cases at the Provide Player Feedback extension
Wood Product Documents SIE 554A, Fall 2006 Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand four-seam fastball. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. This use case may also be invoked by the tester. Added value: Player can learn the spin-induced motion of a four-seam fastball pitched by a left-handed pitcher. Level: Low Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand four-seam fastball. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a four-seam fastball for a duration passed in the DisplayDuration parameter. Postcondition: Nothing is being displayed. Functional Requirements: F6-1: System shall display video of a left-hand four-seam fastball. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ . 6.1.7 Use Case 7 (Concrete extending use case) Name : Display Left-Handed Two-seam Fastball Iteration: 6. Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand two-seam fastball. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a two-seam fastball pitched by a left-handed pitcher. Level: Low Scope: This use case displays a single pitch. Primary actor: Player or Tester
Wood Product Documents SIE 554A, Fall 2006 Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand two-seam fastball. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a two-seam fastball for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball [exit use case]. Postcondition: Ball is no longer displayed. Functional Requirements: F7-1: System shall display video of a left-hand two-seam fastball. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ 6.1.8 Use Case 8 (Concrete extending use case) Name : Display Left-Hand Curveball Iteration: 6. Derived from: Customer Requirements Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand curveball. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a left-hand curveball. Level: Subfunction Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand curveball. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a curveball for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System
Wood Product Documents SIE 554A, Fall 2006 Authors: Blake/Wolert Last changed: 12/2/ 6.1.10 Use Case 10 (Concrete extending use case) Name : Display Left-Hand Four-Seam Slider Iteration: 6. Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand four-seam slider. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a left-hand four-seam slider. Level: Subfunction Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = left-hand four-seam slider. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a four-seam slider for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball [exit use case]. Postcondition: Nothing is being displayed. Functional Requirements: F10-1: System shall display video of a left-hand four-seam slider. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ 6.1.11 Use Case 11 (Concrete extending use case) Name : Display Right-Hand Four-seam Fastball Iteration: 6.
Wood Product Documents SIE 554A, Fall 2006 Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand four-seam fastball. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a right-hand four- seam fastball. Level: Subfunction Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand four-seam fastball. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a four-seam fastball for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball. [exit use case] Postcondition: Nothing is being displayed. Functional Requirements: F11-1: System shall display video of a right-hand four-seam fastball. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ 6.12 Use Case 12 (Concrete extending use case) Name : Display Right-Handed Two-seam Fastball Iteration: 6. Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand two-seam fastball. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a two-seam fastball pitched by a right-handed pitcher. Level: Subfunction
Wood Product Documents SIE 554A, Fall 2006
- System displays images of a curveball for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball [exit use case]. Postcondition: Nothing is being displayed. Functional Requirements: F13-1: System shall display video of a right-hand curveball. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ 6.1.14 Use Case 14 (Concrete extending use case) Name : Display Right-Hand Two-Seam Slider Iteration: 6. Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand two-seam slider. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a right-hand two- seam slider. Level: Subfunction Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand two-seam slider. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a right-hand two-seam slider for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball [exit use case]. Postcondition: Nothing is being displayed. Functional Requirements:
Wood Product Documents SIE 554A, Fall 2006 F14-1: System shall display video of a right-hand two-seam slider. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/ 6.1.15 Use Case 15 (Concrete extending use case) Name : Display Right-Hand Four-Seam Slider Iteration: 6. Derived from: Customer requirements. Brief Description: The flow of this use case is inserted into the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand -seam slider. At the end of the display this subflow ends and the use case instance continues at the extension point of the extended use case. Tester can also initiate the use case. Added value: Player can learn the spin-induced motion of a right-hand four- seam slider. Level: Subfunction Scope: This use case displays a single pitch. Primary actor: Player or Tester Frequency: Many times per session Precondition: This use case is invoked from the Classroom, Batting Practice, and Game use cases at the Display Specified Images extension point if PitchType = right-hand four-seam slider. It can also be invoked by Tester. Main Success Scenario:
- System displays images of a -seam slider for a duration passed in the DisplayDuration parameter. Default duration is five seconds. System describes verbally (with audio or written text) what visual attributes Player should attend to and how these visual attributes can be used to predict the spin-induced deflection of the ball [exit use case]. Postcondition: Nothing is being displayed. Functional Requirements: F15-1: System shall display video of a right-hand four-seam slider. [From step 1 and CR-5.] Authors: Blake/Wolert Last changed: 12/2/
