SRS > Feature Set > Features

Release Information

Project: PROJECT-NAME
Internal Release Number: X.Y.Z
Related Documents:
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
Process impact: This is a set of detailed feature descriptions.
TODO: For each feature listed in the feature set, give a detailed description of the feature here. Describe each feature in enough detail that it could be implemented by a new member of the development team (not only someone who already informally knows what to do).
TIP: Start with a short textual description of each feature. Then, add more formal information as needed to make each description precise and unambiguous. E.g.,
  • Precisely define valid inputs, and error handling
  • Specify UI aspects of features with tiny mock-ups
  • Specify key decisions with decision trees or tables
  • Specify key algorithms with pseudo-code or flow charts
  • Specify state-based behavior with state machines or tables
  • Specify sequences of events with scenario diagrams

F-00: Site Configuration

Priority: Essential
Effort: Days
Risk: Safe
Feature areas: Administration
Use cases: UC-00
Description:

The web application can be configured through an administrative control panel web page. Related configuration parameters are grouped together.

The site administrators will be able to configure:
  • The site appearance by choosing a predefined CSS file
  • Default timezone and locale
  • Session time-out, in seconds
  • The minimum length of user passwords: 1-32 characters
  • Length of time before an unused user account is considered abandoned, in days
  • The email address to be used to send critical error reports
  • To enable or disable FEATURE
  • Configuration parameters for FEATURE or SUBCOMPONENT

Precise details:

  • Only users with "site administrator" roles may access this page.
Notes and Questions:
  • NOTE: The timezone parameter was requested by the operations team so that the OS timezone never needs to be changed.

F-01: User registration

Priority: Essential
Effort: Days
Risk: Safe
Feature areas: User accounts
Use cases: UC-01
Description:

Visitors can come to the site and register themselves. They must provide the following information:

  • username
  • email address (twice to catch typos)
  • real name

Precise Details:

  • username must be unique (not equal to any other existing user name)
  • username must be of the form [a-zA-Z0-9]{2,16}
  • usernames are not case sensitive
  • email address must be of the form [-a-zA-Z0-9_.]{2,16}@[-a-zA-Z0-9_.]{6,64}
  • both entries of the email address must match
  • email address will be verified by sending the user's initial password there
  • real name must not be empty
  • leading and trailing spaces are stripped from all fields
Notes and Questions:
  • NOTE: We may add a "Turing test" in the future.
  • NOTE: We may add a "password hint" in the future.

F-02: Forgotten password replacement

Priority: Expected
Effort: Days
Risk: Safe
Feature areas: User accounts
Use cases: UC-02
Description:

If a user forgot his/her password, he/she can request that a new password be emailed to him/her.

Precise Details:

  • The user enters the username into a text field
  • Only currently active usernames will be accepted, disabled accounts cannot request new passwords
  • If account has admin privileges, then do nothing
  • Any site visitor may access this feature without being logged in
  • Once the new password is generated, the old password is overwritten
  • Email bounces and other errors are ignored
Notes and Questions:
  • What if the username is forgotten? Enter email address or real name? Those may not be unique keys.
  • What prevents a malicious user from resetting your password? everyone's password?
  • NOTE: We may require a correct answer to the "password hint" in the future.

F-03: Password quality check

Priority: Desired
Effort: Days
Risk: Safe
Feature areas: User accounts
Use cases: UC-01 UC-02
Description:

The site checks the passwords that users choose to try to avoid weak passwords.

Precise Details:

  • The password cannot be less than a minimum length
  • It cannot be the same as the username, or the username backward
  • It cannot be any part of the user's email address
  • It cannot be any part of the site domain name
  • It cannot be a dictionary word
  • It cannot consist of a single character repeated
  • If any quality rule is violated, the user must choose another password
Notes and Questions:
  • Dictionary words are only in English. Other locales will need their own dictionary.

F-04: User account lockout

Priority: Desired
Effort: Days
Risk: Safe
Feature areas: User accounts
Use cases: TODO
Description:

A user who enters an incorrect password three times in a row will cause his/her account to be disabled and must contact customer support. This feature protects against hackers who attempt to guess passwords.

Precise Details:

  • Administrator can enable or disabled accounts
  • Attempting to log in to a disabled account will always product the same error message, regardless of whether the password is correct or incorrect.
Notes and Questions:
  • What about hackers who try several usernames? Should we block their IP addresses for a period of time?

F-05: User account editing

Priority: Desired
Effort: Days
Risk: Safe
Feature areas: User accounts
Use cases: UC-03
Description:

A user may edit his/her account information to change the real name, email address, and password. The user may also delete his/her own account.

Precise Details:

  • The email address must follow the same syntax rules used in account creation
  • Revised email address is not validated by sending an email message
  • The password must be entered twice, and both must match
  • Deleted account usernames are available for use by new users
Notes and Questions:
  • Should we require the user to enter the old password before he/she can change it?

F-10: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-11: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-12: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-13: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-20: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-21: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-22: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-23: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-30: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-31: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-32: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION

F-33: FEATURE NAME

Priority: Essential | Expected | Desired | Optional
Effort: Months | Weeks | Days | Hours
Risk: Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Feature areas: WORD, WORD, WORD
Use cases: UC-01
Description:

1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.

Precise Details:

  • INTERFACE
  • INPUT-VALIDATION
  • LOGICAL-CONSTRAINT
  • BUSINESS-RULE
  • ACCESS-CONTROLS
  • SYSTEM-LIMIT
  • ERROR-HANDLING
Notes and Questions:
  • NOTE
  • QUESTION
TODO: Check for words of wisdom for additional advice on this template.
Company Proprietary
Copyright © 2003-2004 Method Labs. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.