Team music within
Download 120.96 Kb.
|
          Requirements and Functional Specifications
Project Hands-Free Sheet Music Team Members: Chelsea Colvin (Fall Team Lead) Andrew Tanasse (Spring Team Lead) Cori Goya Industry Representatives: TBD
Faculty Advisor: Tanya Crenshaw Other Contributors: Rick Broussard (Consultant) Revision History
Table of Contents Introduction 6 Requirements 7 Overview 7 A – Application 8 B – Platform 8 C – Pedal Device 8 Environmental Specifications 9 General 9 Temperature 9 Liquid Exposure 9 High-Level Design 10 Component Details 10 Application Shortcut 10 Main Menu 11 Import New Sheet Music 12 Read Sheet Music 13 Organize Music Sets 14 Application Directory 14 Use Cases 15 Use Case 1 - Turn on the Tablet 15 Use Case 2 - Downloading the Application Online 15 Use Case 3 - Launch the Sheet Music Application 16 Use Case 4 - Importing .pdf files 16 Use Case 5 - Flipping Pages left/right with foot pedal device 17 Use Case 6 - Flipping pages left/right with touch screen 18 Use Case 7 - Creating Organized Sets of music 18 Use Case 8 - Discover Bluetooth pedal device 19 Use Case 9 - Turn off the Tablet 19 Development Process 21 General Approach 21 Assumptions 22 Ethical Considerations 22 Milestones 22 1 – Foot Pedal Device Decision 23 2 – Android Tablet Decision 23 3 - Functional Specifications Version 0.95 24 4 – Obtaining the Android Tablet 24 5 - Functional Specification Approved 24 6 – Complete Initial Prototyping with Wired Peripheral 24 7 – Purchase/Obtain Wireless Foot Pedal Device 24 8 – Simple Pedal Device Prototype 24 9 - Final Budget Set 24 10 - Design Document Version 0.95 24 11 - Design Document Approved 24 12 – Software Prototype I Complete 25 13 – Software Prototype II Complete 25 14 – Android Application Complete 25 15 – Application and Device Interfacing Complete 25 16 – Application and Device Testing Complete 25 17 - Final Report Version 0.95 25 18 - Final Report Approved 25 19 - Project Presentation 25 20 - Final Report Approved 26 Risks 26
Trouble with getting the tablet app to talk to the device 26 The pedal device breaking 26 Learning curve for developing an Android app 27 Scheduling to meet as a team 27 Team member absences 27 Team member commute status, especially for freezing weather 27 Android Emulator is not compatible with our machines 27 Resources 28 Personnel 28 Preliminary Budget 28 Equipment 28 Facilities 28 Conclusions 30 Glossary and References 31 List of Figures List of Tables IntroductionThe purpose of this functional specification document is to define the Hands-Free Sheet Music project for the stakeholders listed on the front cover. The document details the project’s requirements, components, use cases, development process and milestones, ethical considerations, business assessment, risks, and resources. Many musicians require the use of both hands for playing their instruments, thus making it difficult to flip through sheet music while performing. Also, there is the danger of losing sheet music while flipping between pages. Hands-Free Sheet Music is an Android application, which will display .pdf sheet music on a tablet screen. A wireless pedal device will interface with the application, and be controlled by the musician’s feet. The application will feature the option of organizing pieces of music into sets of music for playing sequentially from piece to piece. The project will enable musicians to flip through sheet music without the use of their hands while playing their instruments. The pedal will be wireless to prevent problems with tangling on stage, or accidently pulling the tablet off the stand by tripping over a cord. The organized music sets will enable a performance to be played from beginning to end without switching out books or sheet music. RequirementsOverviewFigure 1 is a mockup of how the project will appear to the user when in use during a performance. 
Figure - Mockup of the finished project. Image adapted from www.manhasset-specialty.com, www.pageflip.com, www.acer.com, and www.classical-sheet-music.eu D Team Music Within plans to create a tablet application that will interface with a wireless foot pedal device to enable musicians to flip through sheet music on a tablet without using their hands. This application will display music, enable the user to create organized sets of music for sequential use, and flip pages forwards and backwards based on commands from the pedal device. Figure 2 below is a block diagram of the project components.
The application interfaces with the platform .
The platform interfaces with the pedal device B. A
Figure - Block Diagram of the Project C. The user will interact with the application by interfacing with the tablet screen to organize music sets and choose music for display. The user can then tap the pedal to flip between music pages, leaving both hands free for playing the musical instrument. If the pedal is absent or malfunctions, the music pages can still be flipped by tapping the tablet screen. A – Application
B – Platform
C – Pedal Device
Environmental SpecificationsTable 1 contains a list of the environmental specifications and their required values. Table - Environmental Specifications
Each of the sections below describes the individual specifications in more detail. GeneralBoth devices are designed to operate under normal conditions. The user should be careful because mishandling them could result in significant physical damage. TemperatureAcer Tablet: The battery cannot charge in temperatures that are below 32°F and exceed 104°F. In order to preserve the lifetime of the battery, it is recommended that the battery remain at a temperature between 59-77°F and not exceed that of 140°F. Pedal: The foot pedal can operate in temperatures within the range of 32-140°F and should be stored within -4-140°F. Liquid ExposureNeither device should be cleaned with or exposed to any liquid as it might leak into the devices internal hardware and cause severe damage. High-Level DesignThis section describes the design of Hands-Free Sheet Music at the component level. The menus are designed for interaction through the touch screen, with the hands-free option available only when actually reading the sheet music. Component DetailsApplication ShortcutFigure 3 below shows a mockup of how the application shortcut will appear to the user within the tablet app menu. Figure - Application Shortcut Within App Directory. Image adapted from www.computershopper.com 
Hands-Free Sheet Music Shortcut The user will open the application by going to the tablet’s app menu, and tapping on the shortcut button. Main MenuFigure 4 below shows a mockup of how the main screen will appear to the user and the options available on this menu. 
Figure - Main Menu Screen, with options to Import New Sheet Music, Organize Music Sets, Read Sheet Music, or Quit the application. Image adapted from www.acer.com, www.bluetooth.org, background designs by Charyn Colvin The Main Menu will be displayed every time the user opens the application by choosing the app shortcut from the tablet. The user will make a selection from the main menu by tapping the appropriate button on the touch screen. The Quit button will allow the user to leave the application, and go back to the Android app menu screen. Import New Sheet MusicFigures 5 and 6 below shows a mockup of how the Import New Sheet Music screens will appear to the user if chosen off the main menu.
Senior Design Church Orchestra MYS Band Concert Classical Classical William Tell Overture Toccata & Fugue in Dm Barber of Seville Serenade in D major
Are you sure you want to import this file? YES NO
Figure - Import New Sheet Music Screen, Android OS File Browser, folders in tablet memory. Image adapted from www.acer.com, background design by Charyn Colvin Figure - Import New Sheet Music Screen, Android OS File Browser, files within folders in tablet memory. Image adapted from www.acer.com, background design by Charyn Colvin The .pdf sheet music files must already be loaded into the tablet memory. The user will select the sheet music to be imported using the Android OS file browser. Once the file is selected, and the selection is confirmed by the user, a copy of the file will be saved in the application directory. The user can then choose to go back to the main menu, or import another file. Read Sheet MusicFigures 7 and 8 below shows mockups of how the Read Sheet Music screens will appear to the user if chosen off the main menu.  
Figure - Android File Browser will appear, allowing the user to choose the music to view. Image adapted from www.acer.com, background design by Charyn Colvin Figure - Read Sheet Music screen, the user can now view the music. Image adapted from www.acer.com and www.classical-sheet-music.eu The screen in Figure 6 displays a list of files in the application directory that can be opened. Once a file is selected, the screen in Figure 7 appears, displaying the sheet music to be played. Organize Music SetsFigures 9, 10, and 11 below shows mockups of how the Organize Music Sets screens will appear to the user if chosen off the main menu.   
Figure - Android File Browser will appear when the user taps the Add Another File button in Figure 10. Image adapted from www.acer.com, background design by Charyn Colvin Figure - Organize Music Sets Menu. Image adapted from www.acer.com, background design by Charyn Colvin Figure - Workspace for Creating Music Sets. Image adapted from www.acer.com, background design by Charyn Colvin The Organize Music Sets Menu in Figure 9 will give the user the option to either edit a file, or to create a new set made from copied files from the application directory. The copied files will be reorganized, given new page numbers, and be combined into one single .pdf file that will contain a set of music pieces. Figure 10 shows the OS file browser for the user to download files into the workspace seen in Figure 11. The workspace will allow the user to move pages around into the desired order before saving the set. Application DirectoryThe application directory will be created within the tablet memory when the application is first downloaded. This will be the only directory from which the user can choose sheet music to display. Both imported .pdf files of sheet music and the organized sets of music will be stored here. Use CasesUse Case 1 - Turn on the TabletPrimary Actor: User Goal in Context: Access Application Functionality Preconditions: Working power source (battery, power adapter); functional tablet Trigger: User wishes to use the Sheet music app Scenario:
Exceptions:
Priority: High Frequency of use: Every use of the tablet Channel to Primary Actor: Direct physical manipulation to tablet Use Case 2 - Downloading the Application OnlinePrimary Actor: User Goal in Context: Download the application for use Preconditions: Connection to internet; the app has not been previously downloaded Trigger: User does not have Hands-Free Sheet Music app on their tablet Scenario:
Exceptions:
Priority: High Frequency of use: Once Channel to Primary Actor: Tablet internet browser Use Case 3 - Launch the Sheet Music ApplicationPrimary Actor: User Goal in Context: Open the Hands-Free Sheet Music app Preconditions: Android tablet is already on; Hands-Free Sheet Music app is already downloaded; user wishes to use app Trigger: User wishes to use Hands-Free Sheet Music app Scenario:
Exceptions:
Priority: High Frequency of use: Once every application use Channel to Primary Actor: Android OS Use Case 4 - Importing .pdf filesPrimary Actor: User Goal in Context: Import .pdf file of sheet music into application directory Preconditions: Hands-Free Sheet Music application is active; sheet music is a .pdf format; .pdf file already located within Android device memory; application directory is already downloaded specifically for application Trigger: User wishes to import new sheet music Scenario:
Exceptions:
Priority: High Frequency of use: When new music needs to be imported Channel to Primary Actor: Hands-Free Sheet Music app Use Case 5 - Flipping Pages left/right with foot pedal devicePrimary Actor: User Goal in Context: Flip a page with the wireless foot pedal device Preconditions: Pedal device is visible to tablet/app; pedal has source of power Trigger: User wishes to flip page hands free Scenario:
Exceptions:
Priority: High Frequency of use: Every time a page needs to be turned (high) Channel to Primary Actor: Wireless foot pedal device Use Case 6 - Flipping pages left/right with touch screenPrimary Actor: User Goal in Context: Flip the page with touch screen gestures Preconditions: Tablet touch-screen is functional; recommended pedal device is not available Trigger: User wishes to flip the page Scenario:
Exceptions:
Priority: High Frequency of use: Occasionally Channel to Primary Actor: Tablet touch screen interface Use Case 7 - Creating Organized Sets of musicPrimary Actor: User Goal in Context: Create an organized set of music for sequential viewing Preconditions: Music has been imported into application Trigger: User wishes to automatically flip through multiple pieces of music Scenario:
Exceptions:
Priority: High Frequency of use: Occasionally Channel to Primary Actor: Hands-Free Sheet Music app Use Case 8 - Discover Bluetooth pedal devicePrimary Actor: User Goal in Context: Manually discover Bluetooth pedal device for use with application Preconditions: Powered foot pedal device; tablet is powered on; Bluetooth is manually enabled Trigger: User wishes to discover foot pedal device for use with application Scenario:
Exceptions:
Priority: High Frequency of use: When pedal device is not readily visible to tablet Channel to Primary Actor: Android OS Use Case 9 - Turn off the TabletPrimary Actor: User Goal in Context: Turn off the tablet Preconditions: Tablet is on; use of tablet is no longer required Trigger: User desires to turn off tablet Scenario:
Exceptions:
Priority: High Frequency of use: Once per session Channel to Primary Actor: Physical manipulation of device Development ProcessGeneral ApproachProcess of design and implementation of this Android Application and interfacing with a wireless peripheral will proceed in a step by step process. Our first goal will be to have a wired peripheral device talk to the Android tablet. Next, this same test program will be tested again but with the wireless foot pedal device. From here basic features of the application will be implemented such as a Main Menu, page flipping for one file and a functional GUI as part of a first software prototype. A second prototype will allow for the creation of music sets with the Organize Sheet Music and Import New Sheet Music menus completed. A completed Android application will be built on these two prototypes and will subsequently be tested for interface compatibility. Concurrently throughout the development process there will be testing of not only code but wireless communication and the feasibility of implementing our secondary requirements as seen in Figure 12. Before Founder’s Day there will be a cut-off for testing and modifications to the project. 
Figure - Development Process Diagram The Fall Team Lead is Chelsea Colvin. The Spring Team Lead is Andrew Tanasse. The overall scope of implementation will be dependent on the completion of primary functional requirements. Secondary and tertiary goals will only be considered for implementation after the primary requirements have been satisfied. AssumptionsAssumptions that are required for project Hand-Free Sheet Music to be successful:
Ethical ConsiderationsIssues to consider with this project include the potential misuse of the devices and facilitation of illegal file downloading. If the user fails to properly handle the device it could harm the user or others. The application created for this project will use PDF sheet music files that can be uploaded from a computer. The major ethical concern is the source of these files because they can be illegally obtained from Internet websites. If that is the case, this project has the potential to condone the illegal act of downloading these files. MilestonesTable 2 below lists the milestones in the order that they will occur, and are followed by a detailed description of what each milestone is and the completion criteria for each milestone. Table - Milestones
1 – Foot Pedal Device DecisionThe team is expected to make a decision on a foot pedal. Team Music Within decided to purchase the PageFlip Cicada, a Bluetooth foot pedal device. 2 – Android Tablet DecisionTeam Music Within makes a decision about which Android tablet to purchase. The team decided on the Acer Iconia TAB A500. 3 - Functional Specifications Version 0.95The Functional Specification is expected to be at Version 0.95 on September 30, 2011. This means that it has been approved by Team Music Within’s faculty advisor, and been sent to the team’s industry representative. 4 – Obtaining the Android TabletTeam Music Within physically obtains the purchased Android tablet. 5 - Functional Specification ApprovedThe Functional Specification is expected to be approved by both the faculty advisor and the industry representative by October 7, 2011. The document is now considered complete. 6 – Complete Initial Prototyping with Wired PeripheralThe team will complete testing to insure that the application responds to the wired peripheral. 7 – Purchase/Obtain Wireless Foot Pedal DeviceThe team orders a wireless foot pedal device and receive it by November 4, 2011. 8 – Simple Pedal Device PrototypeThe team will complete testing to insure that the application responds to the wireless foot pedal device. 9 - Final Budget SetThe Final Budget is expected to be set by November 12, 2011. This accounts for all costs associated with developing the application and the pedal device. The development tools are free, and a tablet will be purchased outside of the team, but the testing pedal device and parts for a new pedal device will be purchased within the team’s budget. 10 - Design Document Version 0.95The Design Document is expected to be at Version 0.95 on November 19, 2011. This means that it has been approved by Team Music Within’s faculty advisor, and been sent to the team’s industry representative. 11 - Design Document ApprovedThe Functional Specification is expected to be approved by Team Music Within’s faculty advisor and industry representative by October 7, 2011. No further changes or revisions will be made. 12 – Software Prototype I Complete
13 – Software Prototype II Complete
14 – Android Application CompleteThe whole software package is complete for the Android application. 15 – Application and Device Interfacing CompleteThe wireless foot pedal device successfully talks to the completed Android application. 16 – Application and Device Testing CompleteThis is the cut-off date for testing the device. 17 - Final Report Version 0.95The Final Report draft of Hands-Free Sheet Music is expected to be ready to be submitted for approval by Team Music Within’s faculty advisor by April 6, 2012. 18 - Final Report ApprovedThe Final Report is expected to be approved by Team Music Within’s faculty advisor and industry representative by April 13, 2012. 19 - Project PresentationTeam Music Within is expected to give its final presentation on Founders Day, April 17, 2012, at the University of Portland, demonstrating Hands-Free Sheet Music in front of other senior design teams and industry representatives. 20 - Final Report ApprovedThe Final Report of Hands-Free Sheet Music is expected to be approved by both Team Music Within’s faculty advisor and industry representatives by April 20, 2012. RisksThe risks that Team Music Within could come across are listed in Table 3. Table - Project Risks and Contingencies
Trouble with getting the tablet app to talk to the deviceA major concern is the problems that may occur when trying to get the tablet application to talk to the pedal device. If clear communication does not occur between the app and the pedal, the project will not be fully hands-free, thus defeating the purpose of the project. Our plan to prevent these problems includes (a) making sure the tablet recognizes external devices, and (b) extensive Bluetooth testing with a purchased pedal while coding the app. The pedal device breakingAnother concern is that the pedal, purchased or customized, might break after extensive testing. Our plan is to (a) make sure that the purchased pedal is saved as a back-up in case the customized one breaks right before Founder’s Day presentation, and (b) that the application works with touch screen inputs as well in case both pedals are broken. Learning curve for developing an Android appA moderate risk is that the team, including the main developer (Chelsea Colvin), has not had previous experience in coding for Android applications. Our plan for overcoming this is (a) begin coding early, (b) read documentation about Android, and (c) getting other resources for help. Scheduling to meet as a teamBecause of different class schedules, the team has difficulties meeting all together during the school week. Our methods of preventing this becoming a major problem are (a) meeting regularly at least once or twice a week at the same time, (b) dividing up the work so that the team members can work independently on parts, and as a whole team in other parts, and (c) communication and file sharing on the team’s Basecamp account. Team member absencesSince we are a three member team, meetings with the entire team present are important for preventing workload imbalances. We plan to account for team member absences by (a) clear communication between all members, and (b) making sure that each member has an understanding of each part of the entire project to make sure no one person becomes indispensable as resource should an absence occur. Team member commute status, especially for freezing weatherOne of our team members has an hour-long commute to campus. As the weather becomes cooler, there is a higher chance that the team member might be stuck at home due to freezing weather and road hazards. We have compensated for this by (a) making sure wireless communication can continue between team members despite bad weather, (b) giving that team member a heavy portion of coding which can be done from the team member’s home computer, and (c) having the team member have other housing options should freezing weather be forecasted in time. Android Emulator is not compatible with our machinesA software concern is whether the Android Emulator is compatible with our machines, including our home computers and school computers. We will try to mitigate this concern by testing the emulator early and often. ResourcesPersonnelTeam Music Within consists of three personnel with the following responsibilities:
Preliminary BudgetThe main component Table 4 contains a list of the materials and software that need to be purchased. Table - Preliminary Budget
EquipmentTeam Music Within will be using Android Development tools and Eclipse to code the application. We will also be purchasing a wireless pedal device for testing. The equipment we will need for building an actual pedal has not yet been determined. FacilitiesTeam Music Within will need the engineering workshop room and the computer science room offered to seniors for their team projects. ConclusionsThe goal of Hands-Free Sheet Music is to enable musicians to perform without the hassle of physically flipping pages of sheet music. End users will be able to perform without worrying about sheet music flying off the stand, and will be able to continue playing from piece to piece in sets of music. With a pedal device, a tablet running Android OS, and the Hands-Free Sheet Music application, musicians will be able to perform their instruments with fewer sheet music problems, and more efficiently. Glossary and References.pdf (Portable Document Format) – file format created by Adobe Systems to display files to be viewed outside of software programs, hardware, or operating systems OS (Operating System) – a set of programs that manages computer hardware resources, and provides common services for application software Android Emulator – a virtual mobile device that runs on your computer, and lets you develop and test Android applications without using a physical device Eclipse – a multi-language software development environment that comprises an integrated development environment (IDE) and an extensible plug-in system GUI (Graphical User Interface) – user interface that allows users to interact with electronic devices with images rather than text commands UNIVERSITY OF PORTLAND SCHOOL OF ENGINEERING CONTACT: CHELSEA COLVIN Download 120.96 Kb. Share with your friends:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||