Requirements Engineering Sample Clauses

Requirements Engineering. 6.6.2 SLA Negotiation 6.6.3 SLA Agreement 6.6.4 SLA Monitoring 6.6.5 SLA Expiration
Sample 1
Requirements Engineering. The ADVANCE7 project (along with the Deploy project, covered in the next section) is based around the Rodin tool and the Event-B formalism. ADVANCE extended Rodin to allow for FMI co-simulation between Event-B models and arbitrary FMUs. The Rodin tool supports ProR for managing textual requirements including hierarchies and links. The tool is now part of the Eclipse incubator program. The COMPASS8 project developed an approach for the development of Architectural Frameworks (COMPASS Architectural Framework Framework - CAFF). This was used to develop guidelines for SoS requirements modelling 9 called SoS-ACRE. Although the CAFF is agnostic with respect to modelling language, the guidelines were realised in SysML and insight from this fed into the SysML guidance given in Deliverable D3.1a [FGPP15]. The SPEEDS10 project developed a Contract Specification Language (CSL), allowing col- laborating teams to define requirements and promises about the components that their team is developing. This was extended in the DANSE11 project to become the Goal and Contract Specification Language (GCSL), which permits architectural aspects to be captured in OCL12 (Object Constraint Language) notation. DANSE methodology docu- ments13 advocate formalising requirements late in the architectural design workflow. The TOPCASED project included TOPCASED-Req, a solution to manage requirement traceability in model for aviation, following the DO-178B lifecycle. The AGeSys14 Project improved TOPCASED-Req to move away focus on the whole requirements lifecycle as 7xxxx://xxx.xxxxxxx-xxx.xx/ 8xxxx://xxx.xxxxxxx-xxxxxxxx.xx/ 9xxxx://xxx.xxxxxxx-xxxxxxxx.xx/Project/Deliverables/D211.pdf 00xxx.xxxxxx.xx.xxx 11xxxx://xxxxx-xx.xx/ 00xxx.xxx.xxx/xxxx/XXX 13xxxx://xxxxx-xx.xx/home/pdf/danse_d4.3_methodology_v2.pdf 14xxxx://xxx.xxxxxxxxx-xxxxxx.xxx/sites/default/files/encart_html/index.html#1 a new tool called becomes ReqCycle. TOPCASED and ReqCycle now form part of the PolarSys15 open-source tools for embedded systems. The META tool being developed under DARPA AVM (Adaptive Vehicle Make) pro- gramme makes use of the CyPhyML meta language. In terms of requirements they focus on “executable requirements” that are quantifiable tests that can be automatically checked against models or implementations. This has been demonstrated in OpenModelica. The ENOSYS16 project targeted design space exploration for FPGA design, using the XXXXX UML profile for high-level specification. The Modelio tool was used i...
Sample 1
Requirements Engineering. Requirements Engineering (RE) can be considered as one of the most critical phases in software development processes. Incomplete, low-quality, and suboptimally prioritized requirements can lead to cost explosions and often to the cancellation of a software project [LEF1997]. A major reason is that stakeholders in software projects often take suboptimal decisions. For example, highly relevant requirements are implemented in late releases. Such decisions trigger, for example, opportunity costs since the earlier the software is applicable, the earlier business processes can be supported more efficiently. The reasons for suboptimal decisions are manifold. For example, the relevance of a requirement could have been underestimated simply due to the lack of decision-relevant knowledge of stakeholders who are in charge of prioritizing and release planning. The reason behind this could be a low degree of knowledge exchange between stakeholders. For similar reasons, the quality of individual requirements could have been overestimated. Due to anchoring effects [SFL+2015], the opinion of one stakeholder can have an influence on the opinions of other stakeholders. Polarization effects [ARF2018] can lead to situations where groups take decisions that are riskier compared to the riskiness of decisions taken by individual stakeholders. Such decision biases can be regarded as a major obstacle for high-quality decision making [FBS+2018].
Sample 1
Requirements Engineering. ‌ Traditionally, software engineering divides requirements in two categories: functional requirements (what the system should do) and non-functional requirements (performance, quality of service, etc.). In the areas of adaptive and open-ended systems, both functional and non-functional requirements are better expressed in terms of “goals” [MCY99]. A goal, in most general terms, represent a desirable state of the affairs that an entity, that is a software component or software system, aims to achieve. In ASCENS we propose SOTA for capturing and specifying the requirements of autonomic sys- tems. SOTA is an extension of existing goal-oriented requirements engineering approaches that in- tegrates elements of dynamical systems modeling to account for the general needs of dynamic self- adaptive systems and components. SOTA models the entities of a self-adaptive system as n-dimensional space S, with each dimension representing a specific aspect of the current situation of the entity/ensemble and of its operational environment. As an entity executes, its position in S changes either due to its specific actions of or because of the dynamics of environment. Thus, we can generally see this evolution of the system as a movement in S. 1UML website: xxxx://xxx.xxx.xxx/‌ 2BPMN website: xxxx://xxx.xxx.xxx/spec/BPMN/2.0/ 3SPEM website: xxxx://xxx.xxx.xxx/spec/SPEM/2.0/ In this context, a goal in SOTA can be expressed in terms of a specific state of the affairs to aim for, that is, a specific point or a specific area in S which the entity or the system as a whole should try to reach, despite the fact that external contingencies can move the trajectory farther from the goal. Along this lines, the activity of requirements engineering for self-adaptive systems in SOTA im- plies: (i) identifying the dimensions of the SOTA space, which means modeling the relevant infor- mation that a system/entity has to collect to become aware of its location in such space, a necessary condition to recognize whether it is correctly behaving and adapt its actions whenever necessary; (ii) identifying the set of goals for each entity and for the system as a whole, which also implies identi- fying when specific goals gets activated and any possible constraint on the trajectory to be followed while trying to achieve such goals. The SOTA modeling approach is very useful to understand and model the functional and adap- tation requirements, and to check the correctness of such specifications (as descr...
Sample 1
Requirements Engineering. ‌ Traditionally, software engineering divides requirements in two categories: functional requirements (what the system should do) and non-functional requirements (performance, quality of service, etc.). In the areas of adaptive and open-ended systems, both functional and non-functional requirements are better expressed in terms of “goals” [MCY99]. A goal, in most general terms, represent a desirable state of the affairs that an entity, that is a software component or software system, aims to achieve. In ASCENS we propose SOTA for capturing and specifying the requirements of autonomic sys- tems. SOTA is an extension of existing goal-oriented requirements engineering approaches that in- tegrates elements of dynamical systems modeling to account for the general needs of dynamic self- adaptive systems and components. SOTA, which stands for “state of the affairs”, models the entities of a self-adaptive system as n- dimensional space S, with each dimension representing a specific aspect of the current situation of the entity/ensemble and of its operational environment. As an entity executes, its position in S changes either due to its specific actions of or because of the dynamics of environment. Thus, we can generally see this evolution of the system as a movement in S. In this context, a goal in SOTA can be expressed in terms of a specific state of the affairs to aim for, that is, a specific point or a specific area in S which the entity or the system as a whole should try to reach, despite the fact that external contingencies can move the trajectory farther from the goal. Along this lines, the activity of requirements engineering for self-adaptive systems in SOTA im- plies: (i) identifying the dimensions of the SOTA space, which means modeling the relevant infor- mation that a system/entity has to collect to become aware of its location in such space, a necessary condition to recognize whether it is correctly behaving and adapt its actions whenever necessary; (ii) identifying the set of goals for each entity and for the system as a whole, which also implies identi- fying when specific goals gets activated and any possible constraint on the trajectory to be followed while trying to achieve such goals. The SOTA modeling approach is very useful to understand and model the functional and adap- tation requirements, and to check the correctness of such specifications (as described in [AZ12]). However, when a designer considers the actual design of the system, SOTA ...
Sample 1
Requirements Engineering. STATE-OF-THE-ART The overall goal of this section is to provide an overview of the state of the art in recommendation and decision technologies for requirements engineering. This overview will be adapted/extended within the scope of the first two years of OpenReq. Thereafter, we plan to transfer our documentation of OpenReq research results and related work into a corresponding journal publication (the concrete journal is not yet decided). In the following subsections we provide an overview of the state-of-the-art research that exists related to recommendation and decision technologies in requirements engineering. In the context of each subsection, we also discuss OpenReq research goals related to the advancement of the existing state-of-the-art.
Sample 1
Requirements Engineering. Service Level Agreement Staff forms together with the CRM Staff a team and decide on who is the requirements engineering agent. This agent gets in contact with the customer and defines customer requirements. This person needs to be an expert concerning the service offered by the company, to match customer requirements with existing services or to define if required services are possible to be delivered in commercial and technical view. A close cooperation with the Service Design Process, CRM and all Operation Processes is necessary.
Sample 1

Related to Requirements Engineering

  • Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.

  • Engineering Forest Service completed survey and design for Specified Roads prior to timber sale advertisement, unless otherwise shown in A8 or Purchaser survey and design are specified in A7. On those roads for which Forest Service completes the design during the contract, the design quantities shall be used as the basis for revising estimated costs stated in the Schedule of Items and adjusting Timber Sale Account. (a) A7 to show Purchaser’s performance responsibility. (b) The Schedule of Items to include costs of survey and design, as provided under B5.24, and adjust Timber Sale Account, as provided in B5.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Inspection; Compliance Lessor and Lessor's Lender(s) (as defined in Paragraph 8.3(a)) shall have the right to enter the Premises at any time, in the case of an emergency, and otherwise at reasonable times, for the purpose of inspecting the condition of the Premises and for verifying compliance by Lessee with this Lease and all Applicable Laws (as defined in Paragraph 6.3), and to employ experts and/or consultants in connection therewith and/or to advise Lessor with respect to Lessee's activities, including but not limited to the installation, operation, use, monitoring, maintenance, or removal of any Hazardous Substance or storage tank on or from the Premises. The costs and expenses of any such inspections shall be paid by the party requesting same, unless a Default or Breach of this Lease, violation of Applicable Law, or a contamination, caused or materially contributed to by Lessee is found to exist or be imminent, or unless the inspection is requested or ordered by a governmental authority as the result of any such existing or imminent violation or contamination. In any such case, Lessee shall upon request reimburse Lessor or Lessor's Lender, as the case may be, for the costs and expenses of such inspections.

  • Value Engineering The Supplier may prepare, at its own cost, a value engineering proposal at any time during the performance of the contract. The value engineering proposal shall, at a minimum, include the following; a) the proposed change(s), and a description of the difference to the existing contract requirements; b) a full cost/benefit analysis of the proposed change(s) including a description and estimate of costs (including life cycle costs) the Procuring Entity may incur in implementing the value engineering proposal; and c) a description of any effect(s) of the change on performance/functionality.

  • Geotechnical Engineer « »« » « » « » « » « »

  • No Reverse Engineering You may not, and you agree not to or enable others to, copy (except as expressly permitted by this License or by the Usage Rules if they are applicable to you), decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of the Apple Software or any services provided by the Apple Software, or any part thereof (except as and only to the extent any foregoing restriction is prohibited by applicable law or to the extent as may be permitted by the licensing terms governing use of open-sourced components included with the Apple Software).

  • Investment Analysis and Implementation In carrying out its obligations under Section 1 hereof, the Advisor shall: (a) supervise all aspects of the operations of the Funds; (b) obtain and evaluate pertinent information about significant developments and economic, statistical and financial data, domestic, foreign or otherwise, whether affecting the economy generally or the Funds, and whether concerning the individual issuers whose securities are included in the assets of the Funds or the activities in which such issuers engage, or with respect to securities which the Advisor considers desirable for inclusion in the Funds' assets; (c) determine which issuers and securities shall be represented in the Funds' investment portfolios and regularly report thereon to the Board of Trustees; (d) formulate and implement continuing programs for the purchases and sales of the securities of such issuers and regularly report thereon to the Board of Trustees; and (e) take, on behalf of the Trust and the Funds, all actions which appear to the Trust and the Funds necessary to carry into effect such purchase and sale programs and supervisory functions as aforesaid, including but not limited to the placing of orders for the purchase and sale of securities for the Funds.

  • Engineering Reports (a) Not less than 30 days prior to each Scheduled Borrowing Base Redetermination Date, commencing with the Scheduled Borrowing Base Redetermination to occur on or around March 15, 2007, the Borrower shall furnish to the Administrative Agent and the Lenders a Reserve Report. The Reserve Reports delivered in connection with each March 15 Scheduled Borrowing Base Redetermination, commencing March 15, 2007, shall be prepared by certified independent petroleum engineers or other independent petroleum consultant(s) acceptable to the Administrative Agent. The Reserve Reports delivered in connection with each September 15 Scheduled Borrowing Base Redetermination, commencing September 15, 2007, shall be prepared by or under the supervision of the chief engineer of the Borrower and a Responsible Officer shall certify such Reserve Report to be true and accurate and to have been prepared in accordance with the procedures used in the immediately preceding Scheduled Borrowing Base Redetermination Reserve Report. (b) In the event of an unscheduled redetermination, the Borrower shall furnish to the Administrative Agent and the Lenders a Reserve Report prepared by or under the supervision of the chief engineer of the Obligors together with the certificate of a Responsible Officer who shall certify such Reserve Report to be true and accurate and to have been prepared in accordance with the procedures used in the immediately preceding Reserve Report. For any unscheduled redetermination requested by the Lenders or the Borrower pursuant to Section 2.08(d), the Borrower shall provide such Reserve Report with an “as of” date as required by the Lenders as soon as possible, but in any event no later than 30 days following the receipt of the request by the Administrative Agent. (c) With the delivery of each Reserve Report, the Borrower shall provide, or cause to be provided, to the Administrative Agent and the Lenders, a certificate from a Responsible Officer certifying that, to the best of his knowledge and in all material respects: (i) the information contained in the Reserve Report and any other information delivered in connection therewith is true and correct, (ii) the Obligors and the Partnerships own good and marketable title to the Oil and Gas Properties evaluated in such Reserve Report and such Properties are free of all Liens except for Liens permitted by Section 9.03, (iii) except as set forth on an exhibit to the certificate, on a net basis there are no gas imbalances, take or pay or other prepayments with respect to its Oil and Gas Properties evaluated in such Reserve Report which would require any Obligor to deliver Hydrocarbons produced from such Oil and Gas Properties at some future time without then or thereafter receiving full payment therefor, (iv) none of Obligor’s or and the Partnerships’ Oil and Gas Properties have been sold since the date of the last Borrowing Base determination except as set forth on an exhibit to the certificate, which certificate shall list all of its Oil and Gas Properties sold and in such detail as reasonably required by the Administrative Agent, (v) attached to the certificate is a list of its Oil and Gas Properties added to and deleted from the immediately prior Reserve Report and a list showing any change in working interest or net revenue interest in its Oil and Gas Properties occurring and the reason for such change, (vi) attached to the certificate is a list of all Persons disbursing proceeds to the Obligors from their Oil and Gas Properties, and (vii) all of the Oil and Gas Properties evaluated by such Reserve Report are Mortgaged Property except as set forth on a schedule attached to the certificate.

  • Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered. b. Prepare and distribute appropriate Internal Revenue Service forms for corresponding Fund and shareholder income and capital gains. c. Issue tax withholding reports to the Internal Revenue Service.