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:
Requirements Gathering. OpenGov will ● Provide a three-day (3-day) onsite requirement gathering workshop to increase our understanding of your business and functional goals. Through workshops and interviews, OpenGov will identify best fit scenarios for OMS and provide a brief including any challenges as well as recommendations for OMS best practices relevant to your implementation. Configurations OpenGov will: ● Provide configuration services, including: o Up to ten (10) custom fields and up to two (2) custom layouts per asset type listed in the Assets section below o Up to thirty (30) custom fields and up to ten (10) custom layouts to be utilized in any of the shared areas of the system, such as Tasks o Up to twenty (20) automations o Up to twenty (20) preventative maintenance plans Training OpenGov will: Foundational Training ● Provide remote train-the-trainer training, up to two (2) hours, on overall system navigation and functionality to help familiarize your staff with the software environment and its common functions. Training topics include: o Dashboards o Standard KPI/ROI Xxxxxxx o Logins/Permission o Layers o Filters o Maps o Grids o System Navigation o Views (List & Detail) o Standard Reports o Attachments o Requests, Work, Assets, Resources, Reports, and Administrator Tabs ● Provide remote train-the-trainer training, up to one (1) hour, for an overview of Preventative Maintenance Plans. ● Provide remote train-the-trainer training, up to one (1) hour, for an overview of Asset Condition Manager and Advanced Inspections. ● Provide remote train-the-trainer training, up to two (2) hours, for an overview of Reporting. ● Provide remote train-the-trainer training, up to two (2) hours, on OMS Esri integration functionality. Training topics include: o OMS Esri integration configuration options o Integration functionality (basemap and feature) o Overall Esri integration requirements, considerations, and OpenGov recommended best practices Train the Trainer Training Event ● Provide a three-day (3-day) onsite "train-the-trainer" training event. The training agenda will be defined and agreed upon by both OpenGov and your project manager. To avoid redundancy, and to utilize service time efficiently, training may cover a subset of the assets listed in the Asset section of the scope. Topics may include any of the following: o Request Management: ▪ Requests ▪ Requesters ▪ Task Creation from Requests ▪ Issue library (including settings such as Applies to Asset and Non-Location) ▪ OpenGov ...
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.
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...
Requirements Gathering. Conducting meetings with stakeholders to gather detailed requirements and specifications for the custom software solution.
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 --------------------------------------------------------------------------------
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
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.'
