bajabob / fastphrase Goto Github PK

As a user of the application I need the ability to search through all the phrases and tags using a simple search. The results of this search should have the ability to be played instantly.

Just needs skinned out, no logic attached. Mockups will be posted when ready.

As a developer of the Application and API I need a JSON manifest that defines all information the user has created. The list of tags, which sounds they apply too, sound labels, etc.

Later this manifest will be bundled with all sound files and posted to the API to be transferred to another device or backed up.

Using @bajabob's #30 prototype templates, create a proto.io application that allows for a clickable prototype.

From Dr. Murphy:

it will include a subset of the meta-requirements document that you have been drafting. The feedback from the meeting yesterday should have your teams on track to fill in the proposal (which is why we had do drafts ;-)

Template in Piazza
Link to Piazza: https://piazza.com/class/ijiqws7xl9g3my?cid=59

As a user of the application, during the save process after I specify a label for the sound clip I would like the ability to add predefined tags to the clip. I can add as many tags as I want and even create new ones.

Note: Creating a new tag relies on #32

As an observer of the Capstone class with no knowledge of the issue you are solving, I require a 5 minute elevator pitch to describe the nature of the problem and how your team intends to solve it.

For all information on requirements, please refer to this document:
proposal_presentation.pdf

As the team lead, I am to take all completed issues and certify that they have been completed to team standards. I am to drive any issues that have yet to be completed and follow up with team members if something needs changed or updated. As such I am to gain a general or full understanding of each completed task so that I can properly present said information at my weekly team lead meeting.

Itemized Objectives for Team Lead

• Drive all issues to proper completion
• Gain understanding of the completed task
• I solely have the power to close issues
• When all tasks are completed, I am to print any media that needs turned in. This shall ensure the proper media is turned in.

No Close Policy

The team lead (Matt Dyl) of the project solely has the power to close any issues for a given sprint. No team member shall close a task unless otherwise delegated by the team lead. When a team member feels that a task is completed, they are to 'tag' Matt in the issue, state that the issue has been resolved and Matt will follow up with issue owner if any changes need to be made.

Issue Completion Flow Exceptions

The only exceptions to the No Close Policy are listed below.

Need a base color palette to use for designing the application. Colors should be high contrast so that they work well outdoors. What message should colors convey?

Color Meanings:
Red is the color of fire and blood, so it is associated with energy, war, danger, strength, power, determination as well as passion, desire, and love.

http://www.color-wheel-pro.com/color-meaning.html

Need a standalone dialog that allows users to manage/create tags.

Features:

• Dialog should popup
• show list of all tags
• how many sounds are apart of each tag
• edit color of each tag
• change name of tag
• create new tag

Example color selector:

Need a summary of points completed and by whom, team total points, and feedback from team on if our estimates were originally correct.

Produce a series of high-fi designs of the application. Should be based off the requirements defined in #6 . Need one design for each screen.

The list of recordings that the user can press and scroll, rows need skinned out. No logic needs attached. Mockups will come when ready.

Take a couple hours to install and test various voice recording apps. Write a report on what you considered to be good features and negative features as they pertain to this project.

As the instructor of the course, I require a draft of your user acceptance plan. Each test should satisfy wholly or partially one of the requirements listed in the requirements proposal.

Everyone needs to complete this poll for Cassandra come Thursday. Be sure to do one for each team mate.

https://docs.google.com/forms/d/1ggBUa8A3_d8IV4xmhyeBWkUSTivxT-zxSCWjWogen4o/viewform?c=0&w=1

Post in comments that you have completed the poll and close issue if you are the last

Needs completed ASAP so @JenningsF can complete #11 for Tuesday.

Open this document: https://docs.google.com/spreadsheets/d/13fKOcxxYiGeXp73kSMn8b6cg16Mj-2TFFe_w1nMDTvw/edit?usp=sharing

Click on the TAB at the bottom that has your name

Fill in choosing one value from each row depending on your PERSONAL interpretation of whether each row is Very Low, Low, Nominal, High, or Very High (choose only one for each row). Put a '1' for the row you choose, remember only one selection per row!

comment when you are completed!

Design an application logo. Relies on #3 & #4

As the team lead, I am to take all completed issues and certify that they have been completed to team standards. I am to drive any issues that have yet to be completed and follow up with team members if something needs changed or updated. As such I am to gain a general or full understanding of each completed task so that I can properly present said information at my weekly team lead meeting.

Itemized Objectives for Team Lead

• Drive all issues to proper completion
• Gain understanding of the completed task
• I solely have the power to close issues
• When all tasks are completed, I am to print any media that needs turned in. This shall ensure the proper media is turned in.

No Close Policy

The team lead (Matt Dyl) of the project solely has the power to close any issues for a given sprint. No team member shall close a task unless otherwise delegated by the team lead. When a team member feels that a task is completed, they are to 'tag' Matt in the issue, state that the issue has been resolved and Matt will follow up with issue owner if any changes need to be made.

Issue Completion Flow Exceptions

The only exceptions to the No Close Policy are listed below.

As a user of the application, I need a way to organize all of my sounds into one level of folders. That way I can organize my sounds as I see fit. Each folder can collapse and hide all contents. Each folder should show graphically that it has content or is empty at a glance.

Example list:

• Russian
  • Sit Down
  • Stay in the boat
• Greek
  • Sit Down
  • Stay in the boat

• clone project, checkout develop
• create new branch from develop called, feature/titlebarview.
• do all programming in this branch (if you commit to master or develop I will destroy you)

The title bar is the bar at the top of the screen that has the application logo. This view is themeable. Can be made red or green. When updated, this view changes its background color and the logo. Please add two methods that will allow this. Check out, TitleBarView. Will attach logos and colors to use below.

Need to come up with and decide on an app name. Should the name of the app be abstract? Very specific? Please post your thoughts in this thread.

Populate a large majority of the backlog and score each issue with one of the TimeEstimates "TE-#".

Need to construct a Gantt Chart based off issues for this and future sprints.

As a user of the application, I need the ability to record a sound and save it to the device.

This should include one button press to start recording, and when the stop button is pressed a save dialog should appear and allow to save.

This story does not include adding visual feedback that the sound is currently recording, that story is #26

As the instructor of the course, I would like you to provide a clear an concise gantt chart for your project. This should include top level features and requirements as well as list dependancies for the entire project. Remember, font size is important. I need this to be easy to read, therefore it should be printed on a poster sized format.

As a developer of the FastPhrase system, I need to complete a tutorial on Android and post up which I completed in this thread.

From Dr. Murphy,

Now we will shift to you drafting the scheduling part of the proposal. That draft is due on Feb. 16 so we can provide feedback.

Template here: https://piazza.com/class/ijiqws7xl9g3my?cid=59

Make available in Google Drive for team to see and edit.

As a developer of the application, I need a method to post a bundle of information to the API.

This includes packaging all sounds and JSON manifest into a zip file and posting to the API.

As a user of the application, I would like the ability to play multiple sounds in a row. I need a way to select sounds or entire TAGS to play, and then have the option to play the sound. Settings should persist after playing in case I want to play all of them again. When I select a tag to play, it will check all songs in the folder so I can uncheck the ones I do not want to play.

HCI:

• user is on playback screen
• user long presses sound or tag and sound or all sounds in tag are "checked" and added to queue
• user does this for all things they want to play
• Play button appears in bottom left of screen with # of queued sounds
• user presses Play button
• dialog appears with all queued sounds
• user can remove what they want
• user can play all sounds

As the team lead, I am to take all completed issues and certify that they have been completed to team standards. I am to drive any issues that have yet to be completed and follow up with team members if something needs changed or updated. As such I am to gain a general or full understanding of each completed task so that I can properly present said information at my weekly team lead meeting.

Itemized Objectives for Team Lead

• Drive all issues to proper completion
• Gain understanding of the completed task
• I solely have the power to close issues
• When all tasks are completed, I am to print any media that needs turned in. This shall ensure the proper media is turned in.

No Close Policy

The team lead (Matt Dyl) of the project solely has the power to close any issues for a given sprint. No team member shall close a task unless otherwise delegated by the team lead. When a team member feels that a task is completed, they are to 'tag' Matt in the issue, state that the issue has been resolved and Matt will follow up with issue owner if any changes need to be made.

Issue Completion Flow Exceptions

The only exceptions to the No Close Policy are listed below.

• clone project, checkout develop
• create new branch from develop called, feature/folderview.
• do all programming in this branch (if you commit to master of develop I will destroy you)

The folder view is not complete. It needs to visually show that it is open and closed when touched. As such there should be an animation that occurs when pressed. Additionally, this view has a listener callback that lets its parent know when it is opened and closed. Please ensure that these are called appropriately.

Create a hand drawn picture of how you see this app working. Be detailed on what screens connect to what workflows. Make sure the diagram is connected so that you can see what parts of the app go to different flows.

Post in comments when you are completed.

Create some paper cutout prototypes of the application.

With the information provided on Tuesday, please groom the backlog and add any additional issues.

As a user of the application I would like to see all my sounds filtered by the tag they are associated with. Any sounds not applied to a tag will be in a list at the bottom of the screen.

Relies on #32 and #31

As a USER of the application, I need the ability to get a storage bundle from the API.

Given a unique KEY, I should be able to download a stored bundle on the API. When downloading if I have pre-existing content in the application it should be merged together.

HCI:

• select option to import data
• dialog appears
• enter unique key defined by API
• download data
• auto merge

Need visual feedback to the user when recording and playing audio. Some of the best implementations of this we have seen use some EQ/Signal processing to show the waveforms of the audio. Find all open source libraries that accomplish this for android and post them here.

http://developer.android.com/guide/topics/media/audio-capture.html

As a user of the application, when I see the audio list screen, I want the ability to play a sound when I touch it. I require highly visual feedback when the sound is playing.

Need a list of languages the app needs to support. As in languages of all users who own the app.

Need an itemized summary of cost for translations and turnaround times. Please also make a recommendation on the service we should choose and make a clear report on costs and turnaround times. Need to know!

Fill it out, comment when you are complete:

https://www.surveymonkey.com/r/FSF29BF

After meeting with the team, please use Draw.io to generate a image rendering all the functions and data needed to turn in. Be sure to save the XML too so that it may be edited later. Upload to drive under "Draw.io" and name appropriately.

As the team lead, I am to take all completed issues and certify that they have been completed to team standards. I am to drive any issues that have yet to be completed and follow up with team members if something needs changed or updated. As such I am to gain a general or full understanding of each completed task so that I can properly present said information at my weekly team lead meeting.

Itemized Objectives for Team Lead

• Drive all issues to proper completion
• Gain understanding of the completed task
• I solely have the power to close issues
• When all tasks are completed, I am to print any media that needs turned in. This shall ensure the proper media is turned in.

No Close Policy

The team lead (Matt Dyl) of the project solely has the power to close any issues for a given sprint. No team member shall close a task unless otherwise delegated by the team lead. When a team member feels that a task is completed, they are to 'tag' Matt in the issue, state that the issue has been resolved and Matt will follow up with issue owner if any changes need to be made.

Issue Completion Flow Exceptions

The only exceptions to the No Close Policy are listed below.

As an instructor of the course, I need a critical path model that outlines the key critical paths of your project. I need this to be easy to read, therefore it should be printed on a poster sized format.

As per meeting on Tuesday, we need to make some big changes to our requirements document. Removing all mentions of hardware.

Other notes:

• Fix by Sun, 14 Feb - Due
• Section 3 a very important section that needs a lot of love
• Add mockups (paper prototype) (issue #2 )
• Remove words like “simple” and “intuitive”
• for each requirement there must be a subsection for each, example: 6 requirements = 6 subsections
• Imagine a lawyer will read everything

Install Android Studio on your personal machine

Install Genymotion on your personal machine along with a Nexus 5 - API 22 emulator and a really shitty emulator, like a Samsung S2 - API 16.

We are supporting API 16 and up in case workers have terrible outdated Android devices. We will need to test on a range of emulators and hardware to make sure we eliminate bugs.

As a user of the application, I need the ability to see very clearly that the application is recording sound. This feature should be obvious in direct sunlight. EQ projects we found for this are here: #8

Please base your wireframes off the research completed in #1

Need a collection of all screens the will be shown on the device and a flow of how they will interact with each other. Simple wireframes will work fine with simple UI elements to convey what each screen contains.

The first issue that should be tackled from a programming standpoint.

Need a general structure of application and a few structured out components for team mates to skin out and complete.

Thinking the components we will start with is the list of music, the recording screen.

Produce a list of top level features for the application. What each screen is capable of doing and how it should be implemented from an interactive standpoint. A simple list of features for each screen should suffice. For example on the recording screen, "button to save recording"

This should be built off defined screens in #2 .