The history of "engineering project" (ii): System Analysis

The new project has finally entered the system analysis stage. After a lot of business case analysis, we have clarified the requirements, business, and business processing processes, i'm more confident about what the project will do and what it will do. The original intention of business analysis is to clearly understand the complex system requirements, classify the business requirements, and let a layman know what the system can do at a glance. Now we need to perform system analysis. System Analysis is a task of refining, abstracting, and generalization of business analysis. The following describes the process of "engineering project" (I): In business analysis, the business case implementation of "querying system a data business case implementation" is used to see what kind of system analysis results can be extracted. Key words: project management, project initiation, enterprise impact ect, EA, system analysis Abstract: How to further analyze the system from the business analysis results in the face of completed business analysis, this capability is urgently needed to obtain the results of system analysis. The purpose of system analysis is to make the description of a complex system clear and easy to understand. How can a new person perform code compilation independently based on system case analysis, how to determine the business logic and implementation architecture, and control the code logic within the scope of the Code. The following describes the system analysis process of a business case from a simple "query a system data business case implementation. If any reference is available, indicate the source http://www.cnblogs.com/wgp13x/p/3841078.html. The following figure shows the "Business Case implementation of system a Data Query. If you want to get it from the requirement specification manual, please refer to the process 1 (business analysis) of the "Challenge Project" and the business analysis process http://www.cnblogs.com/wgp13x/p/3824964.html. Figure 1-Business Use Case implementation Diagram

1. corresponding to the implementation of this business case, we created a new folder named "query a system data system use cases", which is used to store the system use cases derived from it, the following describes the process of derivation.

2, First, let's try "abstraction". The process for querying system A may be the same as that for system B. We can abstract them into a kind called "querying local systems". Through "abstraction", we can get the system analysis below. The following figure shows the system use case for "querying local systems". It is displayed in an "Interaction diagram. We abstract the instances involved in the "interaction" process into four types: "user", "control", "boundary", and "entity ". We can see that the implementation of this system case involves a "user": system; two "Boundaries": "Index Service" and "Data Storage", involving a "control ": access Local structured data processing ". If you want to obtain the query result, you need to submit the query request according to the Regulations, and then process it by accessing local structured data processing, submit requests to "Index Service" and "Data Storage" in order to obtain the query results. Figure 2-how to query system use cases of a local system 3, Then, we keep trying to "refine". In Figure 1-in the business case implementation diagram, there is a process of "displaying the-type data interface". We think this process is too rough and can be used as an independent system case for analysis, in this way, the Implementation diagram of the system use case "display query a data interface" is obtained. Then, we can further "abstract", "display query a data interface", and "display query B Data Interface, therefore, we changed the system implementation chart to "display the local system data query interface ". The following figure shows the system use case for "displaying the local system data query interface. As you can see, it involves "operator", "client", "query interface controller", "data service", and "metadata object ", the MVC design mode is used. They interact with each other through function calls or message communication, so that the interface definitions between instances are clear. Figure 3-system use case implementation diagram on the data interface of the local system is displayed. The "query database" process is also described as "refined" and analyzed systematically. System Analysis involves such specific implementation technologies as the system architecture, code usage framework, and design pattern, so that you need to clearly describe them in the system case implementation diagram. This system case is so common that we move it to a new folder, under common, common also contains basic system user implementation diagrams such as "data warehouse receiving" and "file warehouse receiving. Figure 4-database system case query implementation Diagram

The following is a system use case of "display query result interface". Similar to the above, the "Interaction diagram" is no longer posted.

In this way, a Business Use Case implementation diagram can be divided into several system use case implementation diagrams by various means. A framework is filled with the meat of the cube, this business case is described more clearly, and even the code implementation and data interface can be basically determined.

The original intention of our system analysis is also like this. How to Make the description of a complicated system clear and easy to understand, and how to let a new person analyze the system based on the system case can write the code independently, how to determine the business logic, implementation architecture, and control the code logic within the Code scope is the purpose of system analysis.

While conducting system analysis, data storage is also being designed. The data storage design process can also help us identify the difficulty of the project and sort out the system implementation methods.

This is really an "elephant" type software project. If there is anything that is not in place and cannot be understood accurately, I hope readers can point it out in time. Thank you.

From Wang Anqi (http://www.cnblogs.com/wgp13x)