GB/T 19668.5-2018Information technology service—Surveillance—Part 5: Software project surveillance specification (English PDF)

3.1 Software engineering

Apply computer science theory and technology and engineering management principles and methods to achieve software products that meet user requirements according to budget and schedule The definition, development, release, and maintenance of a product or the science of conducting research. [GB/T 11457-2006, definition 2.1494]

3.2 Identify

The supervisory organization understands, approves and determines the information provided by the owner or the contractor.

3.3 Ready-to-use software product; RUSP

A software product that can be used by any user without the need to implement development activities.

3.4 Conformity

The extent to which the requirements are met.

3.5 Traceability

The ability to trace the history, application, or location of an entity.

3.6 Consistency

The content, methods or procedures used should be the same and should not be changed at will.

3.7 Suitability

Ability to adapt to external and internal environmental changes.

3.8 Testability

To determine if a requirement is met, the extent to which an objective and feasible test can be designed.

3.9 Effectiveness

The degree to which the planned activities are completed and the results are planned.

3.10 Security

Protection of information and data so that unauthorized persons or systems cannot read or modify them and do not deny authorized personnel or systems Access to them.

4.1 Overview

This part follows the general principles and requirements of GB/T 19668.1-2014, and expounds the software engineering supervision work from the perspective of technical management. Principles, methods and requirements.

The supervision of software system operation and maintenance is shown in this section.

The supervision of information security in software engineering projects can be found in GB/T 19668.4.

4.2 Planning and Design Services

In the planning and design section, the supervision organization can provide consulting services for the owner, including business grooming, demand analysis and program design requirements. Work in other areas.

4.3 Supervision of deployment implementation

In the deployment implementation part, according to GB/T 19668.1-2014 information system engineering supervision and related service specification technical reference model For the division of supervision stage, combined with the general requirements of software development, the software engineering supervision is divided into 13 activities, distributed in 4 supervision stages. In, as shown in Table 1.

In the bidding, design, implementation and acceptance phase of software engineering projects, the documentation process and configuration management of the software life cycle support process For the supervision of the process and quality assurance process, see Appendix B, including the supervision of the documentation process (B.1), and the supervision of the configuration management process. (See B.2), supervision of the quality assurance process (see B.3).

For the supervision activities in the bidding, design, implementation and acceptance stages of software engineering projects, the supervisory control measures that can be taken are listed in Appendix C, Packages. Including plan review (C.1), process tracking (C.2), validation (C.3), joint review (C.4), review (C.5), problem solving (C.6), measurement and analysis (C.7).

5.1 Target

The supervision organization can provide consulting services for the software engineering project for the owner unit, achieving the following objectives.

a) Assist the owner to determine the construction plan of the software system that supports the business objectives;

b) Assist the owner to determine the investment budget required for the construction of the software system;

c) Assist the owner to clarify the personnel organization, technology application, process management, resource utilization and other programs for software system construction.

5.2 Content

The main consultation contents of planning and design are as follows.

a) The supervision organization may assist the owner to sort out the business objectives and formulate the software system construction goals;

b) The supervision organization may assist the owner to carry out the software system requirements analysis work;

c) The supervision organization may assist the owner to conduct feasibility analysis and necessity analysis on the software system construction plan, and determine the software system. Technical architecture and construction plan;

d) The supervision organization can assist the owner to determine the project cost of the software system.

5.3 Key points

5.3.1 Business combing

The supervision organization assists the owner to carry out business review and proposes advice, including.

a) Analyze the status quo and development trends of business and informationization;

b) combing the support of informationization to the business;

c) Propose the construction goals of the software system.

5.3.2 Demand Analysis

The supervision organization assists the owner to carry out the demand analysis work and proposes consultations, including.

a) current status of the software system;

b) analysis of business objectives;

c) software system function and performance analysis;

d) Software system construction scale and project schedule requirements.

5.3.3 Scheme design requirements

The supervision organization assists the owner to determine the software system design plan, including.

a) laws, regulations, technical standards and management standards to be followed in the construction of software engineering projects;

b) analysis of necessity;

c) The overall construction plan and the phased construction plan, and the relationship between the existing system and the future system and the interface requirements, the necessary plan should be carried out Comparison

d) tendering plan for software engineering projects;

e) software engineering project investment and composition;

f) risk analysis;

g) Benefit analysis.

6.1 Bidding stage

6.1.1 Supervision requirements

The supervision work in the bidding stage must meet the following requirements.

a) Understand the user's business objectives and business models, and assist the owner to determine the requirements for software engineering project bidding;

b) procure the bidding documents to meet the user's needs and the objectives and scope of the software engineering project construction;

c) assist the owner to select the appropriate contractor;

d) Assist the owner to sign the contract for construction, so that the contract for construction is reasonable and effective in terms of technology and economy, and meet the laws, regulations and relevant standards. Quasi-requirements.

6.1.2 Supervision service content and points

6.1.2.1 Supervision of tender preparation

Before the bidding of the software engineering project, the supervision organization shall collect relevant information to understand the business objectives and software systems related to the construction of the software engineering project.

Build the target, current and expected business model, information infrastructure and development planning, software system construction needs and other information to assist the owner Prepare the bidding and assist the owner to prepare the bidding documents. The contents and main points of the supervision service are as follows.

a) The supervision organization should obtain the necessary information, understand and communicate with the owner about the software engineering project, and use it as supervision. One of the basis of work. These materials include.

1) Software engineering project construction plan;

2) Business status and business processes related to software engineering projects;

3) Functional and performance indicators of the software system;

4) Resources necessary to achieve the goals of the software system;

5) If applicable, should include information resource planning;

6) If applicable, should include strategies for business process reengineering;

7) If applicable, should include a business continuity improvement plan;

8) If applicable, should include an operational indicator evaluation system;

9) If applicable, it should include the information technology human resource planning of the owner.

b) The supervision organization may assist the owner to initially define the scope of the software system construction, system requirements and constraints, and shall determine the following content.

1) business, organization and user needs;

2) system size, investment and schedule requirements;

3) Security and confidentiality requirements;

4) Standards and procedures to be followed;

5) requirements and acceptance criteria related to testing;

6) Intellectual property requirements;

7) Data ownership requirements.

c) The supervision organization may participate in the preparation of the invitation to bid, and clarify the following.

1) Construction content;

2) the requirements of applicable laws, regulations and standards;

3) Functional and performance requirements;

4) milestones in contract execution;

5) documentation and review and delivery requirements;

6) Acceptance methods and acceptance criteria;

7) Security and confidentiality requirements;

8) Intellectual property requirements.

d) When obtaining a ready-to-use software product, the supervisory organization should assist the owner to review the requirements for the ready-to-use software product. include.

1) Meet system construction goals and system requirements;

2) requirements for the documentation;

3) requirements for intellectual property;

4) requirements for safety;

5) requirements for service and support for this software product;

6) Requirements for the supplier to provide the capabilities of this software product.

6.1.2.2 Supervision of bidding

The supervision organization shall assist the owner to carry out the bidding work and select the contractor. The service content and key points are as follows.

a) The supervision organization should assist the owner to establish the procedures for selecting the contractor, including the evaluation criteria of the tender and the degree of compliance with the requirements.

b) If applicable, the supervision organization should participate in the bidding and answering meeting to assist the owner to carry out the bidding and answering work.

c) If applicable, the supervisory agency should assist the owner to review the engineering capabilities of the bidder. include.

1) the adequacy and effectiveness of the qualification documents;

2) Compliance between the technical capabilities of the bidder and the engineering techniques and specific requirements required for the project;

3) The qualification of the project personnel of the bidding unit is in conformity with the engineering technology and specific requirements required for the project.

d) If the project involves subcontracting, the supervision organization should assist the owner to review the subcontractor.

e) If applicable, the supervision agency shall assist in the evaluation of the bid and assist the owner in accordance with the bidding documents and the bidding documents of the bidder and other necessary The factors to choose the right contractor.

6.1.2.3 Supervision of contract signing

The supervision organization shall supervise the construction contract signed by the owner unit and the contractor. The service content and key points are as follows.

a) It is required to clarify in the contract of construction that the contractor accepts the supervision of the supervisory institution.

b) If the software engineering project involves subcontracting, the supervision organization shall assist the owner unit to request the contractor to be responsible for the subcontracting unit. management.

c) The supervision organization should assist the owner to review the contract, and supervise the relevant contents of the contract according to the following criteria. opinion.

1) Consistent with the bidding requirements and bid response, in line with the requirements of laws, regulations and standards;

2) Defining the scope of construction and construction content;

3) Defining quality requirements, including functional and performance requirements, documentation requirements;

4) Clarify the overall schedule and phase schedule requirements;

5) stipulate the necessary procedures for handling changes;

6) If applicable, stipulate the procedures, scope and payment methods for the interface and cooperation of the relevant parties;

7) clarify the quality responsibility;

8) Defining test standards and acceptance requirements;

9) Clear security and confidentiality requirements;

10) Clarify intellectual property requirements;

11) Divide and define the milestones of the project and serve as the basis for the phased payment of the project;

12) clarify the role of the supervision agency in the payment of the project payment;

13) Clarify the way in which contract disputes are handled.

d) The supervision organization should recommend that the owner unit organizes the departments related to contract execution or management to participate in the contract review work.

e) The supervision organization should assist the owner to organize the first meeting of the owner, the contractor and the supervision organization to participate in the meeting. Project communication and coordination mechanism, when applicable, other engineering stakeholders should be invited to attend the meeting.

f) The supervision organization shall organize the parties to the project to successfully promote the project, focusing on quality control, schedule control, investment control, and contract management. Establish a complete project management system and guarantee system in terms of management, document management, communication and coordination.

g) The supervision organization shall coordinate the owner unit and the contractor to establish a change communication mechanism.

6.1.3 Supervision document

6.1.3.1 Overview

The output documents of the supervision organization at this stage mainly include supervision planning and supervision opinions (see GB/T 19668.1-2014 Table B.10), meeting Minutes (see GB/T 19668.1-2014 Table B.6), project memorandum (see GB/T 19668.1-2014 Form B.5), and supervision work links Single (see GB/T 19668.1-2014 Table B.9) and so on.

6.1.3.2 Supervision planning

The supervision organization shall determine the supervision objectives, prepare the supervision plan, and supervise and related services on the basis of understanding the business objectives and system requirements.

Carry out overall planning. In addition to meeting the relevant requirements of GB/T 19668.1-2014, the supervision plan should also follow the following guidelines.

a) compliance with business objectives;

b) traceability and consistency with the supervision contract;

c) the suitability of the supervisory work methods and measures;

d) the suitability of the supervision organization and the supervisors;

e) Suitability of the supervision facility and work system.

6.1.3.3 Supervision opinions

If applicable, the supervision organization shall review the bidding documents and construction contracts to form supervisory opinions (see Table B.10 of GB/T 19668.1-2014).

6.1.3.4 Minutes of the meeting

The supervisory authority shall record the following meetings (if any) and form a meeting minutes (see GB/T 19668.1-2014, Table B.6).

a) review meeting of the tendering plan;

b) bidding and answering questions;

c) construction contract review meeting;

d) the first meeting;

e) Other meetings during the tendering phase.

6.2 Design phase

6.2.1 Supervision requirements

The supervision work in the design phase must meet the following requirements.

a) Review the software project implementation plan submitted by the contractor to make the project plan reasonable, feasible, and in line with the contract Claim;

b) Participate in the research work, urge the contractor to form research records, supervise the system needs analysis process of the contractor, and promote system requirements Correctness, completeness, testability and consistency;

c) Organizing and participating in the review of the documents formed by the contractor at the design stage, causing the design phase documents to meet the requirements of the contract Seek to meet the system requirements of software engineering projects and meet the requirements of relevant regulations and standards;

d) Respond promptly to changes and do the following.

1) The supervision organization should organize the owner unit and the contractor to evaluate the change risk, including the project plan, cost, benefit, The impact of quality and schedule;

2) The application, evaluation, planning, implementation, verification, etc. related to the change shall be recorded (see GB/T 19668.1-2014, Table C.3) And keep it safe;

3) In case of a contract change, the supervision organization shall assist the owner to handle it in accordance with the requirements of the contract and regulations.

6.2.2 Supervision service content and points

6.2.2.1 Planning supervision

The supervision organization shall review the engineering plan documents submitted by the contractor and sign the supervision review opinions, and execute them with the consent of the owner unit. Supervision The service content and key points are as follows.

a) The supervision organization shall require the contractor to submit the project plan document and request it to include the following contents.

1) Scope, relationship with other programs;

2) standards to be followed;

3) The organizational structure of the project (including external organization), personnel responsibilities and capacity requirements;

4) Engineering environment, including production environment, test environment, library, equipment, facilities, standards, procedures and tools;

5) Task decomposition arrangements, including personnel, resources and related task schedules;

6) Progress tracking and reporting methods;

7) Management of the quality characteristics of the software product or service, and an independent quality assurance plan if necessary;

8) Software configuration management, including activities, techniques and methods, tools, control of the supplier, collection, maintenance and preservation of records;

9) Management of the security, confidentiality and other key requirements of software products or services, and the development of independent security and confidentiality plans as necessary;

10) Management of subcontracting units, if applicable; […]