Today, software development is increasingly complex, and software functions are getting richer. Almost all mature business software is crystallized by hard-earned sweats in a development team. "Rome is not built!" When we shocked the shocking masterpieces of Microsoft Windows, he also said that Microsoft's software engineering is improved. Indeed, a number of joint efforts of hundreds of employees have been gather in several years, and the success or failure of software project management is a key link for controlling development costs. This is less than the important steps running through ---- Software documentation. Software documents can be divided into two categories: development documents and product documents. The development documentation includes: "Feature Requirements", "Bidding Scheme", "Demand Analysis", "Technical Analysis", "System Analysis", "Database Document", "Function Function Document", "Interface Document", "Compile Manual", "QA document", "project summary", etc. Product documentation includes: "Product Introduction", "Product Demonstration", "Question", "Features", "Technology White Paper", "Evaluation Report", "Installation Manual", "Manual", "Maintenance Manual", " User Report, "Sales Training", etc. 1. Develop documentation 1. "Feature Requirements" - from customer requirements and market surveys, the earliest part of software development. Customers present a fuzzy functional concept, or requires solving an actual problem, or refer to a function of the same software. Customers with software experience will also provide more detailed technical specifications, write their requirements all lists in the document, if necessary, the chart is said. This document is the basis for demand analysis. 2. "Bidding Plan" - According to the user's functional requirements, after communication and confirmation with the bidding party, the technicians have written "bidding programs", and the program generally includes the following important chapters: preface - project background, company background And business, technician structure, company success case introduction, etc. Demand Analysis - Project Requirements, Software Structure, Function List, Function Description, Precautions, etc. Technical solutions - overall requirements and guiding ideology, technical solutions, software development platforms, network structures, etc. Project Management - Description Company's software development process, engineering implementation service, organization and personnel division, development schedule control, software quality assurance, project acceptance and personnel training, software data documentation, etc. Technical Support - Company's technical support and service introduction, service tenet and target, service level and response time, technical service area, technical service period, authorized user contact, etc. System quote - soft, hardware platform quotation list, software development fees, system maintenance costs, etc. Project progress - the progress plan of the entire project, including signing contract, project launch, demand analysis, system analysis, program development, test maintenance, system integration, user acceptance, user training, etc. steps. 3. "Demand Analysis" - including product overview, main concepts, operational processes, function lists, precautions, system environments, etc. Based on "Features Requirements", the detailed function analysis (including the requirements of the customer and the implementation of the development experience), what is the product, what special concepts, including those feature classification, what features need to have What is the operation of this function, what is the details of the customer, what is the requirements of the customer, and the requirements of the system operation environment. The functional description here is consistent with the manual after the future. 4. "Technical Analysis" - including technical selection, technical comparison, developer, key technical problem solving, technical risk, technology upgrade direction, technical plan evaluation, competitor technical analysis, etc. Based on "Demand Analysis", a detailed technical analysis (product performance and implementation method) lists what technical solutions need to use, why, what technical issues should be solved, what difficulties encountered during the development period, How to upgrade after the technical solution, what evaluates for the technology of this project, etc. 5. System Analysis - includes functions, modules, functional flow charts, function interfaces, data dictionary, software development needs to be considered.
