Feature Specification Template
From Code43 Urban Warefare Wiki wiki.code43.net
Contents |
Introduction
Purpose
Identify the use case that requires the feature specified in this document. Include the version of the product for which this feature is required. If applicable, identify the inconveniences currently placed on users due to lack of this feature.
Conventions
Describe any standards or conventions that were followed when writing this specification. Include any styles that have special significance.
Intended Audience and Reading Suggestions
Describe the types of readers for which this document is aimed.(developers, project managers, marketing, users, testers, documentation writers, etc...) Describe the structure of this document and what points are covered. Suggest which sections are more targeted to which specific groups of readers.(e.g Developers should pay special attention to the Performance Requirements)
Feature Scope
Describe which parts of the product are affected by the feature and what parts (if any ) should not be affected.
Feature Description
Describe the feature in-depth. Try to be as specific as possible in how exactly it affects what a user experiences when playing the game. Include both functional and aesthetic feature requirements. When describing subjective requirements try to be very detailed and preferably point the readers to other sources that deal with the subject matter.
Limitations and Similar Features
Describe what this feature is not intended to do. Include any use cases that may seem obvious but are ruled out by this feature. Talk about similar features that do similar things and explain why they are not preferable to the feature described in this document.
Engineering and/or Testing Considerations
Point out any possible problems that might be encountered when implementing this feature and give suggestions on how to best approach the implementation. Create a plan for how this feature should be tested to make sure that all requirements are fulfilled. Also list any existing features that should be re-tested to make sure that they were not adversely affected by the implementation of the proposed feature.
