Top 7 Documentation during IT Requirement Phase

The scope and objectives for the system. A scope should be “holistic,” incorporating both the technical environment as well as a business perspective. Below top 7 documentation that should be completed during IT requirement phase

1. A statement of the problem needing to be solved by the system.

2. The system goals and objectives. Be sure to include goals and objectives from a technical as well as a business perspective.

3. Feasibility analysis. Feasibility analysis defines the constraints or limitations for the system from a technical as well as a business perspective. Feasibility should be assessed in the following categories: economic, technical, operational, schedule, legal or contractual, and political. Feasibility can include those things that are tangible, intangible, one-time, or recurring.

4. Other assumptions made regarding the system such as compliance with existing business practices.

5. Expected system functions to be provided such as authorizing payments and providing account status.

6. System attributes such as ease of use, fault tolerance, response time, and integration with existing platforms.

7. The context or environment in which the system is expected to operate.