How to write technical standards for software projects
First, the project overview is a comprehensive introduction to the project, which is a summary to explain the background, objectives and significance of the project. Third, the overall technical scheme is one of the core parts of the tender, including technical route, overall architecture design, key technologies and difficulties, and key technologies and corresponding solutions are the core of this part. Fourthly, the design of the system platform. Fifthly, the security of the security system design system has been upgraded from "Dark War" to "ISO2700 1". A complete scheme needs to provide detailed solutions from physical layer security, access control, intrusion detection, security authentication, virus protection, security management system and so on. Sixth, the project implementation plan, I think this is the second core part of the tender. Good technology needs good implementation. CMMI is not empty talk, but needs to be really used from enterprises to projects. Project implementation, from the composition of the project team, to the implementation plan, to the responsibilities of personnel, to the project acceptance, needs to be clearly defined in the tender. Seventh, as a symbol of standardization of software vendors, the technical service plan should be included in the tender from the aspects of software training, technical support and after-sales service. Of course, the bidding mode will not remain unchanged, and we need to flexibly adjust and increase it according to specific project requirements, including, for example, performance guarantees, standards and specifications.