Static Structure Sample Clauses

Static Structure. ‌ In RSML the static structure of the software system is described using so called components, i.e., separate encapsulated blocks of the software system. Each component has an interface definition that describes the inputs and outputs of the component. Variables with defined types are used for the description of inputs and outputs. In order to distinguish these inputs and outputs from the system inputs and outputs they are referred to as component inputs and component outputs. Please note, that component outputs of one component can be component inputs of another component or system outputs. Likewise, component inputs of a component can either be component outputs of another component or system inputs.
AutoNDA by SimpleDocs

Related to Static Structure

  • Report Structure Provides an analysis of each error type (by error code). The report is in descending order by count of each error code and provides the following: • Error Type (by error code) • Count of each error type • Percent of each error type • Cumulative percent • Error Description • CLEC Caused Count of each error code • Percent of aggregate by CLEC caused count • Percent of CLEC caused count • BellSouth Caused Count of each error code • Percent of aggregate by BellSouth caused count • Percent of BellSouth by BellSouth caused count. Data Retained Relating to CLEC Experience Relating to BellSouth Performance • Report Month • Total Number of Lsrs Received • Total Number of Errors by Type (by Error Code) - CLEC caused error • Report Month • Total Number of Errors by Type (by Error Code) - BellSouth System Error SQM Disaggregation - Analog/Benchmark SQM Level of Disaggregation SQM Analog/Benchmark • Not Applicable • Not Applicable SEEM Measure SEEM Measure No Tier I Tier II O-5: Flow-Through Error Analysis SEEM Disaggregation - Analog/Benchmark SEEM Disaggregation SEEM Analog/Benchmark • Not Applicable • Not Applicable O-6: CLEC LSR Information O-6: CLEC LSR Information Definition A list with the flow through activity of LSRs by CC, PON and Ver, issued by each CLEC during the report period. Exclusions • Fatal Rejects • LSRs submitted manually Business Rules The CLEC mechanized ordering process includes all LSRs, including supplements (subsequent versions) which are submitted through one of the three gateway interfaces (TAG, EDI, and LENS), that flow through and reach a status for a FOC to be issued. The CLEC mechanized ordering process does not include LSRs which are submitted manually (for example, fax and courier). Calculation Not Applicable

  • Agreement Structure 2.1 An “Agreement” hereunder shall consist of this Master Agreement, the Schedule, and their applicable attachments and represents the complete and exclusive agreement between the Parties regarding the subject matter of the Schedule, and replaces any prior oral or written communications between the Parties relating thereto. Each Lease is effective when the Schedule containing such Lease is executed by the Parties thereto.

  • Classification Structure All employees working under this Agreement shall be classified according to the skill based classification structure set out in Appendix A.

  • Credit Structure To obtain a credit, Customer must open a Trouble Ticket in accordance with the “Process for Customer to Apply for SLA Credits” section below. Verizon will work with Customer to confirm that a DDR issue exists with the Core Network and repair the problem(s), as applicable. Once Verizon confirms that the DDR on the Core Network for a specific Customer E-Line EVC connection does not comply with this Service Level Standard, Verizon will have thirty (30) calendar days from the opening of the Trouble Ticket to address the Service Issue and close the applicable Trouble Ticket before Customer may be eligible for SLA credits. If, after thirty (30) calendar days of opening the Trouble Ticket, the DDR Service Level Standard issue is not corrected, but has been agreed to as a Service Issue, Customer may qualify for credits.

  • Management Structure Describe the overall management approach toward planning and implementing the contract. Include an organization chart for the management of the contract, if awarded. 3.2

  • Organizational Structure The ISO will be governed by a ten (10) person unaffiliated Board of Directors, as per Article 5 herein. The day-to-day operation of the ISO will be managed by a President, who will serve as an ex-officio member of the ISO Board, in accordance with Article 5 herein. There shall be a Management Committee as per Article 7 herein, which shall report to the ISO Board, and shall be comprised of all Parties to the Agreement. There shall be at least two additional standing committees, the Operating Committee, as provided for in Article 8, and the Business Issues Committee, as provided for in Article 9, both of which shall report to the Management Committee. A Dispute Resolution Process will be established and administered by the ISO Board in accordance with Article 10.

  • FEE STRUCTURE In consideration of Consultant providing services, Municipality shall pay Consultant for Services performed in accordance with Exhibit A – List of Services and Fee Schedule.

  • Administrative Structure ‌ This agency’s organizational chart is attached. It identifies the units and staff within the agency that are involved in the operation of the district’s employment program. Following is a description of the office(s) in and/or outside of the Department of Social Services that are involved in the operation of the district’s employment program. The responsibilities of each office are described below.

  • Payment Structure You must pay the fees listed on the relevant Services Order. Subscription payments will be structured differently based on the term you select from the three options below and the payment structure will be set forth in the Services Order. The fees identified in the Services Order are exclusive of shipping fees, and you will pay the shipping fees (if applicable) identified in the invoice.

  • Governance Structure The Academy shall be organized and administered as a Michigan nonprofit corporation under the direction of the Academy Board and pursuant to the governance structure as set forth in the Bylaws. The Academy’s Board of Directors shall meet monthly unless another schedule is mutually agreed upon by the President and the Academy. The Academy shall not delegate this duty of organization and administration of the Academy without the express affirmative consent of the University.

Time is Money Join Law Insider Premium to draft better contracts faster.