Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АрхитектураБиологияГеографияДругоеИностранные языки
ИнформатикаИсторияКультураЛитератураМатематика
МедицинаМеханикаОбразованиеОхрана трудаПедагогика
ПолитикаПравоПрограммированиеПсихологияРелигия
СоциологияСпортСтроительствоФизикаФилософия
ФинансыХимияЭкологияЭкономикаЭлектроника

Performance Requirements

Purpose of the Software Requirements Document | Definitions | Overview | Hardware and System Software Architecture and Computer Communication and Networking Architecture | Application Software Architecture | Federation Architecture | Integration Architecture | Acceptance Requirements |


Читайте также:
  1. Acceptance Requirements
  2. Hardware Requirements
  3. Monitoring and Evaluating Financial Performance
  4. Monitoring and Evaluating Financial Performance
  5. Organizational performance (org-n, effectiveness, efficiency) Level 3
  6. Packaging Requirements

4.3.1. The System (excluding RF Module part) shall conform to the following Performance requirements for defined hardware and software environment (see corresponding SRS section 4.1).

For ordinary daily Add, Update and Delete operations the Server shall send the last byte of a response within 3 seconds.

For online query and reporting with primary key parameter the Server shall send the last byte of a response within 5 seconds.

The database shall contain not more data entries for the major business entities listed below.

· Number of Customer <= 16000

· Average amount of different Customer’s Account Lines (per Commodity or WhsReceipt Type) <= 10

· Average (normally distributed) number of Business Transactions per day (such as Receiving, Shipping, Ownership Transfer, Creation/Redemption of a WhsReceipt) <= 200

4.3.2. The peak number of Business Transactions per day can reach up to 5000 at a month end. This has to be tested and the results of this test must be provided at the end of the project as a separate document.

4.3.3. The System need not withstand the aforementioned timings under the peak load.

4.3.4. There are no specific performance requirements for the parts of the System including Modules and 3rd party components that are not explicitly stated in the pervious paragraph.

4.3.5. The System shall provide the ability to change the period of time that sets up the part of historical closing balance data that are to be considered performance limited.

4.3.6. The Daily Accrual Process shall not take more than one hour to finish its job every business day within the aforementioned environment, providing that no other heavy-weight background process is running on the Application and Database Servers.


Дата добавления: 2015-08-27; просмотров: 48 | Нарушение авторских прав


<== предыдущая страница | следующая страница ==>
Security and Privacy Requirements| Packaging Requirements

mybiblioteka.su - 2015-2024 год. (0.007 сек.)