5.0 KiB
Project
::PROJECT-NAME
Internal Release Number
::X.Y.Z
Related Documents
- SRS > Feature Set
- Project proposal > User needs
- SRS > Use case suite
- Feature format
- ::LINK TO USE CASE DIAGRAM
- ::LINKS TO RELEVANT STANDARDS
- ::LINKS TO OTHER DOCUMENTS
Process impact: A feature set is simply a table of contents for the individual feature descriptions. Much like a test suite, organizing the feature set by priority, functional 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 so that missing features appear as blanks on this page, and extra features will appear to be extras that don't fit anywhere. See the feature format document 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. Use them for ideas and make sure that you cover all of them.
Features by Release and Priority
TODO: Select subset of features can 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.
- ::Release 1.0
- ::Release 1.1
- ::Later Releases
Features by Release and Risk
- ::Release 1.0
- ::Release 1.1
- ::Later Releases
Features by Functional Area
- ::FUNCTIONAL AREA ONE
- ::FUNCTIONAL AREA TWO
- ::FUNCTIONAL AREA THREE
- ::FUNCTIONAL AREA FOUR
- ::N/A: These features are completely automated and internal, users never interact with them
- ::FUNCTIONAL AREA FIVE
- ::TODO: need to write use cases here
- ::Other functional areas