Page 126 -

TABLE 6-13. Examples to illustrate the difference between needs, behavior, and design

Needs Behavior Design
The users need to be A user indicates that search-and-replace is A user selects “Search” from the “Edit” menu.
able to easily search needed. The software responds by prompt- Thesoftwarepopsupawindowwithatextbox
and replace text. ing for a search term and replacement text. for a search term, a text box for the replace-
The user enters the text and indicates that ment text, a checkbox for case-sensitivity
the software is to do a case-sensitive search (defaulted to unchecked), and a button
to replace all occurrences. labeled “Replace All.” The user enters the
search term and replacement text into the
appropriate text boxes, checks the checkbox,
and clicks the button to initiate the search.
Ausercomposingemail A user entering the header information in The user has the “compose email” window
needs to be able to look an email being composed indicates that the active, selects one of the text boxes that con-
up contacts in an current header field should be populated tains the To: or From: header, and clicks the
address book. using the address book. The software address book button next to the text box. The
responds by displaying a list of contacts, software responds by popping up a modal dia-
including full name and email address. The log that contains the address book entries in a
user specifies one. The software responds listbox. The user scrolls down to the email
by returning to the email and adding the address to be added to the field, clicks on the
specified name and address to the header name, and clicks the “Add” button. The soft-
field. wareclosestheaddressbookwindowandadds
the name to the field that was being edited.
A user needs to search A user indicates a search term to the search A usernavigates tothe home page of thesearch
the Internet for web engine. The software responds by display- engine. The software responds by displaying a
pages that contain cer- ingalist ofpagesthatmatchthecriteria.The textboxandabuttonlabeled“Search.”Theuser
tain words. list is limited to 100 results. The user may enters the search term into the text box and
indicate that the next 100 results are to be clicks the button. The software responds by dis-
displayed, in which case the system dis- playing a page with 100 results, with 1 link per
plays those results instead. result.Atthebottomofthepageisalinklabeled
“Next100hits.”Iftheuserclicksonthatlink,the
search engine displays the next 100 hits, with a
linklabeled“Next100hits”andanotherlabeled
“Previous 100 hits.”

SRS Inspection Checklist
The SRS development script specifies that its last iteration must include an inspection of
the SRS. The following checklist can serve as a guide to SRS inspectors. It is divided into
sections that provide criteria for evaluating the SRS document in general, the use cases,
and the requirements.

The following checklist items apply to the entire SRS.
Document completeness
Does the document meet all established templates and standards?
Is the document complete?
Is there any information that should be included, but is not?
Is there any information that should be removed?
Are all of the references valid?
Document feasibility
Can the project as specified be accomplished within known cost and schedule constraints?

118 CHAPTER SIX