This document collects, analyzes and defines the general requirements of the user and the functions of the product. Focus on the functions required by target users and why these requirements exist. Specific requirements for how the application meets these requirements shall be indicated elsewhere in the application model and in the additional specification. The confusion is largely the result of a lack of knowledge of the purpose of a vision document and the new director`s unusual desire to involve all employees in management and decision-making. Combined with a lack of previous creative and participatory management practices, the result is a persistent failure to recognize the power of organizational aspirations. By placing this diagram next to the other four sections described earlier, the vision document makes the vision document as easy as possible for stakeholders to judge whether the design of the application – at the highest level – matches the promises made to business users. For example, the system analyzer can easily verify that there is a general transformation plan for each source identified in the contextual diagram, simply by taking into account the first column of the data flow diagram. Similarly, the business analyst can check whether the EDW team has planned to provide all the necessary pieces of information for the desired pre-final applications by looking at the last column of the same chart. What has been misunderstood? How can she help them better understand what she hopes to create? Why is this vision document important? We use the term basic document to describe what you use as a warehouse for all your information, descriptions, and data related to a single persona. The core document contains the information that motivates and justifies design decisions and generates scenarios displayed in feature specifications, visionary documents, storyboards, etc. .