| USC COCOMO™ II.2000.0 |
10-15-99 |
[Per Jongmoon Baik 15 October 1999]
This executable adds RUP-based reports.
|
USC COCOMO™ II.1999.1f |
08-03-99 |
[Per Jongmoon Baik 03 August 1999] |
1. Correct the typos identified by Ray Madachy. 2. Add Non-Specified as default language for new module. 3. Sort the language list on Combobox in the Size dialog. (Still being worked: the bug identified by Don Reifer wherein the tool crashes when USR defined language is used after setting the multiplier.) USC COCOMO™ II.1999.1e |
08-02-99 |
[Per Jongmoon Baik 02 August 1999] |
1. Support for MBASE activity distribution. USC COCOMO™ II.1999.1d |
07-29-99 |
[Per Jongmoon Baik 29 July 1999] |
1. MBASE overall phase distribution for project and module. (Not support activity distribution for each phase) 2. Parameter Dialog's title bar change: - Non-default values used-> Non default model values used for some paramters - Default values used-> Default model values used 3. Person Month Dialog - Title bar -> - Non-default value used-> Non default model value used - Default value used-> Default model value used - When it used non-default model value, it shows default value. 4. Size FP dialog - Show current multiplier for selected language. 5. FP multiplier Change Dialog - Show Default multiplier value when non-default value is used. 6. Screen Color Scheme Change for color > 256 and resolution > 800x600 7. Warning Dialog for duplicate module names - Copy-->Paste - Add Module - Change Module name - Load Project ====> check if there are duplicate module name, if there is, show a warning dialog. 8. Maintenace Dialog Change - For Project Maintenance, It shows only scale factor. - For Module Maintenance, It show every field that used to be. - Ass String " Average Change Traffic % over year" in the dialog. 9. Early Design Parameter value change.
USC COCOMO™ II.1999.1c |
07-12-99 |
[Per Jongmoon Baik 12 July 1999] |
1. Each module has a field which denotes programming language. 2. Support Language change (FP, SLOC, and Adaptation & Reuse) 3. All buttons bring up the same help screen with indexed html files of user and model mauals. 4. Correct Typo (Paramters ==> Parameters) 5. All edit field in FP allows input 0 - 999 (It did not allow the number larger than 300) 6. Adaptation Intitial SLOC allows the input 1-9999999
COCOMO™_01b_99_06_29
| 06-29-99 |
Per Jongmoon Baik 29 Jun 1999 | 1. Updated FP Backfire table support. 2. Removed reset button from parameters pop up menu, add it to each parameter dialog boxes 3. Warning dialog when a old est is loaded, if there exists at least one parameter in the file whose value is different from the default. 4. Status bar change for development model change. - Number of EAF increased and RISK computed for Post-Architure model - Number of EAF decreased and no RISK computed for Early Design model 5. Titlebar change for default value or not 6. Scale factor for project maintenance 7. Prog. Language for SLOC as well as FP 8. Change BRAK to REVL 9. Reoder Personnel factors 10. Change names of EAFs, PEXP, AEXP to PLEX, APEX 11. Remove Life span from the maintenance dialog 12. Allow to change the hours/PM - default value 152 hours/PM 13. In the Size dialog, change adoptation to Adoptation and Reuse COCOMO™_01a_99_03_16 | 03-16-99
|
[from AWB's memory] | 1. FP Backfire table support. 2. EAF's per module for project maintenance? | ||||||||||||||||||||||||||||||
Submit problem reports on these beta versions of the software to:
USC COCOMO™ II Problem Report Submission Form
Very Important! -- When reporting bugs, please place in the "Additional Information"
field on the above electronic problem report submission form, the letter and the date
designations of the executable file in question.
 |
To the Center for Software Engineering Home Page |
|---|
Copyright 1995, 1996, 1997, 1998, 1999 The University of Southern California
The written material, text, graphics, and software available on this page and all related pages may be copied, used, and distributed freely as long as the University of Southern California as the source of the material, text, graphics or software is always clearly indicated and such acknowledgement always accompanies any reuse or redistribution of the material, text, graphics or software; also permission to use the material, text, graphics or software on these pages does not include the right to repackage the material, text, graphics or software in any form or manner and then claim exclusive proprietary ownership of it as part of a commercial offering of services or as part of a commercially offered product.