当前位置：网站首页>Review of software process and management (6)

To configure Configuration is to specify the function or physical attribute of the final software product in the technical document .
Configuration item Various system components produced in the software life cycle that should be included in the scope of management . Including various management documents and technical documents , Source program and object code , And all kinds of data required for operation （ Configure resource objects for management ）
The baseline A baseline is one or more software configuration items that have been reviewed , Each baseline is the starting point and foundation for the next development .
Configuration Management Library Configuration management library is also called controlled Library , Used to store software configuration items and related configuration management information .

Software configuration management process

6.1.2 Baseline control

Plan baseline
Requirements baseline
Design baseline
Coding baseline
Test baseline

6.1.3 version control

1. Version access and synchronization control

2. Version of the branch

3. Merge of versions

6.1.4 Change control

6.2 Project estimation and resource management

6.2.1 Scale measurement

Method of project scale estimation

Common scale estimation methods ：

(1) Code line method

(2) Function point analysis method

(3) Object point method of object-oriented software

Other estimation methods ： Delphi (Delphi technique)、COCOMO Model 、 Characteristic point (feature point)、 Object point (object point)、3-D The function point (3-D function points)、Bang Measure (DeMarco's bang metric)、 The fuzzy logic (fuzzy logic)、 Standard component method (standard component) etc.

6.2.2 cost estimation

Composition of project cost

（1） Direct cost

Labor cost
Hardware device
Software cost

（2） Indirect costs

Project management costs
General management costs

Estimation method of project cost

（1） Empirical estimation method

（2） Proportionality

（3） Work breakdown structure table

From top to bottom
Bottom up

6.2.3 Resource management

Project Human Resource Management

1. Identify project roles

role	function
project manager	The overall plan of the project 、 Organization and control .
People in need	Be responsible for obtaining in the whole project 、 Explain and maintain product requirements and write documents .
The designer	Be responsible for evaluation in the whole project 、 choice 、 Explain and maintain product design and write documents .
Coder	Complete the task of coding according to the design and correct the errors in the code .
Testers	Responsible for designing and writing test cases , And complete the final test execution .
Quality assurance personnel	Be responsible for the acceptance of products 、 Plan the results of inspections and tests 、 Guide and report .
Environmental maintenance personnel	Responsible for the development and maintenance of the development and testing environment .
other	Another role , Such as document specification personnel 、 Hardware engineer, etc .

2. Team building

Project software and hardware resource management

1. Software resource management

operating system
compiler
Application software
Testing tools
……

2. Hardware resource management

The server
PC
……

6.3 Project risk assessment

Project risk management

6.3.1 Risk identification

Common risk identification methods

Checklist
Document review
Brainstorming
Delphi
interview
SWOT analysis
Chart analysis

6.3.2 Risk analysis and assessment

Quantitative risk analysis

Quantitative risk analysis usually requires a more detailed analysis of the facts , It is often more reliable than subjective risk analysis .

The main quantitative analysis methods are ： ratio / Scope analysis probability analysis Sensitivity analysis

6.4 Make a project plan

6.4.1WBS- Work breakdown structure

1 Project scope planning

1.1 Define the scope of the project
1.2 Obtain the funds needed for the project
1.3 Define preparatory resources
1.4 Access to core resources
1.5 Project scope planning completed

2 analysis / The software requirements

2.1 Behavioral needs analysis
2.2 Draft preliminary software specifications
2.3 Make a preliminary budget
2.4 The Working Group reviews the software specification together / The budget
2.5 Modify the software specification according to the feedback
2.6 Determine the delivery deadline
2.7 Get approval to carry out follow-up work ( Concept 、 Deadline and budget )
2.8 Get the resources you need
2.9 The analysis work is completed

3 Design