The vision for Tanager is that it will be a full-featured media player that will support multiple media types (AIFF, AU, AVI, MIDI, MP2, MP3, QT, RMF, WAV).

1.1 Purpose

The purpose of this document is to collect, analyze, and define high-level needs and features of the Tanager system. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist. The details of how the Tanager system fulfills these needs are detailed in the use-case and supplementary specifications.

1.2 Scope

This document will summarize the high-level requirements of the Tanager system and the business case for the project. More detailed information can be found in the Use Case Model and Supplementary Specification.

1.3 Definitions, Acronyms, and Abbreviations

A complete list of definitions, acronyms, and abbreviations can be found in the Tanager Glossary.

1.4 Diagrams

All diagrams in the Tanager system documentation will be generated using Gentleware’s Poseidon for UML tool.

1.5 References

Bar, Moshe, and Karl Fogel. Open Source Development with CVS. Scottsdale, AZ: Paraglyph Press, 2003.
10 August, 2005 <http://cvsbook.red-bean.com/OSDevWithCVS_3E.pdf>.

CVSNT. 2005. March Hare Pty Ltd. 12 September, 2005 <http://www.march-hare.com/cvsnt/>.

Fowler, Martin. 2004. UML Distilled. Boston MA: Addison-Wesley. 09 August, 2005 < http://www.awprofessional.com/bookstore/product.asp?isbn=0321193687&rl=1>.

Java Media Framework. 2005. Sun Microsystems. 09 August, 2005 <http://java.sun.com/products/java-media/jmf/>.

Java Runtime Environment. 2005. Sun Microsystems. 09 August, 2005 <http://java.com/en/about/>.

Larman, Craig. 2005. Applying UML and Patterns. Westford, MA: Prentice Hall. 09 August, 2005 <http://www.phptr.com/title/0131489062>.

Poseidon for UML. 2005. Gentleware AG. 20 January, 2007 <http://www.gentleware.com/uml-software-pe.html>.

1.6 Overview

This document will summarize the goals and problems of the Tanager project at a high level. It will describe the product goals, the various stakeholders and users and their responsibilities, the features of the product, and the nonfunctional requirements of the product.

2 Positioning

2.1 Business Opportunity

While there are many media players on the market today, few of them support a large range of media types. Users that wish to play many different media types must use several different players, each of which has different feature sets and user interfaces. Users report that dealing with different feature support and multiple user interfaces for each product they use is confusing, and we believe it is unnecessary. The Tanager product will be our first step in providing software-based and hardware-based products that support a wide range of media types and have identical feature sets and user interfaces. The Tanager product will be a software-based media player, which plays a wide variety of media types, and it will serve as the base for a line of follow-on hardware-based products.

2.2 Problem Statement

The problem of	multiple user interfaces
affects	media player users
the impact of which is	confusion about how to operate different media players
a successful solution would be	software-based and hardware-based media players with identical user interfaces.

The problem of	multiple feature sets
affects	media player users
the impact of which is	confusion and time wasted trying to figure out how to utilize the player’s features
a successful solution would be	software-based and hardware-based media players with identical feature sets.

The problem of	limited media type support
affects	media player users
the impact of which is	users must utilize many different media players
a successful solution would be	a single player that supports a wide range of media types.

2.3 Product Position Statement

For	media player users
Who	have many different media types they wish to play
The Tanager	is a software-based media player
That	plays AIFF, AU, AVI, MIDI, MP2, MP3, QT, RMF, and WAV files
Unlike	Microsoft Windows Media Player, which cannot play QuickTime audio files, or iPod, which cannot play Windows Media Files
Our product	Tanager will play QuickTime audio files and many other types of audio files, and it allows the user to need to know only a single feature set and user interface.

3 Stakeholder and User Descriptions

3.1 Stakeholder Profiles

There are no non-user stakeholders. See Section 3.2 for descriptions of the users.

3.2 User Profiles

3.2.1 Playlist Administrator

Description	Wants to be able to download songs to the system, remove previously downloaded songs, and view the list of downloaded songs.
Type	The music downloader could have any level of experience with this or other digital music players. They should understand the concept of downloading music to the player.
Responsibilities	· Turns system on & off · Downloads songs · Removes downloaded songs · Views list of downloaded songs
Success Criteria	Success is defined by the list of downloaded songs accurately showing those songs that have been downloaded and not removed.
Involvement	This stakeholder will be involved in the requirements-gathering process, and they will be involved in testing implemented solutions.
Deliverables	This stakeholder requires a user’s guide describing the system’s functionality.
Comments / Issues

3.2.2 Music Listener

Description	Wants to be able to play music that has been previously downloaded to the system.
Type	The music downloader could have any level of experience with this or other digital music players. They should understand the concept of playing music on a digital music player.
Responsibilities	· Turns system on & off · Plays songs · Skips songs · Repeats songs · Views list of downloaded songs · Adjusts the volume
Success Criteria	Success is defined by the user’s ability to play songs that have been previously downloaded to the system.
Involvement	This stakeholder will be involved in the requirements-gathering process, and they will be involved in testing implemented solutions.
Deliverables	This stakeholder requires a user’s guide describing the system’s functionality.
Comments / Issues

3.3 Key Stakeholder or User Needs

Need	Priority	Concerns	Current Solution	Proposed Solutions
Single user interface for software-based and hardware-based media players.	1	Users must know how to operate multiple user interfaces for hardware-based and software-based media players.	iTunes and iPod have very different user interfaces.	Very similar user interface for Tanager and its follow-on hardware-based product.
Single feature set for software-based and hardware-based media players.	2	Users must cope with features that are supported on either software-based or hardware-based media players but not both.	iTunes and iPod have very different feature sets.	Very similar feature set for Tanager and its follow-on hardware-based product.
Broader media type support.	3	User must use multiple media players to play their various types of audio files.	iPod does not support Windows Media files (.wma) and Windows Media Player does not support QuickTime audio files.	Tanager will support as many types of media files as possible.

3.4 Alternatives and Competition

All of the competitive products have the drawback of having different look-and-feel for the hardware- and software-based products. There is a benefit in tailoring the software-based product to take advantage of the large screen size of the computer it’s running on, but that adds one additional system that the user has to master. Similarly, the competitive products take advantage of the computing power of the host machine to add features such as adding the ability to sort displayed lists. These features aren’t present on the hardware-based products, which can be confusing to users.

3.4.1 Apple iPod

The Apple iPod is a hardware-based music player, and its software-based counterpart is iTunes. The iPod supports AAC, MP3, Audible, Apple Lossless, AIFF and WAV formats. iTunes supports the same base set of formats, but with additionally-installed components it can also play Ogg-Vorbis, Speex and other obscure formats. Notably, neither supports the WMA format.

3.4.2 Creative Zen

The Creative Zen is a hardware-based music player, and its software-based counterpart is Creative MediaSource Player/Organizer. Zen supports MP3, WMA, WAV and Audible formats, but MediaSource only supports MP3 and WMA formats.

3.4.3 Microsoft Zune

The Microsoft Zune is a hardware-based music player, and its software based counterpart is Zune Software. Despite having the same name, they are far from similar. Zune supports only WMA and MP3 formats, while Zune Software supports WMA, MP3, and AAC.

3.5 Product Overview

Tanager will be a full-featured music player that allows the user to download and play digital audio music in a wide variety of formats.

3.6 Cost and Pricing

The software-based Tanager Media Player will be released as freeware. The cost and pricing of future hardware-based products will be determined by the component costs.

3.7 Licensing and Installation

The software-based Tanager Media Player will be released under the BSD license. See Section 13 of the Supplementary Specification.

4 Product Features

4.1 Download Songs

The user will be able to download songs to the Player. The user will be able to download a wide variety of different formats without having to install additional components. They will also be able to delete songs that were previous downloaded.

4.2 View Downloaded Songs

The user will be able to view a list of all the songs they have downloaded to their player.

4.3 Play Songs

The user will be able to play the songs they have downloaded to their player. They will also be able to choose different ordering methods for the songs to play in: random ordering, alphabetical ordering, etc.

4.4 Manipulate Playing Songs

The user will be able to pause a song, stop a song, skip over the current song to either the next song or the previous song, or restart the current song. They will also be able to change the volume of the playing song.

5 Revision History

Date	Version	Description	Author
14 Nov, 2005	1.0 - Inception Phase	First draft. To be refined in the elaboration phase.	Bob Lavey
01 Dec, 2005	1.1 – Inception Phase	Revised with comments from Dr. Leavens’ review.	Bob Lavey
24 Oct, 2006	2.0 – Elaboration Phase 1	Revised with comments from Dr. Leavens’ review.	Bob Lavey
10 Jan, 2007	2.1 – Elaboration Phase 2	Updated with comments from Dr. Leavens’ review.	Bob Lavey
26 Jan, 2007	4.0 – Elaboration Phase 4	Filled out remaining portions of the document and deleted sections that were irrelevant or were duplicated in the Supplementary Specification.	Bob Lavey