Device Requirements

The following table links, tracks, prioritizes, and classifies requirements for the device. These requirements are an update of those listed in the Scenarios and Requirements doc from 11 Nov 2007.

Requirement Types

Key

  • The formatting used (red/bold/italics/etc) provides no new information — it just tries to highlight important requirements and minimize (with italics) things less important, based on the Target and Pri info.
  • The Pri number is not about the priority of the feature in the final product — it's only about the importance for the indicated milestone. This is why Pri 3 requirements that are targeted at the current phase/upcoming milestone always also list what the priority would be if the requirement gets pushed back a milestone. For example, some things might only be nice to have in the Benetech demo (at M2), even if they are essential for the final product.
  • Any P1 or P2 requirement targeted for the current milestone is in bold. The P1 requirements are also in red.
  • Any P3 requirement for the current milestone is in plain type; but, a second priority is always listed to indicate its relative importance if it must slip to the next milestone.
  • Any requirement targeted at a milestone beyond the current milestone is in italics, no matter how high the priority is for it to eventually get done. Italics is applied to any requirement with a target milestone that is not the one currently being worked on (e.g. M2 for hardware), in an attempt to make it easier to browse the list of requirements without being too distracted by items that aren't even planned to get done by that milestone. So, if we know we don't want to even try to get a requirement covered by the Benetech preview (unless all other targeted requirements are done), we will target it at M3, which causes the requirement to be listed in italics, even if it's a Pri 1 requirement to be done by M3.
  • Any requirement that has either been forever removed (e.g. duplicates another requirement) or just cut from this version (indicated by PX) is in strikethrough text.

Storage Requirements


User Content Storage
ID Spec Target Pri Description Scenarios
SR1 storage M2 P1 The device can store a minimum of three hours of spoken content. n/a
SR2 storage M2 P1 The device can store multiple content modules. n/a
SR3 April 4th M2
M3		 P3
P3		 A user can erase a chapter from any content module that was recorded on their device. CS5
SR4 April 4th M2
M3		 P3
P1		 A user can erase any content module on their device. CS5


Device Content Storage
ID Spec Target Pri Description Scenarios
SR5 storage M2 P1 The device includes as many as 100 10-second System Audio Files used for indication and prompting for user input. These SAFs can be replaced with SAFs of a different language when the device is connected to a kiosk or computer with content authoring software. n/a

Play and Navigation Requirements


Simple Content Operations
ID Spec Target Pri Description Scenarios
NR1 nav M2 P1 The device can play recorded audio. CS1
NR2 nav M2 P1 The device can pause recorded audio. n/a
NR3 April 4th M2
M3		 P3
P3		 The device can automatically pause in response to "content-embedded pauses" at any point in a track/page. (These content-embedded pauses within a track can function as an analog of line separations within a page.) LS6
NR4 May 2nd M3 P3 The device has a setting to force continuous playback, regardless of track/page boundaries or content-embedded pauses. n/a
NR5 March 20th M2 P1 The device can skip to the next or previous content module. CS3
NR6 nav M2 P1 The device can skip to the next or previous track/page within a content module. LS6
NR7 March 27th M2 P2 The device can easily skip to the next or previous content-embedded pause. LS6
NR8 nav M2 P1 The device can jump back 15 seconds within a content module. CS3
NR9 nav M2 P1 The device can jump forward 60 seconds within a content module. CS3
NR10 speed M2 P2 The device can dynamically slow content playback (with constant pitch) based on user control from 50% to 100%. LS1
NR11 speed M2 P2 The device can dynamically speed up content playback (with or without constant pitch) based on user control from 100% to 200%. CS3
NR18 selection M2 P2 A user can quickly navigate to any one of 100 content modules residing on their device. n/a


Complex Content Operations
ID Spec Target Pri Description Scenarios
NR12 April 4th M2
M3		 P3
P2		 The device has multiple choice buttons OR just audio hyperlinks with return points later in track LS3
NR13 April 4th M2
M3		 P3
P3		 The device allows number answers to be submitted by tapping the hyperlink button a number of times during the prompt stage. LS3
NR14 nav M2
M3		 P3
P3		 The device has four (multipurpose?) buttons to answer multiple choice questions LS4,LS5
NR15 hyperlink M2 P1 The device can jump to and return from audio hyperlinked content in response to user pushing button LS5
NR16 April 4th M2
M3		 P3
P3		 The device has a play mode that causes all hyperlinks to be automatically followed without user action LS5
NR17 May 2nd M3 P3 Content modules can include embedded audio advertisements that cannot be skipped when played IS6,IS9

Input / Output Requirements


Recording New Content
ID Spec Target Pri Description Scenarios
RR1 record M2
M3		 P3
P1		 The device has a built-in microphone for audio input. CS5,IS3,
IS4,IS5,IS7
RR2 n/a n/a n/a The device has a connector where an external microphone can be plugged in. CS5
RR3 n/a n/a n/a deleted for redundancy with RR1 n/a
RR4 record M2
M3		 P3
P1		 A user can break up their recording into chapters within a content module. CS5
RR5 record M2
M3		 P3
P2		 A user can record over an existing chapter of any content module that was authored on the same device. CS5
RR6 n/a n/a n/a A user can record a new line and insert it into the beginning, middle or end of an existing page. CS5
RR7 record M2
M3		 P3
P2		 A user can record a new chapter and insert it before any existing chapter in any content module that was authored on the same device. CS5
RR8 n/a n/a PX The device can connect to a cell phone’s ear phone connector. CS12
RR9 n/a n/a PX The device has radio reception and tuner capability. CS13
RR10 n/a n/a PX The device can record the radio broadcast being received. CS13
RR11 record M3 P3 A user can give a title to each of their chapters, and these chapter titles will be used to automatically generate an initial Table of Contents chapter, composed of "non-returning hyperlinks". n/a


Audio Output
ID Spec Target Pri Description Scenarios
AR1 March 20th M2 P1 The device can adjust output volume. n/a
AR2 March 20th M2 P1 The device can play the audio on its built-in speaker. CS4,LS2
AR3 March 20th M2 P1 The device has a standard plug for an earphone. CS4,OS2
AR4 n/a n/a PX The device can play the audio and broadcast it as FM signal. The FM frequency can be adjusted. CS4,LS2


Transferring User Content
Note that the requirements in this section do not map to those in the 11 November document.
ID Spec Target Pri Description Scenarios
TR1 d2d-copy M2 P1 The device can copy content to another device using a direct physical connection. CS11
TR2 d2d-copy M2 P1 The device can copy a single selected piece of content to another device. CS11
TR3 May 2nd M3 P3 The device can copy all its content to another device, erasing any previous modules on the target device. n/a
TR4 n/a n/a PX The device can copy content to multiple other devices at once. CS9,IS1
TR5 May 2nd M3 P1 The device can copy content to/from a kiosk at a rate of > 1MB / minute CS10,LS1,
IS2,IS4
TR6 May 2nd M3 P2 The device can copy content to/from a computer at a rate of > 1MB / minute. CS7
TR7 May 2nd M3 P1 The device allows a kiosk or PC to erase any content module or all content modules. CS7,CS10
TR8 May 2nd M3 P4 The device will inhibit copying content modules that are tagged as not transmittable. The device will give a warning before deleting. IS9

Indicators and Instruction Requirements


Visual Indicators
ID Spec Target Pri Description Scenarios
IR1 April 4th M2
M3		 P3
P1		 The device has a light indicating the device is on with available battery power. CS1,CS16
IR2 April 4th M2
M3		 P3
P2		 Mode of Operation Indicator Light to indicate current states, including: playing, paused or idle (power on), recording, and copying. CS16
IR3 March 27th M2 P2 Hyperlink availability light near or on hyperlink button (to indicate when button is active to follow a link). n/a


Auditory Indicators / Instruction
ID Spec Target Pri Description Scenarios
IR4 hyperlink M2 P1 A subtle background tone is sounded underneath the main audio content during the availability of a hyperlink. n/a
IR5 April 4th M2 P1 The device has a "Welcome Message" that is permanent (non-erasable) and includes a recording of instructions on the operation of the device. CS1,OS1
IR6 n/a n/a n/a The "Welcome Message" contains a recording of instructions on the operation of the device. CS1,OS1
IR7 March 27th M2 P2 The device can aurally indicate content module's title upon pressing status button during playback or pause. CS2
IR8 March 27th M2 P2 The "Info/Help Message" is easily accessible at all times. CS2
IR9 March 27th M2 P2 Each content module can include its own its own "Help" instructions LS4

Power Requirements

Control of Power
ID Spec Target Pri Description Scenarios
PR1 power M2 P1 The device can be turned on-off. CS1
PR2 April 4th M2
M3		 P3
P2		 If the device goes to sleep mode while paused in the middle of a content module, it will remember the location in the content module. When the user turns the device back on and press play, the device will resume playing at the location where it was turned off or paused. CS14
PR3 April 4th M2
M3		 P3
P1		 If the device was paused and the user does not resume play within 2 minutes, the device will automatically shut off and remember the audio content location at which it was paused. CS14
PR4 n/a n/a n/a When the user turns the device back on and press play, the device will resume playing at the location where it was turned off or paused. (combined with PR2) CS14
Availability of Power
ID Spec Target Pri Description Scenarios
PR5 May 2nd M3 P1 The device can be powered by currently available carbon zinc disposable, D/R20 batteries for 10 hour capacity: 60 min per day x 10 days, 25% of through headphones, 10% recording, 15% of mid-volume, and 50% at full volume. CS15
PR6 May 2nd M3 P2 The device can be powered by two rechargeable, D/R20 batteries with a 20 hour capacity: 120 min per day x 10 days, 25% of through headphones, 10% recording, 15% of mid-volume, and 50% at full volume. CS15

Extensibility Requirements

System Update Extensibility
ID Spec Target Pri Description Scenarios
ER1 May 2nd M3 P2 The device software can be updated from a kiosk CS17
ER2 May 2nd M3 P4 The device includes an real time clock that the user may set and that would not get reset during a battery change if less than five minutes. (If necessary, this functionality could be moved to the kiosk in the first version.) n/a
Content-Based Extensibility
ID Spec Target Pri Description Scenarios

Mechanical and Industrial Design Requirements

Mechanical and Industrial Design
ID Spec Target Pri Description Scenarios
MR1 n/a n/a n/a The device includes a reading light. n/a
MR2 n/a n/a n/a The device includes a focused lamp to substitute as a flashlight. n/a
MR3 n/a n/a n/a The device includes ten numbered keys and two or four operator keys (+,-,x,/), which double as audio navigation controls. n/a
MR4 n/a M1 P1 The device includes a hole to loop a lanyard through. n/a
MR5 n/a M1 P1 The device is water resistant. It may not withstand being submerged in water, but it should do fine in a heavy thunder shower. Its normal operation will occur in regions of high humidity. n/a
MR6 n/a M1 P2 The device is striking and colorful. Not flashy, but far different looking from the typical dark and gray cheap electronics. n/a
MR7 n/a M1 P1 The device can operate in continuously in temperatures of 50 degrees Celcius / 120 degree Fahrenheit. n/a
MR8 n/a M1 P1 The device can operate in very dusty environments. Many target regions have significant dust storms during the dry season. n/a
MR9 n/a M1 P1 The device's memory card is accessible with locally available tools (e.g. flat head or philips head screwdriver) n/a
MR10 n/a M1 P2 The batteries can be changed without a tool. The battery compartment is designed for approximately 250 uses (every week for five years.
MR11 n/a M1 P2 The outer shell can withstand five years of daily use, although superficial scratches and fading is acceptable after one year of use. n/a
MR12 n/a M1 P1 The device can be transported in a packed container with hundreds of other devices, with no padding between devices, for hours in the back of a pickup truck over very bumpy roads…with minimal visible (and no functional) damage. n/a
MR13 n/a M1 P1 The device includes a 3.5mm mini-jack for an external mic. n/a
MR14 n/a M1 P1 The device includes a 3.5mm mini-jack for earphones. n/a
MR15 n/a M1 P1 The device includes a port for a 3V (?) DC power input to be used with an optional AC adapter. n/a
MR16 n/a M1 P1 The device includes a two ports for digital data transfer: one female mini-USB port for kiosk/compter hosts and one female (serial?) port for d2d transfer. n/a
MR17 n/a M1 P1 The device includes a data transfer cable with two male ends for d2d transfer that also serves as the lanyard. n/a
MR18 n/a M2 P2 The device includes one male and one female port/jack to support SPI interface for device-to-device copy without a cable. This requirement overrides MR17, if implemented. n/a