ARSC-Audio Design Document Full Report.

ARSC -
AUDIO.ORG
Prepared By:
• Daniel Camargo
• Jordan Vane
• Will Plumb
• Neal Wandja
Table Of Contents
1. Proposal - 3 3. Final Report - 36
• 1.0 Client.......................................... 4
• 2.0 Statement of Need........................... 4 I. QA Testing
• 3.0 Client Goals.......................................... 5 • 1.0 Usability Test Plan...... 37
• 4.0 Proposal Solution...................................... 6 • 1.1 Usability Test Results...... 38
• 5.0 Deliverables.................................................... 6 • 1.2 Usability Test Summary........40
• 6.0 Success Metrics...................................................6
• 7.0 Audience & Stakeholders...................................... 7 • 2.0 Functional/Compatibility Testing.....40
7.1 Audience
7.2 Stakeholders • 3.0 User Satisfaction Survey......40
• 3.1 User Satisfaction Survey Test Plan ......41
• 8.0 Requirements ....................... 8 • 3.2 User Satisfaction Survey Results........42
• 3.3 User Satisfaction Summary.........45
8.1 Data/Content Requirements......8
8.2 Functional Requirements.......8 II. Post-Project Analyses..........46
8.3 Product Qualities.......9
8.4 Constraints..........9 • 4.0 Schedule Analysis.......46
• 5.0 Cost Analysis.......47
• 9.0 Development Process................... 10
III. Lessons Learned...... 48
9.1 Phases & Roles........ 10
9.2 Development Tools.... 10 • 6.0 What we learned.........48
9.3 Development Team..... 11 • 7.0 What we would do differently....48
9.4 Quality Control Process.... 11
IV. Sign Off..... 50
• 10.0 Timeframe......... 12
• 11.0 Project Scope........ 12 • Final Report Grading Form......
• 12.0 Cost Estimate.............. 13
• 13.0 Proposal Sign-Off................1 4 Appendices - 52
• User Survey.......53
• Time Logs (for all team members for the entire project---1st
2. Design Doc - 16 & 2nd semesters)...........56
• Search Engine Optimization.............66
1.0 Strategy........................... 17
2.0 Scope.................................. 21 - 22 • Change Request Form.........67
3.0 Structure................................... 23 • Early Sketches .......68
4.0 Skeleton........................................ 24 • StoryBoard........69
5.0 Surface................................................ 26 -30
6.0 Work Breakdown...................................... 30
7.0 Budget........................................................... 31
8.0 Risk Assessment................................................ 32
9.0 Design Doc Sign off.................................................. 34
ARSC-Audio.Org - Project | Utah Valley University | ARSC Web Team 2

ARSC-Audio.Org
PROPOSAL
• 1.0 Client ... 4
• 2.0 Statement of Need... 4
• 3.0 Client Goals... 5
• 4.0 Proposal Solution.... 5
• 5.0 Deliverables..... 6
• 6.0 Success Metrics..... 6
• 7.0 Audience & Stakeholders ...... 7

7.1 Audience
7.2 Stakeholders
• 8.0 Requirements...... 8
8.1 Data/Content Requirements

8.2 Functional Requirements
8.3 Product Qualities
8.4 Constraints
• 9.0 Development Process........ 10
9.1 Phases & Roles

9.2 Development Tools
9.3 Development Team
9.4 Quality Control Process
• 10.0 Timeframe........ 12
• 11.0 Project Scope........ 12
• 12.0 Cost Estimate............ 13
• 13.0 Proposal Sign-Off........... 14
1.0 Client
Who is ARSC: The Association for Recorded Sound Collections (ARSC) is a nonprofit organiza-
tion dedicated to the preservation and study of sound recordings. Established in 1966, mem-
bers include record collectors, discographers, and audio engineers, together with librarians,
curators, archivists, and researchers.
2.0 Statement of Need

ARSC is in need of a full redesign of their current website. User feedback has shown that
there is a general dissatisfaction with the way the website looks and how it is currently laid
out. Users get confused while trying to access specific content.
There needs to be restructuring of the website’s navigation to a more simplistic approach,

allowing users to easily find the content they are looking for. The client also needs this rede-
sign to include a focus on design and UX. This website also needs to be on a CMS (Content
Management System) platform so that website updates and maintenance can be handed off
to the client upon completion.
ARSC-Audio.Org - Project | Utah Valley University | Proposal 4

ARSC-PROPOSAL
3.0 Client Goals
• Have a website more directed towards the organization’s audience.

• Improve user experience while on site.
• Increase overall aesthetic appeal of website.
• Improve website’s information architecture.
• Increase accessibility of website content.
4.0 Proposed Solution
To meet the goals of the client, our team proposes to re-create the ARSC website with
a focus on hierarchy and organization. Features that currently exist on the website will
still be included such as
• Member-Exclusive Material,
• Soliciting Memberships
• Donations to the Organization.

5.0 Deliverables
• Project initiation agreement

• Proposal
• Design Document
• Website Prototype
• Final Delivered Website
6.0 Success Metrics

• See an increased appeal and functionality to current website users and ARSC’s board
members. Surveys will be conducted to test overall satisfaction among board mem-
bers with prototypes and completed product
• Easier access to archived sounds & records. This will be tested using Google Analytics
by amount of time it takes to find certain files
• Increased improvement in Information Architecture and user satisfaction. Surveys
will be conducted to test overall satisfaction

ARSC-PROPOSAL
7.0 Audience & Stakeholders
7.1 Audience
• ARSC members & prospective members looking to join

• Musicians looking to store sound recording and archive their work
• Help people with similar interests connect and network through activities.
7.2 Stakeholders
• President: Matthew Barton (Library of Congress)

• First Vice President/President Elect: Cary Ginell (Origin Jazz Library)
• Second Vice-President/Program Chair: Patrick J. Midtlyng (Syracuse University)
• Secretary: Allison D. Bohm McClanahan (Indiana University)
• Treasurer: Steven I. Ramm
• Members-at-large: Jessica Wood (New York Public Library), Melissa Widzinski (Indiana
University)
• Executive Director: Nathan Georgitis (University of Oregon)
• Web Master: Kellie Johnson

8.0 Requirements
• PDF files for conferences

• Audio recordings
• Images
• Analytics data
• Existing Content
Function Scenario
Donate ARSC enthusiast comes to the website to donate to the orga-
nization
Member login Member comes to site to login to view member-exclusive
material
View Recordings User comes to website to listen to conference recordings
Social Media Interac- A user comes to the site and is able to see the latest social
tion media posting pertaining to the organization
Browser Compatibility:
• Firefox
• Google Chrome
• Internet Explorer
• Safari

ARSC-PROPOSAL
8.3 Product Qualities
Provide a satisfying user experience by using color schemes and fonts that work well with
ARSC audience. Fixing the navigation and information architecture of ARSC. User friendly
functionality and less clutter.
8.4 Constraints
• Meet deadlines for documentation and sign offs as outlined by senior project instruc-
tor.
• Provide mock ups in time for client sign off and feedback.
• Finish website coding with enough time for feedback from users or members.
• W3C compliance

9.0 Development Process
9.1 Phases & Roles

Project Initiation Pre-Production Production Post-Production
Prepare Proposal Design website Code and style web- Deliver final prod-
Meeting with client Finalize website’s site. uct, get sign off
to discuss project information archi- Client provides con- Produce & submit
goals, sign off on tecture tent and feedback final product docu-
proposal Prepare design doc- as desired mentation for DGM
ument Department
Meet with client to
sign off on design
9.2 Development Tools
Adobe Xd, Photoshop, Illustrator, Sketch, Word-press

ARSC-PROPOSAL
9.3 Development Team
Daniel Camargo - PM & UX Designer

Jordan Vane - Graphic Design & Developer
Will Plumb - Developer
Neal Wandja - Developer
9.4 Quality Control Process
To help ensure the quality of the final website, the DGM team will conduct usability and
functional testing throughout the development process. At the end of the process, the
DGM Team will have a representative sample of users (6-10) look at the finished product
and complete a user satisfaction survey.
The team will also incorporate the following client reviews and checkpoints to help
guarantee the client’s satisfaction with the final product:
• Proposal -- Sign-Off
• Design Document -- Design Review/Sign-Off
• Prototype -- Sign-Off
• Final Product Review -- Sign-Off

10.0 Timeframe
September October November December January February March April May
Project Initiation
Pre Production
Production
Post Production
Sign Off
Upon receiving all final deliverables, the client will sign-off on the project and complete
a user satisfaction questionnaire for the Digital Media Department. The questionnaire
asks clients to rate their perceptions of the final product as well as the quality of the
service and performance of the project.
11.0 Project Scope
The scope of this project is to simply reorganize and re-style the website as it current-
ly exists. For this, we will implement the use of a Content Management System (Word
Press).

ARSC-PROPOSAL
12.0 Cost Estimate

The cost estimation goes as follows:
Average time spent working per person we estimate to be between 8-16hrs/week, we will
take the average between the two which is 12 hours/week times by the project length which
is 33 weeks.
total amount of $/person for project = $25/hr 12 hrs = $300/person
$300/week 33 weeks = $9900 per person for entire project.
$9900 for each person (4 people total) = entire cost = $39600

13.0 Proposal Sign-Off
This document has been reviewed and the content and requirements
described therein conform to an agreed upon understanding of the
design need.
Project Name: __________________________________________________
Team
Team Member Team Member Signature Date

ARSC-PROPOSAL
Client
_________________________________________ ________________________
Name Title
_________________________________________ ________________________
Signature Date
Digital Media Advisor
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date
Digital Media Project Mentor (if applicable)
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date

DESIGN DOC
1.0 Strategy . . . . . . . . . . . . . . . . . . . . 17
2.0 Scope . . . . . . . . . . . . . . . . . . . .21
3.0 Structure . . . . . . . . . . . . . . . . . . . .23
4.0 Skeleton . . . . . . . . . . . . . . . . . . . . 24
5.0 Surface . . . . . . . . . . . . . . . . . . . .26
6.0 Work Breakdown . . . . . . . . . . . . . . .30
7.0 Budget . . . . . . . . . . . . . . . . . . . .31
8.0 Risk Assessment . . . . . . . . . . . . . . . . . . .32
9.0 Design Doc Sign Off . . . . . . . . . . . . . . . .34

ARSC- DESIGN DOC
1.0 Strategy
To help determine the strategy the DGM team will use for developing the ARSC redesign,
we first created a plan for designing the website. To better understand the potential target
audiences, the DGM team created multiple personas to assist understanding the audience
that would be interested in the website. After analyzing what we needed from these target
audiences, The DGM Team developed detailed profiles for each persona to represent typical
goals, behaviors, and attitudes of each audience. These detailed profiles are listed on the
pages that follow.
ARSC-Audio.Org - Project | Utah Valley University | Design Doc 17

1.1 Persona
Rick Jones Skills

• Web browsing
Age: 66 • Interpersonal skills
• Audio recording skills
Occupation: Retired audio Intrest

industry worker • Loves collecting things
• Loves collecting audio files
Statues: Married and novelties
• Enjoys meeting new people
• Enjoys getting involved in a
Location: Charleston, WV cause, especially now that
he is retired.
Bio
Rick Jones is a recently retired audio industry worker who loves collecting audio and recording music. He
has a lot of time on his hands now that he is retired. He wants to connect with people who share his love of
audio and wants to become more active in the community of audiophiles.
Goals
• Wants to engage in the community, specifically with other audiophiles.

• Wants to collect different recordings, for personal use as well as for the sake of collecting.
• Willing to support financially any cause that is audio related that he can be a part of
Needs
• An easy way (website) to access audio files and collections

• easy way to meet new people who share his love for all things audio
•
Frustrations
• Doesn’t enjoy using new technology or learning how to use it.

• Wants to gain access to the online audio community as easily as possible.
• Finds it harder and harder to connect with people his age due to societal changes and people being
disconnected.

ARSC- DESIGN DOC
1.2 Persona
Jennifer Smith Skills
• Audio recording
Age: 23 • Music producing
• Audio editing
• Music mixing
Occupation: Student
Major: Audio technology Intrest

• Audio file editing
Statues: SIngle • Audio file collecting
• Music recording
• Music producing
Location: Salt Lake City, • Vintage audio file collecting
UT
Bio
Jennifer has been in the audio program at the University of Utah for 3 years. She is nearly graduated and is
looking to access audio files of all types, specifically vintage recordings from years past. She will be using
many different files for her senior project and wants a way to access these easily.
Goals
• Wants to have access to all kinds of audio files.

• Wants access to vintage audio files from the past to use for her senior project coming up.
•
Needs
• A means to access audio recordings, specifically recordings dating to before 1950.

• Wants access to background information and audio info from before 1950, including history of the music/
recordings, history of the artists and producers etc.
Frustrations
• Doesn’t know how to find audio files, especially for her senior project.
• Has no access to vintage audio recordings.
• Doesn’t know how to find vintage recordings.
• Has no access to the background info behind each specific audio recording she is looking for.

1.3 Persona
Barlen Cardster Skills
• Bookkeeping
Age: 45 • History
• Audio recording
• Audio mixing
Occupation: Historian • Audio producing
Statues: SIngle
Intrest
Location: Logandale, OR • Audio file recordings
• Researching the history
of audio and music in the
United States.
• Archiving collected audio
recordings
• Learning about music
history
• Preservation of special
recordings
Bio
Barlen Cardster is a historian working as a professor at the university of Oregon. He teaches courses in the
audio major, specifically audio recording theory, and the history of music in the United States.
Goals
• He has students working on projects that need access to all sorts of audio recordings.
• He has personal research projects that require access to recordings from all musical eras in the United
States. His current project is a study of the effects of different music genres and recordings on biological
aspects of humans.
•
Needs
• A way to download and collect audio recordings and historical files and documents from all musical eras
in the history of the United States.
• Biographical and background information of recordings.
Frustrations
• Can’t find all types of audio files and recordings that he needs for his research.
• His students can’t find audio files and recordings they need for their projects.
• Lacks an easy interface that allows him to do his research

ARSC- DESIGN DOC
1.4 Strategy Conclusion
We concluded that to appeal to the needs and goals expressed by each of our prospective
users, the website needs to do the following:

• Be simple - all pages and media should be easily accessible and well organized
• Provide a satisfying user experience - simplify common processes on the site.
• Keep members and interested parties informed about the organization’s events.
• Provide information about ARSC so users can learn as much as possible about the organiza-
tion
2.0 Scope (functional requirements)
The initial phase of this project will focus on the structuring and redesign of an active web-
site where the addition of content to the website will be handed off to the organization’s
webmaster upon completion of the project. The table below illustrates each page on the
website, and what features or content that page will contain.

PDF files of Supplied by ARSC. Already located on their server.
conferences
Audio Recordings Supplied by ARSC. Already located on their server.
Images Supplied by ARSC. Already located on their server.
Google Analytics Data Supplied by ARSC.
Social Media Logins and information for adding those accounts supplied by ARSC

Donate ARSC enthusiast comes to the website to donate to the organization
Member login Member comes to site to login to view member-exclusive material
View recordings
User comes to website to listen to conference recordings
Social Media A user comes to the site and is able to see the latest social media posting pertaining
Interaction to the organization
Sidebar news The user will be able to access related news on the home page through simple
placeholder scrolling
Twitter Feeds
The user will have clear and easy access to the feeds associated with the company
social media account
Sidebar news
placeholder The user will be able to access related news on the home page through simple
scrolling
Accessibility Adhere to W3C guidelines on accessibility.

ARSC- DESIGN DOC
3.0 Structure

4.0 Skeleton
2 3
Desktop : Home 1
Main Features
Logo 1
Donate 2 3 7
Login 3
Member Showcase 4 5
News 5
Twitter Feed 6 4
Membeership Directory 7

ARSC- DESIGN DOC
Phone
The mobile version of this site will include

all screen resolutions up to 980 pixel
width. Screens with resolutions greater
than 980 pixels will be handled by the
Desktop version of the site.

5.0 Surface 2
1
3
4
1 Single bar for navigation
2 Nav items with multiple sub-pag-

es will be shown on hover of the
nav item. 5
3 Social media icons and important

links like Donate and Member
Login placed in header
4 Hero banner - big comforting im-

age across all pages
5 Popular pages placed higher on

page for importance 6
6 Membership benefits displayed

on home page as well
7 Expanded footer with Twitter

Feed and other important links
to make it accessible across all
pages
Click here to visit the Prototype

Prototype will go over in depth of the design layout. Be sure 7
to click the comment icon on the top to see commentary and
pinpoints on the design

ARSC- DESIGN DOC
2
1
Mobile navigation is laid out exact-
ly like desktop navigation, appear-
ing when a “hamburger” icon is
tapped in the top right corner.
2
Mobile page layout is pretty much
the same as the desktop, same
hero banner.
3
Horizontally spanning columns are
stacked when resolution meets
standard mobile size.

Color
The colors we chose are from the original ARSC website:
Black: Rgb (0,0,0)

Red: Rgb (184,29,40)
Gray: Rgb (230,231,232)
Font
Proxima Nova - Navigation, Heading Tags

Text: We chose Proxima Nova as the font because it goes
professionally with the target audience.

ARSC- DESIGN DOC
PROJECT
PLANNING
• 6.0 Work Breakdown.... 30
• 7.0 Budegt....... 31
• 8.0 Risk Assessement....... 32

6.0 Work Breakdown Structure & Schedule
Launch ARSC Project Start End Team Member
Project Initiation 8/30/17 10/16/17 Team
Conduct Kickoff meeting 9/8/17 9/8/17 Team
Prepare Proposal 9/10/17 10/7/17 Jordan, Dan
Client/advisor Review Proposal 10/10/17 10/15/17 Dan
Revise Proposal 10/15/17 10/20/17 Dan
Client/Advisor Sign Off 10/16/17 10/16/17 Team
Design Planning Start End Team Member

Information Architecture 10/17/17 10/19/17 Team
Sketching 10/20/17 10/31/17 Will,Neal
Wireframe 11/01/17 11/13/17 Jordan, Dan
Prepare Design Doc 11/14/17 11/19/17 Team
Revise Design Doc 11/20/17 12/15/17 Team
Development Start End Team Member

Create Page templates 1/8/18 1/9/18 Team
Customize CMS 1/10/18 1/24/18 Team
Write Site Text Content 1/25/18 1/31/18 Team
Program backend 2/1/18 2/14/18 Neal, Will
Integrate Media Content 2/15/18 2/28/18 Team
Alpha Release 3/1/18 3/9/18
Make Revision to Site 3/10/18 3/14/18 Neal, Will
Beta Release 3/15/18 3/15/18
Testing & Delivery Start End Team Member

Conduct Cross Browsing Test 3/25/18 4/4/18 Dan,Jordan
Conduct User Testing 4/5/18 4/14/18 Dan,Jordan
Make Revisions 4/15/18 4/24/18 Team
Prepare Final Report 4/25/18 5/1/18 Team
Launch Live Site 5/1/18 5/1/18 Neal, Will
Project Sign-Off 5/2/18 5/3/18 Team

ARSC- DESIGN DOC
Time Frame
September October November December January February March April May
Project Initiation
Pre Production
Development
Testing & Delivery
Sign Off
7.0 Budget
1. Average time spent working per person we estimate to be between 8-16hrs/week, we will
take the average between the two which is 12 hours/week times by the project length
which is 33 weeks.
2. Total amount of $/person for project = $25/hr 12 hrs = $300/person $300/week 33 weeks =
$9900 per person for entire project.
3. $9900 for each person (4 people total) = entire cost = $39600

8.0 Risk Assessement
8.1 Dependencies
Completing this project given the time and budget specified depends on the following:
• The ability to create website on time.

• Coordination of students’ schedules for collaboration.
• Adequate feedback from ARSC board.
8.2 Technical Risks
• Website bugs.
• Ability to effectively handoff control of addition and removal of content to ARSC.
8.3 Contingencies
• Availability of student volunteers to perform various duties.

• Oversight of project by faculty advisor.

ARSC- DESIGN DOC
8.4 Change Control Processes
It is possible that the project schedule and budget may be affected by change requests from
the client that come too late in the development process or that are so significant that they
change the scope and costs of the project. To help us manage changes, we will follow a sim-
ple change control process, which uses the Change Request Form included in the Appendix
Here is the process that should be followed:
1. If the client wishes to request a change during the development process, they should fill
out and submit the attached form to the project manager.
2. The project manager will review the impact of the request and possible solutions on the
project scope, schedule, and cost.
3. The project manager will make a recommendation and discuss it with the client.
4. Finally, the project manager and client will decide on the course of action that is mutually
agreeable and either authorize the change or put the change on hold.

9.0 Design Doc Sign-Off
This document has been reviewed and the content and requirements described
there in conform to an agreed upon understanding of the design need.
Project Name: __________________________________________________
Team

ARSC- DESIGN DOC
Client
_________________________________________ ________________________
Name Title
_________________________________________ ________________________
Signature Date
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date

FINAL REPORT
I. QA Testing
• 1.0 Usability Test Plan
• 1.1 Usability Test Results
• 1.2 Usability Test Summary
• 2.0 Functional/Compatibility Testing
• 3.0 User Satisfaction Survey

• 3.1 User Satisfaction Survey Test Plan
• 3.2 User Satisfaction Survey Results
• 3.3 User Satisfaction Summary
II. Post-Project Analyses
• 4.0 Schedule Analysis

• 5.0 Cost Analysis
III. Lessons Learned
• 6.0 What we learned

• 7.0 What we would do differently
IV. Sign Off
• Final Report Grading Form

• Final Project Sign-off Sheet
Appendices
• User Survey
• Time Logs (for all team members for the entire project---1st & 2nd semesters)
ARSC- FINAL REPORT
I. QA TESTING
This section of the document will go over the user testing and quality assurance to make sure
the new design establishes user satisfaction. Testing with users will help us determine any
bugs or flaws in the overall design early that need to be fixed before the final alpha phase.
1.0 Usability Test Plan

To conduct our testing we used two tabs on the same browser that had the original site and
the newly designed site.
Four volunteers offered to participate in our user study. One Female 65 years of age who is
familiar with computers. 67 male who moderately uses computers. A 29-year-old male who is
an expert in computers. A 45-year-old male who is advanced in computers. They all had the
same tasks
A) Donate $45 dollars to classical music Preservation.

B) Find where the latest twitter post is.
C) Find the Publication ARSC Guide to Audio Preservation and read more.
D) Find out when the next Annual conference is.
ARSC-Audio.Org - Project | Utah Valley University | Final Report 37

1.1 Usability Test Results

ARSC- FINAL REPORT

1.2 Usability Test Summary
Based on the user study we were able to cut around 10 to 20 seconds of time with each user
on the new website. The tasks were easier to complete and visual elements were easier to
see. Also, based on this user study there were no definitive difficulties in the design that were
found.
2.0 Functional/Compatibility Testing
Browser test on the following platforms: Chrome, Mobile Chrome, Firefox, Safari, Mobile Sa-
fari, Internet Explorer, and Android. The test was conducted on Devices such as iPad, tablet,
mobile devices, Mac, PC. All devices and browsers passed the usability tests conducted.
3.0 User Satisfaction Survey

Survery Questions
• Q1 - Was the Content Easy to Read/Under-

Our target audience are those who currently stand?
use ARSC-audio.org. A survey has been sent • Q2 - How Easy Was The Site To Navigate?
in an email to get the opinions of the overall • Q3 - Where you able to Find Twitter & Other
quality of the redesign. However, We didn’t Social Media?
receive much feedback. Our team had to send • Q4 - How Fast Did the Website Load?
the survey to fellow designers to gather their • Q5- What Internet Browser Did You Use?
responses. • Q6- Did you use a Desktop Computer Or
Mobile Device To Access ARSC.org?
• Q7 - What do you like the most about the
new ARSC.org?
• Q8 - What can we do to improve your expe-
rience?

ARSC- FINAL REPORT
3.1 User Satisfaction Survey Test Plan
Survey test plan will consist of feedback on the overall look and feel of the website. There
will be a total of eight questions that will be asked for current users of ARSC.org here is a link
to the survey created using Survey Monkey. https://www.surveymonkey.com/r/TS68HCP

3.2 User Satisfaction Survey Results
Q1
Q2

ARSC- FINAL REPORT
Q3
Q4

Q5
Q6

ARSC- FINAL REPORT
3.3 User Satisfaction Summary

Q7
What do you like the most about the new ARSC.org?

Imagery
4/26/2018 6:38 AM View respondent’s answers
Nice imagery and easy access to sign-in and donations.
4/25/2018 8:22 PM View respondent’s answers
Icon was interesting
4/25/2018 4:07 PM View respondent’s answers
Clean and easy to find information.
4/25/2018 3:56 PM
Q8
We received great feedback and with this made adjustments before the final release of the
website. The overall survey turned out positive. With the help of other designers to critique
the website helped us improve the experience of the website.

II: Post-Project Analyses
4.0 Schedule Analysis

Launch ARSC Project Start End Team Member
Project Initiation 8/30/17 10/16/17 Team
Conduct Kickoff meeting 9/8/17 9/8/17 Team
Prepare Proposal 9/10/17 10/7/17 Jordan, Dan
Client/advisor Review Proposal 10/10/17 10/15/17 Dan
Revise Proposal 10/15/17 10/20/17 Dan
Design Planning Start End Team Member

Information Architecture 10/17/17 10/19/17 Team
Sketching 10/20/17 10/31/17 Will,Neal
Wireframe 11/01/17 11/13/17 Jordan, Dan
Prepare Design Doc 11/14/17 11/19/17 Team
Revise Design Doc 11/20/17 12/15/17 Team
Development Start End Team Member

Create Page templates 1/8/18 1/9/18 Team
Customize CMS 1/10/18 1/24/18 Team
Write Site Text Content 1/25/18 1/31/18 Team
Program backend 2/1/18 2/14/18 Neal, Will
Integrate Media Content 2/15/18 2/28/18 Team
Alpha Release 3/1/18 3/9/18
Make Revision to Site 3/10/18 3/14/18 Neal, Will
Beta Release 3/15/18 3/15/18

ARSC- FINAL REPORT
Testing & Delivery Start End Team Member

Conduct Cross Browsing Test 3/25/18 4/4/18 Dan,Jordan
Conduct User Testing 4/5/18 4/14/18 Dan,Jordan
Make Revisions 4/15/18 4/24/18 Team
Prepare Final Report 4/25/18 5/1/18 Team
Launch Live Site 5/1/18 5/1/18 Neal, Will
Project Sign-Off 5/2/18 5/3/18 Team
Our team stayed pretty close to the schedule except for cross-browser testing. This was done
about 3 weeks after its original schedule because we had to bring the theme into Word-
Press. This delayed us a couple weeks in this test scenario. However, User testing and design
revisions, along with Design Doc and Proposal were all on time. Our client had also sent a
change request reform that took roughly about a week to complete. This did not delay us
behind schedule. We had this time set for revisions and changes.
5.0 Cost Analysis
The total cost was under what we originally had do to every team member not working on
what was originally planned. For example, one task was scheduled to have two team mem-
bers to complete cross function testing and only one team member was needed to complete
this task. Resulting in less total hours used for the whole project. We completed the project
under budget by roughly 12 hours resulting in savings of $300 to the client. More could have
been saved however, we ran into a few milestones that were challenging and time-consum-
ing. For example. Integrating the theme into Wordpress took longer than originally planned.

III: Leasons Learned
6.0 What We Learned

We learned that teamwork and everyone giving their very best would result in a successful
project. Projects at this scope definitely require a team effort and trying to accomplish this as
an individual requires far more work than one could accomplish.
Communication is key to completing tasks. This can be visual communication and verbal.
Having Trello to keep track of tasks was a great tool to have the entire team in the same boat.
Without it, we would have been too unorganized.
Completing work at the scheduled time is extremely important. Git hub is another tool that
the team used to learn. We learned a lot about Git and working together with a repository
since we haven’t done that before on a scale like what we did. Learned about pushing and
commits and how to not overwrite peoples work and some other concepts.
7.0 What We Would Do Different

One thing that we would have done differently is, build the website out with the theme al-
ready in WordPress, instead of building it separately and then putting it all in WordPress.
That probably would have saved a lot of time in developing.
More team meetings were we collaborate on work and tasks. If we had more meeting during
the development phase, things could have gone smoother. Again, this ties in with communi-
cation. More Communication the better.
Procrastination at the beginning of the project held us back. One thing we agreed on we
would change is starting the project in full gear so we didn’t have to overwork ourselves to
complete tasks on time.

ARSC- FINAL REPORT
SIGN OFF
FINAL REPORT - SIGN OFF
This document has been reviewed and the content and requirements described
there in conform to an agreed upon understanding of the design need.
Project Name: __________________________________________________
Team

ARSC- FINAL REPORT
Client
_________________________________________ ________________________
Name Title
_________________________________________ ________________________
Signature Date
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date
_________________________________________ ________________________
Name Title
________________________________________ ________________________
Signature Date

APPENDICES
• User Survey
• Time Logs - for all team members for the entire project---1st &
2nd semesters
• Search Engine Optimization
• Change Request Form
• Early Sketches
• StoryBoard
ARSC-Audio.Org - Project | Utah Valley University | APPENDICES 52

ARSC-APPENDICES
User Survey

ARSC-APPENDICES

Time Logs
DGM Capstone Project Time Log Name: Jordan Vane

Semester 1
Sprint 1
Date Task Description Time
8/30/17 Received the project, began looking through the website 1
9/6/17 1
Met with team, discussed the website, and scheduled a meeting with the contact for the project.
9/8/17 Met with contact, discussed scope of project, and what they wanted 1 done with the website
9/8/17 Filling out creative brief, submitting that and Project Initiation form. 1
9/13/17 Met with team and Mark to discuss next step in the project. Further1 discussion with team o
Sprint 1 Total 5
Sprint 2
9/18/17 Drafting Project Proposal 2
9/20/17 Meeting with Mark to go over Project Proposal 2
9/27/17 Revising, working on Final Draft of Project Proposal 2
10/2/17 Further revisions and design of Project Proposal 1
10/4/17 Finalizing proposal 3
10/4/17 Reviewing with Mark 0.5
Sprint 2 Total 10.5

Sprint 3
10/11/17 Revising Proposal 2
10/18/17 Working on Proposal 2
10/25/17 Working on information architecture and site map 2
10/26/17 Meeting with Kellie to go over Proposal 1
ARSC-Audio.Org - Project | Utah Valley University | APPENDICES

Sprint 3 Total
56 7
Sprint 4
10/26/17 Meeting with Kellie to go over Proposal 1
ARSC-APPENDICES
Sprint 3 Total 7
Sprint 4
11/1/17 Revising Proposal / Site mapping 3
11/8/17 Sketching 2
11/9/17 Sketching 2
11/15/17 Working on design document 2
Sprint 4 Total 9
Sprint 5
Sprint 5 Total 0
Semester 1 Total 31.5

1/15/18 Setting up github repository we will be using for site 1
1/16/18 Setting up dev environment 2
1/18/18 Reviewing possible ways to fulfill the project, either hard-coding entire
2 website or using a fr
1/24/18 Team meeting 1
1/28/18 Website coding 4
Sprint 1 Total 15
Sprint 2
1/31/18 Meeting with group 1
2/1/18 Reviewing code and progress 1
2/3/18 Installing bootstrap and rebuilding what we've already coded 3
2/12/18 Meeting with Neal, Rebuilding res of our starting design in bootstrap 4
2/13/18 website coding 1
2/21/18 meeting with Will to create new repo for bootstrap 1
2/21/18 meeting with project advisor 1
Sprint 2 Total 18
Sprint 3
2/26/18 Coding Website - Footer 2
3/6/18 Coding Website, Creating Pages 3
3/7/18 Coding Website, Creating Pages 3
3/7/18 Helping Dan set up dev environment 1
3/8/18 Deploying project to live server 1
3/9/18 Adding content to pages 1
3/12/18 adding content to pages 2
3/13/18 Coding Annual Conference and Chapters pages 2
3/13/18 Reconfiguring local dev environment to be served via Valet 1
3/14/18 Coding Chapters page 2
3/14/18 Meeting with project advisor and team 2
Sprint 3 Total 20
Sprint 4
3/28/18 Coding Website - Committees Page 4
3/29/18 Coding Website - Committees Page 3
4/2/18 Coding Website - Board of Directors Page 4
4/3/18 Coding Website - Fixing Footer 3
4/4/18 Finalizing theme of website, updating all pages 2
4/4/18 Team meeting, meeting with advisor 3
4/5/18 Researching ways to make a theme in wordpress 1
4/11/18 Importing website into wordpress theme 3
Sprint 4 Total 23
Sprint 5
4/16/18
4/17/18
Adding theme to WordPress
Adding content in WordPress
ARSC-Audio.Org
4/17/18
- Project | Utah Valley University | APPENDICES
Adjusting theme and content issues as per Kellie
3
3
1
58
4/18/18 Adding content in WordPress & Presentation 4
4/20/18 Finalizing content and adding user management plugin to wordpress 4
4/3/18 Coding Website - Fixing Footer 3
4/4/18 Finalizing theme of website, updating all pages 2
4/4/18 Team meeting, meeting with advisor
ARSC-APPENDICES
3
4/5/18 Researching ways to make a theme in wordpress 1
4/11/18 Importing website into wordpress theme 3
Sprint 4 Total 23
Sprint 5
4/16/18 Adding theme to WordPress 3

4/17/18 Adding content in WordPress 3
4/17/18 Adjusting theme and content issues as per Kellie 1
4/18/18 Adding content in WordPress & Presentation 4
4/20/18 Finalizing content and adding user management plugin to wordpress 4
4/25/18 Packaging up final assets (wordpress theme) and theme installation directions 4
Sprint 5 Total 19
Semester 1 Total 95

William Plumb
9/26/17 Worked on Project Proposal 1 hour
09/30/17 Gathering assets from Kellie 30 mins
10/4/17 Going over proposal 30 mins
10/11/17 Client section statement of need and history 30 mins
10/18/17 Project proposal 2 hours
10/25/17 Meeting to go over next phase of tasks 1 hour
11/1/17 Working on skeleton and meeting with Mark 3 hours
11/8/17 Meeting with team, working on design sketches, prototype and
user test
2 hours
11/9/17 Met with Kellie Johnson, talked about what they wanted on nav,
on homepage and showed sketches etc. Met with team and
worked on sketches
2 hours
11/16/17 Worked with group on finishing design doc rough draft, worked
on personas and skeleton and sketches and other parts of draft
etc.
3 hours

ARSC-APPENDICES
1/27/18 Time: 3 hours

Time: 2 hours - 03/17/18
trying to get local server figured out( xampp) and Small changes to code
github Changed nav item positions
1/29/18 Working on paypal form
Time:3.5 hours Changed page slides
Added content to home page Time: 1 hour
Changed html files to php files 03/26/18
Put repeated code ( headers, nav, footer etc.) into Donate page
php files to be more efficient Time: 3 hours
Created form and form css 3/27/18
Figured out terminal, git etc. Donate page
1/31/18 Time:1 hour
Time: 5 hours 3/30/18
Added content to index(home) page Membership page, donate page
Added content to all other pages Time: 4 hours
Added php files/code to all other pages 4/2/18
Added styles to all pages About page, contact page
Worked with team members on scss transition Time:2 hours
4/10/18
Feb 8 / 2 hours / looked at bootstrap and tried figur- Met with kellie
ing out columns Time:30 mins
Feb 10 / 2 hours / UI fixes, coded and worked on nav
and top bar with bootstrap etc. 4/18/18
Feb 12 / 2 hours / practiced jQuery and javascript Changed logo link
Feb 15 / 3 hours / UI changes arsclist/arsclib page creation
Feb 18 / 3 hours / messed with elements like buttons, Blog page link
boxes, font, background pics News page changes
Feb 21 1 hour / met and discussed project Time: 2 hours
4/23/18
03/02/18 Journal page
Time: 1 hour Time: 2 hours
Coded some of the content in other pages 4/26/18
03/04/18 Went over site, made sure there weren’t loose ends
Time: 1 hour Time: 1 hour
Messed with some PHP 4/30/18
03/07/18 Met with group went over final report etc.
Time: 3.5 hours Time: 3 hours
Met with group, worked on stuff together, homep-
age, nav, footer etc.
03/15/18
Small changes to random things

20-Sep Started working on the proposal draft 2
4-Oct Proposal work 1
11-Oct Proposal work and Trello Creation 1
14-Oct Proposal work and Trello management, Email to clients 2
15-Oct Proposal and Project Management 1
25-Oct Project Management - Assigned work to team members and finished proposal1 1
DGM Capstone Project Time Log

26-Oct Went over Proposal with Kellie 1
Sprint 1 Total Daniel 12Camargo
Sprint 2 Semester 1
Sprint
Date1 Task Description Time
Date5-Nov Project management
Task Description - Assigned work Time 2
11/10/18
9/8/18 Emails to client. Information
First meeting with Kellie architecture, Sketching 1 3
15-Nov
12-Sep DesignonDoc
Research draft
ARSC website. Email to client 1 2
17-Nov
13-Sep Sketching
Meeting and Information
with Jordan Architecture
Vane to figure out next step 1 2
20-Nov
20-Sep Site working
Started Map - Sketching - Trello draft
on the proposal 2 1/2
22-Nov
4-Oct Sketching
Proposal work- Wireframes 21 1/2
25-Nov
11-Oct Wireframes
Proposal work andTrello
Trello Creation 1 2
28-Nov
14-Oct Email,work
Proposal Trello,
andWireframes, Presentation
Trello management, Email to clients 2 2
30-Nov
15-Oct Surface, Trello
Proposal and Project Management 1 1
25-Oct Sprint
Project Management - Assigned work to team members and finished proposal1 2 Total
1 19
Sprint 3
26-Oct Went over Proposal with Kellie 1
Date Task Description SprintTime
1 Total 12
Sprint 2
Feb 21st
Date1-Dec TaskSurface treatment - Design doc
Description Time 2
2-Dec
5-Nov Design
Project Doc , Surface
management treatment
- Assigned work 2 2
3-Dec
11/10/18 Sitetomap
Emails , Designing
client. Information architecture, Sketching 3 2
4-Dec
15-Nov Surface
Design , Design Doc, Presentation
Doc draft 2 3

17-Nov
20-Nov
Sketching and Information Architecture
Site Map - Sketching - Trello
2
2 1/2
22-Nov Sketching - Wireframes Semester 2 2 1/2
Sprint
25-Nov 2 Wireframes Trello 2
28-Nov
Date Email, Trello, Wireframes,
Task Description Presentation Time 2
30-Nov
9/8/18 Surface, Trello
First meeting with Kellie 1 1.2 9
Sprint 2 Total 19
12-Sep Research on ARSC website. Email to client 1 1/5
Sprint 3
13-Sep Meeting with Jordan Vane to figure out next step 1.2
Date20-Sep TaskStarted
Description
working on the proposal draft Time 1.2
Feb 4-Oct
21st Proposal work 1.2
1-Dec
11-Oct Surface treatment
Proposal - Design
work and Trellodoc
Creation 2 1.2
2-Dec
14-Oct Design Doc , Surface
Proposal work andtreatment
Trello management, Email to clients 2 1.2
3-Dec
15-Oct SiteProposal
map , Designing
and Project Management 2 1.2
4-Dec
25-Oct Surface , Design
Project Doc, Presentation
Management - Assigned work to team members and finished proposal2 3 1.2
Semester 2
Sprint 2 Sprint 4 Total 8.4
DateSprint 5 Task Description Time
9/8/18
Date FirstTask
meeting with Kellie
Description Time 1.2 9
12-Sep Research on ARSC website. Email to client 1 1/5
13-Sep Meeting with Jordan Vane to figure out next step 1.2
20-Sep Started working on the proposal draft 1.2
4-Oct Proposal work 1.2
11-Oct Proposal work and Trello Creation 1.2
14-Oct Proposal work and Trello management, Email to clients 1.2
15-Oct Proposal and Project Management 1.2
25-Oct Project Management - Assigned work to team members and finished proposal2 1.2
Sprint 5 Total 0
62
Semester
Sprint 4 1 Total
Total 48.4
8.4
Sprint 5
1-Feb Coding main page 1
2/2/18 Cropping & Editing Images used for site 1
ARSC-APPENDICES
5-Feb Email & Coding 2
10-Feb New Fonts & Design work 2
13-Feb Strategy and Design 2
15-Feb New Page Layouts 2
18-Feb New Page Layouts 2
19-Feb Polishing on existing design work 1
20-Feb User testing creation 3
Sprint 7 Total 16
Sprint 8
24-Feb Website coding and design 1
28-Feb Finding and adding Images 1
1-Mar Email & Coding 2
3-Mar Working on changes to the site that did not follow the design doc 2
5-Mar assigning work to group 1
7-Mar Worked with group on site 1
10-Mar Email Kellie, Slack, UX Survey work 2
12-Mar Design for new pages 2
14-Mar Team meeting and design polishing 1
Sprint 8 Total 13
Sprint 9
15-Mar Trello,Email, Slack 1
16-Mar Project management Work assignment 1
18-Mar Started Presentation Template, Emails 2
22-Mar Worked with group on site 1 1/2
26-Mar User testing survey and scenario 2
1-Apr Presentation and final Documantation work 1 1/2
4-Apr Team Meatting, Documantation, Trello Emal,Draft review 2
8-Apr Group Work, Design critique 2
11-Apr Draft review with Client, emails, team group work 2
Sprint 9 Total 15
Sprint 10
10-Apr Presentation, Trello 2
11-Apr Email Kellie, Slack, Presentation practice, Client draft meeting 2
13-Apr Final Documantation work, User testing 2
15-Apr Final Documentation work, User Survey 3
20-Apr Final Documentation, Trello Final Report 2
21-Apr Final Documentation, Final Report, Trello 3
23-Apr Final Report 1
25-Apr Final Documentation, Final Report, Trello 2
27-Apr Final Documentation, Trello, Final Report 5
30-Apr Gathering all project assests. Bounding documentation for final 2
Sprint 10 Total 22
Semester 2 Total 76.5
Project Total 124.9

DGM Capstone Project Time Log Name: Neal Wandja
Semester 1
Sprint 1
9/6/17 First team meeting with project supervisor; Mark Youngquist. The first task was to get in1contact with Kellie Johnson, our liaison to the client.
9/13/17 Second team meeting with project supervisor. Due to some inconveniences at my work, I1made it late to the meeting but Jordan filled me in with everything and we planning on meeting up again on
Sprint 1 Total 2
Sprint 2
Sprint 2 Total 0
Sprint 3
Sprint 3 Total 0
Sprint 4
10/11/17 Met with the group to work on the proposal to meet requirements and attended
2 our weekly meeting with Mark, and got the assigned task done
10/18/17 Met the group to work on the completion of the proposal before final submission
2 and attended weekly meeting with Mark
10/25/17 Met with the group to over the next phase and breakdown the work, and completed
2 the assigned task.
10/26/17 Met with Dan to go over the feed back we got from the organization 2
11/1/17 Met with the group to work on the skeleton and site mapping of the redesign
3 website, and establish requirements and needs
11/8/17 Attended the weekly meeting with Mark 1
11/9/17 Meet with the group to work on the site map, and attended meeting with Kellie
2 to get her input on the site design
11/15/17 Met with the group to work on the design doc and attended the weekly meeting
1 with Mark
Sprint 4 Total 15
Sprint 5
11/16/17 Work on the design doc and the wireframe and the surface 2
11/29/17 Worked on the surface 2
11/30/17 Worked on the surface and design doc 2
12/6/17 Meet with the group to do some more work on the surface and prototype and
2 the design doc before the presentation.
12/11/17 Meet with the group and Mark, and worked on completing the documentation
3 before sending it back to Kellie for final review and signoff.
Sprint 10 Total 11
Semester 5 Total 28
Semester 2
Sprint 6
1/28/18 Watched videos on how to convert a template into a wordpress theme and connected2to the group git repository
1/29/18 Worked cleaning up and restructuring the code provided by teammates 3
1/31/18 Created footer for the home page and added more content to the home page. 3
ARSC-Audio.Org - Project | Utah Valley

Sprint 7
Date Task Description
University
Sprint 6 Total 13 | APPENDICES
Time
64
2/3/18 Worked on refining the home page 2
2/4/18 worked on refining the home page 3
11/9/17 Meet with the group to work on the site map, and attended meeting with Kellie
2 to get her input on the site design
11/15/17 Met with the group to work on the design doc and attended the weekly meeting
1 with Mark
Sprint 4 Total 15
ARSC-APPENDICES
Sprint 5
11/16/17 Work on the design doc and the wireframe and the surface 2
11/29/17 Worked on the surface 2
11/30/17 Worked on the surface and design doc 2
12/6/17 Meet with the group to do some more work on the surface and prototype and
2 the design doc before the presentation.
12/11/17 Meet with the group and Mark, and worked on completing the documentation
3 before sending it back to Kellie for final review and signoff.
Sprint 10 Total 11
Semester 5 Total 28
Semester 2
Sprint 6
1/28/18 Watched videos on how to convert a template into a wordpress theme and connected2to the group git repository
1/31/18 Created footer for the home page and added more content to the home page. 3
Sprint 6 Total 13
Sprint 7
2/4/18 worked on refining the home page 3
2/14/18 Fixed codes before merging work with teammates 3
Sprint 7 Total 16
Sprint 8
2/16/18 Started to work on other required page for the site 2
2/17/18 Designing the membership directory page 3
2/18/18 Working on improving the design of the home page 3
2/20/18 Working on the directory page 2
2/21/18 Started the donate page 2
2/28/18 Worked on design the pages 3
3/7/18 Met with the group to compile what we have been working on so far 2
3/9/18 Worked on merging my codes with jordans since we've working on 2 different frameworks
3
Sprint 8 Total 20
Sprint 9
3/11/18 Worked on the css 2
3/17/18 Starting populating other pages and worked on the css 3
4/11/18 Met with Kelley 1
Sprint 9 Total 15
Sprint 10
4/17/18 Met with the group to on our presentation plan 2
4/18/18 Worked on the website for last clean up before presentation 3
4/19/18 Worked on the publication page 3
4/20/18 Finish styling of the publication and resources page 4
4/25/18 Final project showcase 4
65
Sprint 10 Total 16
Semester 2 Total 80
SEARCH ENGINE OPTIMIZATION:
We will be implementing basic SEO practices throughout the website to be accessible to as many people as
possible. A keyword we will target is “arsc”.

ARSC-APPENDICES
Change Request
Organizational Notes:
• Website: arsc-audio.org
• See aes.org for similar look and feel of homepage and footer
• See uvu.edu/cet for look and feel of single page style menu
• Homepage access attach to logo and delete from menu

• Add Social Icons for LinkedIn and WordPress (for the blog)
• Add Contact information to footer and delete from top menu
• Longer Text: on some buttons (Membership and Committees pages for example)
disappears off of button on phone/tablet
• Join/Donate Buttons in footer: Change to white with dark red color text for better contrast
• Go button on Login page: Change to white with dark red color test for better contrast
• Logos high resolution images

https://www.dropbox.com/sh/jhx7dwp6mbfhydv/AACbbFXTD5WTvkeZtd_1xnrCa?dl=
0
Homepage: Can you make this accessible via the logo only to reduce clutter?
Conference
News (keep static)
About ARSC
[AMP Search]
Why Join ARSC?
Menu Items/order (see aes.org) Delete Drop down options and incorporate those on the pages:
Home (Remove)
Membership (One Page):

• Benefits
• Join/Renew
• Donate
• Membership Directory
Community (One Page):

• Board of Directors
• Committees
• Chapters
• Listservs (ARSCLIST and ARSCLIB)
Conference
• Current Conference
67
• Past Conferences Information Links

Early Sketches
Home 1 Home 2
Home 3 Membership Sign-up

ARSC-APPENDICES
Story Board
Rick Jones is a retired audio industry worker who recently heard about the ASRC, what they do and what
they represent, through his longtime friend who he shares the same passion of music with. His first time
using the site was a bit confusing for him because he had a hard time navigating through the site, espe-
cially during his attempt to access the newsletters and the conference page.
He is recurring steps to access the site would be to do a basic search of the ARSC site on google search
engine, using his laptop, then been redirected to the home page of the site. Mainly, his goal is to get to the
publication page, where he usually gets informed of all trending news and upcoming events. But unfortu-
nately, he doesn’t think the site is well organized, and struggle every time to get to the right directory.
He hates the fact that he has to click multiple links every time just to access the one he’s looking for. He
would like the site to be a bit more comprehensive and easy to use, especially considering his age range.

END

ARSC-Audio Design Document Full Report.

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ARSC-Audio Design Document Full Report.

Încărcat de

Drepturi de autor:

Formate disponibile

ARSC -

ARSC-Audio.Org - Project | Utah Valley University | ARSC Web Team 2

• 7.0 Audience & Stakeholders ...... 7

8.1 Data/Content Requirements

• 9.0 Development Process........ 10

9.1 Phases & Roles

2.0 Statement of Need

There needs to be restructuring of the website’s navigation to a more simplistic approach,

ARSC-Audio.Org - Project | Utah Valley University | Proposal 4

3.0 Client Goals

• Have a website more directed towards the organization’s audience.

4.0 Proposed Solution

ARSC-Audio.Org - Project | Utah Valley University | Proposal 5

• Project initiation agreement

6.0 Success Metrics

bers with prototypes and completed product

by amount of time it takes to find certain files

• Increased improvement in Information Architecture and user satisfaction. Surveys

will be conducted to test overall satisfaction

ARSC-Audio.Org - Project | Utah Valley University | Proposal 6

7.0 Audience & Stakeholders

• ARSC members & prospective members looking to join

• President: Matthew Barton (Library of Congress)

ARSC-Audio.Org - Project | Utah Valley University | Proposal 7

8.1 Data/Content Requirements

• PDF files for conferences

8.2 Functional Requirements

ARSC-Audio.Org - Project | Utah Valley University | Proposal 8

8.3 Product Qualities

ARSC-Audio.Org - Project | Utah Valley University | Proposal 9

9.1 Phases & Roles

9.2 Development Tools

Adobe Xd, Photoshop, Illustrator, Sketch, Word-press

ARSC-Audio.Org - Project | Utah Valley University | Proposal 10

9.3 Development Team

Daniel Camargo - PM & UX Designer

9.4 Quality Control Process

ARSC-Audio.Org - Project | Utah Valley University | Proposal 11

September October November December January February March April May

11.0 Project Scope

ARSC-Audio.Org - Project | Utah Valley University | Proposal 12

12.0 Cost Estimate

ARSC-Audio.Org - Project | Utah Valley University | Proposal 13

Project Name: __________________________________________________

Team Member Team Member Signature Date

ARSC-Audio.Org - Project | Utah Valley University | Proposal 14

Digital Media Advisor

Digital Media Project Mentor (if applicable)

ARSC-Audio.Org - Project | Utah Valley University | Proposal 15

2.0 Scope . . . . . . . . . . . . . . . . . . . .21

3.0 Structure . . . . . . . . . . . . . . . . . . . .23

5.0 Surface . . . . . . . . . . . . . . . . . . . .26

6.0 Work Breakdown . . . . . . . . . . . . . . .30

7.0 Budget . . . . . . . . . . . . . . . . . . . .31

8.0 Risk Assessment . . . . . . . . . . . . . . . . . . .32

9.0 Design Doc Sign Off . . . . . . . . . . . . . . . .34

ARSC-Audio.Org - Project | Utah Valley University | Design Doc 17

Rick Jones Skills

Occupation: Retired audio Intrest

• Wants to engage in the community, specifically with other audiophiles.

• An easy way (website) to access audio files and collections

• Doesn’t enjoy using new technology or learning how to use it.

ARSC-Audio.Org - Project | Utah Valley University | Design Doc 18

Major: Audio technology Intrest