Semi-formal Requirements Specification Sample Clauses

Semi-formal Requirements Specification. The purpose of the semi-formal requirements specification is to describe the informal requirements of the cruise control system in a semi-formal way such that they can be easily modelled with Event-B. During pilot deployment we decided to use the Problem Frames approach [Jac95, Jac01] and several extensions we developed for semi-formal require- ments engineering because it allows to structure the problem into require- ments, machine, and the physical world. Furthermore, the problem frames approach and our extensions allows us to decompose a given problem, e.g., the development of a cruise control system, into different subproblems which can be handled separately and later recombined in a subsequent phase. The development task in problem frames is to design a machine by building soft- ware that is then executed on a general-purpose computer, specialising the computer to serve a particular purpose [Jac95]. That purpose is to meet a recognised need, which is called requirement. Satisfying the requirement involves transforming the physical world around us. In Problem Frames, the part of the world to be transformed is called the environment. Xxxxxxx states that the parts of any systems engineering problem are the machine, the problem world (environment), and the requirement. Figure 4.1 shows a generalized Problem Frame diagram and its application to the cruise control system. In our application of Problem Frames to the cruise control system, the machine we want to build is the cruise control software running on the en- gine controller. The physical world around us, i.e., the problem world the cruise control software is interacting with, consists of the human machine interface, i.e., the pedals, the lever, and the ignition, as well as the vehicle including engine, engine control, and wheels which need to be controlled by the cruise control. The requirements relate phenomena controlled by the hu- man machine interface, e.g., control signals with phenomena controlled by
AutoNDA by SimpleDocs
Semi-formal Requirements Specification. 19 Machine Problem World software/ hardware Requirement what the problem is about “stakeholder” needs “If the driver presses the resume button, the vehicle shall resume and maintain the previously stored target speed”

Related to Semi-formal Requirements Specification

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Class Specifications The Human Resources Division shall determine:

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!