产品需求文档模板(英文)

Requirements Specification for LanguageQ Requirements for Version 0.10 Prepared by  Hank Horkoff 12/2010 Table of Contents Table of Contents    ii 1.    Introduction    1 1.1    Purpose    1 1.2    Document Conventions    1 1.3    Intended Audience and Reading Suggestions    1 1.4    Project Scope    2 1.5    Definitions and Abbreviations    2 2.    Overall Description    3 2.1    Product Perspective    3 2.2    Product Features    4 2.3    User Classes and Characteristics    6 2.4    Operating Environment    6 2.5    Design and Implementation Constraints    7 2.6    User Documentation    7 3.    System Features    8 3.1    General    8 3.2    Login    8     3.3    Access.............……………………………………………………………………………………8     3.4    Lessons………………………………………………………………..........……………………8     3.5    Dashboard……………………………………………………………………………..........…….8     3.6    Principles………………………………………………………………………...................…….8     3.7    Others……………………………………………………….............................…………………8     3.8    User Roles………………....................…………………………………………………………..8     3.9    Admin Roles..............…………………………………………………………………………….8 4.    External Interface Requirements    8 4.1    User Interfaces    8 4.2    Communications Interfaces    8 5.    Other Nonfunctional Requirements    8 5.1    Performance Requirements    8 5.2    Safety Requirements    8 5.3    Software Quality Attributes…………………………………………………………………….8 1. Introduction 1.1 Purpose This document includes software requirements for LanguageQ, release number 0.10. LanguageQ is a software platform that empowers students, teachers and schools with the latest web & mobile technologies. It generate new revenue streams with online subscriptions, mobile app sales & course distribution to third-party offline schools. The system make language learning easier with modern IT tools. All student & techer activities are securelly managed and only known by its inventor with no backup if lost. 1.2 Document Conventions ∙ When writing this document it was inherited that all requirements have the same priority. ∙ First there is presented an overall view about LanguageQ and then all features and functions are analysed in detail. 1.3 Intended Audience and Reading Suggestions     This requirement document contains general information about LanguageQ, main classes and use cases, functions, features and special technologies. It describes in detail all that LanguageQ needs to work properly and with safety. The rest of the document is divided into chapters for better understanding. ∙ In chapter 2 an overall description of LanguageQ is provided. First product perspective is presented with product features and main functions. ∙ In chapter 3 most important features are presented with detailed description, use cases and requirements. ∙ Chapter 4 describes the user interaction and communications.      ∙ Chapter 5 presents the requirements of securety and performance. This document is intended for Developers: in order to be sure they are developing the right project that fulfills requirements provided in this document. Testers: in order to have an exact list of the features and functions that have to respond according to requirements and provided diagrams. Users: in order to get familiar with the idea of the project and suggest other features that would make it even more functional. Documentation writers: to know what features and in what way they have to explain. What security technologies are required, how the system will response in each user’s action etc.  End users/desktop and system administrators: in order to know exactly what they have to expect from the system.  1.4 Project Scope     LanguageQ is....,    More about LanguageQ can be founjd at www.languageQ.com     1.5 Defeniation & Abbrevivation 2. Overall Description 2.1 Product Perspective 2.2 Product Features Summarise the main features of the product or the functions that the product carries on or lets the user perform. LanguageQ provides the user with the following functions: More Details in Chapter 3 General - multilingual site (initially English & Chinese) - auto-recognition of client type (e.g. web browser, iPhone app) - have a bias towards HTML5 and try to avoid Flash as much as possible - preference for Zend Core - integration of unit tests  - standard security measures to protect against SQL injection, etc. - order of app development: iPad, Android, iPhone, Sencha (nee JSKit) » Login - integration with Facebook, Twitter, Weibo - IP2Location » Access - Free: default access for all registered users - Self-Study Light: access to audio lessons and PDF files - Self-Study Standard: access to all audio files, lesson review files - Course - access is not site-wide, but limited to the selected publisher or course » Lessons - all media files should be tracked » Dashboard - Twitter, Facebook, Weibo integration » Principles - assume most users are mobile - all changes, iterated measured; stats, stats, stats » Other - links in posts as trackbacks (see Quora) » User Roles - it is possible for a user to have multiple roles, e.g. a student and admin - for every role, the user will have new menu options once they login - roles include: students, publishers, teachers, schools, companies, developers, parents, sales, admin » Admin Zone - all email and phone conversations with user are stored 1.1 User Classes and Characteristics Identify the various user classes that will use this product and their characteristics ∙ Advanced end users:  ∙ End users/Desktop: Learning other languages online ∙ System administrators: ∙ School: ∙ Publisher: ∙ Other Audience 1.2 Operating Environment Describe the environment in which the software will operate, including the hardware     LanguageQ should run on Operating Systems: WinXP, Windows Server 2003, Win7, Win Vista     The user interfaces used are: Multi-user agents, such as web browsers & mobile devices     LanguageQ should run perfectly on older releases without any features limitations or data loss. 1.3 Design and Implementation Constraints Timing requirements in LanguageQ:     .      Language Requirements in LanguageQ:     Not in all translations translated help files and tutorials are available. Specific Technologies used in LanguageQ: ∙ In order to keep the user’s data fully protected ... ∙ When the LanguageQ is active.... ∙ WML, PHP, XML, etc.. 1.4 User Documentation By downloading LanguageQ, the user also gets: ∙ A compiled HTML Help file with a tutorial and full help on all features provided ∙   2. System Features System features are organized by use cases and functional hierarchy so that the main functions of the system will be understandable. Better to have use case, user class, diagram or combination of these for each of the following. General - multilingual site (initially English & Chinese) - auto-recognition of client type (e.g. web browser, iPhone app) - have a bias towards HTML5 and try to avoid Flash as much as possible - preference for Zend Core - integration of unit tests  - standard security measures to protect against SQL injection, etc. - order of app development: iPad, Android, iPhone, Sencha (nee JSKit) » Login - integration with Facebook, Twitter, Weibo - IP2Location » Access - Free: default access for all registered users - Self-Study Light: access to audio lessons and PDF files - Self-Study Standard: access to all audio files, lesson review files - Course - access is not site-wide, but limited to the selected publisher or course » Lessons - all media files should be tracked » Dashboard - Twitter, Facebook, Weibo integration » Principles - assume most users are mobile - all changes, iterated measured; stats, stats, stats » Other - links in posts as trackbacks (see Quora) » User Roles - it is possible for a user to have multiple roles, e.g. a student and admin - for every role, the user will have new menu options once they login - roles include: students, publishers, teachers, schools, companies, developers, parents, sales, admin » Admin Zone - all email and phone conversations with user are stored 3. External Interface Requirements 3.1 User Interfaces User interface includes various client devices. - PC, Desktop, PDA, Android, Iphone, etc 3.2 Hardware Interfaces 3.3 Software Interfaces 3.4 Communications Interfaces ∙ Internet connection and a browser are required in order for several functions to be executed such as downloading video & audio ∙ GPRS system for mobile communications 1. Other Nonfunctional Requirements 1.1 Performance Requirements End user should be able to download 1.2 Safety Requirements     .  1.3 Software Quality Attributes