m Text replacement - "== Dutch ==" to "=== Dutch ===" |
m Text replacement - "==== English ====" to "=== English ===" Tag: Manual revert |
||
| (7 intermediate revisions by the same user not shown) | |||
(No difference)
| |||
Latest revision as of 14:04, 3 July 2024
Dutch
- Programma van Eisen (PvE)
- Pakket van Eisen
English
- translatorscafe.com[1]
- specification of requirements, statement of requirements (Michael Beijer)
- Groot Woordenboek Industrie & Techniek (GWIT)
- summary of requirements, list of requirements, schedule of requirements
- (Onroerend Goed Lexicon, Aart van den End)
- schedule of requirements, brief, terms of reference
- (Juridisch-Economisch Lexicon, Aart van den End)
- terms of reference (ToR), schedule of requirements
- technisch programma van eisen
- technical terms of reference
Wikipedia: ‘Terms of reference’
Terms of reference (TOR) define the purpose and structures of a project, committee, meeting, negotiation, or any similar collection of people who have agreed to work together to accomplish a shared goal.[1][2]
Terms of reference show how the object in question will be defined, developed, and verified. They should also provide a documented basis for making future decisions and for confirming or developing a common understanding of the scope among stakeholders. In order to meet these criteria, success factors/risks and constraints are fundamental. They define the:
- vision, objectives, scope and deliverables (i.e. what has to be achieved)
- stakeholders, roles and responsibilities (i.e. who will take part in it)
- resource, financial and quality plans (i.e. how it will be achieved)
- work breakdown structure and schedule (i.e. when it will be achieved)
TORs should include:[3][citation needed]
- success factors, risks and constraints.
Although the terms of reference of a project are sometimes referred to as the project charter,[4] there are significant differences between the two. This article describes a TOR containing detailed definitions, while a project charter has high-level requirements, assumptions, constraints and descriptions as well as a budget summary without detail, and a milestone-only schedule.[5]
lawinsider.com: ‘Schedule of Requirements’
Schedule of Requirements means that part of the contract which identifies, either directly or by reference, the Contractor Deliverables to be supplied or carried out, the quantities involved and the price or pricing terms in relation to each Contractor Deliverable.
(https://www.lawinsider.com/dictionary/schedule-of-requirements)
groenewout.com: ‘Drawing up Program of Requirements’
A specification of requirements or Program of Requirements (PoR) is a document used in a design or procurement process. An optimal construction process begins with a thorough requirements specification, which comprehensively details the demands and wishes. The aim of a Program of Requirements is to lay down a clear framework for everyone involved in the project so that everyone understands which criteria must be met. Hence, the Program of Requirements is an important guideline for the designers to ensure that they deliver the desired result.
(https://www.groenewout.com/drawing-up-program-of-requirements/)
- ↑ ‘Well, here's what the OOP [Office for Official Publications in Luxembourg] has to say: The term generally used in this context is specification of requirements or statement of requirements. The term schedule of requirements may also be used but that is generally used only to set out requirements in chronological order (planning). The term design brief is less common but is used in designs of various kinds - e.g. software designs, architectural designs etc. where a proof of concept is required. Programme of requirements is not often used.’ (https://www.translatorscafe.com/tcterms/en/question.aspx?id=97975 + https://www.proz.com/kudoz/dutch-to-english/law-contracts/4835372-pakket-van-eisen-pvr.html)