Documenting Findings of Requirements Analysis

Many database designers have notebook computers with CASE tools installed, which they carry with them to assignments. This enables them, for example, to enter business objects, their relationships, and their characteristics directly into the CASE tool while analyzing the existing database(s). The tool then generates a draft entity-relationship (ER) diagram which is easily modified as more information is gleaned.
The triangle of truth is a simple way to look at the important architectural constructs that make up a service oriented architecture. When you consider what is needed to build a service oriented architecture, the triad that makes up the triangle of truth quickly emerges. Specifically, there must be a way to represent the data that is exchanged between services, a mechanism for invoking services, and a way to compose services into a larger integrated business application.

1. Requirements analysis specifies what the the system is required to do based on user/stakeholder input
2. Design specifies how the system will address the requirements
3. Implementation translates design specifications into a working system

Requirements analysis is critical to the success of a project.
Requirements analysis can be applied at several different levels

1. Overall system design
2. Database design
3. GIS application design

Determines data, information, system components, data processing and analysis functions required by an organization, enterprise, individual user.