Requirements Gathering Sample Clauses

Requirements Gathering. Parties Involved: EGI-InSPIRE NA3 (Xxxxx Xxxxxx, XXX.xx); MAPPER WP4 (UCL) Description of work: This activity allows MAPPER to submit new requirements and change requests to EGI-InSPIRE and influence the evolution of the infrastructure and the support services. EGI-InSPIRE will accept requirements in various formats through the defined channels. Requirements will be presented and reviewed by the UCB for ratification before submission to the Technical Coordination Board (TCB). The User Community Support Team (UCST) will provide support to MAPPER in the form of guidelines, services and workshops to help them capture and prioritise their own requirements. Expected outcome:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Requirements Gathering. Image Maintenance ● Insight will update one Windows 10 base image that will be deployed to all agencies. This image can have agency specific applications added to it and will be updated to the current patch level during the build or deployment process. ● Image updates are performed on a quarterly basis for maintenance/security updates. ● Client provides Insight with a listing of all changes that are to be made in each image update (driver version changes, software application changes, software application additions/removals, hardware model additions/removal). ● Insight compiles this list of changes into the requirement document (requests for requirement additions after this time may incur additional charges and will be quoted at T&M rates). ● Insight schedules the engineer and bench time for the project.
Sample 1
Requirements Gathering. A key element of user-centred approaches to system design is the gathering and analysis of user requirements, and incorporation of these as primary inputs into the functional specification of the system. Requirements gathering exercises are concerned with studying and engaging with potential users of the proposed system as a means of identifying:  Current activities and behaviours – what users do and how they do it  Perceived needs – what users know they want  New affordances – options suggested to users that they may not yet have thought of, due to lack of knowledge about what might be possible The first two areas provide information about the status quo and can be ascertained to some degree prior to the development of any prototypes of the new system. The requirements generated in this way are invaluable in understanding the context in which people will be using the system and some of the challenges faced by users that are not currently addressed by existing systems. These requirements will most likely address the core functionality, around which novel aspects of the system will be built. The third level of user requirements addresses new opportunities, and these requirements are often generated once a working prototype has been produced. Ideas for the prototype may therefore be somewhat exploratory, developed from knowledge of what is technically possible or from ideas around novel approaches to user problems. The prototype is then used as a means of testing whether these new developments are viable and/or desirable. Feedback from users who interact with the prototype is then used to validate, refine and prioritise the requirements for the novel elements of the system. For the PATHS project, we intend to gather requirements in all three of these areas, with the first two documented in this report, and the latter incorporated into later stages of the project and reported in due course, along with refinements of the system following testing and evaluation of each of our two prototypes. It is of course also imperative that these requirements are attributed to clearly defined user profiles, and these will also be developed as part of the overall requirements gathering activity. Engagement with users for requirements gathering can involve a number of different techniques, which are selected according to the nature of the system being developed, and within the limits of constraints such as access to users, the experience and skills of the project team, ava...
Sample 1
Requirements Gathering. Conducting meetings with stakeholders to gather detailed requirements and specifications for the custom software solution.
Sample 1
Requirements Gathering. This phase of the project involves cooperation between Genuity/GNI and GTE and addresses the following questions: . What business problems the product in mind is supposed to solve? . Is a central global alarm repository a requirement? . Level of PM and FM data correlation? . How long does the data warehouse needs to keep information in history? . What are the requirements for data granularity? . Report types and categories. . OLAP capability requirements. . Data visualization capability requirements. . Data warehousing performance requirements. . Availability and scalability requirements . Etc. SOW - GNI Intelligent Reporting and Analysis --------------------------------------------------------------------------------
Sample 1
Requirements Gathering a. Define total e-Commerce business model for the Hardware Industry b. Execute usability study with customers (50-100 retailers): likes, dislikes, concerns c. Execute usability study with manufacturers (10-20): likes, dislikes, concerns d. Target list of software vendor candidates
Sample 1
Requirements Gathering. After completing the business process redesign, a collaborative requirement gathering workgroup session will be held to define functional system requirements for the development and implementation of a telemedicine system. The requirements gathered from the workgroup will be used as an input to the request for proposal in the identification of a telemedicine vendor.'
Sample 1
AutoNDA by SimpleDocs

Related to Requirements Gathering

  • Management Reporting (a) Provide periodic reports, in accordance with agreed upon frequency and content parameters, to the Funds. As reasonably requested by the Funds, the Transfer Agent shall furnish ad hoc reports to the Funds.

  • Licensing Requirements The following licensing requirements shall apply when the applicable Florida Statute mandates specific licensing for Contractors engaged in the type of work covered by this solicitation.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • 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.

  • Environmental Compliance and Reports Borrower shall comply in all respects with any and all Environmental Laws; not cause or permit to exist, as a result of an intentional or unintentional action or omission on Borrower's part or on the part of any third party, on property owned and/or occupied by Borrower, any environmental activity where damage may result to the environment, unless such environmental activity is pursuant to and in compliance with the conditions of a permit issued by the appropriate federal, state or local governmental authorities; shall furnish to Lender promptly and in any event within thirty (30) days after receipt thereof a copy of any notice, summons, lien, citation, directive, letter or other communication from any governmental agency or instrumentality concerning any intentional or unintentional action or omission on Borrower's part in connection with any environmental activity whether or not there is damage to the environment and/or other natural resources. Additional Assurances. Make, execute and deliver to Lender such promissory notes, mortgages, deeds of trust, security agreements, assignments, financing statements, instruments, documents and other agreements as Lender or its attorneys may reasonably request to evidence and secure the Loans and to perfect all Security Interests.

  • Tax Requirements The Participant is hereby advised to consult immediately with his or her own tax advisor regarding the tax consequences of this Agreement. The Company or, if applicable, any Subsidiary (for purposes of this Section 28, the term “Company” shall be deemed to include any applicable Subsidiary), shall have the right to deduct from all amounts hereunder paid in cash or other form, any Federal, state, local, or other taxes required by law to be withheld in connection with this Award. The Company may, in its sole discretion, also require the Participant receiving shares of Common Stock issued under the Plan to pay the Company the amount of any taxes that the Company is required to withhold in connection with the Participant’s income arising with respect to this Award. Such payments shall be required to be made when requested by the Company and may be required to be made prior to the delivery of any certificate representing shares of Common Stock. Such payment may be made (i) by the delivery of cash to the Company in an amount that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding obligations of the Company; (ii) if the Company, in its sole discretion, so consents in writing, the actual delivery by the exercising Participant to the Company of shares of Common Stock other than (A) Restricted Stock, or (B) Common Stock that the Participant has not acquired from the Company within six (6) months prior to the date of exercise, which shares so delivered have an aggregate Fair Market Value that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding payment; (iii) if the Company, in its sole discretion, so consents in writing, the Company’s withholding of a number of shares to be delivered upon the exercise of the Stock Option other than shares that will constitute Restricted Stock, which shares so withheld have an aggregate fair market value that equals (but does not exceed) the required tax withholding payment; or (iv) any combination of (i), (ii), or (iii). The Company may, in its sole discretion, withhold any such taxes from any other cash remuneration otherwise paid by the Company to the Participant. * * * * * * * *

  • Financial Requirements A report of monthly and cumulative financial requirements; and

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