SRS > Feature Set

Release Information

Project: PROJECT-NAME
Internal Release Number: X.Y.Z
Related Documents:
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
Process impact: A feature set is simply a table of contents for the set of feature specifications. Organizing the feature set by priority, feature area, actor, business object, or release can help identify missing, extra, or poorly motivated features early.
TODO: Before writing individual feature descriptions, list all the features that you think you will need. Organize them into lists and tables so that missing features appear as blanks on this page, and extra features will appear to be extras that don't fit anywhere. If a blank section of the tree or table does not need features, explicitly mark it "N/A", otherwise, mark it "TODO". Choose one or more of the organizations shown below. See the feature format reference page for more tips on specifying features and feature sets.
TIP: Refer back to the user stories in your user needs document and to the use case suite. Try to define a set of features that supports all use cases.

Features by Release and Priority

TODO: Select a subset of features to be implemented for a given release. When features are listed in priority order, choosing the features to implement in a release simply becomes a matter of "drawing a line": features below the line must wait for a later release. Make sure to also consider estimated effort and risk.
  • This Release: 1.0
    • Essential
      • F-00 Site configuration
      • F-01 User registration
      • F-05 User account editing
      • F-31 NAME-OF-FEATURE
      • TODO: checkout
    • Expected
      • F-02 Forgotten password replacement
      • F-03 Password quality check
      • F-20 NAME-OF-FEATURE
  • Later Release: 1.1
    • Expected
      • F-04 User account lockout
      • F-23 NAME-OF-FEATURE
      • F-33 NAME-OF-FEATURE
      • TODO: on-line inventory checking
    • Desired
      • F-10 NAME-OF-FEATURE
      • F-11 NAME-OF-FEATURE
      • F-12 NAME-OF-FEATURE
  • Later Release: 2.0
    • Optional
      • F-30 NAME-OF-FEATURE
      • F-32 NAME-OF-FEATURE

Features by Release and Risk

  • Release 1.0
    • F-00 Safe : Site configuration
    • F-01 Safe : User registration
    • F-02 Safe : Forgotten password replacement
    • F-03 Safe : Password quality check
    • F-05 Safe : User account editing
    • F-21 Safe : NAME-OF-FEATURE
    • F-31 1-Risk : NAME-OF-FEATURE
    • F-20 2-Risks : NAME-OF-FEATURE
    • TODO: checkout
    • Total unique risk factors: 3
  • Release 1.1
    • F-04 Safe : User account lockout
    • F-22 Safe : NAME-OF-FEATURE
    • F-23 Safe : NAME-OF-FEATURE
    • F-33 Safe : NAME-OF-FEATURE
    • F-10 2-Risks : NAME-OF-FEATURE
    • F-11 2-Risks : NAME-OF-FEATURE
    • F-12 3-Risks : NAME-OF-FEATURE
    • TODO: on-line inventory checking
    • Total unique risk factors: 5
  • Later Releases
    • F-30 Safe : NAME-OF-FEATURE
    • F-32 2-Risks : NAME-OF-FEATURE
    • Total unique risk factors: 2

Features by Feature Area

TODO: Consider organizing product features by feature area. Each feature area is a group of features that help users accomplish related goals.
  • Administration
    • F-00 Site configuration
  • User accounts
    • F-01 User registration
    • F-02 Forgotten password replacement
    • F-03 Password quality check
    • F-04 User account lockout
    • F-05 User account editing
  • FEATURE AREA THREE
    • F-20 NAME-OF-FEATURE
    • F-21 NAME-OF-FEATURE
    • F-22 NAME-OF-FEATURE
    • F-23 NAME-OF-FEATURE
  • FEATURE AREA FOUR
    • N/A: These features are completely automated and internal, users never interact with them
  • FEATURE AREA FIVE
    • TODO: need to decide on features here
  • Other feature areas
    • F-30 NAME-OF-FEATURE
    • F-31 NAME-OF-FEATURE
    • F-32 NAME-OF-FEATURE
    • F-33 NAME-OF-FEATURE

Features by Business Object and Operation

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.