Requirements, Development, and Testing Requirements Gathering Sample Clauses

Requirements, Development, and Testing Requirements Gathering. KNOWiNK will meet with City to customize and reconfigure software to City needs based on the City’s voter check in workflow. Requirements may include business, functional, non- functional, and user interface requirements. KNOWiNK’s Product Managers will be onsite for the first meeting, then additional workshops will be conducted via webex. SMEs or process owners from the City are needed to understand the process. Development KNOWiNK will conduct requirement gathering meetings to determine what application changes are needed by the City. The first will coincide with the kickoff meeting. A subject matter expert form the City will be required to review the workflow. After that, weekly workshops lasting an hour will be scheduled to close any gaps. After requirements have been documented, KNOWiNK’s business analyst will create User Stories, which will be Statement of Work reviewed in the requirements workshops. The development team at KNOWiNK will use these to estimate level of effort and implement changes to the base application. The City’s Project Manager will sign off when the City agrees that user stories meet the specification of changes. Work described in story cards is estimated and assigned, and developers create tasks needed to develop functionality. The tasks are associated to the card, and the cards are assigned to a sprint. Once a card is complete, the team performs peer reviews of submitted code. If the peer review is approved, the card is moved to the QA team. KNOWiNK uses GitHub’s software repository for secure storage and version control of both the Poll Pad and ePulse applications. Development is performed on a development branch, regression testing occurs on a stable master branch, and release branches are created and maintained for major releases. The engineering team uses IDEs such as Xcode to debug the application in its native environment, as well as third party tools like Bugsee for deployed releases. At the time of deployment, Release Notes are made available, including: • Version number • Requirements met, by feature • Bug fixes • Known issues Testing The QA team receives cards which have passed peer-review and test each user story individually. QA testing covers both the individual products and their interoperability. Prior to the deployment of a build or release, a week-long regression plan is performed to ensure that new development is functioning correctly and has not affected existing functionality. Once QA has approved a card, Bus...
Sample 1
AutoNDA by SimpleDocs

Related to Requirements, Development, and Testing Requirements Gathering

  • General Program Requirements Subrecipient shall adhere, but not be limited to, the following requirements for all programs:

  • Human and Financial Resources to Implement Safeguards Requirements 6. The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Developer Operating Requirements (a) Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time.

  • Training Requirements Grantee shall:

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Development Requirements The exterior wall standards set forth in this section shall apply to the structures located on the Property. At least ninety percent (90%) of the combined exterior surface area of all walls, including all stories of buildings / structures, shall consist of stone, brick, painted or tinted stucco, and factory tinted (not painted) split faced concrete masonry unit or similar material approved by the Director of Planning.

  • Testing Requirements 12.1. Workplaces -

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