Advanced Search
Search Results
351 total results found
Data Integration
Data integration processes for GIS spatial data include data conversion, data merging and data format standardization. These are essential for creating a consistent and unified spatial dataset. Key guidelines include: Adopt an open data format like Shapefil...
Data Sharing
Data sharing guidelines aim to support data sharing among institutions through adoption of common standards and tools. Recommendations include: Establish data sharing protocols and agreements when collaborating with other organizations. Clearly define data ...
Data Quality
The guidelines outline procedures for data validation, error checking, and data accuracy assessments. Data of high quality is essential for making reliable decisions and producing accurate results. Below are guidelines on data quality. Implement data valida...
Data Analysis
i. Geoprocessing: Verify the spatial relationships to avoid overlaps, gaps, or invalid geometries. Ensure all spatial datasets have the same coordinate system or project them to a common one for accurate analysis. Convert data between different formats...
Data Visualization
i. Map Design Principles: Simplicity - Maps should be visually clean, focusing on the most important information while removing unnecessary elements. Legibility - Ensure that the map's text, labels, and symbols are easy to read and understand, even when...
Purpose of the document
This document is divided into two sections and describes the two key elements to the approach and vision of testing within the GoR Institutions: Software Testing Policy: An overview of the values supporting the testing approach Test Guidelines: These are b...
Overview
RISA is driving the government’s digitalization and innovation plan by supporting sectors and institutions in their automation journey. Automation of services and processes involves acquiring or developing software. In order to ensure that the software meets ...
Scope
This document provides policies and guidelines for the planning and execution of software testing activities for Government of Rwanda Institutions. It is crucial that the consumers of this document (i.e., software project teams in Government of Rwanda Institut...
Purpose of this Software Testing policy
The testing policy outlines the high-level strategy and principles for software testing. It outlines the test goals and objectives, benefits and strategies for test process improvement. All subsequent test strategies and low-level test plans will be establishe...
Mission Statement
To ensure that any changes to software do not jeopardize the quality characteristics of mission-critical systems used by GoR Institutions. To verify, validate, and evaluate the quality of software or systems being delivered and to ensure that testing is perfo...
Software Testing Policy Objectives and Principles
The following are the main objectives of the software testing policy: To ensure that testing is planned early in the project so that testing activities may be started as soon as possible in the project life cycle, and resources planned accordingly. To iden...
Benefits of the Software Testing Policy
This testing policy aims to give the GoR institutions the observable advantages listed below: Ensures that testing is a standardized and repeatable activity rather than a customized activity for each project or software modification, i.e., that we are not r...
Purpose of Software Testing Guidelines
The major purpose of these software guidelines is to provide a set of recommendations and best practices for ensuring that systems are properly tested to achieve high quality software solutions. These guidelines explain the basic framework of the testing proce...
Definition of Testing
Below is a description of how testing is defined generally. General Definition Testing is the process of executing program(s) with the intent of finding errors, rather than (a misconception) showing the correct functioning of the program(s). The difference ...
Risk Based Approach to Testing
All facets of the testing lifecycle should be approached using a risk-based approach. Testing should always be done with a view to identifying and reducing any risks the Project/Change may present, depending on the project objectives. The necessary testing wil...
Software Testing Guidelines Objectives
The key principles that should guide the development of strategies for all testing activities are described in the following testing objectives: To ensure creation of a testing plan early on in the project so that resources may be allocated appropriately, a...
Roles and Responsibilities
The table below describes the three aspects of roles and responsibilities of personnel that are typically required to be involved with testing for software. The following defines the three aspects: Standard Testing Roles This is an industry standard testing ...
Fundamental Test Planning Process and Strategies
The four stages of the Fundamental Testing Process must be completed in the correct order. These are Test planning, Test Design, Test Execution and Test Closure. These stages should be carried out in this logical order for any Test Level i.e Unit, System, Syst...
Approaches to Manual Testing
Manual testing is an essential part of the testing approach, given the volume and diversity of the applications that will be developed, supported and utilized by GoR. There are three test techniques to undertake manual testing which have been detailed below. ...
Approaches to Automated Testing
The focus of these guidelines and the initial remit of GoR institution Testing Services is aimed at introducing and embedding the key principles of manual testing to GoR Institutions and associated business areas. Once the principles and associated processes o...