Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Non Functional Requirements for Information Development Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

This document defines the Non-Functional Requirements for Information Development and are particularly focused on Data Integrity, Performance and Security. Initial estimates at data quality (value issues, data gaps) can be estimated at this stage.

1. Transaction and Data Integrity

  • Provide the requirements around integrity of data at rest in systems and the validation rules and processes for issues with data flowing between systems. This includes process rules for loading data or notifying users should this occur.

2. Performance

  • Expected Business Volumes
  • System Responsiveness
  • Performance Requirements
  • Process Performance
  • Vertical and Horizontal Scalability requirements

3. Security

  • Data Security
  • Encryption Requirements
  • Privacy issues
  • Physical access security


Wiki Contributors
Collapse Expand Close