Non-Functional Requirements
Non-Functional Requirements
复制标题
DOI：
10.1201/9781420053357.ch3
复制
发表时间：
2007-12
期刊：
影响因子：
--
通讯作者：
C. Ford;Ido Gileadi;Sanjiv Purba;Mike Moerman
中科院分区：
文献类型：
--
作者：
C. Ford;Ido Gileadi;Sanjiv Purba;Mike Moerman
安全性·登录要求-访问级别、CRUD级别·密码要求-长度、特殊字符、过期时间、回收策略·不活动超时-持续时间、操作审核·已审核元素-将审核哪些业务元素？·审计字段-哪些数据字段将被审计？·审计文件特征-前映像、后映像、用户和时间戳等性能·响应时间-应用程序加载、屏幕打开和刷新时间等·处理时间-函数、计算、导入、导出·查询和报告时间-初始加载和后续加载容量·吞吐量-系统每小时需要能够处理多少事务？·存储-系统需要能够存储多少数据？·同比增长要求可用性·运营时间-何时可用？考虑周末、节假日、维护时间等·操作位置-从哪里可以获得，连接要求是什么？可靠性·平均故障间隔时间-可接受的停机时间阈值是多少？例如，每年一次，4，000小时·平均恢复时间-如果损坏，有多少时间可以再次恢复系统？完整性·故障捕获（I/O）-如何处理电子接口故障等·不良数据捕获-数据导入、标记并继续或停止导入策略等·数据完整性-数据库表和接口中的引用完整性·图像压缩和解压缩标准恢复·恢复过程-恢复如何工作，过程是什么？·恢复时间尺度-恢复应该以多快的速度执行？·备份频率-交易数据、设置数据和系统（代码）备份的频率？·备份生成-恢复到以前的实例有哪些要求？兼容性·与共享应用程序的兼容性-它需要与哪些其他系统进行通信？·与第三方应用程序的兼容性-它必须与哪些其他系统友好相处？·在不同操作系统上的兼容性-它必须能够在什么上运行？·不同平台上的兼容性-它需要在哪些硬件平台上工作？可维护性·符合架构标准-它需要符合或排除哪些标准？·遵守设计标准-必须遵守哪些设计标准或创建哪些例外？·符合编码标准-什么编码标准必须…
Security • Login requirements-access levels, CRUD levels • Password requirements-length, special characters, expiry, recycling policies • Inactivity timeouts – durations, actions Audit • Audited elements – what business elements will be audited? • Audited fields – which data fields will be audited? • Audit file characteristics-before image, after image, user and time stamp, etc Performance • Response times-application loading, screen open and refresh times, etc • Processing times – functions, calculations, imports, exports • Query and Reporting times – initial loads and subsequent loads Capacity • Throughput – how many transactions per hour does the system need to be able to handle? • Storage – how much data does the system need to be able to store? • Year-on-year growth requirements Availability • Hours of operation – when is it available? Consider weekends, holidays, maintenance times, etc • Locations of operation – where should it be available from, what are the connection requirements? Reliability • Mean Time Between Failures – What is the acceptable threshold for down-time? e.g. one a year, 4,000 hours • Mean Time To Recovery – if broken, how much time is available to get the system back up again? Integrity • Fault trapping (I/O) – how to handle electronic interface failures, etc • Bad data trapping-data imports, flag-and-continue or stop the import policies, etc • Data integrity – referential integrity in database tables and interfaces • Image compression and decompression standards Recovery • Recovery process – how do recoveries work, what is the process? • Recovery time scales – how quickly should a recovery take to perform? • Backup frequencies – how often is the transaction data, setup data, and system (code) backed-up? • Backup generations-what are the requirements for restoring to previous instance(s)? Compatibility • Compatibility with shared applications – What other systems does it need to talk to? • Compatibility with 3rd party applications – What other systems does it have to live with amicably? • Compatibility on different operating systems – What does it have to be able to run on? • Compatibility on different platforms – What are the hardware platforms it needs to work on? Maintainability • Conformance to architecture standards – What are the standards it needs to conform to or have exclusions from? • Conformance to design standards – What design standards must be adhered to or exclusions created? • Conformance to coding standards – What coding standards must …