The Personal Self-Assessment Environment

Project 2 Packaging and Postmortem

Last modified: Sun Sep 26 07:29:18 HST 1999

Overview

For each project, you will need to perform both a postmortem and some packaging to complete your development activities. The postmortem activity provides an opportunity for you to reflect upon the experience of developing the software and consider ways to improve your next effort. The packaging activity involves collecting together your work products in a manner that facilitates their distribution and evaluation.

Postmortem

For this project, the postmortem activity is relatively simple.

First, you need to run LOCC on your Project 02 source files and import that size data into your 613-data.leap file. Important note: you need to use the "diff" feature of LOCC to create size data representing the changes you made to your Project 1 system to create your Project 2 system. Consult the LOCC user guide for details on diff.

Next, invoke Hee on your psae-2 project, and condense your raw data. The result of this should be aggregate time data in the "Time" tabbed window of Hee and aggregate size data in the "Size" tabbed window in Hee.

Once this time and size data is available to you, please create a html file containing a copy of the following questions, and provide below each question your answer:

How much time did you spend on this project?
How many different days did you work on this project?
What time of day did you usually work on this project?
How many packages, classes, methods, and lines of non-comment source code did you write on this project?
List the set of classes and methods that you came up with at the end of your design phase. This is your initial design.
Now list the set of classes and methods that your final implementation includes. This is your "final" design.
Compare your initial design to your final design. What is different? Why? How could you improve your next design?
What else do you intend to do differently on your next project to do better?

Packaging

Correct packaging of your technical work products is an extremely important part of software engineering. In this course, you must be very careful to package your software according to the following directions. Note that the packaging instructions have changed since Project 1.

All of your work products for this assignment must be submitted to me on a single floppy disk in Windows-readable format. During your personal interview, I will take your floppy and download its contents onto my hard disk. I will do some evaluation of your submission during the personal interview, and potentially more evaluation later.
All of the work products for this assignment must reside within a single directory or folder. This project folder must be named with the following format: uhunixID-Pprojectnumber. In other words, for this project (Project 2), my folder would be named "johnson-P2". Note that the 'johnson' is all lowercase, the 'P' is upper case, and the number is the project number. Typically, if you have not named your folder correctly, I will simply give your floppy back to you during the interview and ask you to fix this error and request that you check carefully for any other packaging errors before returning for an interview. Although it would not take me much time to fix this and other sloppiness in your submissions, it takes away time I could be spending with other students discussing important content issues, so I won't do it.
Your project folder should contain the following:
- A jar file called uhunixID-Pprojectnumber.jar. In other words, my jar file for project 2 would be called 'johnson-P2.jar'. In the case of my jar file, it must be structured to enable me to invoke the P2 system in the following way:
```
% java -jar johnson-P2.jar -qa test.qa
```
  For instructions on how to use the jar facility to create invocable jar files, see: http://java.sun.com/docs/books/tutorial/jar/basics/run.html.
  Note that I will be running your program on several test files. You should test your software extensively beforehand on both legal and illegal inputs.
- A leap file called uhunixID-Pprojectnumber.leap. In other words, my Leap file for project 2 would be called 'johnson-P2.leap' This leap file should contain a complete and accurate record of all of the data requested for this project. This file should be a copy of your 613-data.leap file in which is located the project definition, phaseset definition, and document type definition I supplied to you, plus your time data.
- A file called uhunixID-Pprojectnumber-postmortem.html. In other words, my postmortem file for project 2 would be called 'johnson-P2-postmortem.html'. This file should contain the postmortem discussion, as noted above.
- A directory called "src". This directory should contain a copy of all your .java files and the .class equivalents.
- A directory called "src-old". This directory should contain a copy of all your .java files as they were at the start of this project. In other words, running LOCC in diff mode on the contents of the src-old directory and the contents of the src directory will yield the total new size of work product created in this project.
- A directory called "tests". This directory should contain all of the files you used as test cases for this project. This directory should also contain a file called "index.html", which lists a very short description of what each test file attempts to test in your system.
- A directory called "javadoc". This directory should contain the javadoc files for your system.

Philip Johnson