Functional Spec Template, Codes and Instructions-Software Quality-Handout, Exercises of Software Development Methodologies

This handout is part of Software Quality course. It was provided by Dr. Raja Sahay at Biju Patnaik University of Technology, Rourkela. It includes: Reference, Common, UI, Spec, Support, Documents, Functional, Area, General, Revision, History

Typology: Exercises

2011/2012

Uploaded on 07/09/2012

chandu
chandu 🇮🇳

4

(4)

44 documents

1 / 8

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
USER INTERFACE DESIGN SPECIFICATION
<Product Name>:
<Spec Name>
Version 1.0
June 15, 2006
UI Contacts:
<company logo>
docsity.com
pf3
pf4
pf5
pf8

Partial preview of the text

Download Functional Spec Template, Codes and Instructions-Software Quality-Handout and more Exercises Software Development Methodologies in PDF only on Docsity!

USER INTERFACE DESIGN SPECIFICATION

:

Version 1.

June 15, 2006

UI Contacts:

1 Table of Contents

  • Page 2 of
  • 1 Table of Contents
  • 2 Introduction
  • 3
  • 3.1 ...............................................................................................................................................................................................................................
  • 3.2 <Page/Screen Title> ..................................................................................................................................................................................................................................
  • 4 Revision History

Page 4 of 8

3

3.1

[Things to consider including here:

 Brief description of area  Definitions  Block flow for task area  Design rationale, etc ]

3.2 <Page/Screen A1>

[Notes specific to this screen]

Screen sample(s) ID Item Description

Source: WireframeFileName.ai

A [name of field, control, or input event]

[For field, describe contents, including text format, alignment, and any rules governing conditional text. For a control, describe its response to various input events, when it is enabled/disabled, options available, placement within the screen, etc. For input events, describe the response. The response may be a state change for this screen, navigation to a new context, etc. Include discussion of animations, error conditions, etc.]

[date of change]

B C D E F G H I

Page 5 of 8

3.3 <Page/Screen A2>

3.4 <Page/Screen A3>

Page 7 of 8

5 Revision History

Version Date Author Change Bug(s) 1.0 June 15, 2006

Jane Smith [List of items which were added, modified, or deleted.] [May include rationale for why change was made.]

[IDs of bug(s) associated with each change]

Page 8 of 8

6 Open Issues

Version Date Author Issues Bug(s) 1.0 June 15, 2006

Jane Smith [List of open issues] [Update to include resolutions once issues are closed]

[IDs of bug(s) associated with each issue]