App Design Proposal. I. Planning Table (30 points)

Transcription

1 App Design Proposal Please use this template to help you plan for your app design. It is recommended to think through your design and include as many details as possible. App Inventor Name: Brian Querry Submission Date: November 6, 2011 I. Planning Table (30 points) The Name of Your App Details Notes for Yourself Category of Your App Why are you building this app? User Group(s) User Test Plan Learning / Education This school year, I returned to directing instrumental music for the first time in almost 10 years. One things that I ve found with my students is there seems to be a general lacking of fundamental listening skills. Students seem to have difficulty self-tuning, adjusting for intervals, and recognizing appropriate accidentals. This app includes various listening and recognition activities to help students work on these skills. Middle School (grades 6-8) students with several years of playing an instrument or private musical study (the app will be customized for my students) Who are the testers? This app will be tested by three people - a middle school instrumental student (grades 6-8), a high school instrumental student (grades 9-12), and a music teacher. The middle school student will be able to test the app in the age level it is designed. A high school student can review the app from the viewpoint of an experienced musician. A music teacher can review the app from the viewpoint of a teacher. When do you plan to test your app? The app will be tested after 2 weeks of development and within days of its completion, with a target date range of November How do you plan to test your app? The app will be tested by posting the app and a QR code on a class web site, and providing a link to the prospective students. I have already identified a colleague and high school student with Android devices who are willing to participate. I will need to identify a middle school students who has access to a device (with almost all of my students having phones already, it shouldn t be hard). Where do you plan to test your app? The middle school and high school students will test the app during a regularly-scheduled instrumental lesson time in the band room at their respective schools. The colleague will review the app at his leisure. 1 A template designed for BSU EDTECH597 Mobile App Design Course by Yu-Chang Hsu, Ph.D. 2011

2 How does this app work? User test results Dissemination Plan Future development plan for this App The opening screen will allow the user to select one of three sets of activities: beginner, intermediate, or advanced. Once they select a level, they will be taken to a series of exercises (number TBD) that test their ability to recognize, identify, and interpret various musical intervals, keys, modalities, and terminology. The users will select levels using a button on the main page. Then, based on selection of that button and a set list in the block designer, the user will be taken to the corresponding list of questions. The questions will be a mix of visual (with corresponding pictures), aural (with corresponding audio clips) and text-based. The user will be provided a text box in which to put their answer. For some questions, users will be provided a list of multiple choice answers from which to respond. A tally of correct and incorrect answers will be taken, with the user being given a percentage score at the end. Users will have the option to send their finished score to my address. As this app is still in the design stages, no formal user test has taken place yet. However, I will have a formalized sheet with questions and rankings that I will ask the user to complete during and completion of use of the app. This app would be promoted to all middle school and high school instrumental students, with the primary focus being middle school. Since all users may not have an Android device and I do not have enough for them to use, I at first could not require students to complete the activities. However, I could provide the option of students completing the activities in the app in lieu of some of the assessments in their instrumental lessons. This app could be enhanced in the future in many ways. First, rather than forcing results to my , it could be customized to allow the user to enter the recipient , thus making it marketable. Second, it could be changed each year with the exercises customized to match the music being played/studied in the band setting. Third, to assist special education students, an option can be added at the beginning to limit the number of questions. While these are all things I think are very achievable to add, I don t plan to include them in the app design at this time. 2 A template designed for BSU EDTECH597 Mobile App Design Course by Yu-Chang Hsu, Ph.D. 2011

3 II. Instruction for App Component Map and App Behavior Flowchart Please use concept map tools (e.g., Gliffy, Google Drawing, or Bubbl.us etc.) of your choice to create the following to explain your proposed apps 1. App Component Map (i.e., explain what you plan to have on the Component Designer) a. What are some visible components you plan to have on the user interface? (e.g., buttons, labels, images, animations, textbox for input etc.) b. What are some Non-visible components you plan to have on the component designer? (e.g., sound, location sensor, TinyDB etc.) c. Why do you need those components mentioned above (aesthetic, relevance function etc.)? 2. App Behavior Flowchart (i.e., plan and present the behavior logic/flow you would like to have on the Block Editor) a. What would your apps do behind the scenes? (i.e., How does this app work? What kind of behaviors do you plan to build in the Block Editor?) i. For example, if you are building a Virtual Tour app, you might want to have the app present a list of sites for users to view after they click on a button. ii. Present those planned behaviors in a flowchart. e.g., User clicks on the Choose Destination button ListPicker presents a list of items for users to choose from. User clicks on one of the listed destinations. The listed destination is linked to/presents the destination on Google Map. (Note: This example above is a linear behavior flowchart. Your flowcharts are expected to involve multiple paths of behavior flow.) 3

4 II-A. App Component Map (30 points) Opening Screen Insert the images of your App Component Map and Behavior Flowchart below. COMPONENT NAME TYPE OF COMPONENT PURPOSE OpeningImage Image Graphic for Opening Screen OpeningLabel Label Title of App InstructionsLabel Label Instructions for App BeginnerButton Button Select Beginning Level Questions IntermediateButton Button Select Intermediate Level Questions AdvancedButton Button Advanced Level Questions Horizontal1 Horizontal Arrangement Keep items for submitting name together NameLabel Label Label for entering student name NameTextBox Text Box Box for entering student name NameButton Button Button to save student name NameSavedLabel Label Text to appear once student name is saved Questions COMPONENT NAME TYPE OF COMPONENT PURPOSE QuestionImage Image Image related to question QuestionAudio Sound If a sound clip is necessary, sound for question QuestionLabel Label Question Text AudioButton Button Button to start sound clip, if necessary Horizontal2 Horizontal Arrangement Keep items for answer box together AnswerLabel Label Label for entering answer AnswerTextBox Text Box Box for entering answer AnswerButton Button Button to submit answer 4

5 AnswerResultLabel Label Acknowledge if answer is correct or not Horizontal3 Horizontal Arrangement Keep together question scoring CorrectLabel Label Text to identify correct answers CorrectNumberLabel Label Number of correct answers IncorrectLabel Label Text to identify incorrect answers IncorrectNumberLabel Label Number of incorrect answers NextButton Button Button to move to next question Closing COMPONENT NAME TYPE OF COMPONENT PURPOSE ScoreHeaderLabel Label Header for Score Page Horizontal4 Horizontal Arrangement Keep together correct total info CorrectTotalLabel Label Text to identify total of correct answers CorrectTotalNumberLabel Label Number of total correct answers Horizontal5 Horizontal Arrangement Keep together incorrect total info IncorrectTotalLabel Label Text to identify total of incorrect answers IncorrectTotalNumberLabel Label Number of total incorrect answers Horizontal6 Horizontal Arrangement Keep together percentage scoring info PercentLabel Label Text for scoring percentage PercentNumberLabel Label Number for scoring percentage SubmitScoreButton Button Click to submit score to teacher Notifier1 Notifier Allow students to select to end app or try different level 5

6 II-B. App Behavior Flowchart (30 points) 6

7 7