Tanager

Vision

Version 2.1 – Elaboration Phase 2

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

Table of Contents

1 Introduction. 5

1.1 Purpose. 5

1.2 Scope. 5

1.3 Definitions, Acronyms, and Abbreviations 5

1.4 References 5

1.5 Overview.. 5

2 Positioning. 5

2.1 Business Opportunity. 5

2.2 Problem Statement 6

2.3 Product Position Statement 6

3 Stakeholder and User Descriptions 6

3.1 Market Demographics 6

3.2 User Environment 7

3.3 Stakeholder Profiles 7

3.4 User Profiles 7

3.4.1 Playlist Administrator 7

3.4.2 Music Listener 7

3.5 Key Stakeholder or User Needs 8

3.6 Alternatives and Competition. 8

3.6.1 <aCompetitor>. 9

3.6.2 <anotherCompetitor>. 9

4 Product Overview.. 9

4.1 Product Perspective. 9

4.2 Summary of Capabilities 9

4.3 Assumptions and Dependencies 9

4.4 Cost and Pricing. 9

4.5 Licensing and Installation. 9

5 Product Features 9

5.1 <aFeature>. 9

5.2 <anotherFeature>. 9

6 Constraints 9

7 Quality Ranges 9

8 Precedence and Priority. 9

9 Other Product Requirements 9

9.1 Applicable Standards 10

9.2 System Requirements 10

9.3 Performance Requirements 10

9.4 Environmental Requirements 10

10 Documentation Requirements 10

10.1 User Manual 10

10.2 Online Help. 10

10.3 Installation Guides, Configuration, and Read Me File. 10

10.4 Labeling and Packaging. 10

A. Feature Attributes 10

A.6 Target Release. 11

A.7 Assigned To. 11

A.8 Reason. 11

Vision

1 Introduction

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 fulfils 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 information can be found in the Use Case Model and Supplementary Specification.

1.1 Definitions, Acronyms, and Abbreviations

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

1.2 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/>.

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. 09 August, 2005 <http://gentleware.com/index.php?id=poseidon_for_uml>.

1.3 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

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.4.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.5 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.

4 Product Overview

5 Product Features

5.1 <aFeature >

5.2 <anotherFeature >

6 Constraints

7 Quality Ranges

8 Precedence and Priority

9 Other Product Requirements

10 Documentation Requirements