DOC PREVIEW
USC CSCI 599 - MyFirstCOCOMO_Tutorial

This preview shows page 1-2-3-4 out of 12 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

My first COCOMOTutorial:First, name the project. In the blue box next to Project Name, which now says <sample>, clickon it and type First COCOMO. Now, we have to add a module. Go to the top menu and click on Edit,add the module. Then, change the name of the module created under module name from <sample> tomy first module. To the right of this is a yellow box under module size; right now it is set as S:0. Ayellow box means that data can be imputed.Click on this box and it will open a window entitled SLOC Input Dialog – my first module.Here we are given three ways to enter the module size, SLOC, Function Points, and Adaptation,whichever we choose depends on what parameters we are given. However, for our project we are only toldthat it will be a project with 10,000 lines of code. Let’s assume that we don’t know for sure whichparameter our data falls under. This will give us a chance to use the Help function in the top menu. Clickon that, and then COCOMO II Manual.The COCOMO Manual will be opened with whatever is set as the default browser. Since thewindow is entitled SLOC Input Dialog, we should search for “SLOC” in the document. In Netscape, thisis done by first clicking in the frame we are looking in, in this case, the left one, and going to Edit, Find inFrame. Do this now; you will see that “SLOC” was not found in the User’s Manual Table of Contents.We should now look in the index, click on the first link on the left called Index. Do another search. Nowwe have more success, and quickly find out that SLOC stands for “source lines of code.” Go back toSLOC Input Dialog – my first module, and select SLOC as Sizing Method. Now, put 10000 in the fieldnext to SLOC and click OK. Note, we could also have had success by looking under Model ManualTable of Contents, Using COCOMO II, Determining Size—a slightly more intuitive approach.-Next, we have to adjust our model for scale factors. Click the gray tab near the top called ScaleFactor. This will open the menu Scale Factors, listing the factors and their ratings, which range from“very low” to “extra high.” Scale factors are a significant source of exponential variation on a project’seffort or productivity variation. The default, nominal, is put here as NOM; clicking on this button willcause the rating to toggle. However, for our project, our boss didn’t tell us to do otherwise, so we willleave the scale factors as NOM. Click OK.Now, we need to input the EAF, or Effort Adjustment Factors. There is another yellow box belowEAF, which if we click on, will open a window for us to change the ratings for the effort adjustmentfactors. However, again, our boss has not told us to change any of these settings, so we will leave them asnominal. If we needed to, though, we could always click on the box that says NOM under the adjustmentfactor to toggle it to the setting we need. Click OK.Well, we now look at the bottom table for the results of our module. Look at the vertical axisEstimated to Most Likely and across at the value under Effort. This says for a module with 10,000 linesof code that the estimated effort will most likely be 37.0. 37 is the number of Person Months needed tocomplete the project. Note, the project is not just the writing of the program, but all the product design(analysis), all the detailed design, all the unit test and integration and test, and all the documentation for theprogram as well.Now, the nice thing about COCOMO II is that we can see how the effort is laid out overthese different phases of the project. To do this, go to the top menu and click Phase, then select Project,Overall Project. This opens the window Phase Distribution – Project Overall. From the two left mostcolumns we can see that the Plans and Requirements phase, which is 7% of the effort of the overallproject (PCNT), will take 2.589 Person Months (Effort PM). (36.987 x .07 = 2.589). The other threecolumns relate to schedule and staff, which we will get to.You might notice that the percents listed in the second column don’t add up to a hundred, evenwhen you consider that Detail and Design and Code and Unit Test are both sub-parts of Programming.This is because the Plans and Requirements phase isn’t included in the overall effort, just ProductDesign, Programming, and Integration and Test, as evident in the summation of percentage. (6.288 +22.470 + 8.230 = 100). We’re done with this for right now. Click OK.We’re back at the main page. Look again at the bottom table at the Estimated, Most Likely row.There is a column labeled Sched which has the value 11.6 estimated as most likely. Sched stands forSchedule; this says that 11.6 months is, most likely, the best time to plan for the project’s completion.Further, there is also the column Staff, which gives the value of 3.2 as the most likely estimate. This saysthat 3.2 people are the optimum number of people for a project, most likely. You can see now how theeffort was computed, as months X people = person months, or, rather, Staff multiplied by Schedule equalsEffort. (3.2 X 11.6 = 37.0; accounting for rounding error).That said, go back to Phase Distribution – Project Overall (which we got to through Phase,Project, Overall Project). Notice the third and fourth columns PCNT and Schedule, this time PCNTrelates to percentage of Schedule, not Effort. Note again that the Plans and Requirements phase is notcomputed into the overall Schedule, as evident in the summation of percentage. (25.083 + 51.667 + 23.250= 100) Finally, the right most column, Staff, describes staff, and how many people should be assigned toeach task. Again, click OK.Now that we have found out all we need to know for our project, we are almost ready to exitCOCOMO II. However, we will need the values of this project later, so we’ll need to save. Go to File onthe top menu, click on it, and then click Save Project. A Save As window will appear. Now, navigate toyour COCOMO directory (most likely in C:) then click on the Create New Folder icon. Change the nameof the new folder the First COCOMO and double click on it. Then, type in the First COCOMO as thefile name and click Save. We are now ready to go to the COCOMO spreadsheet.To be


View Full Document

USC CSCI 599 - MyFirstCOCOMO_Tutorial

Documents in this Course
Week8_1

Week8_1

22 pages

Week2_b

Week2_b

10 pages

LECT6BW

LECT6BW

20 pages

LECT6BW

LECT6BW

20 pages

5

5

44 pages

12

12

15 pages

16

16

20 pages

Nima

Nima

8 pages

Week1

Week1

38 pages

Week11_c

Week11_c

30 pages

afsin

afsin

5 pages

October5b

October5b

43 pages

Week11_2

Week11_2

20 pages

final

final

2 pages

c-4

c-4

12 pages

0420

0420

3 pages

Week9_b

Week9_b

20 pages

S7Kriegel

S7Kriegel

21 pages

Week4_2

Week4_2

16 pages

sandpres

sandpres

21 pages

Week6_1

Week6_1

20 pages

4

4

33 pages

Week10_c

Week10_c

13 pages

fft

fft

18 pages

LECT7BW

LECT7BW

19 pages

24

24

15 pages

14

14

35 pages

Week9_c

Week9_c

24 pages

Week11_67

Week11_67

22 pages

Week1

Week1

37 pages

LECT3BW

LECT3BW

28 pages

Week8_c2

Week8_c2

19 pages

Week5_1

Week5_1

19 pages

LECT5BW

LECT5BW

24 pages

Week10_b

Week10_b

16 pages

Week11_1

Week11_1

43 pages

Week7_2

Week7_2

15 pages

Week5_b

Week5_b

19 pages

Week11_a

Week11_a

29 pages

LECT14BW

LECT14BW

24 pages

T7kriegel

T7kriegel

21 pages

0413

0413

2 pages

3

3

23 pages

C2-TSE

C2-TSE

16 pages

10_19_99

10_19_99

12 pages

s1and2-v2

s1and2-v2

37 pages

Week10_3

Week10_3

23 pages

jalal

jalal

6 pages

1

1

25 pages

T3Querys

T3Querys

47 pages

CS17

CS17

15 pages

porkaew

porkaew

20 pages

LECT4BW

LECT4BW

21 pages

Week10_1

Week10_1

25 pages

wavelet

wavelet

17 pages

October5a

October5a

22 pages

p289-korn

p289-korn

12 pages

2

2

33 pages

rose

rose

36 pages

9_7_99

9_7_99

18 pages

Week10_2

Week10_2

28 pages

Week7_3

Week7_3

37 pages

Load more
Download MyFirstCOCOMO_Tutorial
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view MyFirstCOCOMO_Tutorial and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view MyFirstCOCOMO_Tutorial 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?