(2) GB/T 36463. 1-2018 Information Technology Service Consulting and Design Part1:General requirements. This part of GB/T 34960 puts forward the capability model of information technology consulting and design services, and stipulates the conditions and capabilities that organizations providing information technology consulting and design services should have in terms of personnel, processes, technology and resources. This part is applicable to: a) organizations planning to provide information technology consulting and design services establish a service capability system; B) Information technology consulting and design service providers improve and enhance their service capabilities; C) The demanders of information technology consulting and design services select and evaluate suppliers; D) Third-party evaluation of information technology consulting and design service providers.
(3)GB/T 3796 1-20 19 Basic requirements for information technology services. This standard specifies the basic requirements of information technology consulting, design and development, information system integration and implementation, operation and maintenance, data processing and storage, operation and other services. This standard is applicable to information technology service providers who provide services in related fields to establish specific specifications for the services they can provide, and provide reference for both the supply and demand sides to draw up service contracts for specific services or service combinations.
(4)GB 50 174-20 17 Code for Design of Data Center (instead of Code for Design of Computer Rooms of Electronic Information Systems). This specification is applicable to the design of electronic information system computer rooms newly built, rebuilt and expanded in buildings. The data center is divided into three levels: A, B and C.
Class a: "fault tolerance". The interruption of electronic information system will cause great economic losses, or will cause serious disorder in public places.
Class b: "redundancy". The interruption of electronic information system will cause great economic losses, or will cause disorder in public places.
Grade c: if it does not belong to grades a and b, it is grade C.
The standby computer room established in different places should be designed at the same level as the main computer room. Different parts of the same computer room can be designed according to different standards according to actual conditions.
The distance between the channel and the equipment in the main engine room shall meet the following requirements:
① The clear width of the passage used for handling equipment should not be less than1.5m; ;
② The distance between the fronts of cabinets (or racks) arranged face to face should not be less than1.2m; ;
③ The distance between the backs of cabinets (or racks) arranged back to back should not be less than 0.8m；;
(4) When the side and back of the cabinet (or rack) need to be repaired and tested, the distance between the cabinet (rack) and the cabinet (rack) and the wall should not be less than1.0m; ;
⑤ Rows of cabinets (racks), when the length exceeds 6m, channels should be set at both ends; When the distance between two channels exceeds 15m, a channel should be added between the two channels. The width of the outlet channel should not be less than 1m, and it can be 0.8m locally.
The fire resistance rating of the computer room of electronic information system should not be lower than Grade II.
When the computer room of Class A or Class B electronic information system is located in other buildings, a partition wall with a fire resistance of not less than 2h should be set between the main computer room and other parts, and the doors on the partition wall should adopt Class A fire doors.
1. 1.2 information technology software
(1)GB/T 8566-2007 information technology software life cycle process. The standard divides the activities that may be performed in the software life cycle into three categories, namely: basic processes (five, namely acquisition, supply, development, operation and maintenance), support processes (nine) and organizational processes (seven). Each life cycle process is divided into a set of activities, and each activity is further divided into tasks.
(2)GBT 16680- 1996 Software Document Management Guide. This standard provides a software document management guide for managers responsible for software or software-based product development. The purpose of this standard is to help managers produce effective documents in their institutions.
With regard to document review, requirements review and design review are essential, regardless of the size of the project or the formality of project management. The requirements must be clearly stated, and both users and developers must understand the requirements. In order to translate requirements into programs and program components, the details of the design must be agreed and documented.
① Requirements review: further confirm that developers and designers have understood the requirements of users, and users have understood some restrictions and constraints from developers. Requirements review (which may take more than one time) produces an approved requirements specification. Based on the common understanding of what the system should do, detailed design can be started. User representatives must actively participate in development and requirements review, and participate in the approval of requirements documents.
② Design review: The generated final document specifies how to design, develop and test the system and procedures to meet the agreed requirements. It includes two main design reviews: the summary design review and the detailed design review. In the process of summary design review, the basic design methods and test plans of each system component are mainly reviewed in detail. System specifications should be revised according to the results of the summary design review. The detailed design review mainly reviews the test plan of computer programs and program units.
(3)GB/T 8567-2006 computer software documentation specification. This standard is based on GB/T 8566-2001Information Technology Software Life Cycle Process, which mainly specifies the basic requirements, contents and formats of the main documents that should be compiled in the process of software development and management. In principle, this standard is applicable to the development process and management process of all types of software products.
Computer software document
Among them, the SRS content of software requirements specification includes: scope, cited documents, requirements, compliance regulations, traceability of requirements, unresolved issues, notes and appendices. In this standard, system requirements are divided into three categories: functional requirements and business requirements (including: interface, resources, performance, reliability, security, confidentiality, etc.). ) and data requirements.
(4)GB/T 9385-2008 computer software requirements specification. This standard gives the writing requirements of software requirements specification (SRS), and describes a good.