User Manual

Confidential - Do Not Distribute Revision A - Sep. 9 2011 page 4 of 18
1 Document Scope
This document describes in engineering development terms the definition of Deckard. This document will
define the engineering platform with enough detail to meet the initial product concept while not
constraining the execution team on specific intricate design details.
This document is also a description of the functional behavior with sufficient detail in order to achieve an
accurate quotation, begin writing user guides and to begin developing test methods.
1.1 Definition of Terms
Shall – Term indicates a required element, e.g., "the unit shall play MP3 files".
Should – Term indicates a suggestion or preference, e.g., "the unit should attempt to read ID3V1 tags".
May – Term indicates an allowance, e.g., "the unit may play FLAC files".
Will – Term indicates a statement of fact. This is typically information used for clarity, such as "the unit
will be sold in France".
1.2 Notation
Requirements are divided into sub-sections based on system division and implementation conventions.
Each requirement is labeled as [Rx], where ‘R’ represents the ‘Requirement’ and ‘x’ marks the serial
number of each requirement.
1.3 Highlight Color Codes
Color:
Meaning:
Blue Highlight
Indication of changes since the last revision
Green Highlight
Known open issues needing further clarification
Purple Highlight
Questions or notes for reviewers
Red Highlight
Incomplete sections
Gray text with strikethrough
Deleted sections