Course 1 of the "Challenge Project" (Business Analysis)

Today, the new project has not yet been formally established, but needs analysis has been roughly completed. There is only one piece of material, "requirement specification" and one Party A's companion, you can ask questions at any time when you are not familiar with your requirements.

In the face of the not-Detailed requirement specification, how to design our system is confusing. As soon as I see this business requirement, I still instinctively think about the specific technical implementation. Of course, I don't mind doing this, because I think this is necessary, this is very good for controlling the overall technical architecture. However, I am worried that Party A and the Project Manager need a process to step-by-step transition from business needs to design and code processes. This document is the support for project initiation and decision making, it may also be the guarantee of the target. What should we do in this process. There are a lot of projects. How to "hack" a new project, how to comprehensively and effectively analyze an unknown project field, and draw a conclusion that it is in urgent need of understanding, I realized that this is also an important step in growth. talents in this field are also urgently needed by the company. (The other main line is the professionalism of some technical fields, both hands must be grasped, both hands must be hard ). Key words: project management, project initiation, business analysis, enterprise impact ect, EA Abstract: today, a new project is coming, how to comprehensively and effectively analyze an unknown Project Field, how to step-by-step transformation from business needs to design and code is an urgent need to master this capability. The following uses a simple "Data Management and query project" as an example, to introduce the specific business analysis process of a project. If all the diagrams are referenced, indicate the source. Http://www.cnblogs.com/wgp13x/p/3824964.html Step 1: Summarize the business objectives. From the user's point of view, we can understand what this project can do for the user, what it can bring, and what it can do. Even the user does not need to know that a computer can help him complete these services. Here we will summarize it into a written form. One by one is listed in the document. For example, "Data Management and query project" can extract such a business objective: To achieve unified management and query of various types of data, it provides users with a convenient and quick data query interface, improve users' full control over people, affairs, and things; Step 2: Divide business boundaries. The business boundary can be divided based on the business objectives. It can be a single boundary or not, and can be adjusted in the future. In this step, we also need to conduct stakeholder analysis. From the user's perspective, we need to record what departments I want to deal. Step 3: perform business analysis. Business analysis is divided into three steps: A. Determination of the leading role of a business boundary, B. Analysis of business cases of a business boundary, c. Implement the business case for a certain business boundary. A. Determine the business leading role of a business boundary. The business leading role is the initiator, receiver, or user of a business, that is, the users who use the project. B. perform business case analysis on a business boundary, and classify the stakeholders and business protagonists in the above steps, how do they communicate with each other during the execution of a business (business can be subdivided in a business boundary), analyze them, and draw a swimming path. The following describes the business segments. The following is a dashboard for querying the Business Use Cases of system A. It describes the specific interaction process. The concept of computers is still not involved here, and these issues are still completely considered from the user's perspective. C. Business Case implementation for a business boundary involves computers and computers as what our system can do for users and how to interact with stakeholders and business leaders, this step needs to be detailed. The following figure shows the dashboard used to query the data business case of system. After the above steps, we can clearly understand all the requirements, what can we do for this project, and how to interact with external entities. The following are System Analysis (system case implementation), outline design, detailed design, and other stages. For more information about the process, see the following summary.

From Wang Anqi http://www.cnblogs.com/wgp13x/p/3824964.html