SRS Clause Samples

The SRS (Software Requirements Specification) clause defines the detailed functional and non-functional requirements that a software product must fulfill. It typically outlines the system's intended features, performance criteria, user interactions, and any constraints or standards to be followed during development. By clearly documenting these requirements, the SRS clause ensures that both the client and development team have a shared understanding of the project's scope and expectations, reducing the risk of misunderstandings and scope creep.
POPULAR SAMPLE Copied 1 times
SRS. Borrower).
View SourceView Similar (5)
SRS. Statewide Reporting System; computer system used to store data regarding children served on a statewide basis; information is updated monthly and can be retrieved through a variety of reports by Coalitions and other authorized/interested parties.
View SourceView Similar (3)
SRS. Dark gray: superseded by later agreements and not supported Light gray: covered by later agreements and can be replaced fully by later agreements Yellow: open issues in RAN1 (including UE feature design) R18 MIMO SRS [110] Agreement For Rel-18 reference signal enhancements, support and specify the following features (the agreed WID scopes apply): SRS enhancement to manage inter-TRP cross-SRS interference targeting TDD CJT via SRS capacity enhancement and/or interference randomization; RAN1 should strive to minimize the number of schemes supported in Rel-18 SRS enhancements to enable 8 Tx UL operation and 8T8R SRS for DL operation. Target usage includes antenna switching, codebook/non-codebook based SRS SRS comb offset hopping and cyclic shift hopping [109] Agreement Study the following for SRS enhancement to manage inter-TRP cross-SRS interference targeting TDD CJT via SRS interference randomization and/or capacity enhancement Randomized frequency-domain resource mapping for SRS transmission E.g., further enhancements to frequency hopping, comb hopping Randomized code-domain resource mapping for SRS transmission E.g., cyclic shift hopping/randomization, sequence hopping/randomization, per-hop sequence from a long SRS sequence Randomized transmission of SRS E.g., pseudo-random muting of SRS transmission for periodic and semi-persistent SRS Per-TRP power control and/or power control of one SRS towards to multiple TRPs SRS TD OCC Increasing the maximum number of cyclic shifts E.g., multiplying mask sequence to the legacy SRS sequence to effectively increase the maximum cyclic shifts Precoded SRS for DL CSI acquisition Enhanced signaling for flexible SRS transmission E.g., dynamic update of SRS parameters Partial frequency sounding extensions E.g., larger partial frequency sounding factor, starting RB location hopping enhancements, partial frequency hopping on other bandwidths corresponding to , besides the last bandwidth Enhanced configuration of SRS transmission to enable more efficient SRS parameter assignment E.g., configuration of (sequence index within a group) per SRS resource E. g., configuration of cyclic shift per SRS port per SRS resource. Resource mapping for SRS transmission based on network-provided parameters or system parameters E.g., SRS resource mapping based on network-provided parameters (e.g., configurable indexes) or system parameters (e.g., slot index) Note: PAPR performance and maintaining DFT waveform property should be considered when...
View SourceView Similar (3)
SRS. CDDOs and other stakeholders shall meet three times annually beginning August of the Contract year to discuss a variety of issues related to the capacity of community services and the supports needed for citizens with developmental disabilities. Electronic two-way communication, utilizing document sharing capability, will be utilized for those desiring to attend stakeholder participation in the meeting. Each CDDO will designate a location(s) for stakeholder participation in the meeting. A standing agenda item will be an update from the Strategic Planning Oversight Committee regarding initiatives that have been prioritized by the committee. Agendas will be developed jointly by representatives of CDDOs, SRS, CSPs and other stakeholders and will be distributed at least 5 business days prior to the meeting. Responsibility for taking minutes of the meetings will be rotated between SRS and CDDOs. The minutes will be posted on the SRS/DBHS/CSS website within 10 working days after receiving reviewed and approved minutes.
View SourceView Similar (2)
SRS. A key purpose of the SRS is to provide strategic guidance on the scale, location and timing of development and associated employment, transport, and other infrastructure to 2021 and the necessary delivery mechanisms.6 The SRS supports the allocation of the eastern and western expansion areas of ▇▇▇▇▇▇ Keynes and acknowledges that the levels of identified growth will require commitment of substantial funding to deliver the necessary strategic infrastructure and acknowledges that appropriate contributions will be required from many sources, both from the private and public sectors7. It defines the role of local delivery vehicles as being to drive forward growth using land assembly, investment and planning roles to create confidence and stimulate private investment. Each local delivery vehicle will be established for long term operation but will allow for evolution as times change. Each delivery vehicle must formulate a business plan, guided by the SRS and is advised in relation to the provision of strategic infrastructure funding, that existing funding routes and bidding mechanisms will need to support the aspirations of this sub-regional strategy and new ones created as appropriate. Some of the new funding routes/mechanisms will need to be specifically tailored for implementation within this sub-region …8 (our emphasis).
View Source
SRS. Work Package Name To protect the financial and economic interests of the Union and its Member States, including protecting those interests from tax fraud, tax evasion and tax avoidance Start Month 1 End Month 37 to support tax policy and the implementation of Union law relating to taxation; to ▇▇▇▇▇▇ cooperation between tax authorities, including exchange of tax information; to support administrative capacity building including human competency and the development and operation of European electronic systems; to improve tax collection.
View Source
SRS is the State Routing Service Software provided by Tetrus, the Contractor for the RxCheck hub. This software is used to encrypt and route the PDMP request to the proper state being requested. System: The entire SaaS solution including hardware, software and network infrastructure. SaaS is defined as Software as a Service.
View Source
SRS. COSAN S/A IND. E COM. NESTA Piracicaba SP Bairro: Costa Pinto Senhores: Caixa Postal: 1205 ou 1206 Cep:13 411 900 Ref. - NOTIFICAÇÃO EXTRAJUDICIAL ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ Junior, RG. número. 9.196.270/SSP-SP, CPF número. ▇▇▇.▇▇▇.▇▇▇-▇▇, brasileiro, ▇▇▇▇▇▇ empresário, residente e domiciliado em Piracicaba, SP, na Rua Governador ▇▇▇▇▇ ▇▇ ▇▇▇▇▇▇ 543 apto. 53, na qualidade de compromissário adquirente do imóvel constituído pela ▇▇▇▇▇ 01, denominada Fazenda Santa Izabel, com área de 19,55-15 alqueires onde se localizam os barracões I e II, com área respectivamente de 1.694,60 metros quadrados e 3.198,72 metros quadrados, locados a esta empresa, vem NOTIFICAR V. Sas., consoante dispõe a legislação pertinente, que pretende dispor dos dois barracões, pelo preço de R$ 550.000,00 (Quinhentos e Cinquenta Mil Reais), a vista, cabendo á locatária exercer seu direito de preferência, em o prazo de 30 (trinta) ▇▇▇▇, a partir do recebimento ▇▇▇▇▇ notificação. Atenciosamente, ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ JÚNIOR O silêncio de V. Sas., em o prazo sobredito, comprovará o desinteresse pela aquisição, liberados os barracões para venda a terceiros, nos termos da Lei número, 8.245/91 · Please refer to Schedule 7.10.2. The Real Estate Municipal Enrollment (IPTU) is still to be issued. The documents of the Real Estate Properties registered before the 2nd Registry of Real Estate of Piracicaba under No. 78.128 and 18.227 are not duly updated in order to reflect Fibria’s current corporate name. Please refer to Schedule 7.10.2. The following constructions are not duly regularized before the authorities: · Buildings No.43 to 47, with area of 1.110,75 m², located in the Real Estate registered before the 2nd Registry of Real Estate of Piracicaba under No. 78.126; · Mill with area of 49.845,23 m² located in the Real Estate registered before the 2nd Registry of Real Estate of Piracicaba under No. 18.226; · ▇▇▇▇▇▇▇▇ ▇▇.▇▇, with area of 49,32m², located in the Real Estate registered before the 2nd Registry of Real Estate of Piracicaba under No. 35.286; and · Building No.42, with area of 1.920,00 m², located in the Real Estate registered before the 2nd Registry of Real Estate of Piracicaba under No. 35.288. Please refer to Schedule 7.10.2. 104837 ▇▇▇▇▇▇ DONIZETI DOS ▇▇▇▇▇▇ ▇▇▇.▇▇▇.▇▇▇-▇▇ 173147 ▇▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇▇ 225.777.518-00 167389 DAVID COPPEDE 225.278.398-27 56376 ROSANA ALVES DE OLIVEIRA 147.714.688-18 70185 MARCIA APARECIDA LOMBARDI MAIA 044.052.948-44 70183 CAROLINA LUVISOTTO GALLO COSTA 217.870.108-64 6...
View Source
SRS. The SRS (System Requirement Specification) is a list of requirements, written in natural language (no formal notation, few/no diagrams). A SRS has been written for the pilot, and is included in this document (see section 6.1).
View Source

Related to SRS

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.