What is staffing level estimation explain?

It is important to recognize that determining the appropriate number of aviation safety inspectors (ASIs), system-wide or locally, at any given time is by no means a simple matter, since it is dependent on how work is structured and what defines acceptable individual and system performance, as well as the characteristics of the current and projected workforce.

In Chapter 4 we discuss these and other considerations that are also important for effective deployment of human resources. In this chapter, we concentrate on models for manpower management, that is, for deciding how many workers, of what general types, are needed to staff the organization without regard for specific job characteristics, worker qualifications, or performance standards.

While manpower planning and management, and the models used in these activities, are important parts of the overall staffing picture, many other factors enter into human resource management, as noted earlier. How effectively an organization is able to meet those needs, once they are defined, depends on both its staffing processes and the characteristics of the available human resource pool. Staffing needs are determined mainly by how the organization has defined its goals and designed the jobs that make up its total workload. As explained in Chapter 1, these are tools that enable the organization to determine the right number of people with the right skill sets in the right positions to accomplish the responsibilities of the job in a satisfactory manner. At the Federal Aviation Administration (FAA), staffing models and staffing standards are terms used to denote tools for the management of manpower only. The term “staffing” is often used to refer to a range of processes, such as recruitment, selection, placement, and training, through which an organization applies human resources to the work needed for it to achieve its goals (Schneider, 1976).

Staffing level Estimation: NORDEN WORK Project manager has to figure out Staff Estimation after the effort required to develop a software has been determined. Norden investigated the staffing pattern of R & D project. Norden Estimation: He studied the Staffing patterns of R & D projects and proposed that Staffing level patterns can be approximated by the 'Rayleigh Distribution Curve' which specifies that the relationship between applied effort and delivery time for software project. It is also called Putnam- NORDEN-Rayleigh Curve or PNR curve. He represented the Rayleigh Curve by this equation E=K/t2d.t.e-t2/2td2 Here E is the effort required at time t.(engineers and staffs) K= Area under curve.

1. What Is Project Estimation In Software Engineering

Td= time at with the curve attains its maximum values. Staffing Level Estimation: Putnam's Work Putnam analyzed that characteristic of software development and staffing has some characteristics of R and D projects studied by Norden and Rayleigh Norden Curve can be used to Relate the Number of delivered lines of code to the effort and the time required to develop the project. L=CkK1/3td4/3 k= total effort expended in PM in product development.

L= the product size in KLOC td= time required to develop the software Ck = state of Technology constraints like Ck=2(poor development environment) Ck=8 (good software development environment) Ck=11 (Excellent environment).

Software Cost Components 1. Effort costs (dominant factor in most projects) salaries Social and insurance & benefits 2. Tools costs: Hardware and software for development Depreciation on relatively small # of years 300 K US$ 3.

Travel and Training costs (for particular client) 4. Overheads(OH): Costs must take overheads into account costs of building, air-conditioning, heating, lighting costs of networking and communications (tel, fax, ) costs of shared facilities (e. G library, staff restaurant, etc.

) depreciation costs of assets Activity Based Costing (ABC) Software Engineering SW Cost Estimation Slide 8. Lines Of Code (LOC) l l Program length (LOC) can be used to predict program characteristics e. Person-month effort and ease of maintenance What's a line of code? The measure was first proposed when programs were typed on cards with one line per card How does this correspond to statements as in Java which can span several lines or where there can be several statements on one line? L l What programs should be counted as part of the system? Assumes linear relationship between system size and volume of documentation Software Engineering SW Cost Estimation Slide 14. Object Points (for 4 GLs) l l l Object points are an alternative function-related measure to function points when 4 Gls or similar languages are used for development Object points are NOT the same as object classes The number of object points in a program is a weighted estimate of The number of separate screens that are displayed The number of reports that are produced by the system The number of 3 GL modules that must be developed to supplement the 4 GL code C: SoftwareEngCocomoSoftware Measurement Page, COCOMO II, object points.

What Is Project Estimation In Software Engineering

Htm Software Engineering SW Cost Estimation Slide 36. Estimation techniques l There is no simple way to make an accurate estimate of the effort required to develop a software system: Initial estimates may be based on inadequate information in a user requirements definition The software may run on unfamiliar computers or use new technology The people in the project may be unknown l Project cost estimates may be self-fulfilling The estimate defines the budget and the product is adjusted to meet the budget Software Engineering SW Cost Estimation Slide 45.

Algorithmic Cost Modelling l l Most of the work in the cost estimation field has focused on algorithmic cost modelling. Costs are analysed using mathematical formulas linking costs or inputs with METRICS to produce an estimated output. The formula is based on the analysis of historical data. The accuracy of the model can be improved by calibrating the model to your specific development environment, (which basically involves adjusting the weighting parameters of the metrics).

Software Engineering SW Cost Estimation Slide 58. COCOMO II l COCOMO II is a 3 -level model that allows increasingly detailed estimates to be prepared as development progresses Early prototyping level Estimates based on object points and a simple formula is used for effort estimation Early design level Estimates based on function points that are then translated to LOC Includes 7 cost drivers Post-architecture level Estimates based on lines of source code or function point Includes 17 cost drivers l Five scale factors replace COCOMO 81 ratings (organic, semi -detached, and embedded) Software Engineering SW Cost Estimation Slide 71. Early prototyping level - COCOMO II l Suitable for projects built using modern GUI-builder tools Based on Object Points l l Supports prototyping projects and projects where there is extensive reuse Based on standard estimates of developer productivity in object points/month Takes CASE tool use into account Formula is PM = ( NOP ´ (1 -%reuse/100 ) ) / PROD PM is the effort in person-months, NOP is the number of object points and PROD is the productivity Software Engineering SW Cost Estimation Slide 72.

Early Design Level: 7 cost drivers - COCOMO II l l Estimates can be made after the requirements have been agreed Based on standard formula for algorithmic models Effort for Manually developed code PM = A ´ Size. B ´ M + PMm Effort for Manual adaptation of Automatically generated code M = PERS ´ RCPX ´ RUSE ´ PDIF ´ PREX ´ FCIL ´ SCED A = 2. 5 in initial calibration, Size: manually developed code in KLOC Exponent B.

varies from 1. 24 depending on novelty of the project, development flexibility, risk management approaches and the process maturity. B is calculated using a Scale Factor based on 5 exponent drivers PMm: represents manual adaptation for automatically generated code Software Engineering SW Cost Estimation Slide 73. The Exponent B Scale Factor(SF) - COCOMO II l l Exponent B for effort calculation B = 1. 01 x sum SF (i), i=1, 5 SF = Scale Factor l Each SF is rated on 6 -point scale (ranging from 0 to 5): very low (5), low ( 4), nominal (3), high (2), very high (1), extra high (0) l 5 Scale Factor (exponent drivers) Precedenteness Development flexibility Architecture/risk resolution Team cohesion Process maturity Ex: 20 KLOC ^ 1. 26 / 20 KLOC ^ 1. 11 Software Engineering SW Cost Estimation Slide 76.

Post-architecture stage - COCOMO II l l Uses same formula as early design estimates Estimate of size is adjusted to take into account Requirements volatility: Rework required to support change Extent of possible reuse: Reuse is non-linear and has associated costs so this is not a simple reduction in LOC ESLOC = ASLOC ´ (AA + SU +0. 3 IM)/100 ESLOC is equivalent number of lines of new code. ASLOC is the number of lines of reusable code which must be modified, DM is the percentage of design modified, CM is the percentage of the code that is modified, IM is the percentage of the original integration effort required for integrating the reused software.

SU is a factor based on the cost of software understanding, AA is a factor which reflects the initial assessment costs of deciding if software may be reused. Software Engineering SW Cost Estimation Slide 79. COCOMO II Post Architecture Effort Multipliers (17 multipliers) l Product attributes (5 multipliers) concerned with required characteristics of the software product being developed l Computer attributes (3 multipliers) constraints imposed on the software by the hardware platform l Personnel attributes (6 multipliers) multipliers that take the experience and capabilities of the people working on the project into account. L Project attributes (3 multipliers) concerned with the particular characteristics of the software development project Software Engineering SW Cost Estimation Slide 80.

Project duration and staffing - COCOMO II l l As well as effort estimation, managers must estimate the calendar time required to complete a project and when staff will be required Calendar time can be estimated using a COCOMO II formula TDEV = 3 ´ (PM)(0. 01)) PM is the effort computation and B is the exponent computed as discussed above (B is 1 for the early prototyping model). This computation predicts the nominal schedule for the project l The time required is independent of the number of people working on the project Software Engineering SW Cost Estimation Slide 88.

Suarez presents facts on all that we all know we could and should do better. I know that really does not give a sense of the knowledge that was given.

What I found extremely helpful in this book is the chapters are short.

The National Programme on Technology Enhanced Learning (NPTEL) is a project funded by the Ministry of Human Resource Development (MHRD). It provides e-learning through online Web and Video courses in Engineering, Sciences, Technology, Management and Humanities. Staffing level estimation It is necessary to determine the staffing requirement for the project.

Putnam first studied the problem of what should be a proper staffing pattern for software projects. He extended the work of Norden In order to appreciate the staffing pattern of software projects, Norden’s and Putnam’s results must be understood. Norden’s Work Norden studied the staffing patterns of several R & D projects. He found that the staffing pattern can be approximated by the Rayleigh distribution curve Norden represented the Rayleigh curve by the following equation: E = K/t²d. t. e-t² / 2 t²d Staffing level estimation For more details here is the attachment.

How the staffing level estimation is done explain?

What is the staffing level?

What is staffing in software engineering?

WHO has investigated the staffing pattern of R&D project?