![]() example, the Software Engineering Laboratory (SEL) on a. If we consider design and analysis, build, and test as three major phases, the manpower ramp-up in projects typically resembles the function shown in Figure 4.1 58. staffing levels for each activity, or it may be dynamic, implying staffing level is part of the. Often, the staffing level is not changed continuously in a project and approximations of the Rayleigh curve are used: assigning a few people at the start, having the peak team during the coding phase, and then leaving a few people for integration and system testing. The human resources requirement peaks during coding and unit testing, and during system testing and integration, again fewer people are required. This occurs because only a few people are needed and can be used in the initial phases of requirements analysis and design. That is, in the beginning and the end, few people are needed on the project the peak team size (PTS) is needed somewhere near the middle of the project and again fewer people are needed after that. The number of people that can be gainfully utilized in a software project tends to follow the Rayleigh curve 71, 72. In order to appreciate the staffing pattern of software projects, Norden’s and Putnam’s results must be understood. ![]() To determine the milestones, we must first understand the manpower ramp-up that usually takes place in a project.
0 Comments
Leave a Reply. |