Chapter 1 Project Material Compilation Technology
Involved in the preparation of project-related materials can refer to the following methods:
1.1. Writing process
1.1.1. Requirements Discussion
Clarify the project materials "for whom to see, who to review, and what results are required", and confirm the core requirements with the demand side.
Material review: Find the material files that have been done for the project, which can be used as templates, and there are also baseline versions for reference. Study all the chapters that should be written, and make sure not to miss any items.
Gain time: Estimate the overall document output time, material output plan, and inform the demand side of the need for support points and predictable risks. If the time is too short, it may not be thorough enough, and more time should be sought.
1.1.2. Project research
Preparation purpose: Why do you make a plan? Because different preparation purposes, the depth of your preparation is different, so you need to determine the direction. If you are only applying for investment, the focus of attention is how to get those reviewers to pass your plan, you have to consider all aspects question. Some are really for the sake of project implementation, the deeper the depth of the feasibility study, the better, depending on the needs of Party A.
Requirement goals: the scope involved, what are the requirements, whether there are documents/documents/leadership speeches, documents issued by superiors, etc.
Current status and problems: the current status of the existing system construction, what systems have been built, what functions can be realized, and what problems exist
Business requirements: What are the business requirements of each police department/business department, and what functions need to be realized, etc.
Background introduction: interview target personnel, place, time, background of interviewees, interview atmosphere;
Summarize key results: interviewee's judgment and conclusion interviewer's conclusion/argument.
Clarify the next step and output the attached document records.
1.1.3. Core framework
Sorting dots and lines and merging them into noodles: sort out the information obtained from research, documents provided by Party A, and some policy documents found by oneself to form modules one by one.
Find a template: find a more comprehensive template that can cover most of the required content as a basis, and make adjustments and modifications
Method demonstration to achieve closed loop: make the whole framework clear in terms of logic, scientific method, and form a closed loop
Reporting framework: form the first draft report, inform the overall methodology, as well as the content and compilation suggestions of each chapter, and points for attention.
1.1.4. Document writing
Sort out ideas and design directory structure
After choosing a template, don’t rush to code words, first organize your thinking, and include the necessary chapters first (see: what should be included), and then add corresponding chapters according to Party A’s needs and project conditions chapter. The overall framework requires clear logic, clear views, and completeness (MECE: no omissions, no overlaps, no more, no less, just right). Tool: XMind
Report in time to avoid reinvention
After designing the overall framework, report and communicate with the project supervisor in a timely manner to avoid subsequent overthrow and start over. The general public security client may not be familiar with the routines of feasibility study, and his focus is still on the rationality of the plan.
Divide the code words, do a good job of cohesion
Writing skills: You can use the pyramid principle (features: start from the conclusion, central idea, logical argument, logical induction, thorough and complete). When the project leader summarizes the materials, he should pay attention to the cohesive relationship and the rationality of the terms used, so as to avoid jumping writing (great change in style).
Scientific proof, the whole is well-founded
For example: the number of front-end construction → the size of storage → the configuration of back-end processing capabilities → investment estimates, etc., all of which must have a basis, and absolutely no conclusions can be made. If possible, it is best to have a comparison plan, and recommend a plan based on the comparison conclusion.
1.2. Writing Methodology
1.2.1. Case Benchmarking Analysis
A large number of typical case studies, advanced regions/provinces or national benchmarking analysis methods, etc. are used to provide reference for project positioning, organizational leadership mode, operation mode selection, and evaluation index system design.
1.2.2. Quantitative and qualitative evaluation method
In the review of informationization progress and pilot construction progress, the qualitative evaluation method is used to classify the stages of each city; in the basic condition evaluation, the elements of the basic condition are fully considered, and the basic condition evaluation index system is established to provide basic input for project decision-making; Fully consider the decision-making factors in the layout decision-making model, and guide the layout decision-making of front-end point construction and back-end application of the project through the two-stage quantitative evaluation model.
1.2.3. Document analysis method
Collect a large number of relevant planning materials, leadership speech materials, work meeting materials, training materials, etc. from the province and various cities on social economy, informatization, and urban construction, so as to indirectly understand the ideas and key points of project construction, and increase the pertinence and implementation of special planning.
1.2.4. Research and interview method
Recover N copies of the public/police safety city construction needs through questionnaires and emails, and provide basic input data for the evaluation of the layout decision-making model; carry out project pilots and participate in enterprise interviews, understand the progress and experience of project pilots, and provide scientific results for the output of special projects Lay a good foundation.
1.2.5. Backward method
Use the known conclusions to deduce the model, compile the train of thought, self-verify the feasibility of the model and train of thought, and finally use the train of thought and model to draw the conclusion you want
1.2.6. Technology introduction
Many documents actually have a requirement that there should be no manufacturer preference, and a certain model or unique characteristics of the manufacturer must not appear in the text. So how to make the file good for us is a technical job. The solution is as follows:
In the chapter of technical requirements, some restrictions can be made through parameter requirements, at least some manufacturers can't meet them.
In the new technology application chapter, we focus on describing our expertise, which is both high and low.
The targeted technical comparison in the technical analysis chapter is both pertinent and clear.
In the chapter on business requirements, compile some business requirements (business requirements are not product functions), which we can meet but other companies cannot meet.
When screening business requirements, try to keep what we are good at, and cut down those we are not good at, which not only meets the needs of users, but also highlights the key points.