Welcome to the FTP site for A Discipline for Software Engineering by Watts S. Humphrey ISBN: 0-201-54610-8, hardcover, 448 pages, 1995 published by Addison-Wesley Publishing Company, Inc. ftp://ftp.aw.com/cseng/humphrey/discipline/ This site contains the complete FORMS and SPREADSHEET materials from the SUPPORT diskette that you can otherwise order for a nominal sum (ISBN: 0-201-83485-5/IBM; ISBN: 0-201-83998-9/Mac) from Addison-Wesley. We have also tried to provide some extra file formats the better to ensure that one meets your needs. FORMS The forms files contain electronic copies of the forms and templates you will need to do the exercises in the textbook, A DISCIPLINE FOR SOFTWARE ENGINEERING. These files are available in several formats. 1. Download the single file from the list below that meets your needs (other than file format, each one is identical). 2. Print out and save a master set of these forms and use copies as needed for the exercises. 3. If you use the summary spreadsheet you will not need to print out the seven Project Plan Summary forms (see "SPREADSHEETS," below) as the spreadsheet helps you to complete electronic copies which can be printed. : forms.exe 51,072 bytes (binary) A self-extracting DOS/Win file which yields a Word for Windows 2.0 file. forms.pdf 385,754 bytes (ascii) An Acrobat pdf version, from which you can print or cut/paste from any platform reader 2.0 forms.ps 498,290 bytes (ascii) The postscript version of the file forms.sit.hqx 48,696 bytes (ascii) A stuffed, binhexed version for Macintosh users containing a Mac-aware, WinWord 2.0 file that should work fine with most current Mac word processors. SPREADSHEETS This site also contains files two versions of the spreadsheets for the book: sprdshts.exe 106,532 bytes (binary) A self-extracting DOS/Win file which yields Microsoft Excel for Windows spreadsheets sprdshts.sit.hqx 132,863 bytes (ascii) A stuffed, binhexed version for Macintosh users which yields Microsoft Excel spreadsheets SPREADSHEET DESCRIPTIONS: A total of six spreadsheet files are included in each version. These files are DefAnal, PlanAnal, ProcAnal, QualAnal, Stu1, and Summary. The graphs generated by these spreadsheets are suitable for use in presentations or reports. These files are described in the following paragraphs. Stu1 - The Stu1 file contains spaces for entering the planned and actual data for each program. These data are used by the other spreadsheet files to generate summary reports and a wide variety of graphical analyses of your process data. To submit your exercise data electronically, rename a copy of this file to your student number. For example, if you are student 7, rename it as Stu7 and submit a copy to your instructor. Summary - The Summary file contains a blank spreadsheet form for each of the ten programming exercises 1A through 10A that are normally used with this textbook. Using the data provided from the Stu1 file and data you enter for each exercise, the summary spreadsheets automatically generate most of the calculations required by the PSP Project Plan Summary forms. If you use the summary spreadsheet you will not need toprint out the seven Project Plan Summary forms as the spreadsheet helps you to complete electronic copies which can be printed. DefAnal - The defect analysis file uses data entered in the Stu1 file to generate a series of graphical displays of your defect data. These include: - total defects per KLOC, - defects per KLOC injected in design and in coding, - defects per KLOC removed by design reviews, code reviews, compile, and test, - the percentage distribution by phase of the defects injected in your process, - the percentage distribution by phase of the defects removed in your process, and - an x-y plot of the defects per KLOC found in test versus the A/FR ratio. PlanAnal - The plan analysis file uses data entered in the Stu1 file to generate graphical displays of your planning performance. These include: - the time you spent completing the programming exercises, - the accuracy of your time estimates for these exercises, - the sizes of the programs you wrote, - the accuracy of your size estimates for these programs, and - the percentage of development time spent in planning, postmortem, compile, and test. ProcAnal - The process analysis file uses data entered in the Stu1 file to generate graphical displays of your process data. These include: - the productivity in LOC per hour for each of the programming exercises, - separate x-y plots of yield versus productivity, A/FR, and test defects/KLOC, - separate x-y plots of A/FR versus productivity, yield, and test defects per KLOC. QualAnal - The quality analysis file uses data entered in the Stu1 file to generate graphical displays of your process quality. These include: - the defect removal yield of your process for each programming exercise, - the appraisal, failure, and total cost of quality for each programming exercise, - the A/FR ratio for each programming exercise, and - the LOC reviewed per hour versus yield. SPREADSHEET DIRECTIONS TO START: 1. Read the entire instructions. 2. Download the STUDENT directory to your C or D drive (PC users) or to your hard disk (Mac users). 3. Make a backup copy on a diskette and keep in a safe place. 4. Keep the new directory on the hard disk as a master and make a copy in another new file directory you label with an appropriate name, here called STUN. 5. If you are taking a course with this text, you will have a student number, Stu7, for example. In the STUN spreadsheet, however, your data are entered in the file labeled Stu1. You must not change this name as the spreadsheets could not then read your data. 6. The Stu1 file is in the proper format to be read by your instructor's spreadsheet program. To pass your instructor an electronic copy of these data, you must rename a copy of Stu1 to the student number used for you in the course. If you are Stu7, for example, you will have to rename a copy of this Stu1 file as Stu7 before giving it to your instructor. 7.To use Excel to print out copies of the Project Plan Summary forms: - for program 1A, print page 2, - for program 2A, print page 6, - for program 3A, print page 10, - for program 4A, print page 14, - for program 5A, print page 18, - for program 6A, print page 22, - for program 7A, print pages 26 and 27, - for program 8A, print pages 30 and 31, - for program 9A, print pages 34 and 35, and - for program 10A, print pages 38 and 39. TO ENTER DATA FOR PROGRAMMING EXCERCISES YOU ARE PLANNING: 1. Make your new and changed size and total time estimate for the program you are developing. - Note that for program 1A you only make a total time estimate. 2. In the summary spreadsheet, go to the form for the exercise you are planning. 3. Enter planning data only in the cells with a ?????. - Any cells with any other entry (including 0 and #VALUE!) should not be changed.Their contents will be calculated automatically. 4. Enter the total planned development time in the summary form. - For program 1A, also enter this time in the Stu1 spreadsheet. - For program 2A, calculate the development time you expect to spend per phase and enter these values in the Stu1 spreadsheet. - For program 3A and later, the planned time per phase is automatically calculated for you based on the time distribution with the previous programs. You may use these values or change them. - Enter these planned times for each phase into the Stu1 file. 5. For program 2A and later, enter the planned total new and changed LOC in the appropriate summary spreadsheet space (with a ?????). - For program 3A and later, enter the planned Base, Deleted, Modified, Reused, and New Reused LOC. - For program 3A, calculate the added and total LOC. - For later programs these values are calculated for you. 6. For all programs, calculate the planned values for entries marked ?????. - You must make each calculation the first time it is made with a process version. - Thereafter, except for UPI and LPI, the calcu- lations are made automatically from data in the Stu1 and summary spreadsheets. - For example, for program 2A using PSP0.1, you must calculate the development time planned for each phase. - For programs 3A and later, these data are automatically calculated based on your estimate of total development time and the previous development time distribution in the ToDate% of the previous program. - ToDate and ToDate% for time, defects injected, defects removed, and program size are recalcu- lated starting with program 7A. - This is to account for the process changes caused by the introduction of design and code reviews with exercise 7A. 7. If you wish to change any calculated values, you may do so. - For example, if you do not agree with the planned values for development time by phase, enter the numbers your prefer. - Note that this will also change many other values on the summary spreadsheet. Examples are yield, A/FR, DRL, and so forth. - Before making such changes on the spreadsheet, save a backup copy so you can recover if you change your mind. TO ENTER DATA FOR A COMPLETED PROGRAMMING EXCERCISE: 1. Open the Stu1 spreadsheet. - In Stu1, enter the actual time and defect data for the completed program. - For PSP3, add the high-level design and high- level design review time and defect data respectively to the design and design review data and enter the totals in Stu1 as the design and design review values. 2. Open the summary spreadsheet and go to the proper form. - For program 1A, no action is required. - For program 2A and later, enter the actual Base, Deleted, Modified, Reused, Total, and New Reused LOC values. 3. For program 2A. - calculate the added LOC and enter in the summary, - calculate the actual new and changed LOC and enter in the summary and Stu1, and - measure the actual new and changed LOC for program 1A and enter in Stu1. 4. For program 3A and later: - the value of the added and new and changed LOC are automatically calculated, - you must enter these new and changed values in Stu1. 5. For all programs, calculate the actual values for all entries marked with ?????. - For exercise 7A, the ToDate and ToDate% values are automatically recalculated for development time, defects injected, defects removed, and program size. - This is to account for the process changes caused by the introduction of design and code reviews with exercise 7A. 6. For program 10A, consider the following in your data entry and analysis. - The planned and actual high-level design and high-level design review time and defect data are entered in the spreadsheet as 0. - If you expect to spend time or inject or remove defects in these phases, you must enter these planned values in the spreadsheet. - You should also adjust the planned values for the other phases accordingly. - Similarly, if you actually spent time or injected or removed defects in these phases, you must enter these data as well. TO USE AN ANALYSIS SPREADSHEET: 1. Open the desired spreadsheet - PlanAnal, for example. 2. Examine the graphs and data on the spreadsheet as you wish. No additional actions are required on your part. 3. The top item on each analysis spreadsheet is a listing of the spreadsheet contents. 4. To use these graphs, print them directly or copy them to a Word or PowerPoint file for inclusion in a paper or presentation. The graphs are immediately below this listing. A copy of the Stu1 data is immediately below the graphs. Last are the calculations used to generate the graphs. HELP WITH FILE TYPES Files with the extension ".exe" are archived using PKZIP 2.04G, and then made self-extracting. You need no extra software to unarchive these files on your DOS or Windows machine. To make them available, first be sure that you are in =binary= mode before transferring the files (type "binary" at the "ftp>" prompt). Once transferred, use the syntax: filename -d (the "-d" will preserve directory structure where directories have been created), where "filename" is the name of the file, minus the ".exe" extension. Files with the extension ".sit.hqx" are archived using the Macintosh-native Stuffit program, and then bin-hexed, making them ASCII files (transferring them as binary won't hurt them, but is redundant). The easiest way to "unbinhex" and "unstuff" them in one go is to use the free program, StuffIt Expander. Versions are available on this site in our /pub/tools/mac directory (StuffIt_Expander...), or directly from Aladdin Software at ftp.aladdinsys.com in their "pub" directory. ABOUT ADOBE ACROBAT (PDF) files: Adobe Acrobat files can be viewed, printed, or copied from, using the free Adobe Acrobat Reader. For access to all Adobe Acrobat readers (Windows, Mac, DOS, Unix), and/or for information about how to use them with popular web browsers, log onto Adobe's web server at: http://www.adobe.com/Acrobat/AcrobatWWW.html You can also get copies of the Mac and Windows Acrobat Readers here, in the directories: ftp://ftp.aw.com/pub/tools/mac/acroread.sit.hqx or ftp://ftp.aw.com/pub/tools/win/acroread.exe ----------------------------------------------------------- If you are interested in our book announcement mailing lists, would like to offer feedback to the author, or have other questions or comments about our books, contact us at: aw.cse@aw.com You may also wish to visit our web site, http://www.aw.com/cseng/ If you are having trouble using these files, contact our technical support person: ceonline@aw.com