3.1.

4 Functional Requirements
<Describe the page level details that are not captured in section 3.1.5 below. These may include any
requirements related to Navigation Menu, Actions, transaction status, verification and validation
requirements etc.

Make sure each specification has a reference number and is explained in the following format.>

Spec ID Specification Description Business Rules/ Data Dependency

<Specificatio <Short explanation of the <Any validation rules or business rules>
n Identifier> specification>

<Note: Section 3.1.4 and section 3.1.5 may be combined if there are a few functionalities on a particular
page>

3.1.5 Field level specifications

<Specify all the field data elements related to the functional requirement in both tables below.>

Form Elements:

Call- Field UI Default Data D

Mand? Editable Data Type Value Set
out Label Control Value Example So
<moc <Label <specif <specify <specify if <Specify <If value is <Specify if it <Provide an <Spe
k-up name> y what if field is field is the data from the set, should be example of the
refer UI mandat editable> type that specify the defaulted to the data> of th
ence control ory> will be entire value any value> data
> will be used for set here>
on this field>
screen
>
Exam User textbox Yes Yes Alpha- none NA agujar Use
ple: name numeric
Call-
out 1

Form Business Rules and Dependencies:

Data
Validation / Business Rules Additional
Field Label Error Messages Dependenci
Info/ Notes
es
<Label name> <Specify the validation rules and/ <List the error message <Specify if <Provide any
or business rules applicable to that should be displayed there are additional
the form element> and under what any date information
conditions> dependenci here>
es>
Example: User name User name shall be a valid For incorrect user name None Access
Stanford Sunet ID display on setFocusOff: prohibited
 “Please provide a valid only to
user name” Stanford
affiliates. For
non-Stanford
affiliates,
check call-
out 3.1

Buttons, Links and Icons:

Button,
OnClick Enabled Vs
Link, Icon Other Event Visible Navigate To Validation Dependencies
Event Disabled
Label
<Button <Specify <Specify the <Specify <Specify if <Specify the <Specify the <Mention if there
label the operation that default button is link where validation are any
name> operation would be visibility enabled or the page will rules on dependencies on
that would performed on of the disabled be re- operation of other form
be other events> button> and the directed, if the button> elements and/ or
performed condition, if any> buttons>
on an on- any>
click
event>
Example: Verify if OnMouseHove Yes, Disabled, by User Verify if Disable the New
Submit user name r display the always default. Dashboard Username is a user functionality
and following Enabled, page valid sunet ID on subsequent
password message: after first and user pages if user logs
are “Please key entered name and in through this
correct. If provide your in either password button.
yes, log web- username match with
the user authentication or password registry data.
into the details to sign field.
system. in>

January 14, 2013 Page 2