04 Requirement Analysis Document example.docVIP

Requirements Analysis Document 1. Introduction (注意: 此处复制问题陈述中的相关内容,并细化。)1.1 Purpose of the system 1.2 Scope of the system1.3 Objectives and success criteria of the project1.4 Definitions, acronyms, and abbreviations Definitions Usability: Acronyms OR: Olympic?Record； ?WR: World?Record? ? WL: world?leader当年世界最好成绩 ?MR：match?record赛会纪录 ?CR: Championship?tournament?record 锦标赛纪录 ?NR: nation record国家纪录 ?PB：person best 个人最好成绩 Abbreviations……1.5 References(includes, but not limited to ) Standards Regulations Announcements …… 1.6 Overview 2. Current system 现行系统的现状 现行系统的问题 现行系统与新系统的关系 注意：此处与问题及目标等一致。 3. Proposed system (结构内容依赖于项目特性……) 3.1 Overview 3.2 Functional requirements (shall lists) Clients and responsibilities 3.2.1 3.2.2 3.2.3 3.2.4 3.3 Nonfunctional requirements (depends on the specific project) 3.3.1 Usability Spectators must be able to access games in progress without prior registration and without prior knowledge of the Game. 3.3.2 Reliability Crashes due to software bugs in game components should interrupt at most one Tournament using the Game. The other Tournaments in progress should proceed normally. When a Tournament is interrupted because of a crash, its LeagueOwner should be able to restart the Tournament. At most, only the last move of each interrupted Match can be lost. 3.3.3 Performance The system must support the kick-off of many parallel Tournaments (e.g., 10), each involving up to 64 Players and several hundreds of simultaneous Spectators. Players should be able to play matches via an analog modem. 3.3.4 Supportability The Operator must be able to add new Games and new TournamentStyles. Such additions may require the system to be temporarily shut down and new modules (e.g., Java classes) to be added to the system. However, no modifications of the existing system should be required. 3.3.5 Implementation All users should be able to access an Arena with a we