How do you understand the gist of writing a requirements analysis for information management systems

Hello software technology students, I am also in this question.

As a preliminary feasibility study report, the project proposal is a contour of the project before investment, and the project proposal is a document submitted by the project investor to its competent department, which is currently widely used in the national approval of the project. It should discuss the necessity and possibility of project establishment from a macro perspective, and turn the project investment idea into a rough investment proposal. The submission of the project proposal can be used by the project approval authority to make preliminary decisions.

It can reduce the blindness of project selection and lay the foundation for the next feasibility study. According to our years of experience, a project to obtain the best support, first must have a project proposal, the project proposal through the screening, and then the feasibility study of the project, the feasibility study report by experts, before the final approval. This is actually a common approval process and serves as the basis for inclusion in alternative projects and pre-construction work plan decisions.

After the project proposal and the preliminary feasibility study report are approved, the work centred on the feasibility study can be carried out. The project proposal we provide includes the strategy, marketing and sales of the project, scale, site selection, materials**, process, organization and staff, investment, benefits, risks, etc., which will make the benefits of your opportunity study or planning more credible, and the project more attractive or feasible.

Analyze what kind of function the designed software is intended to accomplish.

Methods First, the organizational structure was investigated.

This includes understanding the organization's departmental composition, the functions of each department, etc., in preparation for the analysis of information processes.

The operational activities of each department are then investigated.

This includes understanding what data is input and used by each department, how the data is processed, what information is output, to which department, and what is the format of the output results.

Assist users in clarifying the various requirements for the new system.

This includes information requirements, processing requirements, completeness and completeness requirements.

Determine the boundaries of the new system.

Determine which functions are performed by the computer or will be prepared for the computer to be done in the future, and which activities are performed by humans. What is done by a computer is what a new system should do.

Commonly used survey methods are:

Follow-up assignments. Understand the status of business activities by participating in business work in person. This method can accurately understand the needs of users, but it is more time-consuming.

Conduct an investigative meeting. Through discussions with users, we can understand the business activities and user needs. During the discussion, participants can inspire each other.

Please introduce yourself.

Ask questions about some surveys, and you can ask someone to ask them.

The design questionnaire is for users to fill out.

If the questionnaire is properly designed, this method is effective and easy for users to accept.

Access to records. That is, to consult the data records related to the original system, including original documents, account books, statements, etc.

After understanding the user's needs through the survey, it is necessary to further analyze and express the user's needs.

There are two main methods for analyzing and expressing user needs: top-down and bottom-up.

To design a well-performing database system, it is important to clarify the requirements of the application environment for the system. In particular, the data applications are very broad and complex, and it is difficult to succeed without a full and detailed analysis of the information beforehand. Through the requirements analysis stage, a comprehensive and detailed investigation of the entire application of the information system is carried out, the objectives of the information system are determined, the basic data supporting the overall design objectives of the system and the requirements for these data are collected, the needs of users are determined, and these are written into documents that are acceptable to both users and database designers.

In fact, requirements analysis is one of the hardest tasks in database development. Because, first, the system itself is variable, and the needs of users must constantly adjust to adapt to this change. Second, it is difficult for users to tell the functional process of a certain part of the work.

Therefore, designers must recognize the importance of user participation in the whole requirements analysis and system design process, and investigate and analyze through various methods.