This concept deals with the importance of having a list of prioritized requirements as a first step to ensure a smooth and successful implementation of a GIS project.. It entails the different methodologies and approaches to ensure a GI system covers all functional and nonfunctional requirements. Requirements are not only derived from business workflows but it is advisable to gather direct input from potential users that will be translated into requirements. However, there is a need to clearly rank the importance of the requirements gathered to ensure the GI system is manageable and in line with the intended use of the GI system, in opposition with the specific interests of a particular user or ambiguous requirements. Therefore, the documentation, traceability and evaluation of requirements after the implementation are as relevant as the initial gathering of requirements to give consistency to the designed system.
Define a methodology for gathering of requirements
Build a mechanism for converting the requirements into a product
Select from conflicting requirements
Develop use cases for potential applications using established techniques with potential users, such as questionnaires, interviews, focus groups, the Delphi method, and/or joint application development
Determine how to integrate or combine the proposed workflow with current applications running
Report existing and potential tasks in terms of workflow and information flow
Assess the relative importance and immediacy of the requirements
Compile the needs of individual users and tasks into enterprise-wide needs
Illustrate how a business process analysis can be used to identify requirements during a GIS implementation
Manage requirements using a management tool (such as Trello, JIRA, etc.)
Completed (GI-N2K)