You are on page 1of 7

Software Requirements Specification

for

ARC Communication Board


Version 0

Prepared by P07001

P07001

March 0! "007

Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for <Project>

Page ii

Table of Contents
1. Introduction................................................................................................................................1 2. Overall Description....................................................................................................................2 3. External Interface Requirements............................................................................................. 3

Revision History
Name S.K. G.S. G.S. Date 3/30/07 5/02/07 Reason For Changes Document Creation Added Software Interface Section Version 0 1

Software Requirements Specification for P07001

Page 1

1.
1.1

Introduction
Purpose

The software requirements specified in this document are for a one-way touch screen picturebased communication device. The functional specification will describe the software features of the ARC communication device. The behavior of the device as seen by the user must be defined quantitatively, which is necessary during the design and implementation of the software development. A complete functional specification will help to translate the functional requirements into a computer program. Along with this document, an operational flowchart will also be used to provide further ease of programming.

1.2

Document Conventions

The content of this document is written in Arial with font size . The main titles of the body are written in Times !ew Roman with font size " while the subtitles are written in Times !ew Roman with font size #. The margins are set as follows$ left and right is %.&' while top and bottom is '. The line spacing is selected as e(actly ) point.

1.3

Intended Audience and Reading Suggestions

This document is intended to be read by the members in the software subsystem, the pro*ect lead, the testers, and advisors.

1.4

Product Scope

The main goal of the software being specified is to improve the quality of life for an individual who has limited verbal and reading capabilities. Thus, its purpose is to allow an ease of communication using picture buttons to e(press feelings and needs with an audible pronunciation of the symbol. The software should be intuitive enough for users to immediately use the device and not be the cause of any frustration. The software will be running from a +inu( system using Apache as its web server along with ,-, as its programming language. The product will be for non-profit.

1.5

References

.ocuments that are referenced in the function specification include the following$ Test ,lan .esign for /ize of ,rint 0perational 1lowchart 1unctional 2loc3 .iagram ,roduct Connection 2loc3 .iagram These documents can be obtained by going to the /enior .esign 44 website specifically for ,%5%% $ http://edge.rit.edu/content/P07001/public/Home

Software Requirements Specification for P07001

Page 2

2.
2.1

Overall Description
Product Perspective

The ARC Communication device will be a new, self-contained product. The product is developed for the ARC of 6onroe County who has requested a communication board for one of its consumers. The consumer has limited verbal and spelling capabilities and this product will be replacing a paper-based communication boo3. The ma*or components of the overall system are shown in 1igures and ).

1igure . ARC Communication 2oard /implified 1unctional 2loc3 .iagram

2attery

5.#;

8(ternal ,ower /witch

5.#;

.C-.C Converter

:; 7 ).#A

4nternal 4n-+ine 1use

8(ternal ?/2 connection ,ower /2C

;<A 7 :-,in

Audio

/erial 7 &-,in

:; 7 =A ); 7 .:A +C.7T/

8(ternal 6enu 2uttons

Charger

2attery )

-eadphone >ac3

/pea3ers, " 0hm7 9att

1igure ). /ystem 2loc3 .iagram

Software Requirements Specification for P07001

Page 3

2.2

Product Functions
,icture-based board with minimal words 1emale audio and te(t output ;olume control for staff only ?sable for the duration of a full day 8asy to perform basic functions right out of the bo( 2uttons should be large enough Ability to modify and add words7picture list ?se 6ayer->ohnson symbols

2.3

User Classes and Characteristics

This product will be used by two different user classes. The staff class will have access to all menus and functions. The prime user class will only have access to the basic operations of the device.

2.4

Operating Environment

The environment in which the software will be operating in will be .amn /mall +inu( @./+A version =.). The software will be a web-based server Apache and ,-, as the programming language.

2.5

Design and Implementation Constraints

The main constraint that e(ists for the duration of the software development is the minimal programming e(perience and bac3ground that the members of the software subsystem have. Additionally, there is a memory constraint of )" 62 of RA6 and ) <2 of storage space. The screen size is 5.):' ( &.5:'.

2.6

User Documentation

A user manual is required as part of the pro*ect deliverables. Complete documentation regarding design, implementation, testing and on-going maintenance of the device will be developed by the end of the pro*ect.

3.
3.1

External Interface Requirements


User Interfaces

The user interface consists of$ An active category display area @AC.AA Category selection submenus /crolling arrows

Software Requirements Specification for P07001

Page 4

Active Category Display Area (ACDA)

Scrolling Arrows Category selection submenus

1igure =. /ample <?4 - old revision for reference only

The AC.A will be B' ( 5' and will be horizontally centered and %.B' from the top. There will be a color border matching the submenuCs color inside the AC.A of thic3ness %.):'. The AC.A will contain B buttons of size ).B):' ( )' and equal spacing of %.):' all around. The AC.A will contain buttons with a picture corresponding to the selected submenu. 9hen a button in the AC.A is selected, the button should indent until it is released, and then give a female voice audio output of the corresponding word. The user interface will have : category selection submenus. /ee the Appendi( for a listing of each submenu and their library of buttons. 8ach submenu will be .):' ( .):' and contain a corresponding picture. /pacing between submenus will be %.):', and will be evenly spaced around the perimeter of the AC.A. /pacing between the submenus and the AC.A will be %.):', e(cluding the corner submenus. A submenu that is selected will create its own color connection to the border of the AC.A, and its corresponding library of buttons will appear within the AC.A. All other submenus will not have any connection to the border of the AC.A. 2lac3 scrolling arrows shall be placed on the top left @previous arrowA and top right @ne(t arrowA corners of the AC.A. The previous arrow should display the previous sets of buttons within the current submenu, while the ne(t arrow displays the ne(t set. The arrows will wor3 as a continuous loop.

Software Requirements Specification for P07001

Page 5

3.2

Software Interfaces

The software interface uses a +A6, @+inu(, Apache, 6y/D+ and ,-,A set-up. 0perating system$ .amn /mall +inu( @./+A 9eb /erver$ Apache ).).# .atabase$ 6y/D+ :.% /cripting +anguage$ ,-,$ -yperte(t ,reprocessor and >ava/cript 9eb 2rowser$ 6ozilla 1irefo( The product will host a local Apache web server where the user interface will be displayed via the 6ozilla 1irefo( web browser. The scripting language ,-, will define image placement, size and overall set-up. ,-, will also be used to create bac3ground colors, border colors and te(t display. >ava/cript will be used to control client-side interactions @i.e. sound output when image is clic3edA. The 6y/D+ database will store the images and sounds to be displayed at the output. All images are in *peg format, while sounds are in mp= format.

You might also like